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

# TrustedSetup

> Prepare each Leadping phone number for production calling, texting, routing, registration alignment, and first-use review.

*Revision Date: June 28, 2026*

TrustedSetup is the one-time readiness process for a Leadping phone number. It is required before that number is used for production calls or texts.

Think of it as number provisioning, routing setup, registration alignment, and first-use review for a specific number. A business can be approved and still need TrustedSetup for each number it wants to use.

The outcome is a number that is connected to the right business, source, use case, team, and safeguards before real leads start receiving calls or messages.

## When you need it

TrustedSetup is needed when you add a new Leadping number for production use, including:

* A first number for a new account
* An additional number for more capacity or routing
* A replacement number
* A number that will be used for a new or materially changed workflow

Do not send production calls or texts from a number until Leadping shows it is ready.

## What ready means

A ready number has the operational pieces in place for its intended workflow:

* It belongs to the right Leadping account and business.
* It is assigned to the right team, route, or workflow.
* Voice and SMS readiness have been checked for the intended use.
* Carrier registration is aligned where SMS registration applies.
* The source, consent path, call purpose, or message use case is understood.
* Opt-out, suppression, and early-traffic monitoring expectations are clear.

Readiness does not guarantee carrier approval, delivery, answer rates, or legal compliance. It means the number passed the Leadping setup checks required before production use.

## What Leadping checks

For each new number, Leadping checks and configures the pieces needed to use that number in production:

* Number provisioning
* Business and account alignment
* Intended use case
* Routing and assignment
* SMS and voice readiness
* Carrier registration status where SMS registration applies
* Approved lead sources
* Consent evidence requirements
* Opt-out and suppression readiness
* Initial traffic safeguards and monitoring

The exact work depends on the number, account, traffic type, and registration status.

## What to prepare

Before requesting a number, have the core setup details ready:

* Business identity and website
* Support email or phone number
* Lead source details
* Consent path or TrustedForm expectations
* Intended SMS and call use case
* Example message copy if the number will text leads
* Call script or call purpose if the number will be used for voice
* Any carrier registration details already requested by the app or support

Incomplete or inconsistent details are the most common reason setup takes longer.

## Why each number needs it

Each phone number is its own production endpoint. A number has its own provisioning status, registration relationship, routing, usage pattern, and traffic history.

Adding a number also increases the account's calling or texting capacity, so Leadping reviews every new number before production use.

## TrustedSetup fee

TrustedSetup is a one-time fee for preparing a specific phone number. It is separate from:

* Monthly phone-number rental
* SMS or call usage
* Carrier registration fees shown during setup
* Provider or carrier pass-through charges

If you add another number later, that number has its own TrustedSetup fee.

## What can delay setup

Setup can pause when Leadping needs clearer information about:

* Business identity or website
* Carrier registration status
* Lead sources or consent flow
* Message copy, call purpose, or campaign use case
* Opt-out handling
* Restricted or forbidden content
* Routing, assignment, or team ownership

If setup pauses, support will ask for the missing detail or required change.

## After a number is ready

Before using the number at volume:

* Confirm the number is assigned to the right account, workflow, and team.
* Send or receive a controlled test interaction.
* Confirm calls, messages, replies, and missed events appear in the expected conversation.
* Confirm opt-out handling works for SMS.
* Keep early traffic aligned with the approved source, use case, and sample messages.

Contact support before changing the source, audience, product, message copy, call purpose, link domains, or sending pattern tied to the number.

## Related pages

* [Carrier Registration](/carrier-registration)
* [Lead Sources](/lead-sources)
* [Requiring TrustedForm](/requiring-trustedform)
* [Compliance Overview](/compliance)