Work / Voice & Phone / 10 · Home services & construction
AI Front Desk — Missed Calls, After Hours and Booking
Home services · Clinics · Salons · Dental · Legal
Built — counted from the workflow JSON in the repository; not yet run against live accounts
The problem
Every missed call is a lead that was already paid for, and the caller reaches the next result in under a minute.
A service business misses a large share of inbound calls while staff are on a job, at lunch or gone for the day. An answering service costs by the minute, cannot see the calendar and books nothing.
How it runs
-
Ring the real line first
01 / 07 Workflow 1 of 5 · Inbound Call Router · 10 nodes
Twilio reaches the system only after the business’s own line has rung out — a person always gets first refusal.
-
Decide the hours once
02 / 07 Workflow 1 of 5 · Inbound Call Router · 10 nodes
Whether the business is open is decided in code and handed to the agent as a fact, never reasoned about.
-
Answer, within limits
03 / 07 Workflow 2 of 5 · Agent Tools & Guardrails · 17 nodes
The voice agent takes the call; everything it may not decide alone sits behind a tool webhook it has to call.
-
Price from a table
04 / 07 Workflow 2 of 5 · Agent Tools & Guardrails · 17 nodes
A price comes from a configured table, or the agent says out loud that it will not guess.
-
Escalate on six triggers
05 / 07 Workflow 2 of 5 · Agent Tools & Guardrails · 17 nodes
Gas, flood, electrical, a vulnerable household, a complaint, or asking for a person: any one hands the call to a human.
-
Confirm, re-check, book
06 / 07 Workflow 3 of 5 · Availability & Booking · 15 nodes
A slot, an address, a name and a real phone number — then the slot is checked again, and only then is the job created.
-
Recover and record
07 / 07 Workflow 4 of 5 · Missed Call Recovery · 9 nodes
A caller who hangs up gets a booking link by SMS inside a minute, and every call is summarised into the CRM.
The five workflows, as built
Every node with its icon, as on the n8n canvasstarts a runa model or a parser, wired into the node above itHover a node for its name and type
-
01Inbound Call Router
10 nodes · 10 connections · 2 notes
overflow detection, hours, the call handed on
-
02Agent Tools & Guardrails
17 nodes · 22 connections · 3 notes
the price table, the escalation list, the tool router
-
03Availability & Booking
15 nodes · 17 connections · 3 notes
real slots, the commitment gate, the re-check
-
04Missed Call Recovery
9 nodes · 10 connections · 2 notes
a booking link by SMS, inside a minute
-
05Post-Call Write-Back
13 nodes · 12 connections · 2 notes
signed webhook, summary, CRM
64 executing nodes, by type
The gates, 10 If and Switch nodes, decide whether anything happens next: a countable part of the system, not a claim about it. The 12 sticky notes carry the reasoning on the canvas, at the point it applies.
The guards, and what each one prevents
HoverTap a card to read what it prevents.
- The agent is the overflow, never the front door
Twilio reaches the workflow only as the dial action URL, after the human line has finished ringing; a call a person answered exits at once.
- Hours travel as a boolean
A model that can reason about the time can reason its way into a Sunday appointment. Out of hours it still answers, with a link.
- A price from the table, or none
A prompt saying “do not quote prices you are unsure of” is a request; a lookup that returns a refusal is a control.
- Six triggers, every turn, fixed words
Matched against the running transcript, not left to the model to notice — and answered with fixed wording, because a gas call is the worst moment to improvise a handoff.
- Four confirmations, then a re-check
Without the gate the agent books on “yeah, maybe Tuesday”. The slot was free when offered; two minutes later it may not be.
- If it was not said, it stays empty
The summariser writes only what is in the transcript. An address guessed from an area code looks exactly as confident as one the caller gave.
Limits, stated plainly
- Built, not yet deployed. The five workflows import clean and every connection resolves; no real call has flowed through them end to end.
- The voice agent itself — its prompt, voice and turn-taking — is configured in the vendor’s console. These workflows are everything around it: the routing, the tools and the write-back.
- The field-service CRM is Housecall Pro. Jobber or ServiceTitan means rewriting the booking workflow, and the slot builder assumes one shared calendar.
- There is no call-recording consent announcement yet. Two-party-consent jurisdictions need one before it goes live.
Built with
- n8n
- Twilio
- ElevenLabs
- Housecall Pro
- OpenAI
- Google Sheets
- Slack