GoHighLevel Missed Call Text Back Not Working? 12 Causes and the Fix

A GoHighLevel missed call text back that does nothing is almost never a single bug. The feature is a chain: the call has to reach an LC Phone number, ring past a timeout, be recorded as missed, trigger the send, clear US carrier registration and land on a handset. Break any one link and the caller gets silence. This guide follows one test call through that chain and lists the twelve failures that account for most cases.

Why is GoHighLevel missed call text back not working?

It stops working when one of seven hops in the path fails: the carrier never hands the call to HighLevel, LC Phone never records it as missed, the trigger never fires, or the outbound text is blocked, suppressed or duplicated before it reaches the caller. In practice that reduces to twelve causes, listed below with the fastest check for each.

The table is written so you can match a symptom to a cause before reading further. “No text and no missed call in the log” points to the front of the chain (hops 1 to 3). “Missed call logged but no text” points to the back (hops 4 to 7). That single distinction saves most of the debugging time, because the two halves are fixed in entirely different parts of HighLevel.

#	Cause	Typical symptom	Fastest check
1	Number is not an LC Phone number	No call appears in HighLevel at all	Settings, Phone System, Phone Numbers
2	Carrier forwarding hides the missed call, or a port has not completed	Call log empty, or call shows as answered	Ask the carrier where unanswered calls go
3	Ring timeout mismatch	Voicemail answers before HighLevel decides the call is missed	Compare cell voicemail delay with the incoming call timeout
4	A2P 10DLC or toll-free verification not approved	Missed call logged, text fails	Settings, Phone System, Trust Center
5	Contact on DND or opted out	Works for you, not for that caller	Contact record, DND and communication preferences
6	Toggle plus workflow both active	Two texts, or none if one blocks the other	Automation, Workflows, filter by trigger
7	Feature unticked, or workflow still in Draft	Nothing ever fires	Voice settings tick box; workflow status
8	Wrong sender number	Text arrives from an unfamiliar number	Sending number priority in the help article
9	Number flagged or filtered by carriers	Sent in HighLevel, never delivered	Delivery status, test on several carriers
10	Internal calls triggering texts	Staff and vendors receive customer messages	Contact tags, workflow conditions
11	Repeat callers spammed	Same caller gets three texts	Native feature cannot filter repeats
12	No-response path missing	Caller replies to silence or never replies	Workflow follow-up and reply handling

Two caveats apply to every cause. First, HighLevel’s help articles change; the ones cited here carry September 2026 modification dates for the Missed Call Text Back and phone configuration pages, so re-check the current wording before relying on a specific number of seconds. Second, this guide separates what HighLevel documents from what practitioners report. Where a cause rests on inference or a vendor blog rather than HighLevel’s documentation, the text says so.

How does Missed Call Text Back actually work in HighLevel?

Missed Call Text Back is an LC Phone feature that sends an SMS to a caller when an inbound call goes unanswered past your incoming call timeout. HighLevel’s help article names its requirements as the LC Phone system and at least one SMS-capable number: A2P 10DLC-registered for local numbers, or toll-free verified for toll-free ones (HighLevel: Missed Call Text Back).

The setting lives under Settings, Phone System, Voice, then Voicemail and Missed Call Text Back. You tick Enable Missed Call Text Back, open Customize to write the message with merge fields such as the contact name, send a test and save. HighLevel’s own product blog post describes an older path under Phone Numbers, Advanced Settings, so navigate by the labels rather than a remembered click path.

What counts as a missed call?

HighLevel’s article says only calls that go unanswered past your incoming call timeout are treated as missed, and that answered calls never trigger a text. The distinction matters because a call answered by voicemail can still be a call the customer considers missed. HighLevel’s phone configuration article defines the timeout as the time the system lets an inbound call ring before it is dropped or forwarded to voicemail, and gives 60 seconds as the default that routes to personal voicemail (HighLevel: Phone number configuration options). The missed-call feature’s own slider is described as 10 to 20 seconds.

A workflow-based approach uses a different definition. The Call Status trigger reacts when a call reaches a status such as busy, canceled, voicemail, completed or not answered, with filters for call direction and call details (HighLevel: Workflow trigger, Call Status). HighLevel does not give formal definitions of each status in that article, so decide deliberately whether “voicemail”, “busy” and “no answer” should all count in your build.

Native toggle versus workflow

The toggle is one message, minimal setup and no branching. A workflow lets you add conditions, tags, tasks, pipeline moves and a follow-up. Both are legitimate. Problems appear when both run on the same number, which the duplicate-trigger section covers below.

Question	Native toggle	Workflow with Call Status trigger
Setup effort	Minutes	Longer, one build per rule
Repeat-caller control	None; texts on every missed call	Possible with conditions or cooldown
Business-hours branching	Not described in the help article	Possible in the workflow builder
Staff and vendor exclusion	Not available	Possible with tags or filters
Follow-up if no reply	Not available	Possible with a wait step and reply check
Failure visibility	Failed attempt logs in the conversation with the reason, per HighLevel	Workflow execution logs and enrollment history

Which number does the text come from?

HighLevel’s article lists a priority order for the sender: the called number if it is SMS-capable, then a number that previously messaged this contact successfully, then the default outbound number, then other eligible messaging numbers in the location. It also notes the SMS may come from a different number than the one called. If your customers see a number they do not recognize, that is documented behaviour rather than a fault, and it is cause 8 on the table above.

How do you trace one missed call through the seven hops?

Place one test call and follow it through seven hops: carrier, LC Phone, ring timeout, call status, trigger, A2P route and handset. At each hop you verify one fact in one place. The first hop that shows nothing is where the failure lives, and the fix belongs to that hop, not to a later one.

The seven-hop checklist

Run the checklist top to bottom with a single test call from a mobile phone that is not saved in the sub-account. Record what you see at each hop before moving on.

Hop	What to verify	Where in HighLevel or outside it	Pass looks like
1. Carrier	Calls to the public number reach HighLevel. Ask where no-answer and busy calls go	Carrier account or forwarding codes; Settings, Phone System, Phone Numbers	Inbound test call appears in HighLevel
2. LC Phone	The dialed number is an LC Phone number in this sub-account	Settings, Phone System, Phone Numbers	Number is listed, with SMS capability
3. Ring timeout	Timeout is short enough that HighLevel, not a cell voicemail, decides the outcome	Number settings, incoming call timeout; Voice settings slider	Call drops or routes to CRM voicemail on schedule
4. Call status	The call is logged as missed, busy, no answer or voicemail, not Completed	Conversations, call entry; call reporting	Status is not Completed
5. Trigger	The toggle is ticked, or the workflow is published and enrolled the contact	Voice settings; Automation, Workflows, Enrollment History	Exactly one send, not zero or two
6. A2P route	Number is A2P Verified or toll-free verified and the contact is not on DND	Settings, Phone System, Trust Center; contact record	Message shows a send attempt
7. Handset	Text arrives on the caller’s phone from the expected sender	The test phone	Message received within a few minutes

Steps 1 to 3 are covered in the next two sections, hop 4 in the section on cell forwarding, and hops 5 to 7 in the sections on registration, DND and duplicates. The complete test protocol, including log locations, is later in this guide.

Is your number actually an LC Phone number, or is a carrier forwarding it?

The feature only sees calls that arrive on an LC Phone number, so a business line that lives with a carrier or another provider is invisible to it unless the calls are forwarded in or the number is ported. This is the first hop and the first cause: if you see no call in HighLevel at all, stop here.

There are two supported patterns. In the first, HighLevel is your business number: customers dial an LC Phone number, HighLevel rings your team, and unanswered calls are missed by definition. In the second, your existing number forwards to a HighLevel number, and HighLevel’s help article on forwarding lists carrier codes for it: on Verizon Wireless, *72 plus the HighLevel number forwards all calls and *71 forwards missed calls; on T-Mobile the codes are **21*1 and **61*1 followed by the number and #; AT&T mobile uses *21; other carriers commonly use *72 for all calls and *92 for missed calls (HighLevel: Call forwarding to your HighLevel phone number). The article also says the caller is not notified of the redirect and warns against redirect loops.

Which forwarding mode did you set?

The mode decides what HighLevel can see. Forward all calls and HighLevel receives every call, including ones your team answered on another line; there the missed-call decision happens inside HighLevel and depends on the ring timeout and user assignment. Forward only unanswered calls and HighLevel receives only calls your phone already failed to answer, which is closer to what you want but means the caller has heard your phone ring first. The latter is a common pattern with the conditional codes above, and it is not a HighLevel setting you can inspect: you confirm it by asking the carrier or dialing the deactivation code and testing.

A frequent silent failure is a forwarding code that was set on a personal handset while the public listing number sits with a different provider. The handset forwards nothing because callers never dial it. Verify with a test call to the public number, not to the handset.

What about ported numbers?

A port moves the number from your old carrier to LC Phone so HighLevel becomes the network of record for it. HighLevel’s help center has porting guidance; this guide did not verify port timelines, so check that source for current lead times. The failure mode to know about is a number you believe is ported when the port is still pending. Until the port completes, your old carrier keeps answering the number, and HighLevel sees nothing. Treat the port as unfinished until a test call to the public number shows up in the HighLevel log.

Why does forwarding to a cell phone break the missed-call signal?

When HighLevel forwards an inbound call to an external phone, HighLevel cannot always tell a human answer from a voicemail greeting, so the call can be recorded as Completed and no text is sent. This is the most common reason a text back works in a test and fails for real customers.

HighLevel’s own Call Connect article explains the mechanism. It says the routing provider marks routed calls as Completed once they finish, including unsuccessful ones, so calls sent to voicemail, missed by the agent or timed out can still appear as successfully connected; when numbers forward to external phones or personal devices, distinguishing a human from a voicemail system becomes impossible without confirmation (HighLevel: Using Call Connect to ensure accurate call status tracking). Call Connect requires the agent to press a key, such as 1, before the parties are connected, and it is toggled per number under Settings, Phone System, in Advanced Settings.

How does the ring timeout mismatch happen?

Your cell has its own voicemail delay, typically a set number of rings. HighLevel has its own incoming call timeout. If your cell carrier’s voicemail answers at, say, 20 seconds and HighLevel is waiting 30, the carrier’s voicemail picks up first and the call ends as answered. The numbers here are illustrative; the principle is that the shorter timer wins, and you want HighLevel’s to be the shorter one.

HighLevel’s configuration article describes three tiers: the 60-second default routes to personal voicemail, roughly 20 seconds rings briefly and then routes to CRM voicemail, and 1 to 4 seconds sends the call straight to CRM voicemail. That third tier is useful for an office that never intends to answer live, and it fits the missed-call model cleanly: the text back is the primary response. For a team that does answer, aim for a timeout long enough for staff to get to the phone yet shorter than any carrier voicemail on the forwarded device.

Setup	What happens on no answer	Missed call recorded?	Fix
Timeout 60 seconds, forwarded to personal cell	Cell voicemail picks up first	Often no; may be Completed	Shorten the timeout or disable cell voicemail
Timeout about 20 seconds, CRM voicemail	HighLevel voicemail after brief ring	Yes	Keep; confirm status in call log
Timeout 1 to 4 seconds, CRM voicemail	Straight to CRM voicemail	Yes	Use only if no live answering is intended
Forwarded with Call Connect on	Agent must press a key to connect	Yes, unconfirmed calls do not count as answered	Enable on the number in Advanced Settings

Does voicemail interfere with the text?

Voicemail is designed to coexist. HighLevel’s article says the feature works alongside voicemail settings and that you can upload a custom voicemail in MP3 or WAV format. The caller hears the greeting, may leave a message, and receives the text. The greeting and text should say the same thing; a greeting that promises a call back and a text that asks for a reply pulls the caller in two directions. If you prefer callers to leave a message, say so in the text.

Is A2P 10DLC or toll-free verification blocking the text?

Yes, whenever the number has not cleared US carrier registration. HighLevel’s Missed Call Text Back article lists A2P 10DLC for local numbers or toll-free verification as a requirement, and notes that with no eligible sending number the failed attempt is logged in the conversation with the reason.

HighLevel’s registration overview says A2P registration is required when a business sends SMS or MMS to US recipients from standard 10-digit local numbers, that brand registration comes before campaign registration, that toll-free numbers follow a separate verification process rather than the 10DLC path, and that status is visible under Settings, Phone System, Trust Center, with approved numbers labeled A2P Verified under Phone Numbers (HighLevel: US phone number registrations). It also says a campaign can stay Pending while under review and advises against creating duplicates. If your registration was rejected, see the detailed code-by-code guide at GoHighLevel A2P 10DLC Registration Rejected rather than resubmitting blindly.

Two practical points follow. A missed call can be recorded correctly and still produce no delivered text, so a green call log does not prove the message worked. And a newly purchased number for a second location should be checked for its own A2P Verified label before you rely on the toggle there (this guide inferred that from the per-number label and did not find a HighLevel statement on it).

What if the registration is approved but the text still fails?

Approval clears registration, not every filter. Carriers may still filter individual messages by content, volume or reputation. This guide did not find a HighLevel article that describes reputation-based filtering of a missed-call text specifically, so treat this as general A2P behaviour that the CTIA messaging principles and carrier policies govern. Symptoms are a text that shows as sent in HighLevel but never arrives on some carriers. Test from handsets on at least two carriers, keep the message short and identifiable, avoid shortened public links and include your business name.

Does the wrong sender number matter?

It can. The sending-number priority order means the text may arrive from a number the customer has never seen, and a different number than the one called can cause the caller to ignore it or report it. Set a default outbound number that matches your public number, and if you run several numbers in one sub-account, confirm which one is first eligible for each. A caller texting back to the unfamiliar number will still reach the inbox, but the confusion costs replies.

Why does the caller get no text, two texts or ten?

Silence, duplicates and floods all trace to three places: the contact’s communication settings, duplicated automation, and the absence of any repeat-caller rule. Each has a distinct signature in the logs, which makes them quick to separate once you know where to look.

Could the contact be on DND or opted out?

Yes, and it is invisible to the caller. HighLevel’s article says the feature respects Do Not Disturb settings and communication preferences, and that a contact on DND will not receive the text. A contact who once replied STOP is suppressed by design. Open the contact record, check the DND toggle for SMS and the communication preferences before suspecting anything else. Test contacts are a frequent culprit: a colleague’s phone that opted out during earlier testing silently fails every later test and gives you a false “not working” result. That is cause 5.

Opt-outs are also a legal matter, not just a setting. The FCC’s rule text requires honoring a revocation made by any reasonable method, with replying STOP treated as valid, within ten business days (47 CFR 64.1200). Do not try to work around suppression.

Is the toggle plus a workflow causing doubles or zeros?

It can cause doubles and, less often, zeros. HighLevel’s Call Status article says the trigger activates for each status change and that the same call has multiple statuses in quick succession, so you need conditions or cooldown periods to avoid redundant actions. Layer that on top of the native toggle, which texts on every missed call, and one missed call can produce two messages. A vendor troubleshooting guide reports the same conflict as a top cause and advises disabling one of them; treat that as practitioner corroboration, not HighLevel documentation (GHL Scale Up, secondary source).

Zero texts arise when the workflow is left in Draft, so it never enrolls anyone, or when a workflow filter silently excludes the contact. The mechanics of published state, filters and re-entry are covered in GoHighLevel Workflow Not Triggering and are not repeated here. For missed-call builds specifically, open Enrollment History for the workflow and search for the test contact; if there is no enrollment, the trigger never matched, and the call-status hop is your problem.

Are internal calls and repeat callers being treated as customers?

They are, because the native feature has no allow-list and no repeat filter. HighLevel says it triggers for every missed call, including repeat attempts, and cannot filter repeated calls without workflow customization. A staff member calling from a personal phone, a vendor or a supplier receives the same customer text. A customer who rings three times in ten minutes receives three. The HVAC guide flags the internal-call failure in its own build notes (GoHighLevel for HVAC), and the plumber guide covers the add-a-wait-step recipe for repeats.

The fix is a workflow, not a setting: exclude contacts carrying a Staff, Vendor or Do-Not-Text tag, and add a condition or cooldown so a caller receives at most one message inside a window you choose. Whatever window you choose, write it down; an undocumented cooldown becomes the next mysterious failure.

Symptom	Likely cause	Where to confirm
No text for one caller only	DND, opt-out or an earlier STOP	Contact record, communication preferences
No text for anyone	Not enabled, no eligible number, A2P not approved	Voice settings tick box; conversation failure reason
Two identical texts	Toggle and workflow both active, or repeat status changes	Workflow enrollment history; native setting
Three texts to one caller	Repeat missed calls, no filter	Call log timestamps
Staff receive customer text	No internal exclusion	Contact tags, workflow conditions
Text from an unknown number	Sender priority order	Message details in the conversation

How should business hours, after-hours and the no-response path work?

The text should say something different at 2 a.m. than at 2 p.m., and it should have a plan for what happens if the caller answers or does not. HighLevel’s article says the feature is especially useful for after-hours calls because it acknowledges the caller and lets the conversation continue by text when the team is unavailable, but the pages reviewed for this guide do not describe a business-hours condition on the native toggle.

Can the native toggle change its message by time of day?

Not according to the help article reviewed. If you want an after-hours message that promises a morning callback, or a daytime message that says “we’re on another line”, build it as a workflow using the Call Status trigger with a time-based branch, and disable the native toggle for that number. HighLevel’s phone configuration article does not describe time-based routing either, so hours-based behaviour generally lives in workflow logic or in call flow and IVR settings that HighLevel documents separately. Verify the current option in your account before promising it to a client, since this guide did not confirm a specific hours setting.

What if the caller replies?

A reply is a new inbound message, and it needs a home. Decide who is assigned, how staff are alerted, and what an after-hours reply gets. Without a rule, the reply sits unread in the inbox, which wastes exactly the lead the text back recovered. A simple internal notification when the contact replies is the minimum.

What if the caller never replies?

Most will not. The single acknowledgement text from the native feature ends the sequence there. A workflow can add a wait, check whether the contact has replied or booked, and send one gentle follow-up. Keep it to one, and keep it inside your consent basis, which the TCPA section below covers. One follow-up that offers a booking link often does more than a second “sorry we missed you”.

How do you test a missed call text back end to end?

Call the public number from a mobile that is not saved as a contact, let it ring past the timeout without answering, and verify the outcome at each hop in order. Then repeat from three other starting conditions, because each condition fails differently.

The protocol

1. Use a spare mobile on a different carrier from your business line if possible. Confirm it is not a saved contact and is not on DND.
2. Call the public number, not the HighLevel number directly if they differ. Do not answer. Note the exact time.
3. Wait for the timeout plus a minute. Watch the handset.
4. Open the new contact’s Conversations thread. Confirm a call entry exists and read its status.
5. If no text arrived, open the same thread for a failed-send note; HighLevel logs the reason when no eligible sending number exists.
6. Open Automation, Workflows for any workflow using a Call Status trigger, then Enrollment History and execution logs for the test contact.
7. Check Settings, Phone System, Trust Center for brand and campaign status.
8. Repeat with (a) a saved contact, (b) a DND contact, (c) a second call within the same few minutes and (d) a call after hours.

Where are the logs?

Log	Location	What it tells you
Call entry	Conversations, the contact thread	Whether HighLevel saw the call and its status
Failed-send reason	Same thread, on the message	Why no eligible number or send failed
Workflow enrollment and execution	Automation, Workflows, Enrollment History	Whether the trigger matched and what steps ran
Registration status	Settings, Phone System, Trust Center	Brand and campaign approval or rejection
A2P label	Settings, Phone System, Phone Numbers	Whether the number is A2P Verified
Contact preferences	Contact record	DND and opt-out state

Log names and menu positions shift between HighLevel releases, so use the labels above as a guide rather than an exact path. Save screenshots of a passing test; they become the baseline you compare against after any later change.

What does a missed call cost, and what does fixing it cost?

Revenue at risk is calls times the missed share, times the share of missed callers who never call back, times your close rate, times average job value. The fix costs a few hours of setup and a trivial amount of SMS spend. The arithmetic below is illustrative: every input is an assumption you should replace with your own.

CallRail’s January 2025 benchmark of 1.1 million conversations reported missed-call rates by industry and stated that up to 85 percent of customers whose calls go unanswered will not call back (CallRail benchmark report, January 2025). It is a vendor dataset drawn from CallRail’s own customers and the 85 percent figure is an “up to” ceiling, so it is used here only as a reference and the base case below deliberately assumes far lower loss.

The formula and a worked base case

• Missed calls per month = calls per month x missed share
• Lost prospects = missed calls x callback-loss rate
• Jobs lost = lost prospects x close rate
• Revenue at risk = jobs lost x average job value
• Recoverable revenue = revenue at risk x text-back recovery rate

Illustrative base case: 300 calls a month, 20 percent missed, a 50 percent callback-loss rate, a 40 percent close rate, a $450 average job and a 25 percent recovery rate. That gives 60 missed calls, 30 lost prospects, 12 jobs and $5,400 a month at risk. At 25 percent recovery, that is 3 jobs, or $1,350 a month recovered.

Cost side, also illustrative: three hours of setup and testing at $75 an hour is $225 once. SMS cost is small: one vendor guide quotes about $0.0079 per segment (secondary source, verify against your own bill), so 60 texts at two segments each is roughly $0.95 a month. Payback is $225 divided by $1,350, about 0.17 of a month, or around five days, under these assumptions.

How sensitive is the result?

Scenario (illustrative)	Calls	Missed	Loss	Close	Job	Revenue at risk
Low	150	10%	30%	30%	$300	$405
Base	300	20%	50%	40%	$450	$5,400
High	500	30%	85%	50%	$600	$38,250

The spread is the point. A low-volume business with a light miss rate may have little at stake and be fine with the native toggle. A busy practice near the healthcare or legal miss rate has meaningful revenue behind the same handful of hops. Replace the missed share with your own count: pull four weeks of inbound unanswered calls from your phone system before choosing a value. Industry-specific ROI framing, including plumbing and electrical examples, is in the plumber and electrician guides; this section only adds the adjustable model.

Is an automatic text to a caller legal under the TCPA?

It depends on the content of the message and the consent you can show, so this is a question for a TCPA attorney rather than a settings page. The rule text prohibits autodialed or prerecorded calls to wireless numbers without the required consent, requires prior express written consent for telemarketing, and requires honoring opt-outs by any reasonable method within ten business days (47 CFR 64.1200).

A text that simply acknowledges a call the person placed and offers help sits at the lower-risk end of that spectrum, since the caller initiated contact, but it is not a safe harbor. A text that promotes a discount, or a scheduled follow-up sequence, moves toward marketing that needs documented written consent. The FCC’s one-to-one consent rule was vacated by the Eleventh Circuit in January 2025 and the FCC said in April 2025 it would not challenge that ruling, according to a law-firm summary (Consumer Financial Services Law Monitor, September 2025, secondary source), so the older written-consent standard applies.

Industry rules add another layer. CTIA’s messaging principles call for clear opt-out language, honoring STOP and related keywords and clear disclosure of who is messaging (CTIA Messaging Principles and Best Practices). Medical and legal senders should also consider that message content can be sensitive: keep the text free of health or case details, and write it so that it reveals nothing if a family member reads the screen. This is general information, not legal advice.

How do you stop it breaking again?

Treat the chain as something you audit on a schedule, not a feature you set once. Most repeat failures come from a change made elsewhere: a carrier change, a new workflow, a new number or a registration renewal.

• Run the seven-hop test monthly, and after any change to the phone system, carrier, forwarding, workflows or registration. Store the screenshot.
• Keep a one-page map of where each public number goes on ring, busy and no answer, and who owns each step.
• Choose one mechanism per number, toggle or workflow, and record the choice in the number’s notes.
• Tag staff and vendors and exclude them in the workflow; keep the tag list current.
• Watch Trust Center for status changes, and never create a duplicate campaign while one is Pending.
• Review the failed-send reasons in conversations weekly for the first month, then monthly.
• Keep the message short, name the business, and re-read it whenever your offers or hours change.
• After buying a number for a new location, repeat the whole chain for that number; do not assume it inherits the first location’s settings.

If a workflow stops firing after an edit, go to GoHighLevel Workflow Not Triggering, and if the number’s registration is rejected, use the A2P rejection guide. For a done-for-you build of the workflow version, the sister team at HighLevel Automation Team works on that layer.

Sources

• HighLevel Support, Where and how to configure the Missed Call Text Back feature (modified September 7, 2026).
• HighLevel Support, Overview of phone number configuration options (modified September 1, 2026).
• HighLevel Support, Workflow trigger: Call Status (modified July 24, 2026).
• HighLevel Support, Call forwarding to your HighLevel phone number.
• HighLevel Support, Using Call Connect to ensure accurate call status tracking (September 1, 2026).
• HighLevel Support, US phone number registrations: A2P 10DLC brand and campaign (modified September 4, 2026).
• CallRail, Benchmark report on small business marketing (January 15, 2025; vendor data).
• Legal Information Institute, 47 CFR 64.1200.
• CTIA, Messaging Principles and Best Practices (May 2023).
• Consumer Financial Services Law Monitor, FCC’s final rule on consent (September 2025; secondary).
• GHL Scale Up, GoHighLevel missed call text back guide (secondary; SMS per-segment cost and duplicate-trigger corroboration).