live demo · Chainlinks Receptionist OS
Catch the calls that go to voicemail. Recover the revenue.
Explore how a receptionist workflow can classify missed calls, flag urgent requests, prepare routine bookings and queue quotes. This demonstration uses synthetic examples. Real calls, notifications and bookings require connected services and operator approval; response times must be measured in a pilot.
public vertical demo
The page is HVAC-flavored, but the same intercept pattern fits plumbing, electrical, dental, vet, salon, auto, locksmith, garage door, pest control — any service business where a missed call is a missed job.
Illustrative workflow: the queues, timings and results below are synthetic examples, not client outcomes or service guarantees. Chat can explain the workflow; it does not prove that a call, message or booking was completed.
call types · what the agent classifies
Five call types. Five routings. One ledger.
true emergency
Detection: Safety language: water leak, no heat, no power, gas smell, active fire, sewage backup, injured, locked out at night.
Routing: Example escalation target: page the on-call operator within 90 seconds. Text + call + secondary backup. Agent never quotes price, never promises arrival window, never diagnoses.
proof: 38 emergencies escalated in the last 7 days · 94 sec avg handoff
quote / estimate request
Detection: New customer asking for a price, project, replacement, or install. Existing customer asking for an addition or change-order.
Routing: Full intake captured (name, address, scope, urgency, photos via SMS if sent). Dropped into the estimate follow-up queue with owner-approved acknowledgement SMS.
proof: 67 quote requests captured + handed off
routine booking
Detection: Existing service-plan customer, tune-up, filter change, inspection, follow-up visit, maintenance window.
Routing: Books directly onto the calendar using operator-defined availability windows. Confirmation SMS sent. Buffer respected.
proof: 21 routine jobs booked without operator interruption
robocall / vendor filter
Detection: Matched against the operator-maintained block list (known spam numbers, vendors, repeat solicitors).
Routing: Call ended without ringing the operator. Logged for the weekly review.
proof: 17 calls filtered, ~0 minutes wasted
voicemail rescue
Detection: Existing voicemail pulled every 15 min, transcribed, classified into one of the above types.
Routing: Drops into the matching queue (emergency / quote / routine / filter). Operator never has to listen.
proof: 100% of voicemails processed within 15 min
work queues · what the operator sees
Emergency goes to a human. Routine goes to the calendar. Spam dies.
| queue | intake | handoff | SLA |
|---|---|---|---|
| Same-day emergency dispatch trigger: Safety-language detection in call or voicemail | Address, callback number, severity (1-3 sentence description), access notes | On-call operator paged via text + call. Secondary backup if no ack in 5 min. | Example target: under 90 seconds; validate delivery in a pilot 38 emergencies routed correctly · 0 missed safety calls |
| Estimate follow-up queue trigger: Quote/project intent detected | Name, address, job description, urgency, photos (SMS-attached), preferred contact channel | Drops into the estimate-follow-up agent's queue with owner-approved acknowledgement | Owner-approved acknowledgement SMS within 2 minutes 67 quotes captured + 31 dollar-band-tagged |
| Routine booking trigger: Existing customer or service plan with calendar availability | Job type, time window, address, special access (gate code, dog, etc.) | Calendar slot booked + confirmation SMS + automatic 24h reminder | Example booking target: 60 seconds; availability must be checked 21 bookings without operator touch · 12% no-show reduction from reminder |
| Voicemail-backlog rescue trigger: Voicemail-system poll every 15 min | Audio → transcribed → classified into one of the above types | Routed into matching queue without operator listening | All voicemails processed within 15 min 94 voicemails rescued · ~7 hrs operator time saved / month |
workflow · catch → classify → escalate → book → prove
01 · catch the call
Every missed call becomes an intercepted call
After-hours, lunchtime, on-the-job, second-line overflow, hold-time abandon — they all route to the agent instead of voicemail. Demo uses safe mock call events; production wires into your real phone number.
02 · classify in plain language
Emergency vs quote vs routine vs spam
The agent listens for safety language (no heat, water leak, no power), pricing intent, existing-customer signals, and the operator block list. Each call is classified in seconds.
03 · escalate true emergencies
Route urgent requests to an operator
Safety calls page the on-call operator via text + call, with secondary backup. The agent never quotes price, never promises arrival, never diagnoses. Just collects address and callback and gets a human on it.
04 · book or queue the rest
Calendar fills, estimate queue grows, spam dies
Routine work books directly onto operator-approved availability. Quote requests hand off to the estimate-follow-up agent. Robocalls and known vendors are filtered without ringing the operator.
05 · proof in the ledger
Every recovered call attributable
Weekly ROI report: missed calls intercepted, emergencies escalated, quotes captured, routine bookings, robocalls filtered, voicemails rescued, and estimated value recovered.
talk to the agent
Ask the Receptionist OS
Try a real call scenario: an emergency, a quote request, a routine booking, or a robocall. The agent responds the way the production system would actually handle it.
Receptionist OS · live
emergency dispatch · quote intake · routine booking · spam filter
Receptionist OS, what's the call? Tell me what's happening — emergency, quote, routine, or just a question. I'll classify, route, and confirm what the operator would actually do next.
you've seen it run
Want this one running in your business?
Book a 45-minute call and we'll scope the same crew on your data — your CRM, your calendar, your branding.