Missed-Call Text-Back

Fixes: after-hours / busy-line calls that hit voicemail and go book a competitor. Highest-ROI first build for any local/service business — a handful of recovered jobs a month pays for the whole engagement.

Stack

• Simplest / all-in-one: GoHighLevel (missed-call-text-back is a native workflow; also brings CRM, calendar, reviews).
• Composable / cheaper at scale: Twilio (number + SMS) + CallRail or Twilio call events → n8n (or Make) → Claude for the reply draft.
• Compliance layer (required): A2P 10DLC brand+campaign registration; consent language; opt-out handling.

field-tested build

1. Audit — how are calls handled now? After-hours? Overflow when busy? Who currently calls back, and how late? Get the number of missed calls/week and rough job value.
2. Optimize — decide the one message and the path it opens: a booking link, a human handoff, or an AI thread. Don’t automate a confusing intake — define the clean flow first (what info to capture, when a human takes over).
3. Automate —
4. Trigger: unanswered inbound call (no answer in N rings, or after hours).
5. Action: instant SMS — “Sorry we missed you at [Business]! Reply here and we’ll get you sorted — what do you need, and when works?”
6. Route replies to the owner/CRM; optional Claude drafts the follow-up; human approves early on (human-in-the-loop first, loosen as trust builds).
7. Verify — test with 3 real scenarios (after-hours, busy, spam). Confirm opt-out works.

Time to ship

Quick Win — < 1 day on GoHighLevel; ~1 session composable.

Compliance

Do not launch without A2P 10DLC + consent. First message must identify the business and honor STOP. This is a TCPA exposure if skipped.

Log in Notion

“Built missed-call text-back. Recovers ~[N] calls/week × ~$[job value] = ~$[monthly] in otherwise-lost jobs.” Attach a screenshot of a live test.