What capacity caps can I set per buyer?

Three: a daily cap (resets at midnight ET), a monthly cap (resets on the 1st), and a concurrency cap on simultaneous active calls. Progress bars turn yellow at 70% and red at 90% so near-capacity buyers are visible at a glance.

How do business hours work for buyers?

You set start/end time in Eastern Time (with DST-aware evaluation) and individually toggle days of the week. A buyer who only accepts calls on weekdays 8 AM – 6 PM can be configured in seconds and is automatically skipped outside that window.

Can I require specific IVR data before a buyer receives a call?

Yes. A comma-separated required-fields list (e.g., "vertical, zip_code") must be captured by the IVR before the buyer is eligible to receive a ping or static route — so buyers never get under-qualified calls.

Can a buyer participate in both static pricing and ping-post auctions?

Yes. Each offer has a static price-per-call and a separate ping-post block (ping URL, post URL, auth, minimum bid, timeout). The routing plan decides which mode applies per campaign, so the same buyer can serve both.

Buyer Management

Q: How do I see a buyer's current status and recent activity?

The offer detail page shows destination number, pricing, caps with real-time usage, total stats (calls, completed, revenue), and the 20 most recent calls for that buyer in one view.

Caps, hours, payouts, and bidding — per offer, fully configurable.

What is Buyer Management?

Buyer management is the layer that controls how calls are distributed across the buyers you sell to. Each buyer is configured with capacity caps (daily, monthly, concurrency), business hours, pricing, ping-post settings, and required qualification fields — so the routing engine only sends calls to buyers who can actually take them under the terms they agreed to.

Key Capabilities

Capacity caps with visual progress bars: daily cap (resets at midnight ET), monthly cap (resets on the 1st), and concurrency cap (maximum simultaneous active calls) — bars turn yellow at 70% and red at 90%
Business hours configuration: start/end time in Eastern Time with DST-aware evaluation, plus per-day toggles (Mon-Sun) for buyers who only accept calls on specific days
Payout configuration: price per call for static routing, and separate ping-post configuration with ping URL, post URL, authentication (Bearer/API Key), minimum bid, and timeout
Required IVR fields: comma-separated list of field names (e.g., "vertical, zip_code") that must be captured by the IVR before a buyer receives a ping — ensures buyers only get qualified leads
Offer detail page showing destination number, pricing, caps with real-time usage, total stats (calls, completed, revenue), and the 20 most recent calls

Key Benefit

Control exactly how many calls each buyer receives, when they receive them, and what qualification criteria must be met — with real-time visibility into capacity utilization.

Real-World Use Case

Auto Insurance Buyer Configuration

A buyer accepts auto insurance calls only on weekdays 8 AM - 6 PM ET, with a maximum of 50 calls/day and 3 concurrent calls. They participate in ping-post auctions with a minimum bid of $35 and require the IVR to have captured "vertical" and "zip_code" fields. On their detail page, the daily cap bar shows 38/50 (yellow), concurrency shows 2/3 (green), and their average bid this month is $52.

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 Buyer Management?

Key Capabilities

Capacity caps with visual progress bars: daily cap (resets at midnight ET), monthly cap (resets on the 1st), and concurrency cap (maximum simultaneous active calls) — bars turn yellow at 70% and red at 90%

Business hours configuration: start/end time in Eastern Time with DST-aware evaluation, plus per-day toggles (Mon-Sun) for buyers who only accept calls on specific days

Payout configuration: price per call for static routing, and separate ping-post configuration with ping URL, post URL, authentication (Bearer/API Key), minimum bid, and timeout

Required IVR fields: comma-separated list of field names (e.g., "vertical, zip_code") that must be captured by the IVR before a buyer receives a ping — ensures buyers only get qualified leads

Offer detail page showing destination number, pricing, caps with real-time usage, total stats (calls, completed, revenue), and the 20 most recent calls

Real-World Use Case