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

# Welcome to Leadping

> Learn how Leadping connects lead intake, consent evidence, conversations, automation, and outcomes in one traceable workflow.

Leadping helps teams receive, contact, route, and manage leads without losing the context behind each conversation.

Use the source to establish where a lead came from, the lead record to review its details and processing status, and the conversation to continue the contact history. External submissions must carry supported [consent evidence](https://leadping.ai/docs/requiring-trustedform.md) associated with that person’s form submission.

## Choose a starting point

> [card] [Launch Leadping](https://leadping.ai/docs/get-started.md)
>
> Prepare one source, one response workflow, and one controlled production launch.

> [card] [Send leads](https://leadping.ai/docs/sending-leads-to-leadping.md)
>
> Connect a form, partner, CRM, or posting system.

> [card] [Build with the API](https://leadping.ai/docs/developers/overview.md)
>
> Choose credentials, endpoints, SDKs, and webhooks.

> [card] [Review trust and security](https://leadping.ai/docs/trust/overview.md)
>
> Understand data protection, privacy, and shared responsibility.

## How the workflow fits together

1. **Source** — Identify the website, form, partner, or system that produced the lead.
2. **Evidence** — Supply a Leadping or TrustedForm certificate, or explicitly attest to Other consent for manual texts only. See [consent states](https://leadping.ai/docs/requiring-trustedform.md#consent-states).
3. **Intake** — Preserve contact, campaign, product, state, tags, and source metadata.
4. **Conversation** — Assign, text, call, automate, and continue from one history.
5. **Control** — Apply number readiness, carrier, suppression, opt-out, and workflow checks.
6. **Outcome** — Review what happened and keep the operational record connected.

## Understand the records

| Record | Question it answers | Example |
| - | - | - |
| Source | Which integration submitted this lead? | A website quote form with its own intake key |
| Lead | Who requested contact, and what information was supplied? | Contact details, an external ID, and a certificate URL |
| Conversation | What has already been said or done? | Messages, calls, and notes that give the next operator context |
| Automation | What configured work should happen for a matching event? | Follow-up steps that you review before enabling |
| Lead status | What is the business outcome? | A status your organization uses to track progress |

Processing status and business status answer different questions. **Ready** describes lead processing; it does not mean the person has replied, an appointment was booked, or a sale was made. Check the conversation and recorded outcome for those results.

For example, a quote form can create a lead successfully while SMS is still unavailable on the selected number. Investigate intake and sending separately instead of submitting the same lead again.

## Start with one workflow

The most reliable first launch is intentionally small:

* one clearly named lead source;
* one documented consent path;
* one ready phone number or follow-up route;
* one clear owner for replies, failures, and opt-outs; and
* one end-to-end test from the production posting system.

Increase traffic only after the submitted lead, conversation, routing, and safeguards behave as expected.

> [!NOTE]
>
> Leadping provides workflow and recordkeeping controls. It does not make a lead lawful, replace legal review, guarantee carrier approval, or guarantee delivery. Your organization remains responsible for consent, source quality, contact rules, message content, suppression, and use of each lead.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.