What is a ping-post auction?

Ping-post is a real-time bidding protocol where CallMatrix sends anonymized lead data (the "ping") to multiple buyers simultaneously, collects dollar bids within a configurable timeout, connects the call to the highest bidder, and then sends the full lead data (the "post") only after the call is bridged.

What data is sent in the ping vs the post?

The ping carries non-PII fields — state, zip code, vertical, caller area code, and any IVR data. The full caller information (phone number, name) is withheld until the post phase after the call connects, so losing bidders never receive PII.

What happens if no buyer bids on a ping?

A global setting controls the fallback. By default, CallMatrix falls back to static auction pricing using the buyers' configured price-per-call, so the call still finds a destination even when every bidder declines.

How long do buyers have to respond to a ping?

The bid timeout is configurable per offer between 1 and 30 seconds. Buyers that do not respond in time are treated as non-bidders for that ping and excluded from the auction.

Can I require specific IVR data before a buyer is allowed to bid?

Yes. Each buyer offer can specify required IVR fields (e.g., vertical, zip_code). Buyers only receive a ping when every required field has been captured, so you never fire an auction on an under-qualified lead.

Ping-Post Auction

Real-time bidding. Every call goes to the highest payer.

What is Ping-Post Auction?

A ping-post auction is a real-time bidding protocol for inbound calls and leads. The platform sends anonymized lead data (the "ping") to every eligible buyer, collects dollar bids within a short timeout, connects the call to the highest bidder, and then transmits the full lead record (the "post") only after that call is bridged. The result: every call finds its true market value instead of clearing at a single static price, and losing bidders never receive the caller's PII.

Key Capabilities

Four-phase auction: Ping (anonymized lead data sent to all eligible buyers) → Bid (buyers respond with dollar amounts within configurable timeout) → Post (full lead data sent to winner after call connects) → Transfer (call bridged to winning buyer)
Per-offer configuration: individual ping URL, post URL, timeout (1-30 seconds), minimum bid threshold, authentication method (Bearer token, API key header, or none), and required IVR fields
Three lead channels supported: inbound calls (IVR-qualified), lead form submissions, and widget callback requests
Privacy-preserving ping payload: sends state, zip code, vertical, caller area code, and IVR data — no PII until the post phase after the call connects
Automatic fallback to static auction pricing when no buyers bid or all bids are rejected (configurable global setting)

Key Benefit

Maximize revenue on every call by letting buyers compete in real time, while maintaining caller privacy until the call is actually connected.

Real-World Use Case

Medicare Enrollment Auction

An insurance network receives a Medicare enrollment call from a 65-year-old in Florida (zip 33109). The ping goes to 6 buyers. Three respond: Buyer A bids $85, Buyer B bids $72, Buyer C bids $91. Buyer C wins, the call transfers, and $91 is recorded as revenue — $46 more than the static $45 price. The post containing the caller's full information is sent to Buyer C only after the call connects.

Request a Demo Request a Demo

Frequently Asked Questions

Stop Leaving Revenue on the Table

Join hundreds of businesses who switched to CallMatrix and cut their call routing costs by 40%.

Request a Demo

What is Ping-Post Auction?

Key Capabilities

Four-phase auction: Ping (anonymized lead data sent to all eligible buyers) → Bid (buyers respond with dollar amounts within configurable timeout) → Post (full lead data sent to winner after call connects) → Transfer (call bridged to winning buyer)

Per-offer configuration: individual ping URL, post URL, timeout (1-30 seconds), minimum bid threshold, authentication method (Bearer token, API key header, or none), and required IVR fields

Three lead channels supported: inbound calls (IVR-qualified), lead form submissions, and widget callback requests

Privacy-preserving ping payload: sends state, zip code, vertical, caller area code, and IVR data — no PII until the post phase after the call connects

Automatic fallback to static auction pricing when no buyers bid or all bids are rejected (configurable global setting)

Real-World Use Case