GoHighLevel missed call text back not working

Short answer
GoHighLevel only sends the missed call text back when a call rings past your incoming call timeout without being answered. The most common reasons it doesn't send: the feature is off, a forwarded call was answered by a cell phone or its voicemail first (Call Connect fixes this), the number isn't A2P 10DLC registered or toll-free verified, or the caller has DND on.
How to fix it
- Turn it on. Go to Settings > Phone System > Voice > Voicemail & Missed Call Text Back. Enable Missed Call Text Back, click Customize to write the message, send yourself a test, and save.
- Check the requirements. Local numbers need A2P 10DLC registration; toll-free numbers need toll-free verification. The location needs at least one verified number that can text.
- Check the ring timeout. Only calls that go unanswered past your incoming call timeout count as missed. HighLevel recommends 10 to 20 seconds.
- Stop a cell phone's voicemail from taking the call. If calls forward to a cell phone, its voicemail can answer first, so the call isn't missed. Under Settings > Phone System > Phone Numbers > Edit Configuration > Set Timeout and Backup, set about 20 seconds, and turn on Call Connect so only calls a person answers count as connected.
- Forward only missed calls from your old line. If you forward your existing business line to your HighLevel number, carriers have codes that forward only unanswered calls. HighLevel's forwarding article lists them by carrier.
- Check the caller's DND. The text only goes out if the contact's communication preferences and DND allow it.
How to find the cause
Start with one call that should have got a text, and follow it. The call shows up in the contact's conversation and in Reporting > Call Reporting, where incoming calls are split into missed, busy and answered.
| What you see | What it means | What to do |
|---|---|---|
| No call recorded at all | The call never reached your HighLevel number | Check that the caller dialed your HighLevel number, or that your old line really forwards to it |
| The call shows as answered or completed, but nobody picked up | A cell phone or its voicemail answered the forwarded call. HighLevel says forwarded calls are marked completed without Call Connect, even when voicemail took them | Set the timeout to about 20 seconds and turn on Call Connect |
| The call shows as missed, but no text was sent | The feature is off for the location, or the caller has DND on | Check the Enable Missed Call Text Back box, then the DND section on the contact |
| A text was sent but has a red marker | The text failed at the carrier | Hover to read the code: 30034 means the number isn't A2P registered yet; 21610 means the caller opted out |
| The text came from a different number than the one they called | HighLevel texts from the dialed number only if it can send SMS; otherwise the number that last messaged the contact, then your default | Make the dialed number SMS-capable and registered |
If you built it as a workflow, open its Execution Logs. If the caller never enrolled, the Call Details trigger's filters didn't match the call: check the direction is incoming and the statuses include not answered and busy. If they enrolled but the Send SMS step shows an error, View Details tells you why.
Also check the number's label under Settings > Phone System > Phone Numbers. A local number without the green A2P Verified label isn't linked to an approved campaign, and its texts won't go out.
How to confirm it's fixed
- Call from a phone that isn't yours in HighLevel. Use a mobile that isn't one of your forwarding phones and isn't saved on a contact with DND. Call the HighLevel number your customers dial.
- Let it ring out. Don't answer on any device. Let it ring past the timeout, or leave a voicemail, then hang up.
- Check how the call was logged. In Call Reporting or the conversation, it should count as missed, not answered or completed. Completed means a phone or voicemail picked it up before the timeout.
- Check the text. A pass is the text arriving on the test phone, from the number you called, with no red marker in the conversation.
- Test the answered case. Call again and answer, pressing a key if Call Connect's whisper asks you to. A pass is no text, because answered calls never trigger it.
- Test your old line too. If your existing business number forwards to HighLevel, call that number as well. Its carrier's forwarding code decides which calls reach HighLevel at all.
Using a workflow? Run the same test and check Enrollment History. One missed call should mean one enrollment and one text; more than one means the trigger fired on several status changes and needs a condition or wait.
Doing it with a workflow instead
The built-in setting sends a text for every missed call, even when the same person calls three times. For more control, build it as a workflow with the Call Details trigger: incoming calls with the status busy or not answered, then a Send SMS step.
The Call Details trigger (HighLevel's new name for Call Status) fires on each status change, so add a condition or a wait step so one caller doesn't get several texts.
Common questions
- Why do calls that went to voicemail not get a text?
- If a cell phone's voicemail picked up, the call counts as answered. Shorten the timeout so the call returns to HighLevel first, and turn on Call Connect.
- The same caller got three texts. Why?
- The built-in text back sends once per missed call. Use a Call Details workflow with a wait step or a tag check instead.
- Can it do more than send one text?
- The built-in feature sends one message. A workflow can add steps, and Conversation AI can hold the conversation: ask what the caller needs, check availability and book. We set either up for you.
Rather we set it up?
We set this up for you as part of a done-for-you package, quoted on a free call.
Speed to lead: never miss a lead
Every lead from every source captured, answered in seconds and qualified, so the calls and messages you'd lose turn into booked jobs.
More phone and call fixes
GoHighLevel voicemail or call recording not working
Usually the ring timeout is too long so your cell's voicemail answers, or recording isn't on for that number.
Porting your phone number into GoHighLevel
A recent bill, your carrier account number and PIN, a matching service address, then two to four weeks. Keep the old service on until it's done.
GoHighLevel calls going to voicemail, or forwarding not working
Usually the timeout, owner routing sending the call to someone else, a user with no device ticked, or Call Connect's press-to-accept being missed.
GoHighLevel mobile app notifications not arriving
Usually the mobile channel is off in your notification settings, you only see assigned conversations, or the phone is blocking the app.
Related fixes
GoHighLevel error 30034: texts fail from an unregistered number
Your US number isn't linked to an approved A2P 10DLC campaign yet. Register in Trust Center, then wait up to 24 hours.
Read the fixGoHighLevel sending duplicate text messages
Usually two triggers firing on one event, re-entry left on, or the same person saved as two contacts.
Read the fixGoHighLevel workflow not triggering: a checklist
Usually it's still in Draft, the trigger filters don't match, or re-entry is off. The execution logs tell you which.
Read the fix
Want GoHighLevel set up and running for you?
Book a free 15-minute call. Tell us what you sell and where your leads come from, new account or the one you have, and we'll tell you what we'd set up, how long it takes and what it costs.