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

# Operate a Responsible Lead Workflow

> Keep lead source, consent evidence, sender identity, message purpose, timing, and recipient preferences aligned.

Responsible outreach begins with a traceable answer to three questions:

1. Where did this lead come from?
2. What did the person agree to receive, from which sender, and through which channel?
3. Why does the planned contact match that agreement?

If any answer is unclear, do not contact the lead. Correct the source, consent record, sender, message, or workflow first.

> [!NOTE]
>
> This page is an operational guide. The [Terms of Service](https://leadping.ai/docs/terms-of-service.md) and [Acceptable Use Policy](https://leadping.ai/docs/acceptable-use.md) contain the formal requirements.

## Keep the workflow aligned

| Control | Required outcome |
| - | - |
| Source | The actual form, publisher, partner, or system is identifiable and uses its own source key |
| Consent evidence | Each lead has supporting evidence or explicit Other attestation; [consent state](https://leadping.ai/docs/requiring-trustedform.md#consent-states) determines whether manual or automated outreach is permitted |
| Sender | The contacting business or brand matches the disclosure |
| Channel | The consent supports the intended call or message |
| Content | The outreach matches the offer and reason for opt-in |
| Timing | Contact hours and frequency follow applicable requirements |
| Preferences | Opt-outs, DNC requests, and suppression records are honored |

## Before production traffic

**1. Identify the source**

Create a source for the real form, publisher, partner, or posting path and use its key for intake.

**2. Verify the evidence**

Confirm the production form captures consent and supplies a [supported certificate or explicit attestation](https://leadping.ai/docs/requiring-trustedform.md#api). Other attestation permits manual texts only; it cannot enable automated outreach.

**3. Prepare the sender**

Align the legal business, brand, website, public policies, phone number, and message identity.

**4. Test the complete route**

Submit a real test lead and verify intake, conversation, routing, opt-out, suppression, and reporting behavior.

Begin with controlled volume. Review complaints, opt-outs, delivery failures, source disputes, and conversation outcomes before scaling.

## Stop conditions

Pause contact and investigate when you find:

* an unknown, disabled, disputed, or misidentified source;
* missing or disputed consent, or malformed, unreachable, reused, or mismatched evidence in a certificate-based workflow;
* a sender, product, state, audience, or use case different from the reviewed setup;
* a number that is not ready for the intended channel or has not completed required carrier registration;
* a prior opt-out, DNC request, or suppression match;
* prohibited or misleading content; or
* unusual complaint, failure, opt-out, or abuse signals.

Passing a technical validation does not guarantee lawful outreach, carrier acceptance, or delivery.

## When the workflow changes

Treat a material change as a new launch. Pause affected traffic and contact [support@leadping.ai](mailto:support@leadping.ai) before continuing after changes to:

* the business, brand, website, privacy policy, or terms;
* the source, publisher, form, opt-in language, or posting path;
* the product, state, audience, or expected volume;
* the sender, number, first message, call script, links, or use case; or
* opt-out, DNC, suppression, routing, or automation behavior.

## Work through a disputed lead

Suppose a recipient says they never requested contact. Stop the affected outreach and preserve the complaint with its time and channel. Find the original source record, form disclosure, certificate, and messages associated with that lead. Compare the sender and requested product with what the recipient actually saw.

If a partner supplied the lead, ask that partner for the original submission evidence. A spreadsheet row marked “consented” is not enough to explain the collection event. Keep the complaint and resolution linked in your operational records, and check whether the same mapping or source issue affects other leads.

## Test preference handling across systems

Use a contact you control to test the opt-out path before launch. Confirm that the preference is visible to the people handling replies and that your connected CRM and other sending systems receive the change through the process you have configured.

Separately test a request received outside SMS, such as an email or a verbal no-contact request. Assign someone to record it and stop affected follow-up. A successful STOP test does not verify those other paths.

## Maintain your records

Keep the records needed to explain and support each workflow, including:

* consent certificates and source records;
* opt-in pages, disclosures, and timestamps;
* message copy, call scripts, and sender identity;
* opt-out, DNC, and suppression events;
* carrier registrations and provider reviews; and
* contracts, approvals, and applicable legal analysis.

> [card] [Configure sources](https://leadping.ai/docs/lead-sources.md)
>
> Keep intake paths separate and traceable.

> [card] [Implement consent evidence](https://leadping.ai/docs/requiring-trustedform.md)
>
> Understand Verified, Unverified, and Quarantined consent and their outreach rules.

> [card] [Prepare numbers](https://leadping.ai/docs/trustedsetup.md)
>
> Complete number readiness checks before calling or messaging.

> [card] [Review prohibited content](https://leadping.ai/docs/forbidden-message-categories.md)
>
> Understand traffic and categories Leadping does not allow.


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