GoHighLevel Missed Call Text-Back: Capturing Leads You're Losing (2026)

Every missed call at a local service business is a customer who picked up the phone, decided to ring you, and got nothing. For a plumber, an electrician, a dental clinic or a mobile mechanic, that's not a soft "maybe" lead — that's someone with a problem right now, money in hand, dialling because they want it fixed today. When you don't answer, most of them don't leave a voicemail and they don't ring back. They scroll down to the next listing and ring your competitor instead. If you're missing even ten or fifteen calls a week — tradies on a job, reception at lunch, after-hours enquiries — you're quietly handing thousands of dollars in revenue to whoever picks up next.

This is where speed-to-lead matters more than anything else in your marketing. The research has been consistent for years: contact a lead within the first five minutes and you're vastly more likely to convert than if you wait an hour, let alone a day. A missed call text-back automation closes that gap to seconds. The moment a call goes unanswered, the caller gets a text from your business number — before they've even finished deciding who to ring next. In GoHighLevel this is a small Workflow with an outsized return, and once it's built correctly it runs forever in the background. Below I'll walk you through exactly how to build it as a GHL Certified Admin, including the Australian compliance bits that most overseas tutorials skip entirely.

What missed call text-back is and why it works

Missed call text-back is a simple piece of automation: when an inbound call to your business number isn't answered, GoHighLevel automatically fires off an SMS to the caller. Instead of a dead end, the prospect gets something like "Sorry we missed your call — how can we help?" and a two-way conversation opens up. The caller can reply by text, your team picks it up in the Conversations inbox, and the lead is saved.

It works for three reasons. First, it removes the friction of a second phone call — texting is lower effort than ringing back, so people who'd never leave a voicemail will happily reply to a text. Second, it's instant, which is the whole game with speed-to-lead. Third, it captures a phone number you can now contact, tag and nurture, even if this particular enquiry doesn't convert today. A missed call is a one-time event; a contact in your sub-account is an asset you keep.

Prerequisites before you build

You can't text from thin air. Before the Workflow does anything useful, your GoHighLevel sub-account needs a few things in place.

A messaging-capable phone number

You need a Twilio or LeadConnector number connected to the sub-account, and crucially it needs to be the same number people are calling — or at least be configured to forward and track calls. LeadConnector is GHL's own re-sold Twilio layer and is the simplest path for most accounts. Make sure the number is voice and SMS enabled, and that call events are being recorded against contacts so the Workflow trigger has something to listen to.

A2P and ACMA registration for Australia

This is the step most people get wrong. To send SMS reliably you must complete A2P (application-to-person) brand and campaign registration. In the United States this is the 10DLC process; for Australian numbers and senders you're working within ACMA's rules and your provider's Australian compliance requirements. Practically, that means registering your business, your use-case and sample message content before you start sending at volume. Skip it and your texts get filtered, delayed or blocked — and an unregistered missed call text-back is just an expensive way to talk to yourself. Get the registration submitted early; approval can take a few days.

Custom fields, tags and a pipeline

Decide in advance how you'll track these leads. At minimum create a tag like "Missed Call" and confirm you have a sales pipeline with a sensible first stage (for example "New Enquiry"). You'll use these inside the Workflow so every missed call becomes a trackable opportunity rather than an orphaned text thread.

Building the Workflow step by step

Open Automation, create a new Workflow from a blank recipe, and build it as follows.

The trigger

Add a trigger and choose Call Status. In the filters, set the call status to Voicemail or No Answer depending on how your number behaves — many setups treat an unanswered, redirected call as "Voicemail" even when no message is left. The key is that you're listening for the specific event "a call came in and nobody picked it up." Add a filter for Direction = Inbound so you only ever respond to people who rang you, never to outbound calls your team made.

The condition / filter

Inside the trigger, restrict it to genuine missed inbound calls. If your provider exposes a "Missed Call" condition, use it. Otherwise rely on the Inbound + No Answer/Voicemail combination above. This filtering is what keeps the automation from misfiring, which we'll come back to under loop avoidance.

The first action: Send SMS

Add a Send SMS action as the very first step after the trigger. Speed is the point, so don't put a Wait before it — fire the text immediately. Use the contact's first name merge field if you have it, and keep it short. We'll cover the actual copy below.

Wait and branch for staff

After the SMS, add a short Wait step (say two to three minutes) followed by an If/Else branch that checks whether the contact has replied. If they have, route into your reply-handling path; if they haven't after a set time, optionally send a single gentle follow-up or notify a staff member to ring them manually. Keep follow-ups minimal — one nudge, not five.

The message copy that actually converts

Your first text does most of the heavy lifting, so write it like a human who's genuinely sorry they missed the call. A version I use and recommend looks like this:

"Hi {{contact.first_name}}, it's Sam from [Business Name] — sorry we missed your call just now. We're with a customer but I can help you here. What did you need a hand with? Reply STOP to opt out."

Notice the elements: a real name, an apology, a reason (so it doesn't feel like a bot), an open question that invites a reply, and a compliant opt-out. Avoid links in the first message — they trip spam filters and you don't need one yet. Keep it under 160 characters where you can. The goal is a reply, not a sale.

Routing the reply into a conversation

Once the caller texts back, that reply lands in the Conversations inbox as a normal two-way thread. You've now got a choice about who handles it. For smaller teams, simply notify staff and let a human reply in real time — this is where setting up solid two-way SMS conversations in GoHighLevel pays off, because the whole back-and-forth stays threaded against the contact record.

If you're getting volume after hours or your team is on the tools all day, route the reply into Conversation AI instead. A well-trained bot can answer common questions, qualify the job, and even book the appointment before a person ever steps in. If you go this route, invest the time in proper Conversation AI setup and training so it sounds like your business and knows your services, pricing bands and service area. A lazy bot is worse than no bot. Either way, build a clean handoff: AI handles the first reply, escalates to a human the moment the enquiry gets specific or the customer asks to speak to someone.

Avoiding loops and staying compliant

This is where a sloppy build causes real damage, so slow down here.

Only text genuine inbound missed calls

Make sure your trigger fires only on inbound, unanswered calls. If you accidentally include outbound calls, you'll text your own customers every time a staff member rings them and doesn't connect — embarrassing and spammy. The Direction = Inbound filter is non-negotiable.

Business-hours logic

Decide whether you want the text-back running 24/7 or only outside hours. Many businesses run it all the time but change the copy by time of day. Use the Workflow's calendar/time conditions to branch: during hours, "we're with a customer, give us a sec"; after hours, "we're closed but I can take your details and we'll call first thing." This stops a daytime text from sounding like an out-of-hours autoresponder.

Opt-out and the Spam Act

Under Australia's Spam Act and ACMA's rules, commercial electronic messages must include a functional unsubscribe and you must honour it promptly. Include a clear opt-out (STOP) in your messaging and make sure GoHighLevel's opt-out handling is switched on so a "STOP" reply actually suppresses the contact. Don't keep texting someone who's asked you to stop — it's both illegal and bad business. Because this is a reply to a call the customer initiated, you're on solid footing for the first message, but the opt-out still belongs there.

Tagging and pipeline updates

Inside the same Workflow, add an action to apply your "Missed Call" tag, and a Create/Update Opportunity action to drop the contact into your pipeline at the "New Enquiry" stage. Now every missed call is visible on your board, not buried in an inbox. You can move the opportunity through stages as the conversation progresses — Contacted, Quoted, Booked, Won — which gives you a real view of how much revenue your missed calls are actually worth. Use custom fields to capture the job type if your AI or staff collect it.

Measuring results

Don't run this on faith. After a few weeks, look at the numbers: how many missed call texts went out, how many got a reply, how many turned into opportunities, and how many of those closed. The Workflow's own execution logs show send and reply counts, and your pipeline shows conversions. A healthy missed call text-back typically pulls a meaningful share of otherwise-dead calls back into live conversations. If your reply rate is low, your copy or your timing is off; if replies are high but bookings are low, the problem is in how you handle the conversation, not the automation.

Extending to voicemail and email

Once the SMS version is solid, extend it. Add a branch for callers who do leave a voicemail — GHL can transcribe it and notify staff, so nothing slips. Layer in an email follow-up for contacts where you have an address but no reply to the text. And for the leads who go quiet, feed them into a longer nurture sequence so you're not relying on a single touch — a structured set of drip campaigns to nurture leads will keep your business in front of them until they're ready to buy. The missed call is the entry point; the nurture is what turns a one-off enquiry into a long-term customer.

Common mistakes to avoid

• Building the Workflow before A2P/ACMA registration is approved — your texts get filtered or blocked and you'll think the automation is broken.
• Forgetting the Direction = Inbound filter, so the system texts customers every time your team makes an outbound call that doesn't connect.
• Putting a Wait step before the first SMS, killing the speed-to-lead advantage that makes the whole thing work.
• Writing a robotic, link-stuffed first message that reads like spam instead of a real apology and an open question.
• Leaving out the opt-out (STOP) or not enabling GHL's opt-out handling, breaching the Spam Act and ACMA requirements.
• Never checking the reports, so you can't tell whether the automation is making money or just sending texts into the void.

If you want a done-for-you missed call text-back workflow built and compliant for your business, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

How fast does the text-back actually go out?

If you build it correctly — Send SMS as the first action with no Wait step in front of it — the text fires within seconds of the call being marked unanswered. That speed is the entire point, so resist the temptation to delay the first message.

Do I really need A2P or ACMA registration in Australia?

Yes. Sending business SMS without proper brand and campaign registration leads to filtering, delays and blocked messages, especially at any volume. Get your registration submitted before you go live; it can take a few days to approve, so don't leave it to the last minute.

Will this text people we ring ourselves?

Only if you forget to filter the trigger to inbound calls. Always set Direction = Inbound so the Workflow ignores outbound calls your team makes. Done right, it only ever responds to people who rang you and got no answer.

Should a human or Conversation AI handle the reply?

It depends on volume and hours. Small teams during business hours can handle replies live in the Conversations inbox. If you get after-hours enquiries or your staff are on the tools all day, a properly trained Conversation AI can qualify and book before escalating to a person.

Is texting someone who missed-called us compliant under the Spam Act?

Responding to a call the customer initiated puts you on solid footing for that first message, but you must still include a working opt-out and honour STOP requests promptly. Enable GoHighLevel's opt-out handling so unsubscribes are respected automatically.