HighLevel missed-call text-back 30909 rejections usually need better CTA evidence.
Use this checklist when a missed-call text-back campaign is rejected because reviewers cannot verify how the caller was told they may receive the automated SMS follow-up.
HighLevel's missed-call text-back feature sends an automated SMS after an inbound call is missed. A 30909 rejection usually means the reviewer could not verify the call-to-action or message flow that explains how the person consented to that SMS program.
Do not rely on the phrase "they called us" as the only consent explanation.
Show where the caller saw the business identity, phone number, messaging disclosure, privacy link, and terms link before the automated text fired.
List every opt-in path used by the campaign, including website forms, contact pages, QR codes, signage, verbal scripts, paper forms, or other offline flows.
If the proof lives behind a login or offline, prepare hosted screenshots or public evidence the reviewer can access.
Evidence to collect before resubmission
Treat the missed inbound call as the automation trigger, then document the consent evidence that came before it. The reviewer needs a complete path from first CTA to first SMS.
The page, ad, form, voicemail, signage, or script that invited the person to call or request follow-up.
SMS disclosure language near the phone-number collection or call-to-action, including message type, frequency, rates disclosure, and opt-out instructions where applicable.
Public privacy policy and terms URLs tied to the same client brand, with mobile non-sharing language where required by the provider flow.
Screenshots showing the consent experience exactly as the caller or prospect sees it.
A message-flow description that explains the missed-call automation and every other path that can produce an SMS.
First SMS sample direction
The first missed-call reply should identify the brand and explain why the person is receiving the message. Keep it customer-care or conversational unless the campaign also has separate marketing consent.
[Business Name]: Hi [First Name], we missed your call about [Topic]. Reply here or call [Phone Number]. Reply HELP for help. Reply STOP to opt out.
[Business Name]: Sorry we missed you. Our team can help with [Service Request]. Reply 1 for a callback, HELP for help, or STOP to opt out.
Avoid discounts, lead-nurture sequences, review requests, or referral asks unless the selected use case and consent path cover promotional messaging.
If the live message includes a link or phone number, make the sample message and provider flags reflect that.
What not to put in the message flow
Short or generic message-flow language is the common failure pattern. Reviewers need a clear, verifiable workflow, not a description of the automation button.
Do not write only "Customers call us and we text them back."
Do not describe missed-call text-back without naming the business phone number, CTA location, privacy URL, terms URL, and disclosure path.
Do not mix support replies with marketing offers unless the campaign and consent language are separated appropriately.
Do not use a generic agency brand when the caller expects the local client brand.
Do not create repeated SMS loops from every missed call without documenting how duplicates, opt-outs, and customer replies are handled.
HighLevel workflow check
HighLevel documents missed-call text-back as an automatic SMS response for missed inbound calls. Before resubmission, confirm the configured message, sender number, and workflow controls match the campaign evidence.
Capture the HighLevel missed-call text-back setting, message body, sender number, and any workflow conditions or filters.
Check whether the feature sends on every missed call and whether the account needs wait steps, tags, or guardrails to avoid repeated follow-up texts.
Keep the automated reply aligned with the declared use case, such as customer care, appointment follow-up, or service request handling.
Document HELP, STOP, and support handling so the reviewer sees how the recipient can get help or opt out.
How A2P Desk checks it
Client intake keeps the campaign description, message flow, sample SMS, phone-number flags, policy URLs, terms URLs, screenshots, and rejection text in one review record.
Preflight compares the missed-call text-back sample against the consent evidence, website context, sender identity, and selected use case.
Submission packs preserve HighLevel-ready paste fields plus evidence notes for agency review.
This is workflow support only. It is not legal advice and does not guarantee HighLevel, TCR, carrier, Twilio, or provider approval.