Many lead vendors run on LeadByte. Their leads come into LeadVault through the API, and your returns can go straight back into their LeadByte.
1. Get their leads in
- Make a posting key on the vendor's source: Team, API keys, New posting key. See Get leads from a vendor.
- Send the vendor the key, the address
https://leadvault.com/api/v1/leadsand the API docs, and ask them to set up a delivery to it. - Ask them to send their LeadByte lead ID as `reference_id`. Returns need it.
LeadVault takes a JSON or a plain form post, with the key in a header or as a field named api_key. GET https://leadvault.com/api/v1/lead-types gives them your question keys to map their fields to.
2. Send returns to their LeadByte
Ask the vendor for three things: a buyer API key that may return leads, your buyer ID (BID), and the reason codes they take.
Then, as an account admin: Settings, Lead sources, the vendor's Returns button:
- Pick LeadByte.
- Fill in Their LeadByte address (like acme.leadbyte.co.uk), Your buyer ID, and the Buyer API key.
- Type their code for each return reason. Other's code stands in for any left empty.
- Save.
Now each lead returned to that vendor goes into their LeadByte as soon as it's returned, and the lead's timeline says so. If LeadByte turns one down, Returns shows Didn't go, why, and Send again.
A lead without a numeric LeadByte ID in its reference ID can't go back through LeadByte, and says so. See Duplicates and returns for returning a lead.
Didn't answer it? Ask us.