Missed-call text-back

SMS Follow-Up for Missed Calls: Catch Caller, Not Voicemail

Three triggers one SMS — call rings then hangs up, voicemail timeout, or after-hours overflow. Analese follows up with consent and opt-out handling.

Every missed call is a lost caller. Analese sends an SMS reply with the shared disclosure within seconds of any of three triggers — caller hangs up before answer, voicemail timeout after the beep, or after-hours overflow when the on-call queue is full. The reply is real, written by the receptionist, not a generic 'we'll call you back' autoresponder. STOP-family keywords opt the caller out for good, on the same consent ledger the rest of the SMS pipeline respects.

Every missed call is a lost caller. Analese sends an SMS reply with the shared disclosure within seconds of any of three triggers — caller hangs up before answer, voicemail timeout after the beep, or after-hours overflow when the on-call queue is full. The reply is real, written by the receptionist, not a generic 'we'll call you back' autoresponder. STOP-family keywords opt the caller out for good, on the same consent ledger the rest of the SMS pipeline respects.

What you get

  • Three triggers, one text-back — caller hangs up, voicemail timeout, or after-hours overflow.
  • Shared disclosure on every send — the first SMS in a relationship carries the disclosure line the AI speaks on every channel.
  • STOP-keyword opt-out the moment it arrives — STOP, CANCEL, END, QUIT, STOPALL, UNSUBSCRIBE all honored case-insensitively as a whole word.
  • Analese supports SMS follow-up with consent and opt-out handling.

How the dispatcher runs

  1. 01A caller dials your forwarded number; Analese picks up based on the same routing layer the receptionist uses for every call.
  2. 02If the caller hangs up before the AI answers — or the on-call queue is full — the phone system emits a hangup event.
  3. 03Voicemail timeout fires the same path with a different trigger.
  4. 04/api/missed-call-text-back/dispatch decides which trigger fired and crafts a one-question reply (Do you want to book?).
  5. 05The same consent ledger handles the missed-call reply and honors STOP-family opt-out keywords.
  6. 06If the caller replies STOP, the system acks with the same STOP_ACK string used everywhere and opts the number out of every future SMS — never texting that number again.

A buyer question: what does the first SMS say?

Apologies for the missed call, a question about whether the caller wants to book, and the AI/SMS disclosure line the receptionist speaks on every channel. The line is read straight from the same /lib/business/tcpa-sms-disclosure module the route handlers use, so the wording cannot drift from the canonical language. It includes variable frequency, possible message and data rates, a STOP opt-out, and the Terms and Privacy URLs. After the disclosure, the next send is a trailing opt-out reminder — 'Reply STOP to opt out.' — so the opt-out path stays visible on every send, not just the first.

A buyer question: when does this work?

Missed-call follow-up can run after a caller hangs up, a voicemail timeout, or after-hours overflow. The flow uses the shared consent and opt-out handling.

Ready to see it work?

Ready when you are.

Sign up and you've got a live AI receptionist in about 15 minutes. Self-serve, no sales call in between, no agency setup fee.

Keep reading

More from the blog. Different topic, same playbook.