Tired of getting your A2P number rejected?This will help. 💚

The most common causes are structural, not creative: no website at all, a website with no reachable privacy policy, an opt-in flow the reviewer couldn't find, or a legal business name that doesn't match your EIN records. Carriers and The Campaign Registry review the URL you submit, so anything missing on the page is a rejection even if your use case is legitimate. Fixing the website usually means fixing the privacy policy, the terms page and the opt-in disclosure at the same time — which is exactly what this tool generates.

In practice, yes. Twilio requires a PrivacyPolicyUrl and a Terms and Conditions URL on campaign registration, and a URL has to resolve somewhere. Beyond the API requirement, reviewers use your site to confirm the business is real and that consumers are told what they're opting into. A Facebook page or a bare booking form usually isn't enough on its own.

They are the required-field errors: 30933 means your submission is missing a valid privacy policy URL, 30934 means it's missing the terms and conditions URL. The API returns a 400 — nothing reaches the carriers, so there is nothing to appeal. The fix is to supply two publicly reachable HTTPS URLs and resubmit. Generating a site here gives you both, on the same domain, in one pass.

It means a privacy policy exists but doesn't meet the messaging-specific requirements. Reviewers look for a policy that states what data you collect, describes SMS consent specifically, and says mobile opt-in data and phone numbers are not shared or sold to third parties for their own marketing. Generic e-commerce boilerplate typically fails here because it says the opposite.

Off-the-shelf policy generators are written for general web privacy, not for CTIA and carrier messaging rules. They routinely include broad clauses permitting data sharing with partners, affiliates and advertisers — the clause carriers most often reject. A 10DLC policy has to carve out mobile information and SMS consent explicitly and state it isn't shared with third parties for marketing.

The consent disclosure should sit next to the field or checkbox where consent is given — not buried in a footer — and should name your business, describe what messages the person will receive, and include message frequency, that message and data rates may apply, how to stop (reply STOP) and get help (reply HELP), plus links to your privacy policy and terms. If consent is collected by checkbox it should be unchecked by default and not bundled with other agreements.

A thin page that is just a logo and a signup form is a common rejection reason — reviewers want evidence of an operating business, not a form. That's why A2PFree generates a full site: home, about, services, contact, privacy policy and terms, with your legal name and address consistent across every page. It won't turn a nonexistent business into an approved one, but it removes the website-side reasons a real business gets rejected.

Brand registration fails when the legal business name or EIN you submit doesn't match IRS records character for character, including punctuation and abbreviations. The CP-575 is the authoritative source, so the tool reads it and reproduces the name and address verbatim rather than asking you to retype it. If you can't find your CP-575 you can type the details manually, or request a 147C letter from the IRS.

Fifteen days covers the review window for most campaigns, but carriers can spot-check sites after approval and re-review them when you file additional campaigns. Treat the free subdomain as a way to get unblocked, not a permanent home: before it expires, point your own domain at the same content or move the pages to your real website. The generated HTML is yours to keep and rehost anywhere.

No. It generates and hosts the website, privacy policy, terms and opt-in disclosure — you still register your brand and campaign in Twilio, your CPaaS console or via the API, and you paste in the URLs it gives you. Approval is the carriers' and The Campaign Registry's decision, and depends on your business, use case and opt-in flow as much as your site. Agencies registering many sub-accounts can use the free API.