How to Set Up Missed Call Text Back on GoHighLevel (Step by Step)

GoHighLevel’s Missed Call Text Back (MCTB) is a native feature: when an inbound call to your HighLevel phone number goes unanswered, the platform texts the caller automatically. It takes about five clicks to switch on, and about five minutes to configure correctly.

This is the task-completion guide — the official setup path, the voicemail interaction people miss, the duplicate-text problem nobody warns you about, and what to do if it silently stops working.

Quick answer

In your sub-account: Settings → Phone System → Voice → Voicemail & Missed Call Text Back → Missed Call Text Back → check Enable → Customize → write your message → send a test → Save. Two prerequisites matter more than the click path: the phone number must live inside GoHighLevel, and US business texting requires A2P 10DLC registration — unregistered numbers can fail silently.

Before you start: three prerequisites

1. A phone number inside the sub-account. MCTB operating on a number is what makes the feature work — the platform has to see the call event. In practice you either provision a new HighLevel (LC Phone) number, port your existing business number in, or set up call forwarding from your carrier number to a HighLevel number. Whatever you choose determines what the caller sees.

2. A2P 10DLC registration. US carriers require business texting to be registered. If your brand and campaign are not approved, your auto-text can fail without a loud error. Do this first, before you test and assume the feature is broken.

3. A decided message and an owner. Someone has to write the text and watch the replies. An automatic message creates an expectation of a human follow-up.

The official setup steps

Step 1 — Open Settings

In your sub-account, click Settings in the bottom-left corner.

Step 2 — Navigate to Missed Call Text Back

• In the left-side menu, click Phone System
• In the top navigation, click Voice
• Under Voice, open Voicemail & Missed Call Text Back
• In the side panel, click Missed Call Text Back

Step 3 — Enable the feature

Select the checkbox to Enable Missed Call Text Back, then click Customize.

Step 4 — Customize the message

The Customize button opens a pop-up with an Enter message field. Write the text that goes out when a call is missed. You can insert dynamic placeholders (custom value tags) such as the contact’s name — with a caveat worth knowing: those placeholders only work if the system already recognizes the contact from a prior interaction. For a first-time caller, the tag resolves to nothing useful, so do not build the message around it.

A message that works for a service business:

Hi, this is [Business]. Sorry we missed your call. What can we help with? Reply with what you need and your address, and we will get back to you as soon as we can.

Step 5 — Send a test, then save

Below the message editor there is a field to send a test message. Choose a number you control, preview exactly what the customer will see, then click Save.

Configure voicemail alongside it

MCTB interacts with your voicemail settings, and both live in the same panel.

Incoming call timeout. A slider controls how long the phone rings before the missed-call text fires. Ten to twenty seconds is the commonly recommended range — long enough that you have a real chance to answer, short enough that the caller has not already dialed someone else.

Custom voicemail greeting. Optional, and worth doing. You can upload a pre-recorded file (mp3, wav, or similar) to replace the generic carrier greeting. A caller who hears your business name and a human voice is less likely to hang up before the text arrives.

Decide how the two work together. Some operators turn voicemail off entirely and rely on the text. Others keep both: the text starts the conversation, voicemail catches the detail-oriented caller. Either is defensible — the failure mode is having neither configured deliberately.

The duplicate-text problem

This is the detail that catches people out, and GoHighLevel documents it plainly:

Missed Call Text Back triggers an SMS for every missed call — even if the same caller tries multiple times within a brief window.

A customer who calls twice because the first ring felt short gets two identical texts. That reads like a broken robot, and on a platform plan you are also paying for each message.

The fix GoHighLevel recommends: build the behavior in Workflows instead of relying on the raw toggle, and add logic to spread it out — for example a wait step of around 20 minutes, or a filter using tags such as 1st call / 2nd call so repeat attempts inside the window do not fire a second message.

If you are setting this up for one business, that workflow is a small amount of extra work for a noticeably less robotic experience. If you are an agency setting it up per client, it is worth doing as standard.

What the feature does and does not do

From GoHighLevel’s own FAQ:

• Messaging limits apply. MCTB messages count toward your phone messaging usage. It is not a free channel inside the plan.
• It sends from your default number. The message uses the sub-account’s default number, which is why “which number does the customer see” depends entirely on which number you put in the platform.
• After-hours is supported. The feature is specifically useful for after-hours calls, because it acknowledges the caller without a live person.
• WhatsApp is separate. This feature is SMS-based. Messaging missed callers over WhatsApp uses a different feature (Missed Call WhatsApp Back).
• Repeat callers are not deduplicated by default — see the section above.

Keeping your existing business number

The most common owner-operator question. You have three paths, and they are not equal:

Port your number in. The number moves to GoHighLevel and becomes the carrier of record. Callers keep dialing the same digits, but the line now depends on the platform, and leaving means porting back out.

Conditional call forwarding. Your number stays with your carrier and unanswered calls forward to a HighLevel number. Common agency practice. The trade-offs: the text may come from the HighLevel number rather than the one the customer dialed, the forwarding rule can be disabled by carrier changes or phone resets, and some setups compete with your carrier voicemail.

Run the auto-text somewhere else entirely. An on-device Android app detects the missed call on your own phone and replies from your SIM, with no number change and no forwarding rule. Different trade-offs: no platform, but the automation depends on that phone being on and connected.

If keeping your existing number without adding a forwarding dependency is the priority, see our full comparison of the three approaches.

Troubleshooting: when no text goes out

Work through these in order — the first one is the most common cause and the hardest to see.

1. A2P 10DLC registration. If the brand or campaign is not approved, messages can fail quietly. Check registration status before debugging anything else.
2. Is the call actually hitting the HighLevel number? If you are using forwarding, test the forwarding rule itself. A forwarding rule that broke weeks ago produces silence, not an error.
3. Does the caller reach voicemail before the timeout fires? Adjust the ring timeout so the missed-call event triggers where you expect.
4. Messaging limits or wallet balance. MCTB messages consume usage; an exhausted balance stops the texts.
5. Is the number in the right sub-account? In an agency account, features and numbers live under a specific sub-account.
6. Duplicate suppression working too well? If you built a workflow with tags, confirm the first-call branch is still firing.

Who should not use this setup

GoHighLevel’s MCTB is the right answer if you already run your business inside GoHighLevel, or you are an agency managing client phone systems on the platform. You get the feature inside a system you are paying for anyway.

It is the wrong answer if you are a solo operator who wants one behavior — text back the calls I miss — and nothing else. In that case you would be taking on a platform subscription ($97 to $497 per month plus usage, as published on their pricing page in September 2026), a phone number decision, an A2P registration, and a workflow build to solve a single problem. Our comparison of the three routes covers that decision in detail, and the SMS autoresponder pillar explains which type of responder fits which business.

SnapBack is the on-device option in that comparison: an Android app that sends the missed-call text from the phone and SIM you already carry, with no number move and no registration project.

FAQ

Conclusion

The click path is short: Settings, Phone System, Voice, Voicemail & Missed Call Text Back, enable, customize, test, save. The parts that decide whether it actually works are the prerequisites and the edge cases — a registered A2P campaign, a number the platform can see, a ring timeout that fires where you expect, and duplicate suppression so a caller who rings twice does not get two identical texts.

If you are already inside GoHighLevel, build it properly and use a workflow rather than the raw toggle. If you are considering the platform only for this feature, price the whole thing — subscription, number, registration, and your time — against a simpler on-device route that leaves your existing number alone.