What already works
A warm transfer is nothing more than a phone call to a number, so any Ringba tracking number can be added as a destination in Destinations right now — the same as LeadRouter or any other number. Ringba lets you paste any URL into its own postback settings, and our postback endpoint already recognizes several of Ringba's common field names (target, target_name, campaign_name, payout, duration) among its accepted aliases. A hand-configured Ringba postback pointed at our generic postback URL will likely already work.
What's coming: a guided template
"Coming soon" here specifically means the polished, copy-paste setup instructions and a verified end-to-end test against a live Ringba account — a one-click template tailored to exactly where Ringba's dashboard expects each field, rather than you having to work it out from our generic field-alias list. We're not calling this Live on the marketing site until that specific verification passes, even though the underlying mechanism is the same one LeadRouter already uses successfully.
FAQ
Can I use Ringba with lead2inbound today?
For the transfer itself, yes — add your Ringba number as a destination like any other phone number. For revenue postbacks, our generic postback endpoint recognizes several of Ringba's typical field names, so a manual setup may already work, but we haven't finished the guided, Ringba-verified template yet.
What's the difference between this and LeadRouter's status?
Mechanically nothing — both are “a phone number plus a postback.” LeadRouter is marked Live because we've run and verified that exact path end-to-end with our own tenant; Ringba's guided template and verification are still in progress.