GoHighLevel Missed Call Text-Back: Turning Missed Calls into Booked Jobs (2026)

Every tradie, clinic owner and small business operator I work with has the same blind spot: the phone rings while they are on the tools or in a consult, the call goes to voicemail, and the caller simply rings the next business on Google. As a GoHighLevel Certified Admin here in Australia, I audit accounts every week where 30 to 50 per cent of inbound calls go unanswered, and almost none of those callers are ever contacted again. That is revenue leaking out of a hole you already paid to fill.

GoHighLevel's missed call text-back feature is the cheapest, fastest fix. Within seconds of a missed call, the caller receives an SMS from your business number, the conversation moves to text, and your team (or Conversation AI) picks it up from there. This guide covers how the feature works, native toggle versus custom Workflow build, the setup I use for clients, escalating to Conversation AI, and measuring ROI — all current as of mid-2026 and aligned with Australian SMS compliance.

What missed call text-back actually is

Missed call text-back is a GoHighLevel automation that detects when an inbound call to your LeadConnector or Twilio phone number goes unanswered, then immediately sends an SMS back to the caller. The native version lives under Settings → Phone Numbers as a simple toggle with one editable message template. The custom version is built in Workflows using the Call Status trigger, which fires on outcomes such as "no answer", "busy" or "voicemail", and gives you full control over timing, branching and follow-up.

Either way, the missed call creates or updates a contact record, the SMS goes out from the number the person just called, and the reply lands in the Conversations tab for a human or an AI agent to answer. The caller never knows which method you used — but the two behave very differently once you want anything beyond a single message.

Why missed calls cost more than you think

Run the numbers on your own business. If your average job is worth $400 and you miss 35 of 100 monthly inbound calls, that is $14,000 of potential work hanging up on you. Even at a conservative 25 per cent close rate, a text-back system that re-engages half of those callers puts roughly $1,750 a month back on the table — from an automation that takes under an hour to build.

Speed is the multiplier. In my client accounts, an SMS sent within 60 seconds of a missed call gets a reply from 40 to 45 per cent of callers; sent two hours later, closer to 10 per cent. The caller who could not reach you at 10:02 am has usually booked with a competitor by 10:20.

Native toggle vs custom Workflow: which should you use?

The native toggle is useful for a bare-bones setup: flick it on, write one message, done. But it sends the same message to everyone, at every hour, with no follow-up, no tagging and no awareness of whether the caller is an existing customer or a new lead. A custom Workflow costs you 45 minutes and removes every one of those limitations.

My rule of thumb: turn the native toggle on today to stop the bleeding, then replace it with a Workflow within the fortnight — never run both at once.

Step-by-step: building the custom Workflow

Step 1 — Sort your phone number and SMS compliance first

Your sub-account needs an active LeadConnector or Twilio phone number with SMS capability. For Australian businesses, the US-style A2P 10DLC registration does not apply, but ACMA rules around the Spam Act, sender identification, opt-out handling and alphanumeric sender ID registration absolutely do — get this wrong and your messages get filtered before anyone reads them. I have covered the full requirements in my guide to GoHighLevel SMS and A2P compliance for Australian businesses.

Step 2 — Create the Workflow with a Call Status trigger

Go to Automation → Workflows → Create Workflow → Start from Scratch. Add the Call Status trigger, filter it to your inbound number, and set call status to the missed outcomes: no answer, busy and voicemail.

Step 3 — Branch on business hours with if/else

Add an if/else branch checking the time of day. During business hours: "Hi {{contact.first_name}}, sorry we missed your call — we're on another job. Reply here and we'll get straight back to you, or tap this link to book: [link]." After hours, set expectations honestly: "We're closed until 7am, but reply with what you need and we'll lock you in first thing."

Step 4 — Add the SMS action, tags and a short wait step

Use the workflow SMS action for the message, then add a tag such as missed-call-textback for reporting. Add a wait step of 15 to 30 minutes with the condition "contact replied". If they reply, the workflow ends; if not, send one polite nudge: "Just checking you got sorted — want me to pencil you in?" Two messages is the ceiling; three risks opt-outs.

Step 5 — Notify your team and create the opportunity

Add an internal notification to whoever handles the phones, and optionally create an opportunity in a "Missed Call Recovery" pipeline stage, with a custom field storing the original call time for reporting. Test by ringing your number from a mobile not saved in the account and letting it ring out.

Escalating to Conversation AI

The text-back starts the conversation; someone still has to finish it. If your team is slow to reply in the Conversations tab, you have moved the missed call problem into a missed message problem. This is where Conversation AI earns its keep: configure an AI agent in SMS mode with your services and calendar connected, and it will answer the caller's reply, qualify the job and book an appointment — at 9pm on a Sunday if that is when the customer texts back. See my walkthrough on setting up Conversation AI for SMS and chat booking for the prompts and guardrails I use with Australian clients.

One caution: always give the AI an escape hatch. Anything mentioning "urgent", "emergency" or "complaint" should tag the contact and ping a human immediately.

Where this works best: tradies, clinics and beyond

Tradies and home services. Plumbers, sparkies and HVAC techs miss calls because their hands are literally full. A text-back that says "on the tools, reply here" matches how customers expect a tradie to operate, and the booking link converts urgent jobs before the caller rings a competitor. My GoHighLevel snapshot for tradies and home services ships with this workflow pre-built.

Allied health and clinics. Reception can only answer one line at a time. A text-back with a direct link to the online booking calendar recovers appointment requests without adding front-desk load — just keep messages free of clinical detail for privacy reasons.

Real estate and legal. Enquiries here are high-value and time-sensitive. Route missed calls into a dedicated pipeline stage so a person follows up within the hour, with the SMS holding the lead warm.

Measuring the ROI

Because you tagged every contact who entered the workflow, reporting is straightforward. Each month, count contacts tagged missed-call-textback, count replies, count bookings, and multiply won opportunities by average job value. Benchmarks from my client accounts: 35–50 per cent reply rate on the first SMS, 15–25 per cent of missed callers booking, and payback inside the first fortnight for any business with an average sale over $200. If your reply rate is under 20 per cent, the message is the problem — usually because it reads like a robot wrote it.

Common mistakes to avoid

• Running the native toggle and a custom Workflow at the same time, so every missed caller gets two texts within seconds.
• Sending the same message 24/7 with no if/else branch for after-hours calls, promising a callback that will not come for twelve hours.
• Ignoring Australian SMS compliance — no sender identification, no opt-out handling, and templates written for the US A2P regime rather than ACMA and Spam Act rules.
• Writing a text that sounds automated ("Your call is important to us") instead of human ("Sorry, on a job — what do you need?").
• Having no plan for the reply, so the customer's answer sits unread in the Conversations tab for six hours.
• Skipping tags and reporting, so six months later you cannot prove whether the automation recovered $500 or $15,000.

If you want a missed call text-back system built and tested inside your own GoHighLevel account, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

Does GoHighLevel's missed call text-back work with Australian phone numbers?

Yes. It works with any SMS-capable LeadConnector or Twilio number in your sub-account, including Australian numbers. The key difference for Australian businesses is compliance: you follow ACMA and Spam Act requirements (sender identification and functional opt-out) rather than the US A2P 10DLC registration process, and you should register alphanumeric sender IDs where applicable.

Should I use the native toggle or build a custom Workflow?

Use the native toggle as a same-day stopgap, then replace it with a custom Workflow built on the Call Status trigger. The Workflow adds business-hours branching, follow-up messages with wait steps, tagging for reporting, pipeline automation and Conversation AI handover — none of which the native feature supports. Never run both simultaneously.

How quickly does the text go out after a missed call?

Typically within 10 to 60 seconds of the call ending, for both the native feature and a Workflow build. That speed is the whole point: replying within the first minute keeps you in the conversation before the caller dials the next business on their list.

Can Conversation AI book appointments from missed call replies?

Yes. Once the caller replies to your text-back SMS, a Conversation AI agent configured in SMS mode can qualify the enquiry, answer common questions and book directly into your connected calendar. Always add an escalation branch so urgent or sensitive messages are tagged and routed to a human immediately.

What results should I expect from missed call text-back?

Across my Australian client accounts, a well-written text-back sequence gets replies from 35 to 50 per cent of missed callers, and 15 to 25 per cent of missed callers end up booking. For a business with an average sale above $200, the system usually pays for its build cost within the first two weeks.