> ## 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.

# Let Leadping Handle A2P 10DLC Registration

> Provide the business and messaging details Leadping needs to handle A2P 10DLC registration for you.

U.S. business texting from local numbers commonly requires A2P 10DLC brand and campaign registration before production messages can be sent.

Leadping coordinates and submits the registration on your behalf through its messaging providers, using the information collected during onboarding. You do not need to submit a separate brand or campaign application directly.

You remain responsible for providing accurate business, website, consent, source, use-case, and message information and completing any requested verification. Carriers, registries, and messaging providers make the approval decision and control review timing.

<Note>
  Carrier registration covers the described SMS use case. [TrustedSetup](/docs/trustedsetup) prepares the individual Leadping number. A production workflow may require both.
</Note>

## When registration applies

Expect registration for business SMS from a local U.S. number. Leadping identifies and manages the registration path required for the account, number, and use case.

Do not send production SMS until the required registration is approved and the number is ready.

## What you provide

Leadping uses:

* legal business name, DBA, tax ID, and address;
* a public website for the sending brand;
* privacy-policy, terms, and support links;
* the production opt-in page and exact SMS disclosure;
* the production lead source and TrustedForm flow;
* a plain-language use-case description;
* representative SMS messages;
* opt-out and HELP responses; and
* products, audiences, states, links, and expected volume.

All information must describe the same sender and workflow.

## Track registration

Open **Settings → 10DLC** to review the application assembled from the organization profile. The page shows:

* the customer-facing status;
* organization and contact details;
* use case, expected monthly volume, and message examples;
* opt-in language, privacy policy, terms, and TrustedForm requirement; and
* registration events and logs.

| Status             | Meaning                                                   |
| ------------------ | --------------------------------------------------------- |
| Not started        | No application workflow has started                       |
| Application review | The draft exists but may still be incomplete              |
| Ready to submit    | The draft is ready for the provider submission step       |
| Carrier review     | The brand or campaign has been submitted                  |
| Approved           | Registration completed successfully                       |
| Needs attention    | The provider rejected the submission or requested changes |
| Setup issue        | A registration operation failed and needs intervention    |

## Submission standard

| Area        | What reviewers need                                                          |
| ----------- | ---------------------------------------------------------------------------- |
| Business    | Matching legal name, DBA, website, address, tax details, and support contact |
| Website     | A public, working site clearly associated with the sender                    |
| Consent     | SMS disclosure shown where the phone number is collected                     |
| Source      | A clear explanation of the form, publisher, or partner path                  |
| Use case    | A specific description of why and when messages are sent                     |
| Examples    | Realistic messages that identify the sender and match the use case           |
| Preferences | Clear STOP and HELP behavior                                                 |
| Links       | Domains owned by or clearly connected to the sender                          |

## Write the use case

A useful description answers:

1. Who sends the message?
2. What did the person request?
3. Where and how did they opt in?
4. What messages will they receive?
5. How often might messages arrive?
6. How can they opt out or get help?

Use concrete language:

```text theme={null}
<Business or brand> sends SMS to people who request <product or service>
through <source or form>. Messages help the recipient <specific purpose>,
may include <message types>, and include opt-out instructions.
```

Do not broaden the description to cover future campaigns with different sources, consent, products, audiences, or content.

## Prepare message examples

Examples should:

* identify the sending business or brand;
* match the submitted use case;
* sound like actual production messages;
* use the same domains planned for production; and
* demonstrate expected opt-out language.

Avoid generic examples such as `We are following up on your request` when the real product, sender, and purpose can be stated.

## Common blockers

| Blocker                                 | Correction                                                           |
| --------------------------------------- | -------------------------------------------------------------------- |
| Missing, private, or incomplete website | Publish the business, contact, policy, and offer information         |
| Brand and business mismatch             | Align the legal name, DBA, website, sender, and support details      |
| Missing SMS disclosure                  | Show clear consent language where the number is collected            |
| Unclear source                          | Document the real form, publisher, partner, and TrustedForm path     |
| Vague or mismatched examples            | Use realistic messages tied to the registered purpose                |
| Unrelated links or redirects            | Use domains associated with the registered sender                    |
| Restricted or prohibited category       | Review [Forbidden Message Categories](/docs/forbidden-message-categories) |
| Workflow changed during review          | Update the registration before sending traffic                       |

## Review outcomes

| Outcome          | Next step                                                                    |
| ---------------- | ---------------------------------------------------------------------------- |
| Approved         | Complete number readiness and controlled testing                             |
| Changes required | Correct the requested business, website, consent, source, or message details |
| Rejected         | Do not send the proposed traffic through that registration path              |

Approval does not guarantee delivery, throughput, or continued eligibility. Carriers and providers may filter, throttle, audit, or request updates.

## After approval

Keep production traffic within the registered business, source, consent path, use case, messages, links, audience, and numbers.

Pause affected traffic and contact [support@leadping.ai](mailto:support@leadping.ai) before a material change. A registration update or new review may be required.

## Launch checklist

* The number completed [TrustedSetup](/docs/trustedsetup).
* Required carrier registration is approved.
* The production source uses its own key and includes TrustedForm with every lead.
* Production messages match the registered use case.
* STOP, HELP, replies, complaints, and support requests have owners.
* A controlled end-to-end test passed.