1. Call event
Detect no-answer, busy, or voicemail events and capture a callback number.
Cloud phoneCall trackingWebhook01 · Understand the machine
One event. One fast reply. One human handoff.
The system does not need to “run the business.” Its first job is smaller: acknowledge a caller quickly, learn what they need, and move the conversation to the right next step.
EVENT
Call is missed
The phone system emits a missed/no-answer event with the caller’s number.
FILTER
Check the rules
Ignore blocked numbers, duplicates, after-hours exceptions, and known spam.
MESSAGE
Send the text
A short, human reply goes out from a business-owned number.
ASSIST
Classify the reply
AI can draft or route. Keep high-stakes answers and final decisions with a person.
HANDOFF
Book or alert
Offer the next step, create the lead, and notify the right teammate.
The valuable part is not “AI.” It is closing the gap between an unanswered phone and the next useful action.
02 · Pick the stack
Four layers. Swap vendors without changing the blueprint.
Use tools the business already trusts when possible. The architecture matters more than the logo on each box.
2. Orchestrator
Receive the event, deduplicate, apply business rules, and call the next service.
n8nMakeCustom function3. Messaging
Send and receive SMS from a registered business number with delivery logs.
SMS providerShared inbox4. Destination
Route the conversation into the team’s existing process.
CRMCalendarTeam alert03 · Build it
The minimum reliable workflow
Start deterministic. Add AI only after the basic event, message, and handoff work every time.
WORKFLOW PSEUDOCODE
// Triggered by a missed-call event if !event.callerNumber → stop if event.callerNumber in blocklist → stop if same number was handled in last 15 minutes → stop business = lookup(event.dialedNumber) message = template(business.name, business.replyWindow) sendSMS(from: business.smsNumber, to: event.callerNumber, body: message) createOrUpdateLead(callerNumber, source: "missed-call") notifyTeam(owner, callerNumber, deliveryStatus) log(eventId, sentAt, status) // Optional only after the reply arrives routeReply(intent, urgency, requestedService)
Catch a real event
Place a test call, let it ring out, and inspect the exact payload. Build from the fields you actually receive—not fields a diagram promises.
SAVE: event ID · caller number · called number · timestamp · disposition
Deduplicate before sending
Phone systems may emit more than one event. Create an idempotency key from the event ID, or the caller number plus a short time window.
Map numbers to businesses
If you manage more than one location or client, keep business name, hours, reply text, owner, and destination calendar in a simple configuration table.
Send, log, and expose failures
Store the provider message ID and delivery status. Alert a person if the send fails; do not silently drop the lead.
Handle the inbound reply
Start with routing rules: service question, schedule request, urgent issue, or opt-out. AI may draft, but a human should own ambiguous or sensitive replies.
04 · Write the texts
Sound like a person who just missed the phone.
Short, specific, and easy to answer. Choose a trade and stage to generate a starter message, then edit it to match the business.
Never pretend the text is a human response if it is automated. “Automated reply” can be both honest and warm.
05 · Test it
Six calls before you call it done.
Run the same test from two different phones. Record timestamps and message IDs so a failure is diagnosable.
Normal missed call
Let the call ring out. Confirm one—and only one—text arrives, the business name is correct, and the reply goes to the right inbox.
Duplicate event
Trigger two missed calls close together. Confirm the deduplication rule prevents a message pile-on.
Known customer
Call from a number already in the CRM. Confirm the lead is updated rather than duplicated.
After hours
Confirm the message sets a truthful expectation and does not promise an immediate human reply.
Opt-out
Reply STOP. Confirm future automated texts from that sender are suppressed and the status is visible.
Provider failure
Use a safe test condition to make a send fail. Confirm the workflow alerts the operator instead of reporting success.
06 · Size the value
Use the owner’s numbers, not made-up case studies.
This calculator is a conversation starter—not a revenue promise. Adjust every input with the business owner.
Illustrative monthly recovered value
$2,598
Formula: weekly missed calls × rate × job value × 4.33 weeks. Actual results depend on call quality, capacity, response handling, and close rate.
07 · Package the skill
Sell the outcome. Scope the system.
Once your own workflow is stable, document it. The same installation can become a focused offer for another local business.
Lead with the missed-call gap, demonstrate the reply on the owner’s phone, and make support boundaries explicit.
A clean starter offer
- Connect one phone line
- Write and approve three messages
- Route replies to one shared inbox
- Create or update leads in the CRM
- Run six acceptance tests
- Train the team on handoff and opt-outs
- Monitor delivery failures during the support window
30-second owner pitch
“When your team misses a call, how long does it take that person to hear back? I build a simple text-back system that acknowledges the call, asks what they need, and routes the reply to your team. I can show you the whole flow on one missed call—no slide deck.”
Price the install from your actual software cost, setup time, support load, and business risk. Do not promise a specific number of bookings you have not proven.
08 · Guardrails
Fast does not mean careless.
Messaging rules vary by country, carrier, use case, and provider. Treat compliance and customer experience as part of the build—not cleanup.
Identify the business
The recipient should immediately know who is texting and why.
Honor opt-outs
Respect STOP and equivalent requests. Keep suppression status across every automation path.
Register the sender
Use a business messaging setup approved for the sender’s region and traffic type.
Protect sensitive data
Do not ask people to text payment cards, medical details, passwords, or other sensitive information.
Set honest timing
After-hours messages should not imply that a person is available when no one is monitoring replies.
Keep a human escape hatch
Make urgent, angry, ambiguous, and high-stakes replies easy to route to a person.
Take the blueprint with you
Download the build brief, test plan, message starter, and offer scope as a plain-text working document.