V Vlodar

GoHighLevel (GHL) test and troubleshooting guide

GoHighLevel (GHL) missed-call text-back: test and troubleshoot the full path

A settings check is not the same as proving the live customer path. Use a controlled test to trace one missed call through the correct location, workflow and SMS delivery state, then use the troubleshooting table to find the stage that failed.

Publisher
Published by ELIXON LTD (Vlodar)
First published:
Last reviewed:

Before testing

Use an authorized test number and a client location you are permitted to operate. Do not put real customer records, message contents, recordings or credentials into a test report. Follow the calling, messaging and consent rules that apply to the location and provider.

Seven checkpoints

  1. 1. Fix the expected path before the call

    Record the client location, inbound number, expected missed-call outcome, workflow and sending number. A pass is impossible to judge without an expected result.

  2. 2. Check routing, timeout and voicemail

    Confirm that the inbound number belongs to the intended location and that forwarding, timeout, voicemail and backup behavior will allow the call to be recorded as missed.

  3. 3. Place one genuine controlled missed call

    Call the published inbound number from the authorized test number and deliberately leave it unanswered. Record only the test timestamp and non-sensitive test identifier.

  4. 4. Verify the call in the correct location

    Confirm that HighLevel recorded the expected missed or no-answer outcome in the intended client location rather than another sub-account or external voicemail path.

  5. 5. Verify workflow entry and execution

    Check that the expected workflow enrolled the test contact and that filters, re-entry, DND and timing rules did not suppress or divert the action.

  6. 6. Verify the outbound message state

    Confirm that the expected sending number was used and inspect the provider delivery state. A created workflow action alone does not prove that an SMS was delivered.

  7. 7. Record the result and clean up

    Record pass, failure stage and timestamp without retaining message content or customer data. Remove the test contact when it is no longer required.

Troubleshooting by failure stage

Each row starts from what you see during the test. The numbers point to the HighLevel and Twilio pages the row is based on. Menu paths and wording are taken from those pages as they read on the review date and can change.

Symptom Likely cause What to check
Text-back fails with error 30034, or US texts stop after a number or registration change. The sending number is a US 10-digit local number that is not linked to an approved A2P 10DLC campaign. HighLevel requires A2P 10DLC registration (a brand and a campaign) for SMS to US recipients from local numbers. In Settings > Phone System > Trust Center, check the brand and the campaign status (Pending, Rejected or Approved). In Settings > Phone System > Phone Numbers, confirm the sending number shows the green A2P Verified label. After approval, HighLevel advises waiting up to 24 hours before sending. Sources: 5, 6, 7
Text-back fails with error 30007. The message was filtered by LeadConnector or the carrier because of its content, sender identity or compliance, for example traffic that does not comply with A2P 10DLC registration. Confirm the A2P status of the sending number first, then review the text-back wording. Before contacting HighLevel support, its 30007 guide asks for at least three contact examples from the past 7 days that show the error. Sources: 7, 8
The call was forwarded to a cell phone, nobody answered, and no text-back was sent or the call shows as completed. The cell phone's own voicemail picked up. HighLevel explains that Twilio marks a call as completed once routing finishes, even if no one answers, so a voicemail pickup on a forwarded call can look like a connected call instead of a missed one. Turn on Call Connect for the number (Settings > Phone System, three dots next to the number, Edit Configuration). The person answering must press a key before the call connects, so voicemail is not counted as an answer. Also check the incoming call timeout: only calls unanswered past it are treated as missed, and HighLevel recommends 10 to 20 seconds. Sources: 1, 2
The caller gets two texts for one missed call, or one text for every repeated call. The built-in Missed Call Text Back sends for every missed call, even when the same caller tries several times in a short time. A workflow that also sends on missed calls overlaps with it. Check Settings > Phone System > Voice > Voicemail & Missed Call Text Back and every workflow that sends SMS on a missed call. Decide which one sends. To avoid repeats, HighLevel suggests building the text-back from its workflow recipe and adding a wait step or call-count tags. Sources: 1, 4
The call was missed but the text-back workflow never enrolled the test contact. The Call Status (Call Details) trigger filters do not match the call. The trigger filters on direction (incoming or outgoing) and on status: busy, canceled, voicemail, completed or not answered. Set the direction to incoming and include every status you treat as missed, for example not answered and busy. Then check the workflow logs and the contact timeline for the test call. Sources: 3, 9
No text-back for one contact, or error 21610. The contact has Do Not Disturb (DND) enabled or opted out by replying STOP. Missed Call Text Back respects DND, and after STOP outbound messaging stays blocked until the contact opts back in, for example by texting START. Check the contact's DND settings and conversation for an opt-out. Do not switch DND off to pass a test; use a test number that has not opted out. Sources: 1, 7, 9
The workflow ran and the message shows as sent, but the test phone received nothing. Sent is not delivered. The carrier may still report the message as undelivered, for example error 30003 (handset off or unavailable), 30005 (unknown number) or 30006 (landline or unreachable carrier). Open the message in Conversations: failed messages show a red status and an error code. With your own Twilio account, find the message in Twilio under Monitor > Logs > Messaging. Compare the status with the table below. Sources: 7, 9, 13

Delivery status values: LC Phone and Twilio

LC Phone is HighLevel's built-in phone system; some agencies connect their own Twilio account instead. The two describe statuses in slightly different words, so record which one the location uses.

LC Phone (HighLevel messaging analytics) 10

Sent: the system attempted to send it.

Delivered: it reached the recipient.

Failed: it could not be delivered, for example because of an invalid number, carrier filtering, an opt-out or a compliance restriction.

Twilio (Messages resource) 14

sent: the nearest upstream carrier accepted the message.

delivered: Twilio received confirmation of delivery from the carrier.

undelivered: Twilio received a delivery receipt saying the message was not delivered.

failed: the message failed to send.

For a pass, record delivered. Sent only shows that a send was attempted (LC Phone) or that the carrier accepted the message (Twilio).

When to re-test

A pass applies to the setup you tested. Run the checkpoints again after any of these changes.

  • Number port or move. HighLevel's migration guide says a successful transfer does not automatically complete messaging compliance. Check the A2P campaign link, forwarding, voicemail, call routing and any workflow that references the number. 11
  • Workflow edit. A change to the trigger filters, wait steps, conditions or the SMS action changes the path you proved.
  • A2P change. A new or resubmitted brand or campaign, or a number added to a campaign. Wait for approval and the A2P Verified label, then allow up to 24 hours before the test. 6 7
  • Snapshot load. When a snapshot is loaded into an existing sub-account, Override replaces the existing item with the snapshot version. Check that the text-back workflow and its trigger are still the ones you tested. 12
  • Phone settings. Changes to Missed Call Text Back, the incoming call timeout, forwarding or Call Connect. 1 2

How does your agency verify this today?

Vlodar is testing whether US HighLevel agencies need automatic evidence for this complete path. The questionnaire asks about your current checks, failure frequency and paid-pilot interest. It does not request client data or credentials.

Take the 3-minute questionnaire

Sources

Official HighLevel help articles and Twilio documentation, checked on 2026-10-06.

  1. HighLevel: Where and how to configure the Missed Call Text Back feature
  2. HighLevel: Using Call Connect to ensure accurate call status tracking
  3. HighLevel: Workflow trigger - Call Status (Call Details)
  4. HighLevel: Missed Call WhatsApp Back overview and setup
  5. HighLevel: What is A2P 10DLC - brand and campaign registration
  6. HighLevel: A2P 10DLC campaign registration guide
  7. HighLevel: LC Phone System error code and warning dictionary
  8. HighLevel: How to prevent SMS filtering by carriers (error 30007)
  9. HighLevel: Troubleshooting SMS delivery
  10. HighLevel: Phone System messaging analytics overview
  11. HighLevel: Moving phone numbers - migration guide
  12. HighLevel: Load a snapshot into an existing sub-account
  13. HighLevel: How to check logs for a specific text message in Twilio
  14. Twilio: Messages resource - message status values

Vlodar is independent research operated by ELIXON LTD and is not affiliated with HighLevel. Product and provider interfaces can change; confirm the current HighLevel documentation before relying on this guide.