Missed call text back is a simple idea: when someone calls a business and nobody picks up, the phone system automatically sends that caller a text instead of letting the call disappear into a voicemail nobody checks. The caller gets a reply in seconds, the business gets a second chance at the lead, and the conversation moves to a channel people actually read.
Setting it up correctly, and legally, is less simple than the vendor landing pages make it look. This guide covers how the automation works, the US texting rules that apply before you turn it on, setup steps, ready-to-use scripts by industry, and the failure modes that quietly break it after launch.
How missed call text back actually works
Three things have to be true for it to work:
- Something detects the missed call. A VoIP phone system, a call tracking platform, or a CRM connected to your number through call forwarding watches for a call event, such as "rang and went unanswered," "hung up before voicemail," or "routed to voicemail," and fires a trigger.
- The business number can send SMS. The reply should come from the number the caller dialed, or a number clearly tied to the business, so it doesn't look like spam. If the number that took the call can't send SMS, the text has to route through a separate text-enabled number, which looks less trustworthy to the caller.
- An automation platform sends the message. Once the missed-call event fires, a workflow sends a pre-written text within seconds, usually logging the conversation in a CRM.
Two common setups cover most small businesses. If you already use a VoIP or cloud phone system, or a CRM's built-in calling, the missed-call event and the SMS send happen on the same platform, so there is nothing to forward. If you keep an existing number, often a landline or a carrier mobile line, calls get conditionally forwarded to a text-enabled tracking number on no-answer, and that layer detects the miss and sends the text. Depending on the provider, the caller may see the text arrive from your main number or from the tracking number, so confirm which before promising a client "it'll look like it's coming from us."
Every provider agrees on one thing: the text has to arrive within seconds, not minutes, because the point is to reach the caller while they're still thinking about why they called.
What you need before you turn this on
| Requirement | Why it matters |
|---|---|
| A business number that can send SMS | A standard analog landline cannot send SMS; it was built for voice only (GetWeave). Some landlines can be "text-enabled" through a third-party service. |
| A phone system or CRM that fires on "missed call" | A trigger, not just a ringing phone. Call forwarding with a tracking layer, a VoIP webhook, or a CRM call-log event all work. |
| US SMS compliance registration | A2P 10DLC or toll-free verification, covered below. Skipping this gets messages filtered or blocked, not just delayed. |
| A documented consent basis | The call itself supports an informational reply, but you need a clear basis before using the number for any marketing later. |
| Someone who picks up the reply | The text only creates an opening. If nobody reads the reply, you've automated the same problem you were trying to fix. |
The compliance rules that actually apply
This is the part most vendor pages skip, and the part that determines whether your texts arrive at all. None of this is legal advice. If you're unsure how these rules apply to your specific business or client, check with a telecom attorney before launch, particularly for anything beyond a single informational reply to a missed call.
A2P 10DLC: registration for texting from a normal 10-digit number
If you send application-to-person (A2P) texts from a regular 10-digit US number, carriers require you to register under the A2P 10DLC framework: a Brand, which identifies your business, and a Campaign, which declares what kind of messages you send. Every number you text from is tied to a registered campaign.
This isn't optional. Twilio phased in blocking of unregistered 10DLC traffic starting July 2023, with unregistered messages fully blocked by August 31, 2023 (Twilio Support; MessageDesk). Carriers now block unregistered A2P traffic to US numbers outright, and unregistered traffic also carries higher per-message carrier fees (MessageDesk). If your missed-call text-back number isn't registered, the reply either never reaches the caller or arrives inconsistently filtered, with no clean error telling you why.
Agencies setting this up for multiple clients should register each client's own brand tied to the numbers it texts from. This takes days, not minutes, so register before promising a go-live date.
Toll-free numbers need a separate verification, not 10DLC
A toll-free number (800, 888, 877, 866, 855, 844, 833) doesn't go through A2P 10DLC. It needs toll-free verification instead, required by US and Canadian carriers. Twilio toll-free numbers can't send SMS to the US or Canada until verification is submitted and approved, and as of January 31, 2024, unverified toll-free numbers are blocked entirely (Twilio Support). Verification asks for your business name and website, a use-case category, a description of the messaging program, how you collected opt-in, and two sample messages. It's free and typically takes a few business days, though vague opt-in descriptions commonly get bounced back for more detail (Twilio Support).
TCPA: what a missed-call text can and cannot be used for
The Telephone Consumer Protection Act (TCPA), implemented through FCC rules at 47 CFR 64.1200, draws a line between two categories of automated messages. Informational (non-marketing) messages require prior express consent, which doesn't have to be in writing and can generally be inferred from context, such as someone voluntarily calling your business (Cornell Law, 47 CFR 64.1200; Fransis.ai). Marketing or promotional messages require prior express written consent, a stricter standard defined at 47 CFR 64.1200(f): a signed or affirmatively-given agreement specific to that business, not a pre-checked box or a verbal "sure" on a call.
The reasoning some compliance writers apply here is that a single, strictly informational reply to a call the person just placed, something like "Thanks for calling [Business], sorry we missed you, how can we help?", falls under the lighter informational standard because the caller initiated contact. The moment that reply includes promotional content, or the caller gets added to a marketing sequence, it needs the stricter written-consent standard instead. Several compliance sources are explicit that calling a business is not consent to receive its marketing, and recommend never auto-enrolling a missed-call responder into a marketing list.
In practice: keep the first automated text purely informational, with no sale, discount, or campaign pitch. Don't automatically add missed-call texters to a marketing list; collect separate consent for that. Build in STOP handling regardless. And because this reasoning is "the stronger argument," not a bright-line rule tested in every court, run it past counsel if your volume or client list is large enough that a dispute would be expensive.
STOP, opt-out, and the CTIA rules carriers enforce
CTIA, the wireless industry trade association, publishes the Messaging Principles and Best Practices that carriers enforce on all A2P traffic, registered or not: recipients must be able to opt out at any time through text, call, or email; standard STOP wording should be used and common variants (UNSUBSCRIBE, CANCEL, QUIT, END) honored too; and senders should send exactly one opt-out confirmation message, then nothing further (CTIA, May 2023).
Separately, since 11 April 2025 FCC rules have required businesses to honor a revocation of consent within a reasonable time, not to exceed 10 business days, made through any reasonable method, including replies such as STOP, QUIT, CANCEL, UNSUBSCRIBE, REVOKE, OPT OUT or END. This area is moving. On 30 September 2026 the FCC voted to amend the rules again: businesses will be allowed to name one exclusive way to opt out, and an opt-out from one type of informational message will no longer have to stop every other type. Those changes take effect 30 days after they are published in the Federal Register, and the FCC has also asked whether the 10-day ceiling should be shortened (Crowell & Moring). For a missed call text back the practical answer does not change: when someone replies STOP, stop immediately.
Practical requirement: every missed-call text should either include opt-out instructions or rely on a workflow that watches for STOP-family replies across every number in play and suppresses future texts to that contact.
Setup steps, generic to any platform
- Confirm the number can send SMS. For mobile or VoIP numbers, check with your provider. For a landline, ask about text-enabling it, or route the text through a separate, clearly-labeled business number.
- Register the number. A2P 10DLC brand and campaign for a standard number, or toll-free verification for an 800/888/877-style number. Do this first; it has the longest lead time.
- Set up the missed-call trigger. A workflow trigger on a call event: no-answer, voicemail, or busy. If forwarding from an existing number, forward to the tracking layer only on no-answer or busy, not every call.
- Write the first message. Short, informational, names the business, invites a reply. See scripts below.
- Add opt-out handling. Append "Reply STOP to opt out," or confirm your platform already filters STOP-family replies account-wide.
- Decide business-hours vs after-hours logic. A call at 2pm and a call at 11pm should probably get different messages.
- Route replies to a person. The text should land in an inbox someone is actually watching, with a booking link where you have one.
- Test it end to end. Call the business number from a phone you control, let it go unanswered, time the text, then reply and confirm it reaches the right inbox.
- Document the consent basis. Note that this is a reply to an inbound call, not a marketing send, and keep it separate from marketing opt-in records.
Timing: how fast is fast enough
Every provider agrees on direction, if not the exact number: the text should go out within seconds, not minutes. The whole premise is reaching the caller while the reason they called is still on their mind. If a workflow has a delay step "to avoid looking too automated," remove it. The point of the text is that it lands while the caller is still deciding who to call next.
11 ready-to-use scripts by industry
Keep these as the first message only. No emojis, no pressure, business name included, and a clear invitation to reply. Adjust the booking-link line if you don't have one.
General / any local service
"Hi, this is [Business Name]. Sorry we missed your call! Reply here and we'll get right back to you, or call us back anytime."
Dentist / dental practice
"Hi, thanks for calling [Practice Name]. We're with a patient right now and missed your call. Text us what you need, or book a visit here: [link]."
HVAC / plumbing / home services
"Hi, this is [Business Name] Heating & Air. Sorry we missed you. If this is urgent, reply URGENT and we'll call you back first. Otherwise let us know what's going on and we'll get back to you shortly."
Med spa / aesthetics
"Hi, thanks for calling [Spa Name]. We missed your call but we're here. Text us which treatment you're interested in, or grab a time that works for you: [booking link]."
Auto repair / mechanic shop
"Hi, this is [Shop Name]. Sorry we missed your call. Tell us what's going on with your vehicle and we'll text you right back, or call you if you'd prefer."
Law firm (intake line)
"Thank you for calling [Firm Name]. We missed your call. Please reply with a brief description of your situation and the best time to reach you, and our team will follow up."
Veterinary clinic
"Hi, thanks for calling [Clinic Name]. We're currently with other patients. If this is an emergency, please call [emergency line]. Otherwise, text us and we'll respond shortly."
Salon / barbershop
"Hi, this is [Salon Name]. Sorry we missed you! Reply here to book, or use this link anytime: [booking link]."
Real estate agent / brokerage
"Hi, this is [Agent/Brokerage Name]. Sorry I missed your call. Let me know what property or question you're calling about and I'll get back to you right away."
After-hours (any industry)
"Hi, thanks for calling [Business Name]. We're closed right now, back open at [hours]. Leave us a message here and we'll follow up first thing, or let us know if it's urgent."
Repeat caller (second missed call same day)
"Hi, this is [Business Name] again, sorry we keep missing you. We definitely want to help. What's the best way to reach you, text or a call back at a specific time?"
What happens after the reply
The text-back message is only the opening move. What matters more is what happens when someone replies: route it to a real person fast, so the reply doesn't sit unread for hours and recreate the voicemail problem with better optics; hand it off with context, so whoever answers knows this came from a missed call rather than a cold text; offer a booking link where scheduling is the likely next step, instead of texting back and forth over a time slot; and escalate urgent replies like "no hot water" ahead of the general queue.
How to measure whether it's working
Track these at minimum, by week or month:
| Metric | What it tells you |
|---|---|
| Missed calls | Volume of the opportunity the automation is addressing |
| Texts sent | Should be close to 100% of missed calls, after excluding opted-out contacts and known non-SMS numbers |
| Reply rate | Of texts sent, how many callers responded |
| Time to first reply from staff | How long a caller waited after they texted back |
| Booked appointments / deals from missed-call threads | Whether the conversation converted, tagged distinctly from other lead sources |
If texts sent is noticeably below missed calls, check the failure modes below before assuming the automation itself is broken.
Common failure modes
- The number isn't actually SMS-enabled. The single most common silent failure: a newly ported landline or a number from an old phone system often can't send SMS until explicitly enabled by the carrier or texting provider.
- Unregistered 10DLC traffic getting filtered. If registration lapses or a number is added to a campaign late, texts start getting filtered or blocked, often with no visible error on your side (MessageDesk).
- Texting a landline caller. You can text-enable your own number, but you can't make the caller's landline receive your reply. If the caller phoned from a landline, the text has nowhere to land, and you may need a call-back fallback.
- No after-hours vs business-hours logic. A midday "sorry we're closed" message, or a daytime message sent at 1am, both read as broken automation rather than a responsive business.
- Duplicate texts to repeat callers. If someone calls three times in twenty minutes, most setups fire the same message three times unless you add a cooldown.
- Voicemail and text-back contradicting each other. If the caller also gets a voicemail, the text should reference it rather than ignore it.
- STOP handled per-number instead of per-contact. If a contact opts out via one number but suppression isn't shared across all your numbers, you'll re-text someone who already asked you to stop.
Missed call text back in a CRM
Most missed-call text-back tools are single-purpose: they watch a phone line and send a text, nothing else. The tradeoff is that the conversation and lead record live in a separate system from wherever you manage the relationship, which means a second login and a second place a reply can get missed.
Inflowave has a ready-to-clone missed-call text-back workflow template among its library of automation templates, with calls, SMS, and the lead's conversation history inside the same CRM inbox rather than a separate texting tool. That doesn't replace registering your number correctly or checking your consent basis. It just keeps the missed call, the text, the reply, and the resulting deal visible in one place.
Frequently Asked Questions
Is missed call text back legal?
A single, purely informational reply to a call the person just placed is commonly read as covered by the consent the call itself implies, since the message only responds to contact the person started. The rules do not spell this case out, which is why opinions differ (47 CFR 64.1200). It gets riskier the moment the message includes marketing content or the caller is enrolled in ongoing promotional texts, which need the stricter written-consent standard. This is general information, not legal advice; check with a telecom attorney for your situation, especially at scale.
Can a landline send or receive a missed call text back?
A standard analog landline cannot send or receive SMS; it uses analog voice signaling with no SMS protocol support (GetWeave). Some landline numbers can be "text-enabled" through a third-party service, letting a business keep its number for texting. But if the caller dialed in from their own landline, there's no way to deliver a text reply to them.
Do I need A2P 10DLC registration for missed call text back?
Yes, for a standard 10-digit US business number. Unregistered A2P traffic to US numbers is blocked by carriers outright, not just slowed down, since enforcement completed in 2023 (Twilio Support). Texting from a toll-free number instead needs toll-free verification, not 10DLC registration.
How fast should the text go out after a missed call?
As close to immediate as the platform allows, typically within seconds. The value is reaching the caller while they're still thinking about why they called.
Can I add missed-call texters to my marketing list automatically?
No. Compliance sources are explicit that calling a business is not consent to receive its marketing. Collect separate, specific consent before adding anyone from a missed-call exchange to a marketing list.
What if the caller replies STOP?
Honor it, immediately. CTIA guidance says to accept STOP and its common variants (unsubscribe, cancel, quit, end) and send exactly one confirmation message with nothing further after that (CTIA, May 2023). FCC rules set an outer limit of 10 business days to process an opt-out, and the FCC voted on 30 September 2026 to change parts of these rules, so check the current version before you rely on any deadline (Crowell & Moring). Most platforms process STOP automatically, which is the safest setting.
Sources
Checked 12 October 2026.
- Twilio Support: A2P 10DLC Sole Proprietor Brands FAQ
- MessageDesk: Twilio A2P 10DLC Registration Guide
- Twilio Support: Toll-Free Message Verification for US/Canada
- Twilio Support: Toll-Free Verification Onboarding Guide
- Cornell Law: 47 CFR 64.1200, Delivery restrictions
- Fransis.ai: TCPA Consent Types: Express vs Written Explained
- Crowell & Moring: FCC adopts TCPA rule amendments, October 2026, checked 12 October 2026
- Troutman Pepper Locke: FCC Revises TCPA Revocation of Consent Rules
- CTIA: Messaging Principles and Best Practices, May 2023 (PDF)
- GetWeave: What Happens If You Text a Landline?
