Missed Call Text Back: How It Works, and What We Learned Turning It On
A missed call is usually someone with a need right now: a leak, a booking, a question they want answered today. If all they get is a voicemail greeting, the next business in their search results is one tap away. A text back keeps the conversation open while you’re on a job, with another customer or asleep.
We run missed call text back on our own business line. This guide covers what it does, the carrier registration you need before it works, the opt-out rules, and the mistake we made on our second night live, with dates and times from our own system logs. The rules come from the people who set them: CTIA (the wireless industry’s messaging guidelines), the FCC, Twilio and HighLevel. Links to each are at the end.
How missed call text back works
When a call to your business number isn’t answered (busy, no answer, or it rolls to voicemail), the system sends one text from that same number. The caller can reply right there, and the reply lands in your CRM inbox, where you, a team member or an AI assistant picks it up. Ours also alerts the owner, so a person always sees it.
This is the exact text our line sends:
On the night we tested it, the call went to voicemail and that text went out 43 seconds later. Each part of it does a job: it says who is texting, invites a reply, offers one next step and tells the person how to stop the texts.
In HighLevel (the CRM platform we build on, also known as GoHighLevel) there are two ways to set this up: a built-in setting under Phone System → Voice → Voicemail & Missed Call Text Back, or a workflow you build yourself. HighLevel’s help page suggests letting the phone ring 10 to 20 seconds before the text fires. Pick one of the two, not both. More on why below.
Step 1: Register the number first (A2P 10DLC)
Your phone’s own auto-reply (“Driving now, can’t talk”) counts as personal messaging. A business sending automatic texts doesn’t. CTIA’s guidelines say so directly: automation used by a business to send messages is not typical consumer operation. That puts a missed-call text in the business lane, called A2P (application-to-person).
In the US, business texting from a regular 10-digit local number has to run through a registered A2P 10DLC campaign. Twilio’s announcement is blunt: since September 1, 2023, unregistered messages from +1 10DLC numbers to US phones are blocked. Registration has two parts:
- Brand: who is sending. Your legal business name, EIN, address and contact details, entered exactly as the IRS has them.
- Campaign: what you’ll send and how people agree to it. A description of the messages, how someone opts in, sample texts, and links to your privacy policy and terms.
Then the campaign is vetted by hand. Twilio’s help center says vetting currently takes up to 5 business days for standard use cases. On Twilio, each campaign is charged a $15 vetting fee that isn’t refunded if it’s rejected, and resubmitting can cost again.
Our timeline
For AIOS Coach, it went fast. On September 18, 2026 we bought the number and got the website ready for review: a text opt-in in the homepage chat, no other phone fields on that page, SMS sections in our privacy policy and terms, and our legal name, address, email and phone in the footer. We submitted the brand that afternoon. It was approved that evening, and the campaign went in automatically.
That night we built the text-back workflow and left it as a draft on purpose. Until the campaign was approved, any text it tried to send would fail quietly, and a feature that silently does nothing is worse than one that’s switched off. The campaign was approved on September 19. We published the workflow that day and sent a test text, which was delivered.
It doesn’t always go that smoothly. My other business, an insurance agency, had its campaign rejected three times before the fourth submission was approved. The first rejection said reviewers couldn’t verify how people opt in (Twilio error 30909). The next two were about the terms (error 30882), which Twilio uses when terms suggest opt-in data is shared with third parties or consent isn’t specific to the campaign. What finally passed: two separate consent checkboxes on the contact form (one for service texts, one for marketing), a plain statement in the privacy policy and terms that mobile numbers and opt-in data aren’t shared with third parties for marketing, and privacy and terms links in the footer of every page.
What this means for a small business
- Plan for days, not minutes. Register before you need texting, not the week you launch an ad.
- Don’t switch the text-back on until the campaign is approved. Build it, test everything else, then publish.
- Get your website reviewable first: a privacy policy, terms with an SMS section, your legal business details and a clear way to opt in.
- If you’re rejected, read the error code before you resubmit. Each code points at a specific fix.
Step 2: Write it like a reply, not an ad
CTIA sorts business texts into three kinds, and each one expects a different level of consent:
| Type | What it is | Consent CTIA expects |
|---|---|---|
| Conversational | The customer texts first and the business answers with relevant information | Implied: no extra permission expected |
| Informational | The customer gives their number and asks to be contacted, like appointment reminders | Express consent, given by text, on a form, on a website or verbally |
| Promotional | A sales or marketing message | Express written consent, such as a checked box online |
CTIA also warns that adding a call-to-action like a coupon code can turn an informational text into a promotional one. A missed call is a phone call rather than a text, so it doesn’t fit neatly into CTIA’s examples. We keep ours on the careful side: one reply about the call they just made, with no offer, no discount and no pitch. Anything you send after that, such as follow-ups, offers or newsletters, needs the consent that matches it.
A few more rules from the same guidelines apply to every text:
- Say who you are. The business name belongs in the message itself.
- Keep links honest. CTIA says links shouldn’t hide who sent them, and asks senders who shorten links to use a shortener dedicated to their own business.
- Never text a list you bought, rented or borrowed. CTIA says senders should build and vet their own opt-in lists.
Step 3: Make STOP work, every time
Every text should say how to opt out, and the opt-out has to actually work. Here is what the sources say:
- CTIA: say in the message how to opt out, using standard “STOP” wording, and also act on plain requests such as stop, end, unsubscribe, cancel, quit or “please opt me out”, whatever the capitals or punctuation. Send one final confirmation, then nothing else.
- FCC: under its 2024 consent rules, a reply of “stop,” “quit,” “end,” “revoke,” “opt out,” “cancel” or “unsubscribe” is a valid way to revoke consent to automated texts. The request has to be honored within a reasonable time, no later than 10 business days, and one confirmation text is allowed as long as it has no marketing in it.
The FCC took up changes to its revocation rules at its September 30, 2026 meeting, so check the current version before you build anything around the fine print. Honoring STOP right away, with one plain confirmation, fits both CTIA’s guidelines and the FCC’s 2024 rules. HighLevel’s help page notes that contacts’ communication preferences and Do Not Disturb settings are still respected by its missed-call text.
The mistake we made: two texts for one missed call
On September 20, a little after 10:30 at night, we tested our own line. The call went to voicemail, because of a separate setup problem with our AI receptionist that we fixed within the hour. Our workflow’s text went out 43 seconds later, exactly as designed. Then, about two minutes after that, a second text arrived from the phone system’s built-in missed-call text-back setting, which we had never turned off. Two texts for one call, and the second one had no opt-out line.
We turned the built-in setting off that night, so only the workflow sends now, and every text it sends ends with “Reply STOP to opt out.” On September 29 we read the setting again to make sure it had stayed off. HighLevel’s own help page warns that the built-in feature sends a text for every missed call, even when the same caller tries several times in a short window, and suggests using a workflow instead.
What we took from it:
- Pick one source for the text-back. Check your phone settings and your automations, because either one can send it.
- Read the message log, not just the settings screen. The message history is how we saw the second text.
- Test with a real call from outside your own forwarding. Our line forwarded to the same cell we called from, so the test call had nowhere to ring and dropped to voicemail.
A text-back is a backstop, not the whole answer
The best missed call is the one that doesn’t happen. Since our AI receptionist went live on that line later the same night, every call to it has been answered, so the text-back hasn’t had to fire again. It stays switched on for the call that slips through anyway.
That’s how we set it up for clients too: the AI receptionist answers first, and missed call text back catches anything that gets past it, inside the lead funnels and CRM follow-up we build. If you also text customers for reviews, the same registration applies; our guide on how to ask customers for reviews covers the scripts.
Before you switch it on
- Your number is registered and the A2P campaign shows approved.
- Your website has a privacy policy and terms with an SMS section, plus your legal business details.
- Only one thing sends the text-back: the built-in setting or a workflow, not both.
- The text names your business, asks how you can help, offers one next step and says how to opt out.
- STOP and similar replies end all texts, with one plain confirmation at most.
- Someone on your team gets an alert and follows up.
- You’ve tested it with a real call and read the message log afterwards.
Want every call answered, or at least texted back?
AIOS Coach sets up the AI receptionist and the missed-call text-back in your CRM, handles the carrier registration, and runs it all for you.
Book a free auditCommon questions
What is missed call text back?
An automation that sends a text to anyone whose call to your business goes unanswered, from the same number they called, so they can reply by text instead of waiting for a callback.
Is missed call text back legal?
It is a common business practice, and it comes with rules. In the US the number must be registered for A2P 10DLC, the text should identify your business and say how to opt out, and opt-out requests must be honored. Promotional texts need express written consent under CTIA’s guidelines. This is general information, not legal advice.
Do I need A2P 10DLC registration for missed call text back?
Yes, if the text comes from a regular 10-digit US number. Twilio says unregistered messages from +1 10DLC numbers to US phones have been blocked since September 1, 2023. Registration covers your brand and a campaign that describes the messages you send.
How long does A2P 10DLC registration take?
Twilio’s help center says campaign vetting currently takes up to 5 business days for standard use cases. Ours was approved the day after we submitted the brand. An earlier campaign for another of our businesses needed four submissions.
What should a missed call text say?
Keep it to one short reply: who you are, an invitation to reply, one next step such as a booking link, and how to opt out. For example: “Sorry we missed your call! This is [Business]. How can we help? Reply STOP to opt out.”
Why did a caller get two texts after one missed call?
Usually because two things are sending it, such as the phone system’s built-in missed-call setting and a workflow. HighLevel’s help page warns that the built-in feature texts on every missed call, even repeat calls a few minutes apart. Turn one of them off.
Sources
- CTIA, Messaging Principles and Best Practices (May 2023): sections 4.1.2 (automation), 5.1 (consent types), 5.1.3 (opt-out), 5.1.4 (opt-in lists) and 5.3.2 (links).
- FCC, TCPA consent order, FCC 24-24 (February 2024), including 47 CFR 64.1200(a)(10) and (a)(12).
- FCC, fact sheet and draft order on consent revocation for the September 30, 2026 meeting.
- Twilio, US A2P 10DLC is now a fully verified route (September 1, 2023).
- Twilio Help Center, A2P 10DLC Campaign Vetting FAQ.
- Twilio error references 30909 and 30882.
- HighLevel Help Center, Where and how to configure the Missed Call Text Back feature.
General information only. This is not legal advice. The sources above were read on October 2, 2026. Carrier requirements and the FCC’s rules change, so check the current versions, or ask a lawyer, before you build a texting program around them.