Set Up Leadping

Set up your Leadping organization, complete onboarding, create a lead source, and test production intake with source-key authentication and consent certificates.

Leadping onboarding collects the information needed to create the organization, provision its first phone number, handle A2P 10DLC registration, and activate billing.

Before you begin

Have these items ready:

• your name and phone number;
• the organization’s legal name, phone number, industry, website, and address;
• its EIN and a matching IRS document in PDF, PNG, or JPG format, up to 4 MB;
• a preferred area code for the first Leadping number; and
• a payment card.

Complete onboarding

The setup wizard has eight steps.

Step	What Leadping asks for
Profile	Your name, phone number, and communication preferences
Organization	Legal business details, website, industry, address, and optional offer and audience descriptions
Verify	EIN and the matching IRS document
Phone	The first available Leadping phone number
Consent	Acceptance of the platform, messaging, TrustedForm, and compliance terms
Plan	Monthly or annual billing
Payment	A payment method
Review	Final authorization and the charges due today

Submitting the final step activates the plan, purchases the selected phone number, and starts the setup workflows. Leadping handles the required A2P 10DLC registration; outbound SMS remains unavailable until it is approved.

The Profile step uses Leadping Consent to capture your account SMS consent at /setup/personal. You do not install TrustedForm or supply a certificate yourself for this step. Each external lead needs its own evidence, separate from your account certificate.

Complete Profile consent

1. Open Profile (/setup/personal) and enter your first name, last name, and phone number. Your signed-in email is part of the captured recipient.
2. Wait for the SMS consent checkbox to become available, read the disclosure, and check it. This checkbox is required to continue. Marketing email consent is optional.
3. Select Next once. Leadping saves your personal information, completes the capture, waits for its certificate, and saves the verified consent before opening Organization (/setup/organization).

Autosaved fields or a checked box alone do not mean this step is complete. The server must verify the certificate against your saved contact details and the current Profile form. A previously verified Profile certificate can be reused while the contact details remain unchanged.

Recover Profile consent

What you observe	What to do
SMS checkbox stays disabled, or “We couldn’t verify your information” appears	Reload the page to restart capture, check the saved contact details, then read and accept the disclosure again. If it persists, contact [e-mail] with the page, time, and error.
Next is still loading while the certificate processes	Keep the page open. Leadping repeats issuance for the same capture, backing off from one second to at most five seconds. A pending certificate is not a completed Profile step.
A request fails or the page was closed while waiting	Reopen /setup/personal and check the saved details. If consent was not verified, reload and capture it again. Leaving the page stops its polling; it does not confirm completion.
”Unable to save personal information” or field validation errors	Correct the indicated fields and retry Next. Certificate capture cannot finish the step before personal information saves.
”Something went wrong. Please try again.” after capture	Retry Next on the same page with unchanged details. If verification still fails, reload to obtain fresh evidence and accept again.
”Your contact information changed. Please accept SMS consent again.”	Review the updated contact information and accept SMS consent again; if capture is unavailable, reload first.

If processing remains pending, contact support with the time and page rather than repeatedly starting new captures. Do not send passwords, source keys, or capture tokens.

Create an intake source

After onboarding:

1. Open Sources.
2. Select Add source.
3. Give the source a name that identifies the real form, partner, CRM, or posting system.
4. Store its lp_src_... key in the posting system’s server-side secret configuration. Do not put the key in browser JavaScript or a public form field.

A source is enabled when created. There is no approval action on the customer source page. See Lead Sources.

Add consent evidence to the production form

Each external lead needs evidence captured for that person’s submission. Choose the request format that supports your evidence:

Evidence	Endpoint and field
Issued Leadping Consent certificate ID	POST /leads with metadata.leadpingConsentCertificateId
TrustedForm certificate URL	POST /leads with metadata.trustedFormUrl, or POST /leads/intake with trustedFormUrl

The flat intake endpoint does not map a Leadping Consent certificate ID. Use the structured endpoint for that path. Wait for Leadping Consent issuance to finish before posting the lead, and never reuse the account Profile certificate for a customer lead.

See Consent evidence for request examples, pending-certificate recovery, and validation behavior.

Test one lead

Use a contact you control and a certificate captured from that test submission. Review enabled automations first: creating a lead can start follow-up, and production requests can incur charges. Submit through the actual form or posting system so the test includes every field mapping and handoff.

1. Confirm the request returns 201 Created.
2. Open the lead under the expected source.
3. Check its contact fields, tags, metadata, and consent certificate ID or TrustedForm URL.
4. Wait for the processing status to become Ready.
5. Confirm the conversation and any configured automation behave as expected.

If the lead becomes Invalid, open its processing reason before sending more traffic.

Prepare the phone number

Leadping prepares managed numbers for production and shows their current registration, availability, and limits. Review Number health and Carrier Registration before using a number in production.

Start with low volume. Increase traffic only after intake, processing, conversations, opt-outs, and automation have been verified end to end.

Resolve launch blockers

What you observe	Where to start
No lead was created	Read the posting system’s HTTP response; use the intake error table
A lead exists but is invalid	Open its processing reason and check the certificate handoff
A ready lead has no expected follow-up	Check whether the intended automation is enabled and whether its trigger and conditions match; inspect its run history
SMS is unavailable	Check Settings → 10DLC, then the selected phone number’s status
Replies arrive but nobody handles them	Assign a reply owner and agree on when that person checks the conversation

Record the test lead ID, source, submission time and time zone, processing result, and observed follow-up. Keep that record with your launch notes so another operator can repeat the test after a configuration change.