GoHighLevel Missed Call Text Back: Setup & Why It Fails

myNumberrs · July 2026 · 7 min read

What is Missed Call Text Back, and why does everyone use it?

Small businesses miss calls constantly. You are on a ladder, in a crawl space, with a customer, or it is 7pm. Most callers will not leave a voicemail — they hang up and dial the next business on the list. MCTB catches that moment. The caller gets a text before they have finished dialling your competitor, and the conversation carries on in writing, on their schedule and yours.

The reply lands in GoHighLevel Conversations against the caller's contact record, so you answer it from the same screen you do everything else on. No staff needed, no receptionist, no answering service. It is the cheapest lead-rescue mechanism in the business, which is why it is usually the first automation anyone builds in GoHighLevel.

How MCTB actually works under the hood

MCTB is event-driven. The mechanics matter, because they explain every failure mode.

1. A call comes in to a number GoHighLevel is handling.
2. GoHighLevel tries to connect it — usually by forwarding to your phone.
3. Nobody answers, or the call is declined, before the ring timeout runs out.
4. GoHighLevel marks the call as missed and raises a missed-call event.
5. Your MCTB automation listens for that event and sends your message through whatever texts on the sub-account.

Two things fall out of this. First, GoHighLevel can only raise a missed-call event for a call it handled. If the call never touches GoHighLevel, there is no event, and no automation on earth can trigger on an event that never fired. Second, the text itself goes out through your SMS setup — so if texting on the sub-account is broken or unconfigured, MCTB is broken too, even when the event fires perfectly.

Setting it up: the basics

There are two ways to run MCTB, and both are quick.

• The built-in toggle. In your sub-account settings, enable Missed Call Text Back and write your message. Keep it short and human — name the business, apologise for missing them, ask one question. "Hi, it's Dave from Morales Plumbing — sorry we missed your call. What's the job?" beats anything that reads like a robot.
• A workflow. For more control, build it in Workflows using a call-status trigger. That lets you add a short delay, send different messages inside and outside business hours, or skip contacts you are already talking to.

Then test it properly. Ring your business number from a phone that is not saved in the system, let it ring out, and watch Conversations. If the text arrives, you are done. If it does not, keep reading — the next section is almost certainly your problem.

Why your MCTB isn't firing: the forwarding trap

Here is the trap. Plenty of setups route calls straight from the published number to a cell phone — carrier-level forwarding, SIM-based texting services where voice rides the SIM, or an SMS provider that forwards calls directly to your handset. The phone rings, so everything feels fine. But the call never passed through GoHighLevel. The CRM has no idea it happened.

That means no call record, no missed-call event, and no text back. And because nothing errored, it is miserable to diagnose. The toggle is on. The message is written. The workflow is published. Everything looks configured correctly, and MCTB still does nothing, because from GoHighLevel's point of view there was never a call to miss.

The two-minute check: miss a test call on purpose, then open the caller's contact record in GoHighLevel and look at the activity. If there is no call logged, GoHighLevel never saw the call. Stop adjusting message templates and workflow triggers — the problem is routing, and only routing will fix it.

Once routing is confirmed good, a few smaller culprits are worth a look:

• Voicemail answered the call. If the call forwards to your cell and your cell's voicemail picks up, the call counts as answered — not missed — so nothing fires. Set GoHighLevel's ring timeout shorter than your carrier voicemail's.
• Texting is not working on the sub-account. The event fired, but the message had no working way out. Send yourself a normal test text to rule this out.
• The contact is on DND. GoHighLevel will not text a contact marked do-not-disturb, no matter what triggered it.

The fix: route calls through a GoHighLevel number

The fix is to put GoHighLevel back in the path of the call. Inbound calls should hit a GoHighLevel number first, and GoHighLevel then forwards them to the phone you actually answer. Now the CRM is handling the call, so when it goes unanswered, the missed-call event fires and MCTB does its job.

One piece of admin stands in the way: GoHighLevel requires a one-time identity check before it will carry voice for you. It is a once-and-done step on their side, not a recurring chore. Once you are through it and calls flow through a GoHighLevel number, you get the full package — MCTB fires as normal, every call is logged against the contact, and call reporting and call-based workflows all work.

The call path looks like this: caller dials your number, the call routes through GoHighLevel, GoHighLevel rings your cell, and if you do not answer, the event fires and the caller gets your text. Same phone in your pocket, same behaviour from the caller's side — the only difference is that your CRM now knows what happened.

When direct-to-cell forwarding is still the right choice

Honest answer: not everyone should route through GoHighLevel.

Forwarding straight to your cell is the fastest possible setup. There is no identity check, nothing to configure on GoHighLevel's side, and it can be working in minutes. If you are a solo operator who answers nearly every call, does not use call automations, and mostly wants a business number that rings the phone already in your pocket, direct-to-cell is simpler and there is genuinely less to go wrong.

The trade is total: GoHighLevel never sees your calls, so no MCTB, no call logging, no call reporting, no call-triggered workflows. For some businesses that is a fair swap for zero setup friction. The mistake is not choosing direct-to-cell — it is choosing it by accident and then wondering for three weeks why MCTB is broken. Make it a decision, not a default.

Where myNumberrs fits

We run myNumberrs — managed phone numbers for GoHighLevel sub-accounts. We buy the number, install it as the SMS conversation provider on your sub-account, hand it over working, and monitor it around the clock. Texts and picture messages work both ways in Conversations, with no A2P registration and no per-message billing.

Calling is included, and we support both routes described in this post — because the difference is exactly what this article is about. Route inbound calls through a GoHighLevel number (their one-time identity check applies) and MCTB, call logging, and workflows all keep working. Or forward straight to your cell — fastest to set up, but GoHighLevel never sees the call, so MCTB and call logging do not work. We tell you that up front rather than let you find out from a silent automation.

Worth noting: MCTB traffic is the healthiest kind of texting there is — you are replying to someone who just called you. On our numbers, conversations with people who contact you first are unlimited. Cold outreach to strangers is deliberately capped, because carrier filtering kills numbers that blast, and a filtered number cannot text anyone back.

Pricing starts at $19/month for a single number, with agency rates of $15/number at 5+ and $12/number at 15+, and one agency-level install covers all sub-accounts. Two hours of calling per month are free, then $1/hour bought in five-hour blocks. Prices checked July 2026 and can change — current rates are at mynumberrs.com/#pricing.

Quick answers