Integrations/Call routing & revenue tracking

LeadRouter

Live

LeadRouter isn't a partnership or a piece of shared software — it's simply a buyer-routing platform, integrated the same way any tracking-number destination is: a phone number for the transfer, and a postback URL for the revenue confirmation.

1 Lead in2 Dial3 Prequalify4 Route to buyer5 Track

What it does in the flow

This covers step 4, route to buyer and step 5, track together. A LeadRouter tracking number is configured as a destination like any other — the routing engine dials it, plays your whisper message, and bridges the qualified consumer once LeadRouter finds a live buyer on its end. From lead2inbound's side, LeadRouter is nothing more than a phone number; all the buyer-matching logic on LeadRouter's side is theirs, not ours, and there's no shared codebase or special API coupling between the two products.

The other half is revenue reconciliation: LeadRouter's own postback mechanism can fire the call's result — duration, buyer, payout — to a URL you configure on their side. lead2inbound receives that postback, matches it to the transfer it belongs to by caller ID within a ±4 hour window, and updates that transfer with confirmed (not estimated) revenue and billable status.

How to set it up

  1. In Destinations, add a destination whose phone number is your LeadRouter tracking number, with whatever hours/caps/payout config you want.
  2. Optional, if you route unsold leads back through us: point LeadRouter's outbound webhook at our live lead intake endpoint, POST https://api.lead2inbound.com/v1/leads, with your API key.
  3. In Settings → Destinations → Revenue postbacks, copy your account's postback URL (it includes your private token): https://api.lead2inbound.com/v1/postbacks/calls?token=YOUR_TOKEN.
  4. Paste that URL into LeadRouter's postback configuration. Field names are flexible — common aliases for caller ID, duration, buyer, and payout are recognized automatically, whether LeadRouter sends dollars or cents, JSON or form-encoded, POST or a GET pixel.

Full field-alias reference and a working curl test are in the docs quickstart.

FAQ

Does lead2inbound have a partnership with LeadRouter?

No. The only relationship is operational: LeadRouter is a phone number we transfer to, and a postback we accept. There's no shared code, data access, or business arrangement between the two products.

What happens if a postback doesn't match a transfer?

It's still stored as a raw postback hit and shown in your dashboard as unmatched, so you can see unreconciled revenue rather than have it silently disappear. Matching looks for a transfer to the same caller ID within a ±4 hour window.

What if I don't use LeadRouter?

The same destination-number and postback mechanism works for any buyer platform, including one you build yourself — see “Any number” in our routing category. LeadRouter just happens to be the platform our own tenant uses today.

Related integrations

Point a destination at LeadRouter today.

It's live — add the tracking number as a destination and paste your postback URL in five minutes.

Open the quickstart