Routing and the ping tree

When a call comes in, CallsFlow Plus decides which buyer gets it. The rules you set on the campaign's Ping tree control that decision.

Building the tree

1. Open Campaigns and click your campaign.
2. In the Ping tree section, click Add target.
3. Under Target, pick a target. Each target can appear only once.
4. Set Tier and Weight. Both must be at least 1.
5. Tick Enabled, then click Save tree.

You can remove a row with its remove button, then save again.

How a call is routed

1. The platform pings every enabled RTB target in the tree at the same time. Static targets have a fixed price, so they take part without a live bid.
2. Targets that decline, time out, fail, or bid in a way that leaves no margin after the publisher payout are dropped.
3. The remaining targets are ranked: - Lower Tier first. Tier 1 is tried before tier 2. - Inside a tier, the highest bid wins. - If bids tie, the higher Weight wins, then the faster reply.
4. The call is sent to the winner. If that buyer does not answer, the next one is tried, as long as the target is Failover eligible and the campaign's failover budget has not run out. See Ring timeout, caps and failover.

Use tiers when you want a preferred buyer to get first look, for example a direct buyer in tier 1 and a backup in tier 2.

Other things that stop a call

Before any buyer is pinged, the platform checks that the campaign is active, the source is attached with active terms, your credit balance is above zero, and the daily cap and duplicate rules allow it. See Why a call didn't route.

Static or RTB campaigns

When you create a call campaign you choose its Call routing:

• Static: publishers send callers to the tracking numbers you assign them (Numbers on the campaign). There is no ping URL; a ping to a Static campaign is answered "not configured".
• RTB / dynamic: publishers can also ping the campaign's RTB URL. A bid always gives one of our numbers, never the buyer's, so every call comes through us with its duration and recording:
• the source's own tracking number, if it has one on the campaign;
• otherwise a number from your account's number pool. The pool is set up automatically with your first RTB campaign and run by the platform, at no cost to you. A free pool number is held for one bid until it expires; when all are held, bids share them and the call is matched by the caller's number.
• when the platform has SIP turned on, every bid also carries a sip_address of its own (like RTB…@….sip.telnyx.com). Publishers whose platform dials SIP (Ringba, CallGrid, Retreaver and most others) should transfer to it: the call is matched to that exact bid whatever the caller ID, and the number stays as the fallback.

A call that arrives up to 3 seconds after its bid expired still counts. After that, the campaign's Calls that arrive after the bid expired setting decides: refuse it (the default), route it on the original bid, or run a new auction.

Publishers should always send the real caller's number as caller_id and transfer from that same caller ID. Turn on Require caller ID on pings (campaign settings) to refuse pings without one. A ping with no caller ID while every pool number is busy gets no bid.