> ## Documentation Index > Fetch the complete documentation index at: https://leadping.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Carrier Registration > Prepare a Leadping SMS use case for carrier registration with aligned business, website, source, consent, opt-out, and sample-message details. *Revision Date: June 28, 2026* Business SMS usually needs carrier registration before production texting can start. In the United States, local business texting commonly uses A2P 10DLC brand and campaign registration. Registration tells carriers and messaging providers who is sending messages, what recipients signed up to receive, and how recipients can opt out. Leadping helps gather the details and route the submission, but carriers, registries, and providers decide whether the registration is approved, delayed, or rejected. Treat registration as part of launch readiness, not paperwork after launch. The same brand, website, opt-in language, sample messages, lead source, and sending number should tell one consistent story. ## When registration applies Expect registration when you plan to send business SMS from a Leadping phone number, especially from a local U.S. number. The app or support will tell you what is required for your account, number, and use case. Do not assume a number can text production leads just because it has been provisioned. Number setup and carrier registration are separate readiness steps. ## Fastest path to approval Carrier review moves faster when the registration package is plain, specific, and consistent: | Area | Strong submission | | ----------------- | ------------------------------------------------------------------------------ | | Business identity | Legal name, DBA, website, support contact, and tax details match | | Website | Public, reachable, and clearly tied to the sender brand | | Consent path | Shows the SMS disclosure where the phone number is collected | | Source details | Explains where leads come from and who owns the form or partner path | | Use case | Describes the real follow-up workflow in concrete language | | Sample messages | Match the use case, identify the sender, and include expected opt-out language | | Links | Use domains that belong to or clearly support the registered sender | ## Registration package Have these details ready before registration: * Legal business name, DBA, EIN or tax ID, and business address * Public website using the same brand that will send messages * Privacy policy and terms links * Support email or phone number * Campaign use case in plain language * Example SMS messages * Opt-in form URL or screenshot * Consent language shown where the phone number is collected * Opt-out and HELP language * Lead source details, including publishers or partners when relevant The fastest registrations are straightforward and consistent: the business name, website, opt-in page, sample messages, link domains, and campaign description all describe the same sender and use case. ## Writing the use case Describe what will actually happen after a person opts in. A useful use-case description answers: * Who sends the message? * Why is the person receiving it? * What product, service, or request does it relate to? * How often might messages be sent? * How can the person opt out or get help? Avoid vague descriptions such as "marketing messages" or "lead follow-up" when the real workflow is more specific. Reviewers need enough detail to compare the description, opt-in language, sample messages, and website. A stronger description usually follows this pattern: ```text theme={null} sends SMS to people who request through . Messages help the recipient complete or discuss that request, may include appointment or follow-up reminders, and include opt-out instructions. ``` Keep the description truthful to the actual workflow. Do not broaden the use case to cover future campaigns that have different sources, consent language, products, or message content. ## What reviewers look for Reviewers want to see that: * The business is real and reachable. * The website matches the sender and campaign. * Recipients can understand what they are signing up for. * The opt-in language names the sender and message type. * Sample messages match the campaign description. * Links point to the registered business. * Opt-out instructions are clear. * The use case is allowed by carrier rules. If registration details do not match the website, consent flow, source, or actual messages, expect delays or a request for changes. ## Common blockers Carrier registration often stalls for fixable reasons: * Missing or private website * Website brand does not match the legal business or DBA * Privacy policy, terms, or contact information are missing * Opt-in form does not show clear SMS consent language where the phone number is collected * Sample messages are too vague or do not identify the sender * Message links use unrelated domains or redirects * Lead sources are not explained * The requested use case falls into a restricted or forbidden category * The actual traffic changed after the registration was submitted Fix the blocker, then ask support to continue the review or resubmit when appropriate. ## Review outcomes Carrier registration usually ends in one of these outcomes: | Outcome | What it means | | ------------- | ------------------------------------------------------------------------------------------------------------------- | | Approved | The submitted business and use case passed review for the relevant campaign path | | Needs changes | Reviewers need corrected details, clearer consent, better sample messages, or updated website content | | Rejected | The use case, business details, source, consent path, or content is not acceptable for the requested messaging path | Approval does not guarantee delivery, throughput, message eligibility, or future approval after changes. Carriers and providers may still filter, block, throttle, audit, or require updates. ## After approval Approval applies to the submitted business, use case, campaign, number, links, and consent path. Keep production traffic aligned with that setup. Contact [support@leadping.ai](mailto:support@leadping.ai) before changing: * Business name, DBA, website, privacy policy, or terms * Lead sources, opt-in language, or posting integrations * Message copy, links, campaign purpose, or sending frequency * Phone numbers used for the campaign * Products, states, verticals, or audiences Material changes may need a registration update or a new review. ## Before production SMS Before sending production messages, confirm: * The sending number completed [TrustedSetup](/trustedsetup). * Carrier registration is approved where required. * The lead source is approved and sending valid consent evidence. * Sample messages match the approved use case. * Opt-out and HELP behavior is ready. * Your team knows who handles replies, complaints, and support requests. ## Related pages * [TrustedSetup](/trustedsetup) * [Lead Sources](/lead-sources) * [Requiring TrustedForm](/requiring-trustedform) * [Compliance Overview](/compliance) * [Forbidden Message Categories](/forbidden-message-categories)