Skip to main content
Revision Date: June 28, 2026 Use this checklist to get from account setup to first production lead with fewer review loops. The goal is simple: one approved source, one clear consent path, one ready number or follow-up workflow, and one tested route from lead submission to response. The app will guide you through account setup, but production SMS, calls, intake, and automations may require review before they are available.

​
Launch path at a glance

​
1. Define the first workflow

Before entering details, decide what the first production workflow should do. Be specific:
  • Where new leads will come from
  • Which business, brand, or seller will contact them
  • Whether the first touch is SMS, a call, an alert, or a manual follow-up
  • What the first message or call is about
  • Who on your team owns replies, missed calls, opt-outs, and follow-up
  • What consent evidence will be attached to each lead
If those answers are still changing, finish that planning first. Most setup delays come from mismatched source, brand, consent, and message details.

​
2. Prepare the business profile

Have these ready:
  • Legal business name, DBA if used, EIN or tax ID, and business address
  • Public website for the same brand that will contact leads
  • Business phone number and support email
  • Owner or authorized contact details
  • A supporting business document if requested
  • Payment method
  • Privacy policy and terms links
Use consistent names and domains. If your website, legal business, DBA, support address, opt-in page, and sample messages point to different brands, review will take longer.

​
3. Prepare the lead source

A source is the form, website, partner, buyer, publisher, or internal system that sends leads into Leadping. For each source, gather:
  • Source name and owner
  • Website, landing page, form, or posting system
  • Publisher or partner details, if a third party is involved
  • Products, states, or audiences the source is allowed to send
  • Expected lead volume
  • Consent language shown to the person submitting the form
  • TrustedForm certificate handling, if leads are submitted from outside Leadping
  • Any tags or tracking IDs you want attached to new leads
Create separate sources when publishers, forms, consent language, products, states, pricing, or routing differ in a way your team may need to review later. See Lead Sources before connecting a production integration. For external lead submissions, plan how the lead will carry proof of the opt-in event. Confirm:
  • The opt-in language names the right sender or brand.
  • The consent covers the channel you plan to use, such as SMS or calls.
  • The TrustedForm certificate URL will be sent as trustedFormUrl when required.
  • The submitted phone number, email, source, campaign, and product make sense against the certificate and source records.
  • Your team knows how long certificates and related records are retained.
See Requiring TrustedForm for field names and validation expectations.

​
5. Prepare SMS or calling details

If you plan to text or call leads, have this ready:
  • Intended call or message use case
  • Example SMS copy or call script
  • Sender brand name shown in messages
  • Opt-out and HELP handling for SMS
  • Business hours and recipient locations
  • Phone number needs, including whether you need a new Leadping number
Production numbers must complete TrustedSetup. SMS may also require Carrier Registration before messages can be sent.

​
6. Test before launch

Before sending production traffic:
  • Confirm the source is approved and enabled.
  • Send a test lead with a valid contact method and TrustedForm URL when required.
  • Confirm the lead appears in Leadping with the expected source, tags, product, state, and contact details.
  • Confirm the conversation and workflow behavior match what your team expects.
  • Verify opt-out, suppression, and support handling before using automation at volume.

​
Ready for production

A first workflow is ready for controlled production traffic when:
  • The source is enabled and approved.
  • The real posting system has created a successful test lead.
  • The lead record shows the expected source, product, state, tags, and metadata.
  • TrustedForm or another approved evidence path is present when required.
  • The conversation, assignment, alerts, automations, and reporting behave as expected.
  • The sending number is ready for its intended call or SMS workflow.
  • Your team knows who handles replies, missed calls, opt-outs, support, failed posts, and source changes.
Start with a small volume and verify the workflow before increasing traffic.

​
What can block launch

Leadping or a provider may pause setup when details are incomplete, inconsistent, or risky. Common blockers include:
  • Missing or private website
  • Brand, legal name, DBA, domain, or message copy mismatch
  • Missing privacy policy, terms, or SMS consent language
  • Unapproved source or unclear publisher path
  • Missing, malformed, or unsupported TrustedForm certificate URL
  • Incomplete carrier registration details
  • Forbidden or restricted message category
  • Changed lead source, product, state, or audience after review
Approval, timing, SMS availability, call availability, and delivery are not guaranteed.

​
When to contact support

Contact support@leadping.ai if setup asks for information you do not understand, your business details changed after submission, your source or consent path changed, you want to add a new campaign or publisher, or the app says Leadping review is required.

​
Next pages