Front Desk with Nia
Be there for the next customer.
Useful answers, enquiry capture and a next step that stays attached to the conversation.
Products · Work around your business.
Start with the work that needs help.
A customer waiting for an answer. A lead that needs a next step. A community worth showing up for. A website that needs an update. Start with the job, meet the teammate, and see how the work stays connected.
Lead follow-up with Remy
Keep the follow-through moving.
Replies, evidence and the next action stay together, without treating every lead as urgent.
Community management with Zyla
Keep the conversation going.
Listening, community relationships and considered participation, with review and permission boundaries.
Ariy Sites
Keep your website current.
Supported content changes, reviewed previews and a controlled publishing process.
One connected system
Separate jobs. One customer story.
Follow one illustrative case from the first question through follow-up, research, supervision and the decisions you keep.
Front DeskStep 01 / 06
A customer request arrives.
What’s happening
Nia receives the question, answers it, and captures the first useful context before anything moves downstream.
What changed
A loose message becomes owned customer work.
Customer requestJamieConsultationTuesday afternoon
Incoming request
NiaFront Desk
NiaFront DeskHi — do you have availability next Tuesday?
Yes — I can help with that. Is afternoon best?
Returning customerConsultationPrefers afternoon
Front Desk
ChatStep 02 / 06
The conversation becomes a case.
What’s happening
The customer, request, preference, and open loop are structured together as Case #184 instead of remaining loose chat history.
What changed
The conversation now has working context that can travel.
Customer requestJamieConsultationTuesday afternoon
Conversation
“Hi — do you have availability next Tuesday?”
Nia confirmed the preference and captured the open loop.
Structured case
Case #184
NiaCustomerJamie · returning
NeedConsultation
Open loopConfirm Tuesday afternoon
Next stepCheck availability + context
Chat
PipelineStep 03 / 06
Remy picks up the work without losing the story.
What’s happening
Ownership moves from Nia to Remy. The original request remains attached while Remy focuses on the next commercial action.
What changed
Ownership changes. The customer story does not.
Case #184JamieConsultationTuesday afternoon
NiaRemyownership changed
PipelineJamie / Consultation
RemyLead CoordinatorStatus
Waiting on availability
Next action
Confirm Tuesday afternoon
Original request + case context remain attached
One fact is missing before Remy can safely confirm the next step: current service area and contact record.
Pipeline
ResearchStep 04 / 06
Missing context is gathered where it is needed.
What’s happening
Remy asks Hermes one focused question. Hermes returns enough evidence to resolve the uncertainty and move the case forward.
What changed
A missing fact becomes evidence attached to the same case.
Case #184JamieConsultationTuesday afternoon
Question from Remy
HermesResearch
Is Jamie’s company still within our service area, and is the contact record current?
RemyEvidence attachedFinding-level provenance
First-party website
Service address · observed today
Business profile
Location corroborated · 4d ago
Contact source
Email + phone match record
Local uncertainty · suite number differs across two sources; service-area conclusion is unchanged.
Back to Remy
Proposed slot · Tuesday 3:30 PM
RemyResearch
SupervisionStep 05 / 06
Only the exception reaches you.
What’s happening
Aletheia checks the proposed action against evidence, freshness, and authority. Routine work stays with Remy; this one boundary needs judgement.
Why this reached you
3:30 PM sits outside the configured auto-book window.
Case #184JamieConsultationTuesday afternoon
Remy still owns the work
Confirm Tuesday at 3:30 PM
RemyEvidence returned
Service area verified · contact current
Hermes provenance remains attached to Case #184.
AletheiaSupervisionSupervision
Policy ✓Evidence freshness ✓Authority
Human approval required
3:30 PM sits outside the configured auto-book window.
HoldApprove
Supervision
Command CentreStep 06 / 06
See the outcome — and open the path behind it.
What’s happening
The approved Jamie case arrives already resolved. Command Centre adds the wider operating context, then Show Work can expose the bounded lineage behind that outcome.
What changed
The outcome joins the operating view without losing how it happened.
Case #184JamieConsultationTuesday afternoon
Selected outcome
Jamie / Consultation
Tuesday 3:30 PM · approved
Case #184
Show work
What moved around it
NiaCustomer conversation resolvedFront Desk
HermesEvidence attachedResearch
AletheiaApproval resolvedSupervision
Elsewhere
Zyla has 1 community suggestion awaiting review.
Show Work · Case #184
Bounded lineageHow this outcome happened
CustomerRequest
Nia + RemyOwnership
HermesEvidence
Aletheia + approvalJudgement
OutcomeTuesday 3:30 PM
Show Work exposes this bounded path. The Work Graph remains the underlying operational representation; it is not a seventh public module.
Command Centre
Real Ariy product patterns shown through one illustrative case.
Six parts. One operating rhythm.
Each part takes care of a different moment.
Front Desk starts the conversation. Chat keeps it together. Pipeline protects the follow-through. Research adds context. Supervision watches the system. Command Centre gives you the final operating view.
01
Answer
Front Desk
Nia meets the customer, handles the first question, and captures what matters.
02
Continue
Chat
Conversation ownership can move from Nia to Remy without losing the customer story.
03
Follow through
Pipeline
Remy keeps today’s follow-up visible and future work out of the way until it matters.
04
Understand
Research
Hermes adds useful context before the next move deserves anyone’s time.
05
Evaluate
Supervision
Aletheia watches alignment, patterns, evidence, policy, and exceptions across the system.
06
Oversee
Command Centre
The owner sees what moved, what Supervision surfaced, and where judgement is still needed.
01 · Front Desk
Nia is there when the customer arrives.
She can answer the first question, understand what the customer needs, and leave the conversation with a real next step—even when you are somewhere else.
Explore Front DeskFront Desk
Nia · customer-facingWebsite conversation
New visitor
Nia
Active now
Can someone help me figure out which setup would work for our clinic?
Nia
Absolutely. Are you mainly trying to handle customer questions, bookings, or follow-up?Mostly questions and booking requests. We lose track of people after hours.
Nia captured
Handled byNiaIntent
Front Desk + booking
Need
After-hours coverage
Status
Qualified
Next step
Continue as a qualified opportunity
Next ownerRemyFromNiaNia passes the customer need and conversation context forward.
ToRemyChat
Shared inbox · clear ownershipCustomer conversations
Inbox
The message and who owns the next step stay together.
Nia
3 active
Remy
4 follow-ups
Needs responseInterestedDeal · Qualification
Fieldhouse Co.
From Sam Chen · 12 minutes ago
Re: after-hours booking
“Yes, this sounds close to what we need. Could someone show me how the booking handoff would work?”
Handoff from Nia · booking need already captured
Current ownerRemyRead & respondNeeds responseQuestion
Harbour Dental
From Maya Patel · 12 minutes ago
Consultation booking
“Can we connect this to the website we already have, or would that need to be rebuilt?”
Nia is still handling the active conversation
Current ownerNiaRead & respondFromNiaWhen a conversation becomes follow-up, ownership changes without creating a new customer story.
ToRemy02 · Chat
When the work changes hands, the customer story does not.
Nia may start the conversation. Remy may own what happens next. The reply, what has already happened, and the next step stay together.
Explore Chat03 · Pipeline
Remy keeps the follow-through visible.
Replies, waiting periods, due dates, and future follow-up stay organized around what actually needs to happen next instead of becoming another list to remember.
Explore PipelinePipeline
Remy · follow-throughToday
What actually needs action.
Remy owns the follow-through; future work stays quiet until it matters.
Remy
Working today
Needs action
4
Follow-ups
3
Waiting on reply
2
Researching
8
Carry-over
1OwnerRemyFollow-up
Fieldhouse Co.
Customer went quiet after a promising reply.
Remy carried this forward
Customer context attached
Due today
3OwnerRemyReply
Harbour Dental
New booking question needs a response.
Remy needs to reply today
Customer context attached
Upcoming
2OwnerRemyScheduled
Juniper Studio
Consultation follow-up planned for Thursday.
Remy scheduled the next step
Thursday · 10:00 AM
Hermes
System layer · supports the teammateResearch system
Opportunity dossier
Hermes gathers the evidence; it does not become another teammate the customer needs to understand.
Company1 record
Contact2 records
Website audit1 record
Competitor1 record
5 evidence records · 9 sources
Opportunity evidence
Website + business context
74/100Prepared forRemy
Prepared forRemyTechnical opportunity
82
Commercial signal
68
Pages evaluated
7
Decision makers
2
Audit findings
Weak structured dataBooking frictionContact page foundPortfolio reviewed
Recommended next move
High-confidence opportunity. Remy now has verified context to decide the next follow-up.
Hermes prepared the dossier for Remy
Research complete · sources attached
04 · Research
Research stays behind the scenes until it is useful.
Hermes can gather business context, website findings, likely contacts, and the evidence behind them before Remy—or you—spends time deciding what deserves the next move.
Explore Research
05 · Supervision
Supervision watches the pattern before it becomes your problem.
Aletheia looks across ownership, evidence, policy, patterns, and outcomes for the moments that should not quietly continue on autopilot. She does not replace your judgement; she makes better use of it.
Explore SupervisionAletheia
Supervisor · system-wideSupervision
What deserves a second look?
Aletheia looks across work, evidence, policy, ownership, and outcomes for patterns that should not stay invisible.
Policy checks
28
No blocked actionsPattern reviews
7
Across active workExceptions
1
Needs your judgementContext drift
Low
Within expected rangeCommand Centre
Owner view · attention by exceptionYour operating view
What needs you.
See what the teammates handled, what the system learned, and where judgement is still required.
Nia
8 handled
Remy
4 moving
Needs you
1
Nia handled
8
Remy moving
4
Strong opportunities
6
Work in motion
Every item has a visible actor.
Harbour Dental
Booking conversation · customer replied
HandlingNiaFieldhouse Co.
Consultation follow-up · due today
OwnerRemyJuniper Studio
Pricing exception · judgement required
Activity trail
Who did what
Nia answered a booking question
Harbour Dental · 12m ago
Nia handed follow-up to Remy
Customer context carried forward · 10m ago
Remy scheduled Thursday follow-up
Fieldhouse Co. · 8m ago
Hermes completed opportunity research
Juniper Studio · 4m ago
06 · Command Centre
Know what moved without watching every step.
See what Nia handled, what Remy is moving, what Research found, what Supervision surfaced, and the small number of moments that still need your judgement.
Explore Command CentreOne consistent operating view.
See who is working, what changed, what evidence was added, and what still needs you.
The same signals follow the work from the first customer question through follow-up, research, supervision, and the judgement calls you choose to keep.
Who is working
Who owns next
What Supervision surfaced
What needs you
The platform stays behind the working relationship.