Skip to main content
Opt-outs, suppression, contact hours, and other sending restrictions still apply to every lead. When adding or editing a lead, provide either:
  • A Leadping or TrustedForm certificate URL.
  • Other: check the box confirming that you have consent to text the lead. This gives the lead Unverified consent.
Leadping validates certificates before marking consent Verified. Leadping certificates are checked for accepted consent, a complete recording, and a matching recipient. TrustedForm certificates are checked for URL validity and availability; their contents and recipient are not independently checked. To move from Unverified to Verified, add a supported certificate and wait for validation. Removing attestation without adding a certificate leaves consent Quarantined.

API

Both POST /leads and POST /leads/intake accept these fields. Put them inside metadata for POST /leads, or at the top level for /leads/intake.
Other submissions need an idempotency key or sellerLeadId. Sources configured to require certificates still require them. Leadping sets metadata.consentVerificationStatus automatically. See Sending Leads for certificate examples and authentication.

CSV imports

Map email or phone, plus Consent Certificate Url or Consent attested. Use true to attest to Other consent without a certificate. Blank values, false, and yes do not count as attestation.

Blocked outreach

Check the lead’s Consent verification section and processing reason. Correct missing or invalid evidence, and resolve disputes or opt-outs before contacting the lead. A lead must finish processing before outreach. Ready does not mean Verified: an Other lead can be Ready and still be limited to manual texts.