How fast does Orbit Recall text back a missed call?

Median ~8 seconds from the moment Twilio reports a no-answer/busy/canceled status to the SMS leaving our servers.

Will it text the same caller multiple times if they call back-to-back?

No. A 10-minute dedupe window per (business, caller) pair suppresses repeat text-backs on burst dials. The customer gets one text, not three.

What happens if a customer texts STOP?

Recall honors the opt-out forever and across every BizBot vertical the business runs. If they ever sent STOP to one of your vertical apps, Recall will not text them again — even from a different vertical — until they explicitly text START to resubscribe.

Does it text in the middle of the night?

The first text-back fires immediately when a call is missed — that's the whole point. But the +4h and +20h follow-ups defer until 8am in the customer's timezone so nobody is woken up at 2am.

Is the first message disclosed as AI?

Yes. The first automated text identifies itself as the business's assistant in a short signoff and includes the STOP wording, meeting EU AI Act Article 50 and FTC guidance. Follow-up replies don't repeat the disclosure so the conversation reads naturally.

What stops a dialer bot from running up our SMS bill?

A per-client daily cap of 100 Recall text-backs per UTC day. The owner is SMS-paged on the first breach so the cause (forwarding loop, dialer attack) can be investigated; Recall auto-resumes at the next UTC midnight.

Can I pause Recall while I'm on vacation?

Yes. From the client portal you can snooze 2h, 24h, or 7 days with one click. Snooze is stored per-client in AIConfig and honored on every missed call until you resume.

Does Recall work for Spanish-speaking customers?

Yes. The AI matches the caller's reply language automatically, and PARAR / ALTO / CANCELAR / AYUDA / COMENZAR are recognized as STOP / HELP / START with Spanish reply confirmation.

Module 2 of 6 · Live

Every missed call gets a text in 8 seconds.

"Missed-call text-back" is now a feature in every CRM. The difference is what happens when the customer replies. Most tools dump it in an inbox for you to handle later. Recall reads the reply, decides what kind of customer this is, and chains the next module — Confirm to book, Voice to call back, Stars for a review request — without you touching a phone.

Book a demo → Watch the brain live

Modeled targets — design goals for the Recall flow, not measured customer results.

Time to text-back

~8s

Voice missed → Recall SMS leaves Twilio. Target latency.

Reply rate

~38%

Within 30 minutes of the text — modeled target.

Auto-booked

~22%

Of replies that show book-intent → Confirm without human. Modeled.

Cost per recovered lead

~$0.04

Twilio SMS + Haiku parse. ~$1.80 per booked appointment.

The flow · timeline view

What happens, and when.

Below is the canonical Recall sequence — call missed at T+0s, customer booked at T+~6 minutes — with the actual SMS bodies and the events the brain emits at each step.

T+0.0sCall

Customer calls. Owner doesn't pick up.

Twilio routes the inbound. Owner is on a job site / in a meeting / driving. Call rings out and Twilio fires the status callback to Voice.

EMITS: Voice.MissedCallDetected

T+1.4sDecide

Brain decides: text them.

Orchestrator (Claude Haiku) reads the event + shared customer memory for that phone number. Looks at: Have we talked to this number before? Are they a repeat customer? Was this an after-hours call? Outputs a Recall.SendSms action with the right tone.

ACTION: Recall.SendSms (priority=high)

T+8.2sSMS sent

Recall fires the text.

Personalized to vertical and time-of-day. New customer gets a soft intro; returning customer gets recognized.

Hi — this is Davis Roofing. Sorry we missed you, we're on a job. What can we help with? Reply here and we'll get right back to you.

EMITS: Recall.SmsSent

T+4m12sReply

Customer replies.

yeah hi, looking for a quote on a roof inspection. when can someone come out? saturday possible?

Twilio inbound webhook hits /api/orbit-recall-reply. Recall emits the reply event with the raw text.

EMITS: Recall.CustomerReplyReceived

T+4m13sParse

Haiku parses intent.

Orchestrator decodes the reply: {"intent":"book_appointment","service":"inspection","preferred_day":"saturday","customer_type":"new"}. Routes to Confirm.

ACTION: Confirm.CreateAppointment

T+4m15sBook

Confirm books the slot + texts back.

Reads owner calendar, finds the next Saturday opening, writes the booking, fires the confirmation SMS.

Done — Saturday May 11 at 9:00am, 412 Linden Ave. Dave will text 30 min before he's en route. Reply CANCEL to reschedule.

EMITS: Confirm.AppointmentCreated

T+5dPost-job

Job complete → Stars + Invoicing kick in.

When the owner marks the job done in the dashboard, the brain chains Stars.SendReviewRequest + Invoicing.SendPaymentLink — same number, same record, same conversation thread.

CHAIN: Stars.SendReviewRequest · Invoicing.SendPaymentLink

What makes it different

"Missed-call text-back" vs Recall.

The phrase is the same. The system underneath is the difference between a tool that sends a text and a system that runs the front of the business.

Generic missed-call text-back

Sends a fixed template — same text for every customer.
Reply lands in a separate inbox for the owner to read later.
No memory: a customer who's called 5 times gets the same intro as a stranger.
No handoff: even if the customer says "book me Saturday," nothing happens until a human reads the inbox.
Doesn't know about reviews, jobs, invoices, or scheduling — just SMS.

Orbit Recall

Text body adapts to vertical, time-of-day, and customer history.
Reply parsed by Haiku in ~1s — no inbox queue.
Shared memory: returning customer is greeted by name, prior job referenced if relevant.
Book intent routes straight to Confirm — appointment booked while owner is still on the job site.
Lives on the same brain as Voice, Stars, Scout, Confirm — same customer record across all of them.

Guardrails · always on

The text you don't want to send.

Recall ships with four built-in rules that prevent customer-experience and compliance accidents — the kind that get small businesses into TCPA trouble or one-star reviews. None of these are toggles. They are how Recall works.

STOP is forever

If a number has ever sent STOP / UNSUBSCRIBE / CANCEL — to any of your 15 verticals — Recall will not text it again.
Re-subscribe is opt-in only: customer texts START to come back.
Logged to CallLog as recall_skipped_optout so you can prove honoring on demand.

No triple-text on burst dials

Same caller hits voicemail 3 times in 5 minutes? They get ONE text, not three.
10-minute dedupe window per (business, caller) pair.
Saves the SMS spend and avoids the "stop spamming me" reply.

Quiet hours, customer-local

The first text-back fires immediately — that's the whole point.
But the +4h and +20h follow-ups defer until 8am in your timezone.
No 2am text. No "why is my plumber buzzing my phone at midnight."

AI-disclosure on first contact

First automated text identifies as the assistant in a short signoff — meets EU AI Act Art. 50 + FTC.
Follow-ups don't repeat the disclosure — reads like a real conversation, not a robot.
STOP wording is in every first message. One tap, customer is out.

Included with the + bizbot add-on · see pricing

Pick a vertical. Recall comes with it.

Orbit Recall is included in the + bizbot add-on across all 15 verticals. Or — turn it on inside any vertical's Free tier to test the SMS template before you upgrade.

Browse all 15 verticals See Stars (next in chain) →