- It lives under Settings, Phone System, Voice now, not Business Profile. Older guides point at the wrong screen.
- It fires on every unanswered call that outlasts your inbound call timeout, day or night, repeat callers included. Set the timeout to 10 to 20 seconds.
- The text needs an A2P-registered number. GoHighLevel now picks an eligible number for you, and failed attempts show up in Conversations with a reason.
- A caller who rang you gave you permission to reply. Keep the text a reply, not a promotion, and honor STOP right away, and never later than ten business days.
- Build a workflow instead of the built-in toggle only when you need different messages by hour or by contact, and never run both.
What does missed call text back do in GoHighLevel, and when does it fire?
Missed call text back sends an automatic SMS to anyone whose inbound call goes unanswered. Your caller gets an acknowledgment within seconds, and the conversation moves to text while your team is busy, which is why response time decides who wins the customer. GoHighLevel's setup article, updated 7 September 2026, is precise about when it fires. Any unanswered call that runs past your inbound call timeout triggers it. Answered calls don't.
Three details in that article change how you configure it. It fires regardless of business hours and regardless of whether the caller is already a contact. It fires on every missed call, so a caller who tries three times gets three texts. And it respects Do Not Disturb and the contact's communication preferences, so a person who opted out stays opted out.
Merge fields such as the contact's first name only fill in when GoHighLevel already knows the number. A first-time caller gets the field blank, which is why the templates below don't lean on it.
| Situation | Does it text? | Why |
|---|---|---|
| Call rings past the timeout, nobody answers | Yes | That's the trigger |
| Caller hangs up before the timeout | No | The call never became a missed call |
| Same caller misses you twice | Yes, twice | One text per missed call |
| Caller is on DND or opted out | No | Contact preferences win |
| After hours, weekend, holiday | Yes | It ignores business hours |
| Number can't send SMS or isn't A2P-registered | Attempt fails | See the next two sections |
GoHighLevel, Where and how to configure the Missed Call Text Back feature (official docs, updated 7 Sep 2026).
GoHighLevel missed call text back setup: the five-minute version
In the sub-account, open Settings, then Phone System, then the Voice tab, then Voicemail and Missed Call Text Back. Older guides, including GoHighLevel's own March 2023 post, send you to Business Profile. The setting moved. If you're staring at Business Profile wondering where it went, that's why.
- 01Turn the toggle on and write the message. Name the business in the first line, ask one question, and end with the opt-out line. Templates are below.
- 02Set the inbound call timeout on the number under Settings, Phone Numbers. GoHighLevel recommends 10 to 20 seconds for missed call text back. Longer than that and impatient callers hang up before the call counts as missed.
- 03Turn on Call Connect for numbers that forward to a cell phone. The whisper prompt (press a key to accept) stops a cell's voicemail from answering the call, which would mark it as completed and skip the text.
- 04Send a test from the field under the toggle. GoHighLevel texts the number you enter with the exact message, from the number it would really use.
- 05Check the sending number. The text goes from the called number if it can send SMS. Otherwise GoHighLevel tries a number that has messaged the contact before, then the default outbound number, then any eligible number in the location. That's the order GoHighLevel documents, and it means the reply can arrive from a different number than the one the customer dialed.
Why isn't my missed call text sending?
Four causes cover almost every case, and GoHighLevel now tells you which one it was. Since the number-selection change, a failed attempt appears in Conversations with a reason instead of vanishing.
- The number can't send SMS. Call tracking numbers, number pools and unverified toll-free numbers are built to receive calls, not send texts. GoHighLevel now routes the text through an eligible number instead, but only if the location has one.
- The number isn't A2P-registered. A local number needs an approved A2P 10DLC campaign and a toll-free number needs toll-free verification, or the attempt fails. Our A2P registration guide covers the fees, the 10-to-15-day wait and every rejection code.
- The contact is on DND or opted out. The feature respects both. Check the contact record before you check the settings.
- The call never counted as missed. A forward to a cell phone whose voicemail picked up is a completed call. A caller who hung up at eight seconds against a 30-second timeout never crossed the line. Call Connect fixes the first; a 10-to-20-second timeout fixes the second.
If the toggle is on, the wallet has funds and none of the four apply, open the Conversations view for the contact. The failed attempt and its reason are there.
Read the reason before you touch a setting. Everything else is guessing.
Which call settings decide whether a call counts as missed?
Missed call text back is only as good as the timeout and forwarding settings on the number, and those live on a different screen. GoHighLevel's phone number configuration guide, updated 1 September 2026, gives the values. Inbound call timeout is how long the system lets a call ring before dropping it or sending it to voicemail. Set it for the text, not for the voicemail.
| Setting | Where | Set it to | Why it matters here |
|---|---|---|---|
| Inbound call timeout | Settings, Phone Numbers, the number | 10 to 20 seconds | The call has to outlast it to count as missed |
| Call Connect (whisper) | Same screen | On, when forwarding to a cell | Stops a cell's voicemail from marking the call completed |
| Forwarding | Same screen | External number or ring multiple team members | Decides who gets the chance to answer first |
| Voicemail routing | Same screen | Around 20 seconds for a short ring then CRM voicemail; 60 or blank to reach a personal cell voicemail | Voicemail and the text can both run; the text still fires on the missed call |
GoHighLevel, Overview of phone number configuration options (official docs, updated 1 Sep 2026); timeout recommendation from the missed call text back article (7 Sep 2026).
Missed call text back templates that pass carrier review
Missed call text back (MCTB) templates have three jobs in under 160 characters: say who you are, invite a reply, and give a way out. Those are also the three things carrier reviewers look for in your registered sample messages, so write the real message the same way. GoHighLevel's own example, in its after-hours lead article, reads "Hi! Thanks for calling [Your Med Spa Name]. We missed your call but would love to help. Are you looking to book a service?" Ours keep the question, name the business in the first line, and add the opt-out.
| Use | Template |
|---|---|
| Default, any hour | Hi, this is the team at [Business]. Sorry we missed your call. What can we help with? Reply here and a real person will answer. Reply STOP to opt out. |
| Book instead of call back | [Business] here, sorry we missed you. Grab a time that suits you: [full booking link]. Or reply and we'll call you back. Reply STOP to opt out. |
| After hours | Thanks for calling [Business]. We're closed until [time] but we read texts. Tell us what you need and we'll reply first thing. Reply STOP to opt out. |
| Existing customer (contact known) | Hi {{contact.first_name}}, it's [Business]. We missed your call. Reply here and we'll sort it out. Reply STOP to opt out. |
Webly Studio templates. Booking links must be full HTTPS URLs; carriers reject shorteners such as bit.ly under rejection code 30892, which our A2P registration guide walks through. A real business name plus a full booking URL pushes the second template past 160 characters, so expect it to send as two segments.
Two rules keep these deliverable. No link shorteners, ever, because carriers filter them and the A2P reviewers reject them. And keep promotion out of the text entirely. A missed-call reply is a conversation the caller started. Once it advertises an offer it becomes a promotional message, which needs a different kind of consent, covered next.
Is texting back a missed call TCPA-compliant?
A reply to someone who just called you is close to the safest category the carriers define, but it isn't a perfect fit, and the gap matters. The industry's own rulebook, the CTIA Messaging Principles and Best Practices (May 2023), sorts business texts into three types. Conversational messaging is a back-and-forth the consumer starts, and when the business simply responds, no additional permission is expected. Informational messages, such as appointment reminders, need express consent. Promotional messages need express written consent. One wrinkle: CTIA writes the conversational category around a consumer who texts first. A missed-call text is the business sending the first message, in reply to a call. That gap is the reason to keep the text a plain acknowledgment and nothing more. Federal rules run alongside that. The TCPA treats texts like calls. The FCC's February 2024 order says consumers can revoke consent by any reasonable means. Seven words count automatically: stop, quit, end, revoke, opt out, cancel and unsubscribe. Senders must honor a revocation within a reasonable time, and no later than ten business days. One confirmation text is allowed if it carries no marketing, and sending it within five minutes keeps it inside the caller's existing consent.
So the practical line is short. Text back what the caller would expect from the business they just rang, honor STOP without argument, and keep offers out of it. If your missed-call text is going to carry a promotion, get written consent first. None of this is legal advice, and a texting program that matters to your revenue is worth an hour with a lawyer who does TCPA work.
| Message type (CTIA) | Who starts it | Consent expected | A missed-call text is this when |
|---|---|---|---|
| Conversational | The consumer (CTIA writes this as the consumer texting first) | Implied; none beyond the exchange the consumer started | It acknowledges the call and invites a reply, nothing more |
| Informational | The business, at the consumer's request | Express consent | It includes a reminder or alert they asked for |
| Promotional | The business | Express written consent | It pitches an offer, discount or product |
CTIA Messaging Principles and Best Practices, Exhibit II (May 2023).
When should you build a workflow instead of using the built-in GoHighLevel missed call text back?
Use the toggle until it can't do what you need. Build a workflow when you want different messages by time of day or for existing contacts. Also when you want a follow-up sequence after the first text, or a task for the team. Your trigger is Call Details, filtered to incoming calls with a status of busy or not answered. Then add the actions.
- 01Trigger: Call Details. Direction incoming, status is busy or not answered. Leave voicemail out unless you also want to text people who left one.
- 02If/Else on business hours. Inside hours, the short default text. Outside hours, the after-hours text with when you reopen.
- 03If/Else on the contact. Known contact with a name gets the personal version. Unknown caller gets the default, since {{contact.first_name}} would be blank.
- 04Send SMS, using the Send SMS action. Same template rules: business name, one question, STOP line, full links only.
- 05Wait 15 minutes, then check. If there's no reply, create a task for the team and add the tag missed-call so the contact shows up in a smart list.
- 06Turn the built-in toggle off. Two systems watching the same missed call send two texts. Pick one.
How we set this up for clients
Order matters more than the message. This is the sequence we run on every client sub-account, because each step depends on the one before it.
- A2P registration first, before any texting. Nothing below works until the campaign shows Verified, and that's a 10-to-15-day wait right now.
- One SMS-capable, registered number as the default outbound.
- Inbound timeout at 15 seconds, Call Connect on for every forward to a cell, CRM voicemail after the text so the caller has both.
- The default template above with the client's real booking link, tested from the settings screen to a team member's phone, with a STOP reply tested too.
- The built-in toggle for the first month, then a workflow only if the client wants hour-based messages or a follow-up sequence, with the toggle switched off. And a weekly look at Conversations for failed attempts, because a reason that keeps appearing is a settings problem, not a message problem.
If you'd rather have it done, this is part of our GoHighLevel setup work. The complete GoHighLevel setup guide shows where missed call text back sits in the first thirty days.
- HighLevel — Where and how to configure the Missed Call Text Back feature (official docs, updated 7 Sep 2026)
- HighLevel changelog — More reliable Missed Call Text Back with smarter number selection (undated)
- HighLevel — Overview of phone number configuration options (official docs, updated 1 Sep 2026)
- HighLevel — Call tracking and Missed Call Text Back through Google Business Profile (official docs, updated 24 Feb 2026)
- HighLevel — Never miss a lead again, even after hours (official docs, updated 25 Apr 2025)
- HighLevel — Workflow trigger: Call Details (official docs, updated 24 Jul 2026)
- HighLevel — Workflow action: Send SMS (official docs, updated 31 Aug 2026)
- HighLevel — Understanding A2P campaign rejection reasons and required fixes, code 30892 URL shorteners (official docs, updated 9 Sep 2026)
- HighLevel blog — Quick easy wins with HighLevel Missed Call Text Back (30 Mar 2023; the pre-2026 Business Profile instructions)
- CTIA — Messaging Principles and Best Practices, Exhibit II: message types and consent (May 2023, PDF)
- FCC — Report and Order FCC 24-24, revocation of consent by any reasonable means, ten business days, one confirmation text (adopted 15 Feb 2024, PDF)

Samar runs Webly Studio, the agency behind the paid ads, web builds, and AI systems featured on this blog. See the team's client work and results.





