Missed Call Text Back: GoHighLevel Setup, Templates and Best Practices

Missed call text back is an automated text sent to a caller after their call rings through unanswered. In GoHighLevel with Phone Clover, you turn it on by typing a message (up to 300 characters) into the “Text back if missed” field under Settings > Calls > Missed calls. It is off by default, it sends once per missed call, and it only fires after the full ring, forward and voicemail chain has ended with nobody picking up.

A missed call is a lead going cold in real time. The automatic text tells the caller you saw the call and will follow up, without needing a rep to be free the instant the phone rang. This guide covers how to set it up, three templates to start from, how it behaves around business hours, the limits you should know about, and how to make sure a missed call still gets a human callback.

Note: Missed call text back is included in Pro and above (Pro, Growth 5, Growth 10 and Scale) for sub-accounts covered by the plan. Phone Clover is a private HighLevel app in early access, and calling is early access too.

When missed-call replies help

Most missed calls are not spam. They are a lead, a customer, or a prospect calling at a moment nobody was available, and a caller who hears nothing back may simply try the next business on their list. An automatic text-back changes that in one specific way: it tells the caller you saw the call and you will follow up.

It works best for businesses that get inbound calls when nobody is actively watching the phone: service businesses fielding calls between jobs, small teams where everyone is sometimes on another line, or after-hours calls that still deserve an acknowledgment even if the real follow-up happens the next business day.

Why Phone Clover keeps it off by default

Phone Clover does not turn this on automatically when you install it. An admin has to opt in from Settings, under the Calls tab, in the “Missed calls” card. The control is a single text field labeled “Text back if missed” that doubles as the on/off switch: leave it blank (placeholder “No text (off)”) and nothing sends; type a message and it turns on.

That is a deliberate choice. Automatic outbound texting is customer-facing behavior a business should decide on purpose, with wording they have reviewed, rather than a default message going out under a business’s name the moment an app is installed.

Warning: The text-back is a real SMS sent through Telnyx from the number the caller dialed, but in HighLevel it is logged as a note on the contact’s record, not as a message inside the Conversations thread. If a rep goes looking for it as a normal text exchange, they will not find it there. This is a limitation in how HighLevel exposes this behavior to outside apps, not something that will change with a setting.

How to set up missed call text back on GHL

The setting lives in Settings, under the Calls tab, in the “Missed calls” card, right next to forward-to-mobile and voicemail:

1. Open Settings > Calls in Phone Clover.
2. Find the “Missed calls” card and its “Text back if missed” field. When it is off, the field shows the placeholder “No text (off).”
3. Type your message, up to 300 characters. Use one of the templates below as a starting point.
4. Save the change. A message in the field means text-back is on; an empty field means it is off.

To turn it back off later, clear the field. Phone Clover asks you to confirm first: “Stop texting back missed callers? Nobody will hear from you automatically.” That is a real behavior change for anyone who calls in after that, so the extra step is on purpose.

The step-by-step version lives in the docs: set up missed-call text-back.

Missed call text back templates

A missed call text message that works well is short, names the business, and sets an expectation. Three templates to adapt:

1. The quick acknowledgment: “Sorry we missed your call! This is [Business Name]. We’ll call you back shortly. Reply here if it’s urgent.”
2. The busy-right-now version: “Thanks for calling [Business Name]. We’re with another customer right now and will call you back as soon as we’re free.”
3. The next-step version: “We missed you! A member of the [Business Name] team will reach out today. You can also call us back anytime at this number.”

For more wording by industry and situation, see 25 missed call text message templates.

Avoid promising a response time you cannot keep, and avoid legal or medical claims in the message. Keep it close to what a rep would actually say if they picked up the phone thirty seconds later.

Business-hours behavior

The text-back only fires after the full ring, forward, and voicemail chain has finished with no answer, never before a forward attempt that might still be answered. That matters for how it interacts with business hours:

• During business hours, if ring-all or round-robin routing fails to reach any rep and the call falls through to forward or voicemail with still no answer, the text-back is the last thing that happens in that chain.
• Outside business hours, calls behave as if nobody is available: try forward, then voicemail, then a spoken greeting and hang up. The text-back still only fires once, at the true end of that chain.
• Before it sends, it runs the same checks as your other texts: no text to callers who opted out or are marked do-not-disturb, and with quiet hours on (the default) no text that would land outside the caller’s legal send window, usually 8am to 9pm their time. A late-night missed call is skipped, not held for the morning, and the reason is recorded. See outbound texts and quiet hours.

Because it always fires last, a caller who does reach a real person on a forwarded leg, for example, will not receive the automatic text. It is reserved for calls that genuinely got no human response. To see how the ringing order works before that point, read GoHighLevel call routing and configure business hours.

How it fits with the rest of missed-call handling

Text-back is one piece of a larger missed-call setup, not a standalone feature. The same “Missed calls” card also controls forward-to-mobile and voicemail, and all three interact:

• If forward-to-mobile is on and a rep answers on their cell, the call was answered, so no text-back fires. Your own number is always kept as caller ID on a forwarded call; it is never swapped out for the rep’s personal number.
• If voicemail is on and the caller leaves a message, the call still counts as unanswered for text-back purposes, since nobody picked up live. The text-back and the voicemail can both apply to the same missed call.
• If neither forward nor voicemail is set up, the call still runs to the end of its chain, and text-back fires afterward if it is turned on.

Think of text-back as the layer that always runs last, regardless of which combination of forwarding and voicemail a sub-account has configured.

What automated missed call text back does not do

Being clear about the limits saves your team a surprise later:

• It is one fixed message, not a sequence. If you want more follow-up after the first text, build that separately with a HighLevel workflow.
• The outgoing text does not appear as a Conversations bubble. It is logged as a contact note.
• It is not held for later. A missed call outside the caller’s quiet-hours window gets no text at all, with the reason recorded.
• It does not replace a callback. The text buys goodwill; a person still has to call back.

A note on tone and compliance

Because this message sends automatically and immediately, treat the wording with the same care you would give any other automated business communication:

• Identify your business by name in the message, since the caller may not have your number saved.
• Do not promise a specific response time you cannot reliably meet (“we’ll call you back in 5 minutes” during a busy period sets an expectation you may break).
• Avoid sensitive claims. If you are in a regulated industry, such as medical, legal or financial, run the wording by whoever handles compliance for your business before turning this on.
• Keep it short. The 300-character cap forces this anyway, but a shorter message reads less like an automated form letter.

Follow-up tracking

Sending an automated text is not the same as following up. The real fix for a missed call is still a human callback, and Phone Clover’s dashboard is built around making sure that happens:

• The “To call back” card lists missed calls from the last 7 days that nobody at the sub-account has since called or answered, capped at 20 rows, each with a Call back button. See work the to-call-back list.
• The Recents tab on the Phone page shows a red missed-call badge and lets you filter to Missed specifically, so a rep opening the app sees what needs attention first.
• Logging an outcome after the eventual callback, including a custom outcome with a follow-up task, keeps the record of what happened attached to the contact.

Text-back buys you time. The to-call-back list and outcomes are what close the loop.

Measuring whether it is working

Since the outgoing reply is logged as a contact note rather than a Conversations message, you cannot measure text-back the way you might measure an SMS campaign, with reply rates pulled straight from a thread. What you can measure instead:

• Whether missed calls are getting worked. The to-call-back list is the real signal. If it stays empty or gets cleared daily, follow-up is happening regardless of whether the automatic text played a role.
• Whether callers mention it. Some customers reference the text-back message when they do get a live callback (“got your text, just calling back”), which is a loose but real signal it is being seen.
• Complaint volume. If customers reply with confusion or annoyance, that is a strong signal to revisit the wording.

Set expectations with your team

Tell your team plainly before you turn this on: reps will not see the automatic text-back sitting in Conversations next to a customer’s other messages. It shows as a note on the contact. Texting through HighLevel Conversations on Telnyx is in early access, so if a caller replies, check the contact’s conversation and notes rather than assuming there is a full two-way thread that documents the automated reply.

When Phone Clover fits, and when it does not

Missed call text back in Phone Clover fits a business that wants callers to hear something immediately after a missed call, and is comfortable that the outgoing reply shows up as a note on the contact rather than a Conversations message today. It fits teams that already use the dashboard’s to-call-back list to make sure a real person follows up afterward, not just the automatic text.

It does not fit a team that needs the reply to appear as a normal SMS thread a rep can continue from Conversations, since that is not how it works today. And it is not a replacement for staffing the phone during your busiest hours. An automatic text buys goodwill; it does not close the sale.

Related reading: Set up missed-call text-back, Configure business hours, Work the to-call-back list, and the missed-call text-back product page.