You turned on the checkbox. Then you read your own Conversations tab and watched one caller collect four identical texts. The rest of this page covers what the default feature does and where it stops, then what to ask anyone you hire to finish the job.
The four minutes after a missed call matter more than the call itself. If a missed call only produces a text that nobody notices, the lead is still sitting in a thread waiting for a human. That is an acknowledgement, not a follow-up system.
I am Joe Asis. I work in GoHighLevel daily and have built 100+ client systems while supporting 400 to 700+ subaccounts. Most of the missed call setups I am asked to fix already have the feature switched on. What is missing sits downstream of the text.
It sends one SMS to the caller after an inbound call goes unanswered. You find it in the sub-account under Settings, then Phone System, then Voice, then Voicemail & Missed Call Text Back. Tick the box to enable the feature, click Customize, and write your message in the Enter message field. There is a field below the editor where you can send yourself a test before you save.
Two defaults shape the behavior. The incoming call timeout slider decides when a call even counts as missed, and HighLevel recommends 10 to 20 seconds. Answered calls never trigger a text back. Merge fields only fill in when the system already knows the contact, so a first-time caller sees your message exactly as written. HighLevel also picks the sending number: the number the caller dialed first, then a number you have already messaged that contact from, then your default outbound number.
HighLevel says so in its own documentation: the feature triggers an SMS for every missed call, even when the same caller tries several times within a brief timeframe. Call, hang up, call again, and that caller gets a second text. A third attempt gets a third, and your business starts to look like a malfunctioning robot.
Their recommended fix is to stop treating the toggle as the whole feature: customize the existing missed call text-back recipe in Workflows, then add a wait step of around 20 minutes or tags such as first call and second call so a repeat attempt routes somewhere different. That guidance is also the first honest test of whoever you hire. Anyone who says the checkbox covers it has not read the page.
The toggle answers a call. A build decides what happens to the lead. Six things sit in the gap.
None of it needs exotic tooling. The difference between a text message and a system that owns the lead is what runs after the text.
Order matters because each layer depends on the one beneath it.
Suppression before pipeline entry stops you from creating five opportunities for one caller. Booking links before calendar checks push people toward a diary that is not open.
You cannot QA this from a settings screen. You have to call yourself, from numbers that are not in the CRM.
Log every result with a timestamp. When a test fails, fix the setting behind it and rerun the whole path, not just the step that broke.
These questions separate a builder from someone who knows where the checkbox lives.
The wider list, covering discovery, access, and handoff, sits in the questions to ask before you hire a GoHighLevel expert.
Thirty days in, you should be able to watch these behaviors without asking anyone.
HighLevel's own messaging on this feature notes that most people do not leave voicemails and rarely call back, which is the argument for the automatic reply. One text buys a second chance. Capture, owner, and booking path decide whether it turns into a call.
Yes. HighLevel documents that the feature triggers an SMS notification for every missed call, even when the same caller tries several times in a short window. To avoid repeat messages, HighLevel recommends customizing the missed call text-back recipe in Workflows and adding a wait step of roughly 20 minutes, or using tags such as first call and second call to route repeat attempts differently.
In the sub-account, open Settings, then Phone System, then Voice, then Voicemail & Missed Call Text Back, and select Missed Call Text Back. Enable the feature, click Customize to write the message in the Enter message field, send yourself a test message, then save. Depending on your account version, the same toggle can also appear through a phone number's Advanced Settings or in the location's Business Profile settings.
No. The built-in feature sends an SMS acknowledgement to the caller. Creating an opportunity, assigning an owner, notifying a user, and creating a callback task all come from workflow automation you build on top of it. Those are the parts a switched-on toggle does not cover.
Call the number from a phone that is not in your CRM and let it ring past the incoming call timeout, which HighLevel recommends setting at 10 to 20 seconds. Confirm one text arrives with the saved wording, then call twice more to check repeat-call suppression. Test after hours, reply to the text, click the booking link on a mobile device, and confirm the contact lands in the right pipeline stage with an owner and a callback task.
Send me the number your leads call. I will map what your setup is missing, from repeat-call suppression to after-hours messaging, owner alerts, and the booking path, then hand it over with test call evidence.
Book a Build Call