How to Set Up GoHighLevel Missed Call Text Back

Most calls that go unanswered do not turn into a voicemail and a callback. They turn into the caller hanging up and calling the next business on the list. GoHighLevel missed call text back exists to close that gap: the moment a call goes unanswered, the caller gets a text instead of dead air, and the conversation stays open.

I set this up as one of the first automations on almost every GHL account I touch, because it costs nothing extra to run and the leads it recovers are ones that were about to be lost for good. This post covers how it actually works, how to set it up both ways GHL supports, how to write a message that gets replies, and how to connect it into a real follow-up sequence rather than leaving it as a single text that goes nowhere.

What Is Missed Call Text Back?

It is exactly what it sounds like. A call comes into your GHL-connected number, nobody answers it in time, and GHL automatically sends an SMS to that caller. The caller sees a normal text from your business number, replies land in your GHL Conversations inbox, and from there a human or a workflow can take over.

GHL actually gives you two ways to do this, and they are worth understanding as separate tools rather than one feature. There is a native toggle under location settings that requires no workflow at all, and there is a full Workflow built on a call trigger that gives you branching logic, tagging, and multi-step follow-up. I will cover both, because which one you want depends on how much control you need.

How the GHL Trigger Works

Under the hood, GHL listens for the call status on your tracked number. When a call rings through to voicemail, is not answered within the configured ring window, or the line is busy, that counts as missed. The native feature fires within seconds of that happening. The workflow-based approach uses a Call Status trigger you configure yourself, filtered to incoming calls with a status of no answer, busy, or cancelled.

One detail that catches people out: numbers forwarded in from an external carrier rather than provisioned directly through GHL do not always trigger the missed call event reliably. If you are forwarding an existing business line into GHL and missed call text back is not firing, that is usually the first thing to check.

Create the Workflow

If you want more control than the native toggle gives you, build it as a workflow. Go to Automation, then Workflows, then Create Workflow. Add a trigger of Call Status, filter it to Call Direction: Incoming, and set the call status filter to cover no answer, busy, and cancelled together so you catch every flavor of missed call.

From there add your first action: Send SMS. This is the message the caller receives seconds after the call drops. After that, add an internal notification action so a team member knows a call was missed and a text went out, and consider an If/Else branch that checks whether the caller replies within a set window, and if not, sends a gentler follow-up an hour later.

If you only need the single instant text with no branching, GHL's native Missed Call Text Back toggle under location settings does that in about two minutes with no workflow required. Do not run both the native toggle and a workflow-based trigger on the same number. I have seen accounts where both were active and callers got two texts for one missed call, which reads as sloppy rather than responsive.

Write a Natural SMS

The text needs to read like a person sent it, not a system. "We're sorry we missed your call. How can we help?" works better than anything that sounds automated or corporate. Keep it under roughly 160 characters so it sends as a single SMS segment rather than splitting.

Use GHL's custom values to pull in the caller's name if you have it on file, and consider a version tailored to your business type. A home services company benefits from a line about emergency requests. A clinic benefits from a line about same-day appointments. The generic version works fine as a default, but the specific version gets more replies.

Add Reply Handling

A text that goes out and never gets a follow-up plan is only half the automation. When the caller replies, that message lands in the GHL Conversations inbox as a normal SMS thread. From there you can either let a team member pick it up manually, or build a qualification sequence on top of it that asks a question or two before handing off, similar to the pattern in GoHighLevel SMS Automation.

If the caller does not reply within an hour or two, a second, softer follow-up text tends to recover a meaningful share of the ones who got distracted rather than lost interest.

Add Team Notifications

Set internal notifications to fire around the clock, not just during business hours. A missed call at nine at night still deserves a text back immediately, and your team still deserves to know about it, even if the callback itself waits until the next business day. What should not wait is the acknowledgement to the caller.

For businesses handling anything time-sensitive, a keyword branch is worth building. If the caller's reply contains words that suggest urgency, route that conversation to an immediate alert rather than the standard next-business-day queue. A generic "we'll get back to you shortly" response to someone with an actual emergency is the kind of miss that costs more than the missed call itself did.

Connect Missed Calls to a Pipeline

A missed call that turns into a reply is a lead, and it should show up in your pipeline the same way a form submission or a booked call would. Tag the contact on missed call, tag it again on reply, and use those tags to trigger the same nurture sequence your other lead sources feed into. This is the same lead capture logic covered in CRM Automation for Small Business, just triggered from a phone call instead of a form.

If you are running Retell AI voice agents alongside GHL, missed call text back and an AI voice agent solve different parts of the same problem: the voice agent tries to actually answer the call, and missed call text back catches whatever slips past it. How to Use Retell AI covers the voice agent side if that is the direction you are building toward.

Common Problems

Texts are not sending at all. Check whether the number is GHL-provisioned or externally forwarded, since forwarded numbers do not reliably trigger the missed call event. Also confirm the contact has not opted out of SMS, since GHL will not override that.

No error but the message never arrives. If the number GHL is texting is a landline, the carrier silently rejects the SMS with no error and no extra charge shown in GHL. There is nothing to fix here beyond confirming the number type.

Duplicate texts for one missed call. Almost always the native toggle and a workflow trigger both running on the same number. Pick one.

Notifications firing but the text is generic and gets ignored. Revisit the message copy before adding more automation on top of it. A better first line usually does more than a longer sequence.

Testing Checklist

Before trusting this with real leads, call your own GHL number from a phone that is not in your CRM and let it ring out unanswered. Confirm the text arrives within the window you expect, reply to it and confirm the reply lands in Conversations, check that the internal notification fires, and confirm the contact gets tagged and enters your pipeline correctly. Run the same test outside business hours to make sure the after-hours behavior is what you intended and not accidentally silent.

Building the message, the branching, and the CRM handoff together as one working system is exactly the kind of GoHighLevel project I take on for clients. If you want this set up correctly the first time, including reply handling and pipeline integration, book a free 30-minute call and bring the number and message tone you want, and we can get it running.

Frequently Asked Questions

What is GoHighLevel missed call text back?

It is an automatic SMS sent to a caller the moment their call to your GHL number goes unanswered, whether that is due to no answer, a busy line, or a cancelled call. It can run as a simple native toggle or as a full workflow with branching.

How do I set up missed call text back in GHL?

Either enable the native toggle under location settings for a single instant text, or build a workflow with a Call Status trigger filtered to missed calls, followed by a Send SMS action and any branching you want on top of it.

Can GHL send a booking link after a missed call?

Yes. Add the calendar link directly in the text message, or send it as a follow-up once the caller replies and confirms interest, rather than putting it in the very first automated message.

Can I customize the missed call message?

Yes, fully. Both the native toggle and the workflow version let you write your own message and use custom values like the caller's name if it is already on file in your CRM.

Does GoHighLevel missed call text back work after hours?

Yes, it fires around the clock regardless of your business hours settings. Use the message copy itself to set the right expectation for after-hours callers rather than relying on GHL to change behavior based on time of day.

Why isn't GHL sending my missed call text?

Check first whether the number is provisioned directly through GHL or forwarded in from an external carrier, since forwarded numbers do not always trigger the event reliably. Also confirm both the native toggle and a workflow are not fighting each other on the same number.

Does it cost extra to run?

The feature itself is included on GHL plans at no extra charge. You pay the standard per-segment SMS rate for each text sent, the same as any other SMS your account sends.

If you would rather have this built than build it, I take on GoHighLevel automation work through Upwork.