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

# Compliance Overview

> Use Leadping with approved sources, consent evidence, SMS, calls, automations, opt-outs, and clear operating records.

*Revision Date: June 28, 2026*

Leadping is built for fast lead response with a clear record behind every outreach decision. Speed works best when the lead source, consent record, sender, channel, message, and timing all match what the person agreed to.

Use the legal pages for formal policy language. Use this page as the day-to-day operating checklist.

## The operating standard

Before contacting a lead, your team should be able to answer three questions:

* Where did this lead come from?
* What did this person agree to receive, from whom, and through which channel?
* Why is this call, text, workflow, or automation consistent with that agreement?

If the answer is unclear, pause the outreach and fix the source, consent evidence, message, suppression status, or workflow first.

## What good traffic looks like

A healthy Leadping workflow has all of these pieces aligned:

* The lead came from an approved source.
* The source is tied to the right business, brand, product, and audience.
* The person took an affirmative opt-in action.
* The consent evidence is available, usually through TrustedForm.
* The planned SMS, call, or automation matches the consent language.
* The phone number has completed setup and registration steps that apply.
* Opt-outs, DNC requests, and suppression records are honored.
* Your team can explain why this person was contacted by this business about this offer.

Good traffic is specific. The strongest setups tie one source, one consent path, one sender, one offer, and one follow-up workflow together so the record is easy to review later.

## Before contacting a lead

Confirm these items before sending a text, placing a call, or starting an automation:

* The lead came from an approved source.
* The lead has consent evidence, usually a TrustedForm certificate.
* The consent names the right seller, brand, or business.
* The consent covers the channel you plan to use, such as SMS or calls.
* The message or call matches the reason the person opted in.
* The lead has not opted out or asked not to be contacted.
* The contact time is allowed for the recipient's location.
* The content is not in a forbidden category.

If any of those items are unclear, pause the outreach and resolve the issue first.

## What Leadping may block or review

Leadping checks for common setup and traffic issues. Activity can be blocked, held, or sent to review when those checks fail. Common checks include:

* Source approval and enablement
* TrustedForm presence, format, and source alignment
* Allowed state, product, or vertical settings
* Phone-number readiness
* Carrier registration status for SMS
* Opt-out and suppression status
* Forbidden or mismatched message content
* Complaint, failure, or opt-out patterns
* Suspicious, unverifiable, or disputed source traffic

These checks are there to keep production traffic aligned with the approved setup. Passing a technical check does not guarantee legal compliance, delivery, or future provider approval.

## Records to keep

Keep enough records to answer a simple question: why was this person contacted by this business about this offer?

That usually means keeping:

* TrustedForm certificates or other consent evidence
* The source, publisher, form, landing page, or posting path
* The consent disclosure shown to the consumer
* Message copy, call scripts, sender names, links, and caller IDs
* Opt-outs, DNC requests, suppression records, and contact history
* Carrier registration details and approved campaign information

Leadping can help store and connect parts of this record, but your team still owns source quality and consent proof.

## When to update support

Contact [support@leadping.ai](mailto:support@leadping.ai) before continuing traffic when any of these change:

* Legal business name, DBA, website, privacy policy, or terms
* Lead source, publisher, form, opt-in language, or posting integration
* Campaign use case, message copy, call script, links, or phone numbers
* Products, states, verticals, or audiences
* Opt-out handling or suppression process

Also contact support if complaints, opt-outs, carrier issues, or source disputes increase.

Material changes can affect source approval, TrustedSetup, carrier registration, and automation eligibility. Treat them as launch changes, not routine edits.

## Practical examples

| Situation                                                 | What to do                                                                    |
| --------------------------------------------------------- | ----------------------------------------------------------------------------- |
| A partner changes its landing page or opt-in language     | Pause or reduce traffic and ask support whether the source needs review       |
| You want to send a new first SMS                          | Confirm it matches the registered use case and approved source before sending |
| A lead has no TrustedForm URL but the source requires one | Do not contact the lead until the missing evidence is resolved                |
| A lead replies STOP or asks not to be contacted           | Honor the opt-out or request before any further outreach                      |
| A new product, state, or audience is added                | Update the source and registration context before production traffic          |

## Related pages

* [Lead Sources](/lead-sources)
* [Carrier Registration](/carrier-registration)
* [TrustedSetup](/trustedsetup)
* [Requiring TrustedForm](/requiring-trustedform)
* [Forbidden Message Categories](/forbidden-message-categories)
* [Acceptable Use Policy](/acceptable-use)
* [Terms of Service](/terms-of-service)