How to Get Your A2P Campaign Approved the First Time

A plain-language guide to registering SMS (A2P 10DLC) campaigns that pass carrier review.

Informational only — not legal advice. See the full disclaimer at the bottom of this page. Following this guide does not guarantee approval; approval decisions are made solely by The Campaign Registry, Telnyx, and the mobile carriers.

On this page

• What A2P registration is (in one minute)
• Before you start: the 3-item checklist
• The 3 reasons campaigns get rejected
• Field-by-field: what’s required vs. nice-to-have
• Worked examples by use case
• Sample-message library (good vs. bad)
• Opt-in narratives that pass
• STOP / HELP and keywords
• Privacy policy & terms requirements
• FAQ
• Legal disclaimer

What A2P registration is (in one minute)

To send business text messages from a regular 10-digit US number, the mobile carriers require your business (“brand”) and each texting program (“campaign”) to be registered with The Campaign Registry (TCR) through your messaging provider (Telnyx, in CallVisor’s case). Unregistered texting is filtered or blocked.

Registration is a review: a human (and automated checks) read what you submit and decide whether your program looks legitimate and whether your recipients actually agreed to be texted. Most rejections are not technical — they are because the submitted content reads as unfinished, generic, or as unsolicited outreach. This guide is about getting that content right so you pass on the first try and avoid the resubmission fee.

You register once from inside CallVisor (Trust Hub → A2P). CallVisor provides the registration rails and honors opt-outs (STOP) on your traffic. Obtaining and keeping consent from the people you text is your responsibility, not CallVisor’s — see the disclaimer.

Before you start: the 3-item checklist

Have these ready before you open the campaign wizard:

1. A live, public privacy policy URL that states you do not sell or share customers’ mobile information or opt-in consent with third parties or affiliates for marketing. This link is required — a blank or broken one is a guaranteed rejection. (See Privacy policy & terms.)
2. A clear answer to “how did these people agree to be texted?” — the single most important thing carriers evaluate. If you can’t describe a real opt-in (a form, a checkbox, or verbal consent captured on a recorded call), stop and fix that first. (See Opt-in narratives.)
3. Two real sample messages that name your business and read like messages sent to someone who already opted in. No placeholder text, no cold-outreach wording. (See the Sample library.)

The 3 reasons campaigns get rejected

These are the failure modes CallVisor’s wizard now warns you about. In order of how often they sink a registration:

1. A non-credible opt-in story (the #1 driver)

The Opt-In Workflow / Message Flow field is where carriers decide whether your recipients actually consented. Vague descriptions, or anything that reads as cold outreach to a purchased or scraped list, get rejected.

2. Leftover placeholder text

Template fragments left in your description, samples, or message flow — literally <Business name>, [Company], {{first_name}}, “your company,” “insert here” — make the submission read as unfinished. Reviewers reject it.

Fix: replace every bracketed or generic placeholder with your real business details before you submit.

3. Missing or placeholder privacy-policy link

Carriers run a brand-validation check and reject campaigns without a working privacy policy that addresses mobile data (registry rejection code 804). An empty field, or an obvious example URL like https://example.com/privacy, fails.

Fix: link to your own live privacy policy page that states mobile info and opt-in consent are not sold or shared for marketing. (See Privacy policy & terms.)

Also reinforce, across all fields: brand-named sample messages (not generic), STOP and HELP present, messages written as if to someone who already opted in, and working privacy (and, if used, terms) URLs.

Field-by-field: what’s required vs. nice-to-have

Worked examples by use case

Each example is illustrative — adapt it to your real business, your real opt-in, and your own policies (see disclaimer). The brands below are fictional.

Low Volume Mixed — conversational lead follow-up

Best fit for most CallVisor customers doing 1:1 lead follow-up.

• Description: “Summit Home Offers sends conversational text messages to property owners who, on a recorded phone call with our representative, agreed to be texted about a cash offer on their property. Messages relate to that inquiry.”
• Opt-in / message flow: “Opt-in is collected verbally on a recorded call. Our representative asks: ‘Is it okay if we text you at this number about your cash offer? Msg & data rates may apply; reply STOP to opt out, HELP for help. We won’t sell or share your mobile number.’ The recipient agrees, and the recording is kept as the consent record. We text only recipients who gave this consent. Privacy policy: https://summithomeoffers.com/privacy”
• Sample 1: “Summit Home Offers: thanks for speaking with us about a cash offer on your property. What’s a good time to go over the details? Reply STOP to opt out, HELP for help.”
• Sample 2: “Summit Home Offers: following up on the cash offer you asked about on our call — we can get you a no-obligation number. Reply YES to continue. Msg & data rates may apply. Reply STOP to opt out.”

Mixed — informational + promotional

• Description: “Anytown Realty sends appointment reminders and occasional property updates to clients who provided their number and consented on our website contact form.”
• Opt-in / message flow: “Contacts opt in on our website contact form (https://anytownrealty.com/contact) by entering their number and checking a consent box that says they agree to receive texts and can reply STOP to opt out. They receive a confirmation text.”
• Sample 1: “Anytown Realty: your showing at 123 Main St is confirmed for Tue 2 PM. Reply HELP for help, STOP to opt out.”
• Sample 2: “Anytown Realty: a new listing matching your criteria just hit the market. Want the details? Reply YES. Msg & data rates may apply. STOP to opt out.”

Customer Care — support & account responses

• Description: “Metro Property Management replies to tenant support requests and sends account/maintenance updates to tenants who provided their number on their lease application and agreed to text contact.”
• Opt-in / message flow: “Tenants provide their mobile number and agree to text contact on the lease application (a checkbox with disclosure). They can reply STOP at any time.”
• Sample 1: “Metro PM: your maintenance request #4821 is scheduled for Thu 9–11 AM. Reply HELP for help, STOP to opt out.”
• Sample 2: “Metro PM: we received your message and a team member will reply within one business day. Reply STOP to opt out.”

Marketing — promotional offers

Note: marketing use cases require the clearest opt-in of all — carriers are strictest here.

• Description: “Coastal Home Buyers sends promotional offers and market updates to homeowners who opted in through our online valuation form and agreed to marketing texts.”
• Opt-in / message flow: “Homeowners request a free valuation on our site (https://coastalhomebuyers.com/value), enter their number, and check a box agreeing to receive marketing texts (consent is not a condition of the valuation). Msg & data rates may apply; reply STOP to opt out.”
• Sample 1: “Coastal Home Buyers: your free home valuation is ready — want us to send it over? Reply YES. Msg & data rates may apply. STOP to opt out, HELP for help.”
• Sample 2: “Coastal Home Buyers: cash offers are up this month. Want an updated number on your property? Reply YES. STOP to opt out.”

Sample-message library (good vs. bad)

Every sample should: name your business, read like a message to someone who already opted in, and — in at least one sample — include STOP language.

Opt-in narratives that pass

This is the field that makes or breaks most registrations. Describe who your recipients are and exactly how they agreed to be texted. Any one of these models works if it’s true for you:

• Verbal consent on a recorded call. “During a recorded call, our rep asks permission to text about the inquiry; the recipient agrees; the recording is the consent record.” (Common for wholesalers/investors doing phone-first outreach.)
• Website form with a consent checkbox. “Contacts enter their number on our contact/ valuation form and check a box agreeing to receive texts; consent isn’t a condition of service; they get a confirmation text.”
• Point-of-sale / paperwork checkbox. “Customers provide their number and check a text- consent box on the application/agreement.”

Red flags that trigger a rejection (and the wizard’s warning):

• Contacting people from a purchased, scraped, or public list with no prior agreement.
• “Cold,” “public listing numbers,” “we found your number,” or “no opt-in.”
• A one-line stub that doesn’t say how consent was obtained.

Consent is your responsibility. CallVisor provides the registration rails and honors STOP; it does not obtain, verify, or store your recipients’ consent. Keep your own records (the recording, the form submission, the timestamp) — in a dispute, that record is your defense.

STOP / HELP and keywords

• Opt-out (STOP): keep the defaults — STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT — and an auto-reply confirming the person is unsubscribed. CallVisor honors STOP on your traffic automatically.
• Opt-in (START/YES): the words that (re)start messages, plus an auto-reply confirming enrollment.
• HELP: an auto-reply that names your business and gives a contact point (email or phone) plus a rate/frequency note. An anonymous HELP reply is itself a rejection cause.

Your registered STOP/HELP/opt-in wording is also what your live auto-responders converge to once the campaign is registered, so write them the way you want recipients to see them.

Privacy policy & terms requirements

• Privacy policy (required). A public page stating that mobile information and opt-in consent are not sold or shared with third parties or affiliates for marketing. Link to your own domain — not an example URL. This is the check that produces rejection code 804 when it’s missing.
• Terms & conditions (optional). Your SMS program terms. If your privacy policy already covers SMS, you can leave this blank.

If you don’t have a compliant privacy policy yet, create one before registering — it’s the single most common hard blocker.

FAQ

How long does approval take? Typically 1–3 business days at TCR, then up to ~1–14 days for the mobile carriers to provision. You’ll be notified as the status changes.

What does a rejection cost? Resubmitting a rejected campaign carries a review fee. Getting it right the first time avoids paying it twice — which is the whole point of this guide.

Can I change fields after submitting? Only some (sample messages, message flow, help message) can be edited in place. Your use case, description, keywords, and privacy/terms links are locked once submitted — getting them right up front matters.

What does “MNO provisioned” mean? The mobile carriers have activated your campaign. Once provisioned, the numbers in your linked group can send.

Legal disclaimer

This guide is provided by CallVisor for general informational purposes only. It is not legal advice, and it does not create an attorney-client relationship. CallVisor is a communications service provider — not a law firm, and not a compliance authority.

Following this guide does not guarantee that The Campaign Registry, Telnyx, or any mobile carrier will approve your campaign; those approval decisions are made solely by those third parties. You are solely responsible for the accuracy and legality of what you submit and send, for obtaining and keeping any consent required to message your recipients, and for your compliance with all applicable laws and carrier requirements — including the Telephone Consumer Protection Act (TCPA), state telemarketing and consent laws, and CTIA guidelines. Several US states impose stricter consent requirements than federal law; consult your own counsel about your specific situation.

The examples on this page are illustrative only and must be adapted to your actual business, your actual opt-in process, and your own policies. Copying example text you cannot truthfully stand behind is itself a compliance risk.

To the fullest extent permitted by law, CallVisor disclaims all liability for any rejection, delay, fee, fine, penalty, or damages arising from your campaign registration or your messaging. For advice about your specific situation, consult your own legal counsel.