Voice
Active calls appear in the live operational snapshot.
Operations
See what NLDONA is handling — and what still needs you.
NLDONA brings conversations, bookings, handoffs and operational outcomes into one place so your team can understand what happened and what needs attention.
Live now
- Voice call
- Website Chat
- WhatsApp conversation
Recent outcome
- Appointment rescheduled
- Confirmation sent
Needs Attention
- Customer waiting
- Calendar disconnected
Human handoff
1 waiting
Illustrative operational scene — not live metrics, SLA claims, or Ops KPI facts.
Live now
See what is happening right now.
Active conversations across supported channels stay visible as operational state — not raw provider sessions.
Website Chat
Open website conversations stay visible while they are active.
Supported WhatsApp conversations can appear when that channel is connected.
Public Booking
Public booking interactions are part of the same operational picture.
Live Operations refreshes as a bounded tenant snapshot. It is operational visibility — not a developer realtime stream.
Outcomes
See what happened — not just what was said.
Conversation is not the same as business outcome. NLDONA helps you follow the path from request to recorded result.
Customer request → NLDONA action → business outcome
01
Request
A customer asks to change an appointment.
02
Action
NLDONA checks availability and applies supported schedule rules.
03
Outcome
The booking change is recorded in business authority where completed.
Appointment created
A supported booking is written once.
Appointment rescheduled
A change is reflected in the schedule.
Reservation cancelled
A supported cancellation is recorded.
Confirmation sent
A confirmation can be sent when the channel is configured.
Human handoff completed
A person continues with useful context.
Knowledge gap found
Missing approved knowledge can be flagged for review.
An interaction marked completed means the conversation ended — it does not by itself prove every business outcome succeeded. Durable bookings and work remain server-owned.
Needs Attention
Bring the things that need a person into one place.
NLDONA surfaces operational states that require human review.
Needs Attention is derived from real operational evidence — not an AI opinion about urgency.
Customer waiting
A reply or continuation still needs your team.
Open handoff
A conversation is waiting for a person to continue.
Integration issue
A connected app may need setup or reconnect.
Knowledge gap
Repeated missing answers can be reviewed in knowledge workflows.
Usage or readiness
Launch and usage signals can appear when they need review.
When something does not complete, you can see that too.
Failed or degraded states stay visible so the business does not assume silent success.
- Interaction failed
- Handoff failed
- Provider or channel degraded
- Delivery uncertainty where surfaced
Human handoff
When AI should stop, the person starts with context.
Handoff is a governed continuation — not a failure, and not a raw dump of internals.
AI conversation
NLDONA handles the customer request on a supported channel.
Handoff requested
When a person is needed, the handoff becomes visible in Operations.
Human continues
Your team picks up with the operational context that is safe to show.
What a person can receive
- Channel and current state
- Open issue / handoff reason (sanitized)
- Recent operational activity
- Handoff status (requested, connecting, connected, or failed)
Handoff views do not expose chain-of-thought, hidden model reasoning, secrets, raw tool arguments, or full conversation dumps.
Interaction view
Understand the interaction without reading the internals.
Inspect who contacted you, on which channel, what state it is in, and what happened next — without raw logs.
- Channel
- Website Chat
- Agent
- Published AI agent
- State
- Needs attention
- Handoff
- Waiting for person
- Recent activity
- Availability checked
- Errors
- None shown
Follow the operational story from request to outcome.
- Interaction started on a supported channel
- NLDONA took a supported action
- Handoff requested when a person was needed
- Interaction completed or failed
- Needs Attention remains visible when review is still required
Focus the workspace
ActiveNeeds AttentionHuman handoffsRecently completed
The interaction view is a read projection of operational state. Timeline steps above are illustrative of that journey — not a claim that every booking confirmation appears as a Live Ops activity type. It is not a second source of booking or customer truth, and it does not invent customer identity from a conversation alone.
Health & control
Visibility without changing the source of truth.
Operations is read projection and operational visibility. It does not redefine bookings, customers, billing, or integration authority.
Channel and app readiness (illustrative)
Website Chat
Operational
Voice
Operational
Needs setup
Public Booking
Operational
Google Calendar
Action required
Microsoft Calendar
Operational
Gmail
Needs setup
Google Drive
Needs setup
These status labels match tenant connection and readiness vocabulary used in Home / Connected Apps. They are shown here for clarity — not as a Live Operations KPI mosaic or platform infrastructure monitor.
Examples of operational activity across the platform.
- Answered a customer question
- Checked availability
- Rescheduled a booking
- Escalated to a person
- Identified a knowledge gap
These are platform capabilities and outcomes elsewhere — not a separate “AI Activity” module or productivity leaderboard inside Live Operations.
Derived from real state
Operational views project canonical business and interaction state.
AI does not redefine truth
Recommendations and conversation text do not become booking or customer authority.
Humans review exceptions
Needs Attention and handoffs keep judgment with your team.
Authorised visibility
Team members see what their permissions allow — not unrestricted tenant dumps.
FAQ
Common questions about NLDONA Operations.
Short answers based on current product truth.
What is NLDONA Operations?
It is the business-facing operational workspace that shows active and recent customer interactions, handoffs, Needs Attention items, and related operational state across supported channels.
Can I see active customer interactions?
Yes. Active Voice, Website Chat, WhatsApp and Public Booking interactions can appear in the live operational snapshot when those channels are in use.
Can I see what NLDONA completed?
Yes. Recently completed interactions are visible in a recent window. Completing an interaction does not by itself prove a booking succeeded — supported business outcomes remain recorded in NLDONA’s scheduling and business authority.
What is Needs Attention?
Needs Attention surfaces operational states that require human review — such as waiting replies, open handoffs, or integration issues — derived from evidence, not an AI urgency opinion.
Can I see human handoffs?
Yes. Handoffs appear in Operations so your team can continue with useful context.
Can I inspect a customer interaction?
Yes. You can open an interaction view with channel, agent, state, handoff, activity and timeline — without reading raw system logs or chain-of-thought.
Can I see failed actions?
Yes. Failed and degraded states can be visible so the business does not assume silent success.
Can I see integration issues?
Yes. Tenant-facing connection and readiness issues can appear in Needs Attention and connected-app status when those sources are available.
Does Operations change my business data?
No. Operations is primarily read projection and navigation. Bookings, customers and integrations remain owned by their canonical systems of record.
Is NLDONA Operations an analytics or monitoring tool?
No. It is operational visibility for customer and business activity — not APM, SIEM, BI, or a log explorer.
Can my team see only what they are authorised to see?
Yes. Operational surfaces are permission-gated. Insufficient permission fails closed rather than inventing empty success.
Try NLDONA
See what NLDONA could handle — and what your team would still see.
Paste your public website to start a temporary demo under your review.
Public information only. Demo experiences stay isolated from Production.