A usable payload carries the full contact record, the qualification answers as structured values rather than free text, the attribution data, the consent record reference, and the merchant’s own submission timestamp. The last one matters most: without it you cannot measure your own time to first dial, which means you cannot tell a slow vendor from a slow floor.
Every vendor will describe their data as complete. A sample payload settles it in thirty seconds, and asking for one before signing is the cheapest diligence available.
| Field group | What it should contain |
|---|---|
| Contact | Full name, business name, phone, email, address |
| Qualification | Revenue band, amount requested, time in business, statements available |
| Verification | Whether the phone was code-verified, and when |
| Attribution | Source, campaign, and any ad identifier |
| Consent | A reference the vendor can resolve to the full record |
| Timing | The merchant’s submission timestamp, not the delivery time |
A revenue field containing "about 90k give or take" is not a field you can route, score or report on. Bands and enumerated values are what let a CRM sort a feed automatically, and a vendor whose payload is mostly free text is passing their data-cleaning problem to you.
That last habit costs nothing and saves an afternoon the first time a field silently stops populating after a vendor changes something upstream.
Full contact details, qualification answers as structured values, verification status, attribution data, a consent record reference, and the merchant’s own submission timestamp.
Because it is the only way to separate vendor latency from your own time to first dial. Without it, every argument about whether the leads or the floor were slow is unresolvable.
No. Free-text revenue like "about 90k" cannot be routed, scored or reported on. Bands and enumerated values let the CRM sort the feed automatically.
Send the vendor your field keys or a sample of the JSON your CRM expects and have them shape their POST to match. Then test with a real test lead and confirm the fields landed correctly.
Yes, alongside the parsed record. It costs nothing and it is the only way to diagnose a mapping problem after a vendor changes something upstream.
We will tell you straight up if we cannot help you. No commission deals, no free trials, no chasing you for three weeks.