Offer Cap

An offer cap is a protection mechanism for both publishers and buyers. From a buyer's perspective, it prevents overspend: 'I only want 20 calls per day at $30/call, so my daily spend is capped at $600.' Once 20 calls are delivered, they're paused until the next day. This is essential for small businesses (solo plumbers, small law firms) who can't handle unlimited volume.

From a publisher's perspective, offer caps enable load balancing across buyers: 'Buyer A can take 30 calls/day, Buyer B 25/day, Buyer C 15/day.' The routing engine respects these caps automatically. If Buyer A hits 30 calls before 11pm, the routing engine starts routing to Buyer B instead.

Caps exist at multiple levels:

**Daily cap**: Maximum calls per calendar day. Resets at midnight.

**Weekly cap**: Maximum calls per week. Resets every Sunday.

**Monthly cap**: Maximum calls per month. Resets on the 1st.

**Concurrency cap**: Maximum simultaneous active calls. If a buyer has a concurrency cap of 5, the 6th incoming call is held or routed to the next buyer.

CallMatrix enforces all caps in real time. When a cap is reached, the routing engine immediately routes the next call to the next eligible buyer (by strategy: auction to the next-highest bidder, weighted random to the next weighted buyer, etc.). Calls are never held or delayed due to caps — they're routed or dropped per your fallback configuration.

Cap monitoring is critical. If a buyer has a $10K/month budget and your calls average $50/call, their cap should be 200 calls/month. If you send 250 calls, 50 go unpaid. Proper cap configuration ensures buyers have adequate budgets and publishers get paid for all delivered calls.