How delivery works
DebtLeads.co delivers each lead by webhook or API: when a consumer's inquiry matches your filters, we send the lead's data to an endpoint you give us, with a target of under 60 seconds from form submission. The payload format, authentication and response handling are documented on the API page.
Your side of the integration has four jobs: accept the post, map the fields, check for duplicates, and route the record to a rep. Then test all four before real leads arrive.
Field mapping
Every lead carries the same set of data. Map each item to a dedicated field in your CRM. The table shows the data and a sensible destination; use the exact field names from the API documentation when you build.
| Lead data | CRM field type | Notes |
|---|---|---|
| Name | First and last name | Standard fields |
| Phone | Phone | Normalize to one format before saving; this is your dedupe key |
| Lowercase and trim | ||
| State | State / region | Drives licensing checks, routing and time zone |
| Total unsecured debt band | Picklist | Store the band as delivered; do not convert to a single invented number |
| Debt type | Picklist | Match your program categories |
| Payment status / months behind | Picklist or number | Useful for rep prioritization |
| Income status | Picklist | Part of qualification |
| Already-in-a-program flag | Checkbox | Show it on the rep's screen |
| TrustedForm certificate | URL or text, read-only | Compliance evidence |
| Consent text | Long text, read-only | Store the full wording, not a yes/no |
| Consent timestamp and IP | Date-time and text, read-only | Keep the original time zone or store in UTC |
Add three fields of your own on intake: lead source, tier (exclusive, semi-exclusive, shared or aged) and received timestamp. Never let a later edit overwrite them. They are what make cost per enrolled client and response time measurable.
Protect the consent fields. Make consent text, timestamp, IP and certificate read-only for reps, and exclude them from any automation that updates records. The FTC's Telemarketing Sales Rule requires sellers and telemarketers to keep records of consent (16 CFR 310.5(a)(8)). Ask your counsel what else to retain and for how long.
Notes by platform
Features, plan limits and menu names change. Treat these as starting points and confirm each against the vendor's current documentation or your account representative. We name these products because buyers use them; we are not affiliated with them.
DebtPayPro and Forth CRM
Both are built for the debt relief industry, so most lead fields have a natural home: debt amount, debt type, state and hardship details. Ask your account representative for the lead posting instructions for your account, including the endpoint, credentials, required fields and accepted values for picklists such as state and debt type. Share those instructions with us so delivery can be set up against them.
Salesforce
Leads can be created through the platform's API, through a web-to-lead form, or through middleware. For real-time delivery with custom fields and a proper success or failure response, the API route is usually the better fit. Create the custom fields first, check field-level permissions for the integration user, and check that assignment rules fire for records created by the integration.
HubSpot
Contacts can be created through the CRM API or a form submission endpoint. Create custom contact properties for the debt and consent fields before you start. HubSpot matches contacts by email address by default, so decide how you will handle two consumers sharing an email or one consumer using two.
Zoho CRM
Records can be created through the API or a web form. Check that workflow and assignment rules run for API-created records in your edition, and that picklist values match exactly.
GoHighLevel
The common pattern is an inbound webhook that starts a workflow, which creates or updates the contact, writes custom fields, assigns a user and sends the alert. Map every field explicitly in the workflow; unmapped data is discarded.
LeadsPedia
If you run your own lead distribution on LeadsPedia, set DebtLeads.co up as a source posting into a campaign, then use your existing rules to distribute to your teams or offices. Pass the consent and certificate fields through to the final destination. Do not strip them at the distribution layer.
Zapier
Use a webhook trigger to catch the post, then an action to create the record in your CRM. It is quick to build and reaches almost anything. Check three things: how soon each step runs on your plan, what happens when the CRM step errors, and that someone is alerted when the automation is switched off or runs out of tasks.
Generic webhook
If you have a developer, a small endpoint of your own gives you the most control. It should authenticate the request, validate required fields, save the raw payload before doing anything else, respond quickly, and do slower work such as CRM writes and notifications after responding.
Deduplication
Duplicates waste money and annoy consumers, who get called twice by two reps.
- Normalize first. Strip punctuation and country codes from phone numbers; lowercase emails. Unnormalized data hides duplicates.
- Match on phone, then email. Phone is the stronger key for a call-based sale.
- Check clients too. A lead that matches a current or past client should not land in a new-lead queue.
- Check your suppression list. Anyone who has asked not to be contacted must not be called because a new record appeared. Match every inbound lead against your internal do-not-call list before it reaches a dialer.
- Choose a rule. On a match with an open lead, either update the existing record and alert its owner, or reject the new one. Do not create a second record with a second owner.
Duplicates are one of the listed return reasons, with a 72-hour window, so run the duplicate check at intake and not at the end of the week. Tag sources carefully so you can show where each copy of a record came from.
Routing
- By state. Send leads only to reps and entities permitted to serve that state. State licensing requirements vary and must be confirmed with each state's regulator.
- By availability. Assign to a logged-in, free rep. Reassign automatically if no dial happens within your set window.
- By tier. Give shared leads queue priority; see exclusive vs. shared.
- By program. If you offer more than one program, route on debt type and debt band.
- Alert on arrival. A screen pop or dialer priority, not an email.
Match your filters to your routing. If no rep can take a state after six in the evening, set delivery hours so leads from that state stop then.
Testing before go-live
- Send a test lead clearly marked as a test and confirm it creates a record with every field populated.
- Check each mapped field against the payload, especially picklists, the debt band and the consent text. Truncated consent text is a common, silent failure.
- Send the same test twice and confirm your duplicate rule does what you chose.
- Send a test for each state group and tier and confirm routing and alerts.
- Break it on purpose. Send a payload with a missing required field and confirm your system returns an error instead of silently dropping the lead.
- Time it. Compare the consent timestamp, your received timestamp and the first alert.
- Confirm test records are excluded from dialers and reports, then delete them.
Monitoring after go-live
- Reconcile daily. Leads we report delivered should equal records created. Investigate any gap the same day, while it is still inside the return window.
- Alert on failures. Rejected posts, expired credentials and paused automations should notify a named person.
- Alert on silence. No leads during hours when you expect them is also a signal.
- Review after changes. A renamed field or a new required field in your CRM can break intake without warning. Re-run the tests after any CRM change.
Getting set up
Have your CRM's posting instructions or webhook URL ready, and run the tests above before your first block goes live. Start at the API page, see the overall process on how it works, or book a call to walk through your setup. Questions can also go to info@debtleads.co.
Frequently asked questions
Which CRMs can receive DebtLeads.co leads?
Should we use Zapier or a direct integration?
How do we stop duplicate leads?
What should we store for compliance?
Want to see the leads this is about?
Book a 15-minute call. We will go through pricing, which states and filters are live, and delivery into your CRM.
Book a CallWritten by the DebtLeads.co team. General information for lead buyers, not legal advice. DebtLeads.co sells advertising leads at a flat price per lead. We never take a share of your fees, settlements or enrollments, and we are not a debt relief provider, lender, law firm or credit counselor. Buyers are responsible for their own state licensing and for complying with the FTC Telemarketing Sales Rule (16 CFR Part 310, including its advance-fee rules for debt relief services), the TCPA and state law. Nothing on this site is legal advice or a promise of contact rates, enrollments or return on investment.