What already works
A Retreaver tracking number can be added as a destination in Destinations today — a warm transfer doesn't care whose dashboard is behind the number it's dialing. Retreaver supports posting call events to a URL you specify, and our postback endpoint's flexible field-alias matching (caller ID, duration, buyer/target, payout under several common names) means a manually wired Retreaver postback may already reconcile correctly against our generic postback URL.
What's coming: a guided template
What's left is the same as Ringba: a verified, copy-paste setup guide specific to Retreaver's dashboard fields, tested end-to-end against a live Retreaver account before we call it Live here. Until then, tenants who already run Retreaver can wire the generic postback manually using the field aliases documented in the quickstart.
FAQ
Can I use Retreaver with lead2inbound today?
Yes for the transfer itself — add the Retreaver number as a destination. For postbacks, our generic endpoint's field-alias matching may already work with a manual setup; the guided, verified template is still in progress.
Why is this separate from LeadRouter and Ringba?
Different platforms name their postback fields differently and have different dashboards to walk through, so each gets its own verified setup guide even though the underlying mechanism — a phone number plus a flexible postback — is identical across all three.