By Alpit Patel and the aibrevo team · October 13, 2026 · 7 min read
GoHighLevel Missed Call Text Back: Setup Guide With Wording
Turn on GoHighLevel missed call text back in Settings, Phone System, Voice, then Voicemail and Missed Call Text Back. You need an LC Phone number that can send SMS, a message that acknowledges the call without marketing, and a test from a phone that is not saved as a contact.
Part of the guide: GoHighLevel automation
Key takeaways
- The native setting lives at Settings, Phone System, Voice, then Voicemail and Missed Call Text Back, per HighLevel's help article (modified September 7, 2026): tick the box, open Customize, write the message, send a test, save.
- It needs the LC Phone system and an SMS-capable sending number: A2P 10DLC registration for local numbers or toll-free verification for toll-free ones. Without that, the text fails and the reason is logged in the conversation.
- Write the message as an acknowledgement of a call the person placed: who you are, that you missed them, how to reply. Leave out discounts and offers, which move it toward marketing text that needs documented written consent.
- The native toggle texts on every missed call and cannot filter repeat callers or staff. Use a Call Details workflow when you need conditions, and run only one of the two on a number.
- Test from a phone that is not a saved contact and not on Do Not Disturb, then read the conversation thread. A test phone that once replied STOP will fail silently every time.
How do I set up missed call text back in GoHighLevel?
Open Settings, then Phone System, then Voice, then Voicemail and Missed Call Text Back, and tick the box. HighLevel’s setup article (modified September 7, 2026) gives these steps, checked on 2026-10-13:
Native setup, eight steps
- In your sub-account, click Settings at the bottom left.
- Open Phone System, then Voice in the top navigation.
- Open Voicemail & Missed Call Text Back, then Missed Call Text Back in the side panel.
- Tick the box to enable the feature, then click Customize.
- In the pop-up, type your message in Enter message.
- Use the custom value tag icon to insert placeholders.
- Below the editor, choose a number and send a test message.
- Click Save.
Menu labels shift between releases. If yours differ, search Phone System for ‘Missed Call Text Back’ rather than assuming the feature is gone. This page covers the build; the missed call text back not working guide covers diagnosis when it stays silent.
What do you need in place before it will send?
You need an SMS-capable sending number that is registered, plus a call that actually reaches LC Phone as missed. HighLevel’s article names the LC Phone system and at least one SMS-capable number as requirements, with A2P 10DLC registration for local numbers and toll-free verification for toll-free numbers. Texts also count toward your phone messaging usage limits.
| Requirement | Why | If missing |
|---|---|---|
| Number on LC Phone | The call must land in HighLevel as a call | A cell or carrier voicemail answers first and the call counts as answered |
| Registered SMS number | Carriers filter unregistered business texts | No text; the failed attempt and reason show in the contact’s conversation |
| Feature ticked | The toggle is off by default | Nothing sends |
| Contact not on DND | HighLevel respects Do Not Disturb and communication preferences | Silent for that contact only |
If registration is the blocker, start with the A2P 10DLC rejection guide. Call routing mistakes, such as forwarding to a cell phone, are in the not-working guide.
What should the missed call text say?
Acknowledge the call, name the business and give one easy next step. The caller started the contact, so a helpful reply is the lower-risk end of the consent spectrum, but it is not a safe harbor. HighLevel’s article suggests including the contact or business name; it also notes the contact-name placeholder only fills in if the system already recognizes the caller from a prior interaction, so write a message that reads fine without it.
Reference wording, using custom values for the business details:
Hi, this is {{custom_values.business_name}}. Sorry we missed your call.
Reply here with what you need, or book a time: {{custom_values.booking_link}}| Do | Do not |
|---|---|
| Name the business so the number is recognized | Quote prices or discounts |
| Say you missed the call and invite a reply | Include health, legal or case details |
| Offer one link or one question | Send three links and a paragraph |
| Keep it to one SMS segment where you can | Promise a callback time you cannot meet |
| Add opt-out wording if your compliance advisor recommends it | Add an offer to ‘make the missed call worth it’ |
Storing the business name and booking link as custom values means one edit fixes every message, and a deployed snapshot will not text customers with someone else’s number. The rules behind the ‘no promotions’ advice are in the compliance guide: marketing text needs documented written consent, opt-outs must be honored, and content rules vary by carrier. This is general information, not legal advice.
Which number will the text come from?
Usually the number the customer called, but not always. HighLevel documents a priority order: the called number if it can send SMS; then a number that has successfully messaged this contact before; then your default outbound number; then another eligible messaging number in the location. If no eligible number exists, the failed attempt and its reason appear in the contact’s conversation.
If customers see an unfamiliar number, that is documented behavior, not a fault. Make the message name the business so it still makes sense.
When should you use a workflow instead of the toggle?
Use a workflow when you need to exclude staff, avoid texting repeat callers, branch by time of day or follow up. The native toggle texts on every missed call, including repeat attempts, and the help article does not describe a hours setting.
| Need | Native toggle | Call Details workflow |
|---|---|---|
| Live in minutes | Yes | Slower to build |
| Skip staff and vendors | No | Yes, with tags or filters |
| Different after-hours message | Not described | Yes, with a time-based branch |
| Follow-up if no reply | No | Yes, with a wait and reply check |
| Per-caller cooldown | No | Yes, with conditions |
The workflow build: trigger Call Details, filtered to incoming calls and the not-answered outcomes you want, per HighLevel’s Call Details trigger article (modified July 24, 2026). Add a condition that skips contacts tagged Staff or Vendor, send the SMS, then Add Task and Send Internal Notification so a person follows up. Add a Wait for the contact to reply with a timeout, and at most one gentle follow-up.
Two cautions. HighLevel says the trigger activates for each status change, so add conditions or a cooldown to prevent repeats. And never leave the native toggle on for the same number, or one call can produce two texts. For the broader pattern, see GoHighLevel workflow examples and triggers versus workflows.
How do you test it before real customers call?
Call from a phone that is not a saved contact, let it ring past the timeout and read the conversation thread. Run the test four ways, because each fails differently.
- Use a spare mobile that is not saved in the account and is not on Do Not Disturb.
- Call the public number and do not answer. Note the time.
- Wait for the timeout plus a minute. Watch the phone.
- Open the new contact in Conversations. Confirm a call entry exists and read any failed-send reason.
- Repeat with a saved contact, a contact on DND, a second call within minutes, and a call after hours.
- If you built a workflow, open its Enrollment History and execution log for the test contact.
A test phone that once replied STOP is suppressed by design and will fail every later test, which looks like a bug. Use a fresh number. The full seven-hop trace is in the not-working guide.
What does it cost to run?
Each text is a billable SMS segment, so cost scales with missed calls, not with the feature. Carrier fees are charged per segment, and HighLevel changed carrier fee pricing on October 1, 2026; check its phone pricing article for the current figures rather than a number copied from a blog. The arithmetic for a business is simple: missed calls per month times segments per text times the current per-segment rate. A one-segment text sent 200 times a month is 200 segments. Multiply by the rate shown in your account and compare with the value of one recovered job.
What should you check next?
The setup is one afternoon; keeping it working is the habit. Confirm the registration stays approved, re-run the test after any change to forwarding, numbers or workflows, and read the failed-send reasons weekly at first. Missed call text back is one layer of GoHighLevel automation; the same lead should also reach a new lead follow-up workflow and, once they book, the appointment reminder workflow. To have the phone, registration and workflow built and tested, see GoHighLevel implementation services.
Sources
- HighLevel Support, Where and how to configure the Missed Call Text Back feature, modified September 7, 2026. Supports menu path, requirements, sender priority, merge fields and test option. Checked 2026-10-13.
- HighLevel Support, Workflow trigger: Call Details, modified July 24, 2026. Supports the workflow alternative and status list. Checked 2026-10-13.
- HighLevel Support, Workflow settings overview, modified October 12, 2026. Supports Stop on Response and Time Window. Checked 2026-10-13.
- Legal Information Institute, 47 CFR 64.1200. Consent and opt-out rules referenced in general terms. Checked 2026-10-13.
- Not verified: per-segment SMS rate and the October 1, 2026 carrier fee change are described in aibrevo’s existing not-working guide, which cites HighLevel’s phone pricing articles; recheck before quoting.