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

# Leadping Docs

> Set up Leadping to receive approved leads, respond by SMS or call, and keep source, consent, and conversation context together.

Leadping helps teams turn approved lead submissions into fast, traceable follow-up. It receives leads from forms, partners, CRMs, and internal systems, keeps source and consent context attached, and gives your team one place to text, call, route, review history, and continue the conversation.

These docs are written for the people who launch and operate that workflow: account owners, lead operations teams, compliance reviewers, and developers building integrations.

## What Leadping helps you do

* Accept leads from approved sources without losing source, campaign, product, state, or tag context.
* Keep TrustedForm and other consent evidence connected to the lead record.
* Give teams a shared inbox for SMS, calls, replies, missed interactions, notes, and history.
* Prepare phone numbers for production calling and texting through TrustedSetup and carrier registration.
* Build API, SDK, and MCP-assisted workflows around Leadping data.
* Maintain clearer records for source review, disputes, opt-outs, suppression, and support.

## Where to start

| Goal                                             | Start here                                                                                                           |
| ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
| Launch your first account, source, and number    | [Get Started](/get-started)                                                                                          |
| Connect a form, partner, CRM, or posting system  | [Lead Sources](/lead-sources), then [Sending Leads to Leadping](/sending-leads-to-leadping)                          |
| Require and validate consent evidence            | [Requiring TrustedForm](/requiring-trustedform)                                                                      |
| Prepare SMS or calls                             | [TrustedSetup](/trustedsetup), [Carrier Registration](/carrier-registration), and [Compliance Overview](/compliance) |
| Build with the API or SDKs                       | [API Reference](/api-reference) and [SDKs](/sdks/overview)                                                           |
| Connect an AI assistant to the docs              | [MCP Server](/mcp-server)                                                                                            |
| Review policy, privacy, deletion, or legal terms | [Terms of Service](/terms-of-service), [Privacy Policy](/privacy-policy), and [Subprocessors](/subprocessors)        |

## Launch path

Most production launches follow the same path:

1. Define the first lead workflow.
2. Confirm business, website, billing, and support details.
3. Create and approve the source that will send leads.
4. Confirm the consent path and TrustedForm handling.
5. Prepare the phone number, SMS use case, and call or message plan.
6. Send a test lead from the real posting system.
7. Confirm the record, conversation, routing, automations, opt-out handling, and reporting.

The fastest launches are specific. One approved source, one clear consent path, one ready number, and one tested follow-up workflow are easier to approve and operate than a broad setup that tries to cover every future campaign.

## What to have ready

Leadping setup often depends on information outside the app. Keep these details available before production traffic starts:

* Business, billing, and source details needed during setup
* Phone-number readiness, carrier registration, and SMS availability
* TrustedForm and other consent evidence for submitted leads
* Source credentials and payload expectations for lead intake
* Opt-outs, prohibited content, and compliance-sensitive workflow checks
* Terms, privacy, deletion, BAA, subprocessors, and other policy references

Leadping helps organize the operational records around outreach, but it does not make a lead lawful, guarantee carrier approval or message delivery, or replace your own legal review. Your team is responsible for source quality, consent, suppression, message content, calling rules, and how each lead is used.