Skip to main content

Release Notes: 2026-08-27 — Inbound RTB — Call Flow on live allocated calls

Attach a Call Flow on an Inbound RTB row so Voice Agents and other live-call nodes can run after the publisher dials the reserved number.

D
Written by Denise Abdullah

Run Inbound RTB calls through a Call Flow (Voice Agent and other live-call nodes)

Category: New feature
​ Location: Call Flows; Campaigns → select a campaign → Inbound RTB Publishers
​ Release Date: August 27, 2026

What this solves

Inbound RTB used to pick a buyer and connect the call straight to that destination. You could not put a Voice Agent (or other nodes that need a real phone call) in front of that destination. That is now possible.

How it works (two different moments)

  • Publisher ping (no caller on the line yet): Moja still uses the campaign’s existing Call Flow or Routing Plan to choose a buyer and reserve a number. Nothing new is required here.

  • Live call (publisher dials that reserved number): if you attach a Call Flow on the Inbound RTB row, that Call Flow runs instead of sending the caller straight to the winning destination. This is where Voice Agent, Switch, If, Hangup, and Allocated Number belong.

You use both: the campaign path to win the bid, and a second Call Flow attached on the Inbound RTB row to handle the actual call.

What’s new

  • Each Inbound RTB publisher row can attach its own Call Flow. Leave it empty to keep today’s behavior (campaign routing only).

  • New Call Flow node: Call allocated number. It dials the destination that already won the ping. You do not pick buyers again on that path.

  • That node has Processed and Failover. Connect them only if you want something after that dial (another node or hangup). If you want the call to end with the buyer, you can leave them empty.

  • Switch nodes always show a Default path when no condition matches.

  • Live calls that claimed an allocation get the system tag INBOUND_RTB_ALLOCATION.

How to set it up

  1. Keep your current campaign Call Flow or Routing Plan. That is still what answers the ping and chooses the buyer.

  2. Create a second Call Flow under Call Flows for after the caller is on the line. Do not create or pick this flow as the campaign’s main route type. You attach it later on the campaign page, in Inbound RTB Publishers.

  3. In that second flow: Start → Voice Agent (and any If/Switch you need) → Call allocated number when the call should go to the winning Inbound RTB destination. Use a Routing Plan node only when you want a different destination (for example fraud / outbound-dialer traffic), not for the original winning buyer.

  4. Open Campaigns, select the campaign, go to Inbound RTB Publishers, and attach that second Call Flow on the Inbound RTB row. That picker is what turns this on. Empty = campaign routing only.

Example (fraud screen, then winning buyer)

Start → If (Inbound RTB request) → Voice Agent → Switch

  • Not fraud / Default → Call allocated number (the buyer that already won)

  • Fraud → Routing Plan (hangup, or a buyer who will take those calls)

Do not

  • Put Voice Agent only on the campaign Call Flow and expect Inbound RTB pings to talk to it. Ping has no caller yet.

  • Replace Call allocated number with another Routing Plan when you still want the original winning destination.

  • Attach the campaign’s ping Call Flow on the Inbound RTB row unless that flow is actually what should run on the live call.

Impact

Teams can screen, qualify, or branch an Inbound RTB call with Voice Agents and other live-call nodes, then connect good traffic to the destination that already won, without changing how the ping chooses a buyer.

Did this answer your question?