Skip to main content
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.
Carrier registration covers the described SMS use case. Number health is an optional monthly add-on for individual numbers. Required carrier registration applies independently of this add-on.

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

​
Submission standard

​
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:
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.

​
Example for a single quote-request workflow

This fictional example illustrates the level of detail to provide; adapt it to the actual form and messages rather than submitting it unchanged.
Acme Solar follows up with people who request a residential solar quote through the quote form on its website. The form identifies Acme Solar as the sender and records the person’s SMS opt-in. Messages discuss the requested quote and scheduling a consultation. The application describes the expected frequency and includes the production opt-in, STOP, and HELP text.
An accompanying message might be: “Hi Jordan, this is Acme Solar about the quote you requested. Is tomorrow afternoon a good time to discuss your project? Reply STOP to unsubscribe.” Use your actual brand, purpose, domains, frequency, and disclosures. This example is not consent language or a promise of carrier approval.

​
Respond to a request for changes

Read the specific review feedback before editing the application. If the issue is a website or disclosure mismatch, correct the production page as well as the submitted description. Keep the page URL and a dated screenshot showing the correction. After updating the relevant information, check the registration page for the next action or contact support with the application status and review feedback. Repeatedly submitting unchanged information does not resolve the blocker.

​
Common blockers

​
Review outcomes

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 before a material change. A registration update or new review may be required.

​
Launch checklist

  • The number is enabled and ready for the intended channel. The optional Number health add-on is not required for registration.
  • 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.