GoHighLevel missed call text back is an automation that sends an SMS to anyone who calls a HighLevel phone number and does not reach a person. You build it as a workflow: a call status trigger filtered to missed or unanswered inbound calls, then a Send SMS action with a short message that invites the caller to reply. Done well, it turns a voicemail that nobody listens to into a text conversation your team can pick up in minutes.
For local service clients, this is often the first automation an agency sets up, and it is also one of the most commonly broken. This guide covers the setup, the filters that matter, message copy that gets replies, and the follow-up that makes it worth having.
Why missed call text back automation matters
Service businesses miss calls all the time. The owner is on a job, the office is on another line, or it is after hours. A caller who reaches voicemail often just dials the next business in the search results. A text that arrives within a minute says "we saw you called, how can we help?" and keeps the conversation alive.
The automation is simple. The value comes from getting the details right: only texting real missed calls, sending at sensible times, routing replies to someone who will answer, and following up when the caller does not reply.
How GHL missed call text back works
HighLevel phone numbers log every call to the contact record. The workflow listens for call events and reacts when an inbound call ends without being answered. The basic pieces are:
- A trigger on call status, filtered to inbound calls that were missed, not answered or went to voicemail. Trigger names and filter options shift between HighLevel releases, so look for the call-related trigger in your workflow builder and check the available status filters.
- A Send SMS action with your message.
- Optional steps: a tag, an internal notification, an opportunity in the pipeline, and a follow-up sequence.
HighLevel also offers a built-in missed call text back setting in some versions of the phone settings. I prefer the workflow approach because it gives you filters, business-hours logic and follow-up, which the simple toggle does not.
Missed call text back setup, step by step
- Confirm the phone number is ready. The number needs to be able to send SMS, and for US numbers the sub-account needs A2P 10DLC registration approved. Without it, messages may be filtered or blocked. See my 10DLC compliance guide.
- Create a workflow in the client's sub-account and name it clearly, for example "Missed call text back, main line".
- Add the call trigger and set filters: direction inbound, status missed or no answer. If you have several numbers, filter to the one this workflow covers.
- Add a wait of about a minute. This avoids texting someone who called, hung up and called straight back and got through.
- Add an If/Else check to skip the text if the contact already had an answered call in that window, or if the contact is tagged as a supplier, staff member or existing do-not-text.
- Add business-hours branching. During hours, say someone will reply shortly. After hours, say when you will be back and offer a booking link.
- Add the Send SMS action with the right message on each branch.
- Notify the team. Send an internal notification, a Slack message or an assigned task so a person sees the conversation.
- Create or update an opportunity in the right pipeline stage so missed callers do not live only in the inbox.
- Publish and test from a phone that is not already a contact. Call, do not answer, and confirm the text arrives.
Message copy that gets replies
The text should sound like the business, not a system. Short and specific works best. Some examples:
- During hours: "Hi, this is Sam from Northside Plumbing. Sorry we missed your call. What can we help with? Reply here and I will get back to you in a few minutes."
- After hours: "Hi, this is Northside Plumbing. We are closed right now but saw your call. Reply with what you need and we will text you first thing at 8am, or book a time here: [link]."
- For emergencies: add a line with the emergency number if the business offers 24/7 service.
Things to avoid:
- Long messages with several questions.
- Generic copy like "Thank you for contacting us".
- Links in the very first message unless they are useful, since some carriers treat link-heavy texts with suspicion.
- Missing opt-out language where your compliance setup needs it.
Follow-up after the first text
Many callers will not reply to the first message. A short, polite follow-up recovers some of them:
- If no reply after a couple of hours during business hours, send one more text: "Just checking in, still need help with your call earlier?"
- If still no reply the next day, create a task for a team member to call back.
- Stop the sequence immediately when the contact replies, books, or opts out. Use the workflow's goal or a reply trigger to exit them.
This is where follow-up automation earns its keep. One text is a nice gesture. A short, well-timed sequence with a human callback is a process.
Routing replies so someone answers
The most common failure I see is not technical. The text goes out, the caller replies, and nobody sees it because the sub-account's conversations tab is not anyone's job. Fix that:
- Assign each missed-call contact to a user, round robin or by service area.
- Send the assigned user a push notification or Slack ping on reply.
- Set a rule: if a reply sits unanswered for a set time, escalate to a manager.
For agencies, it is worth reporting this back to the client: number of missed calls, texts sent, replies and booked appointments. Clients often do not realise how many calls they miss until they see it.
Common mistakes with GHL missed call text back
- Texting answered calls. A loose trigger filter sends "sorry we missed you" to people you just spoke to.
- Texting staff and vendors. Exclude known numbers with tags.
- No 10DLC registration. Messages fail quietly or get filtered.
- Duplicate workflows. A snapshot that includes the workflow, plus a manually built one, means callers get two texts.
- No after-hours branch. Promising a reply "in a few minutes" at 11pm hurts trust.
- No tracking. Without tags or pipeline stages, you cannot show the client results.
Going further: AI replies and voice
Once the basics work, some agencies add an AI layer: an assistant that reads the caller's reply, asks a couple of qualifying questions and offers booking times. Others route missed calls to an AI receptionist that answers instead of letting the call go to voicemail at all. Both build on the same foundation, so get the plain workflow right first.
How I build this
I build missed call text back and speed-to-lead flows inside client sub-accounts and as snapshot-ready templates agencies can roll out across many clients, with business-hours logic, exclusions, routing and reporting. See my SMS automation service, and if your current setup is texting the wrong people or not texting at all, the Automation Rescue fixes it in 48 hours. You can also ask for a free 15-minute Loom teardown of the workflow you have now.
FAQ
How do I set up missed call text back in GoHighLevel?
Create a workflow with a call status trigger filtered to missed inbound calls, add a short wait, then a Send SMS action. Add business-hours branches, an internal notification and a follow-up step.
Why is my GoHighLevel missed call text back not working?
The usual causes are an unpublished workflow, a trigger filter that does not match the call status, a number without approved A2P 10DLC registration, or the contact being opted out of SMS.
What should a missed call text back message say?
Name the business, say you missed their call, and ask one simple question like what they need help with. Keep it under two sentences and match the tone of the business.
Does missed call text back need A2P 10DLC registration?
For US numbers sending business texts, yes, registration is generally required. Unregistered traffic is likely to be filtered or blocked by carriers.