Route every call to its
highest-value buyer.
Build ping-post routing plans with four strategies — Highest Bid, Weighted Random, Round Robin, or Priority+Weight+Price. Stack tiers, add conditional branches, configure bidder rules, and simulate 50 calls before you go live. No code required.
Plan · medicare_lead_gen · 2 tiers
LiveFrom plan to live traffic in four steps.
Pick a strategy
Choose Highest Bid, Weighted Random, Round Robin, or Priority+Weight+Price — per tier, not per plan. Mix strategies across tiers in the same waterfall.
Build your waterfall
Add tiers with bidders, caps, price floors, duration filters, and custom fields per buyer. Each tier cascades to the next if primary buyers are capped or pass.
Add branches
Fork the plan on data variables, time windows, call origin, or downstream outcome. Nested conditions and AND/OR logic supported at every level.
Simulate & launch
Replay a deterministic 50-call sample, review fill rate and revenue by buyer, then ship with one click — no deploys, no downtime, live in seconds.
Every routing lever.
Four routing strategies
Highest Bid, Weighted Random, Round Robin, and Priority+Weight+Price — apply a different strategy to each tier within a single plan.
Ping-post auction engine
Two-step handshake: ping sends anonymized call attributes to bidders, post delivers the winning destination — via PP Handoff or Teldrip Call Bridge.
Conditional branches
Split call flow on data variables, time windows, call origin (organic vs ad), or downstream outcome. Branches can be nested and combined.
AI plan builder
Describe your routing goal in plain English — the AI generates a complete plan with tiers, strategies, bidder rules, and branch conditions instantly.
Built-in simulation
Replay a deterministic 50-call sample against your live tier structure. See fill rate, revenue per tier, and buyer breakdown before you ship.
Auto bidder docs
Each bidder automatically gets a tailored integration guide with their exact ping/post JSON schema, field specs, and example requests.
The networks that monetize every ring.
Medicare & insurance
Call-Only RTB with per-state caps, per-record consent gating, DNC scrubbing, and TCPA-compliant quiet-hour enforcement.
Mortgage & finance
Priority waterfall with loan-type data branches, per-buyer duration filters, and conversion-outcome routing to the highest-intent buyers.
Legal & home services
Geo-split plans with time-of-day branching and Round Robin distribution across regional buyer pools — no manual rebalancing needed.
Pay-per-call publishers
Origin branches separate organic vs ad-driven traffic, giving each source its own tier structure, pricing logic, and payout rate.
What teams always ask.
Highest Bid (HB) is a pure price auction — whichever bidder offers the most wins the call. Priority+Weight+Price (PW) layers three factors: first a priority rank, then a weighted random draw among tied-priority bidders, then a price floor check. Use HB to maximize yield per call; use PW when you need structured relationships with key buyer partners.
PP Handoff means the publisher's own infrastructure connects the call to the winning buyer — Teldrip sends the winning destination in the post response and the publisher bridges. Call Bridge means Teldrip itself bridges the call, enabling Call-Only RTB where buyers bid and receive calls without a direct SIP connection to the publisher's network.
When a call qualifies, Teldrip sends a Ping to all eligible bidders with anonymized call attributes — intent, state, vertical, duration, and any custom fields you expose. Bidders respond with a bid or a pass. Teldrip selects the winner per your tier strategy, then sends a Post to the winner with the caller's dynamic destination. The call bridges in under 100 ms from auction close.
Yes. Every plan includes a built-in simulator that replays a deterministic 50-call sample against your tier structure. Results show fill rate, revenue, and buyer-level breakdown using your real bidder caps and filter rules — so simulation output closely reflects production behavior.
Four branch types: Data (fork on any call variable — state, intent, custom field), Time (day-of-week and hour windows per timezone), Origin (organic vs ad-driven traffic), and Result (route based on downstream call outcome such as converted or no-answer). Branches can be nested and combined within a single plan tree.
Related Pulse capabilities.
Your next revenue conversation
is already ringing.
Spin up tracking, telephony and AI in a single platform — the way modern US revenue teams do it.
Cancel any time