Manual today
The call waits for a person to be free
- Response waits until morning
- Details are entered again by hand
- No clear owner is assigned
Interactive demo · Customer response
A call is missed at 10:42 PM.
Play the seven scenes that turn it into a booked job — with a named person approving the exception.
A mapping call is thirty minutes: we map how a missed call moves through your business today, and you keep the map either way.
- Missed-call recovery
- Language detected
- Structured intake
- Exception to a named person
Guided run · seven scenes
One missed call.
Seven scenes.
One record.
Press play, or jump straight to any scene. Each one shows what arrived, what the system did, what the record says, and who owns it.
Every record in this run is synthetic. The workflow is the real one — the caller, the timestamps and the CRM entry were invented so you can click through it.
- Caller
- Elena Martinez
- Channel
- Missed call → SMS
- Request
- Active water leak
- When
- 10:42 PM · after hours
Scene 1 / 7
Scenes 05 and 06 are amber because the system stops there and a named person decides. Every other scene runs on an approved rule.
What arrived
A call at 10:42 PM. Nobody free.
What the system did
Raised an event instead of a voicemail.
What the record says
Source · missed call, after hours
Who owns it
System
What arrived
The recovery workflow started.
What the system did
Sent the pre-approved text-back.
What the record says
Response · approved text-back sent
Who owns it
AI receptionist
What arrived
A reply in Spanish.
What the system did
Switched to the approved Spanish script.
What the record says
Language · Spanish
Who owns it
AI receptionist
What arrived
The address, and the home is occupied.
What the system did
Asked only the approved intake questions.
What the record says
Caller, request and urgency · captured once
Who owns it
AI receptionist
What arrived
An urgent job in an occupied home.
What the system did
Matched the emergency rule and stopped.
What the record says
Rule · auto-booking paused
Who owns it
ODOn-call dispatcher
What arrived
Approval from the dispatcher.
What the system did
Sent the confirmed emergency slot.
What the record says
Booked · tomorrow, 8:30 AM
Who owns it
ODOn-call dispatcher
What arrived
The thread finished.
What the system did
Wrote one record and attached the transcript.
What the record says
Synced · CRM record, nothing retyped
Who owns it
ODOn-call dispatcher
Conversation
Elena Martinez
Missed call → SMS · number withheld
- 22:42 Missed call · 10:42 PM · recovery started
-
AI receptionist · 22:42
Sorry we missed your call — how can we help?
-
Elena Martinez · 22:43
Es urgente — hay una fuga de agua activa. ¿Pueden venir?
EN It’s urgent — active water leak. Can someone come out?
- 22:43 Preferred language: Spanish · thread switched
-
AI receptionist · 22:44
Entendido. ¿Cuál es la dirección, y es seguro estar ahí ahora?
EN Got it. What’s the address, and is it safe right now?
- 22:45 Emergency rule matched · auto-booking paused · approval requested
-
ODOn-call dispatcher · 22:46
Approved — send the emergency slot.
-
AI receptionist · 22:46
La ayuda está programada para mañana a las 8:30 AM. Le enviamos la confirmación.
EN Help is scheduled for tomorrow · 8:30 AM. Confirmation on its way.
- 22:47 CRM updated · transcript attached · owner: On-call dispatcher
The thread writes itself scene by scene. Press Play, or step through with Next.
Operational record
REC-7742
Demo
SourceMissed call · 10:42 PM · after hours
ResponseApproved text-back sent
LanguageSpanish — detected, thread switched
CallerElena Martinez
RequestActive water leak · address confirmed
UrgencyUrgent — occupied home
RuleEmergency match · auto-booking paused
OwnerODOn-call dispatcher
BookedEmergency visit · tomorrow · 8:30 AM
SyncedCRM record · transcript attached
One record, written as each scene happens. Nothing here is retyped later.
Exception
Nothing is waiting on a person yet.
This run stops and asks a named person when:
- an emergency is reported in an occupied home
- the address falls outside the service area
- anything asked is not covered by an approved script
Human attention
Emergency rule matched · auto-booking paused · approval requested
Routed to ODOn-call dispatcher
- Approve
- Decline
- Reassign
22:46 · Approved “Approved — send the emergency slot.” — On-call dispatcher
Activity ledger · through the current scene
| Time | Event | Owner |
|---|---|---|
| 22:42 | Missed call detected | System |
| 22:42 | Approved text-back sent | AI receptionist |
| 22:43 | Language detected; thread switched | AI receptionist |
| 22:44 | Caller details captured | AI receptionist |
| 22:45 | Emergency flagged; approval requested | On-call dispatcher |
| 22:46 | Human approved; slot confirmed | On-call dispatcher |
| 22:47 | CRM record synchronized | On-call dispatcher |
Never automated
- Booking an emergency without approval
- Hiding that a system replied
- Contact without consent
Each mark is a decision the system never takes on its own — it stops and asks a named person.
Before and after
The same missed call,
two ways.
Nothing above depends on a smarter model. It depends on the response existing at 10:42 PM, the details being captured once, and the exception having a name on it.
Connected system
The call becomes a record with an owner
- Approved response begins immediately
- Details are captured once, in structure
- Human exceptions receive a named owner
- Spanish callers are answered, not lost
Other shapes of the same run
Same seven scenes.
Different rule, different person.
Scenario 01 · shown above
Home services — after-hours water leak
- Caller
- Elena Martinez
- Stops for
- On-call dispatcher
- Confirmed
- tomorrow · 8:30 AM
Scenario 02
Dental practice — severe tooth pain
- Caller
- Marcus Lee
- Stops for
- On-call clinician
- Confirmed
- tomorrow · 9:00 AM
Scenario 03
Property management — no A/C in an occupied unit
- Caller
- Dan Kowalski
- Stops for
- On-call maintenance lead
- Confirmed
- tomorrow · 8:00 AM
The scenes do not change — only the rule that stops the run, and the person it routes to.
What this would take to build for you
The demo is simple.
Your rules are specific.
A real build starts from your scripts, hours, service areas, escalation contacts, and calendar rules — mapped together on one call.
Input 01
Your scripts
The exact wording of the text-back and every intake question — in each language you answer in — approved before anything goes out.
Input 02
Your hours
What “after hours” means per line, per location and per holiday, and who is covering each of those windows.
Input 03
Your service areas
Where a request can actually be booked, and exactly what the assistant says when one falls outside them.
Input 04
Your escalation contacts
The named people an exception routes to, their backup, and how long they have before it escalates again.
Input 05
Your calendar rules
Real capacity, travel and buffer time, and which slots the system is ever allowed to offer on its own.
Explore another workflow
Five more systems you can run.
Start with the map
Map your response workflow.
Bring your scripts, your hours and the calls you are losing. In thirty minutes we map how a missed call moves through your business today, name the smallest useful intervention, and tell you honestly whether it is worth building. You keep the map either way.
30 minutes. One workflow mapped. You keep the map either way.