CUSTOMER STORIES
The numbers moved. The names stay out of it.
Seven operators, seven problems you'll probably recognize, and what changed after they moved to CallGrid.
The dashboard is real. The name never leaves our records.
WHY NO LOGOS
Every story on this page comes from a real account and a real dashboard. We don't publish names, in this business your routing setup is your edge, and our customers' edge is not our marketing asset. If you want references, book a call and we'll make introductions the right way.
SEVEN OPERATORS
Find the problem you recognize.
A Medicare aggregator, ~100K calls/mo
How much of your billable duration exists on only one side of the call?
Read storyA high volume Medicare and final expense aggregator, ~99K calls/mo
What happens to the caller when a buyer hangs up mid transfer?
Read storyAn Inc. 5000 performance agency with an in-house call center
What if you could score a call with your own data before you bid on it?
Read storyA Medicare buyer whose agents sit behind a dialer
How many calls did you pay for last week where no agent was actually ready?
Read storyA CTV performance agency shipping 10 to 30 creatives a week
How long does it take you to match a call record to the buyer's report? What if the answer was zero?
Read storyA debt and home services seller, ~16K calls per month
When did you last A/B test your routing strategy instead of arguing about it?
Read storyAn insurance agency owner with a category named 1-800 number
What are the calls you can't sell worth? Right now, for most agencies, the answer is voicemail.
Read storyHow much of your billable duration exists on only one side of the call?
True Connect (answer on bridge billing) plus RPC-E routing
THE PROBLEM
Standard call bridging adds five to nine seconds of duration that one side bills and the other side never sees. At 100K calls a month, roughly 7.8% of billable duration existed on only one side of the ledger. The team was also ranking buyers on raw RPC while their highest quoted buyers were quietly their worst connecting buyers.
WHAT CHANGED
True Connect starts the billable timer only when a human voice confirms on the buyer side, so both parties see identical duration. Routing rank moved from RPC to RPC-E, which builds no-connect and short-call penalties into the number, so a $10 buyer answering half the time ranks below an $8 buyer answering 95% of the time.
THE RESULT
Both sides reconcile to the same number, weekly manual reconciliation became a spot check, and the recovered gap was worth about $24K in the first quarter.
- VERTICAL
- Medicare (Insurance)
- SCALE
- ~100K calls/mo
- ROLE IN CALL FLOW
- Seller (publisher)
- FEATURES USED
- True ConnectRPC-E Routing
- TIME ON CALLGRID
- Live since cutover
"We finally stopped paying for the gap between what we reported and what our buyers measured."
What happens to the caller when a buyer hangs up mid transfer?
Call recovery, retry routing, Turbo Routing
THE PROBLEM
At scale, buyer side terminations and no-connects were a silent leak. A rejected or dropped call was simply a dead call, and slow waterfall routing compounded it.
WHAT CHANGED
Call recovery detects a buyer side termination inside ten seconds and re-routes the live caller, who never knows anything failed. Retry routing was tuned so second chances go to the best available buyers instead of a catch-all. Turbo Routing cut the no-connect rate, which the team credits as a bigger win than any pricing line.
THE RESULT
Roughly eleven thousand dollars in recovered calls, plus meaningfully lower platform overhead at the same volume.
- VERTICAL
- Medicare, Final Expense (Insurance)
- SCALE
- ~99K calls/mo
- ROLE IN CALL FLOW
- Seller (publisher)
- FEATURES USED
- Call RecoveryRetry RoutingTurbo Routing
- TIME ON CALLGRID
- Running at full volume
What if you could score a call with your own data before you bid on it?
Value extraction at bid time, Turbo Routing, duplicate bid management
THE PROBLEM
Their previous setup was losing calls to slow routing, expired bids, and duplicate pings, and the team wanted to hit their own scoring API during the auction and route on the result, without being required to buy anyone else's data.
WHAT CHANGED
Value extraction lets them call their own scoring API mid-bid and act on the response. Turbo Routing and duplicate bid management closed the speed and duplicate leaks. A complex non-standard buyer webhook was rebuilt during onboarding, not quoted as a services project.
THE RESULT
Live and used daily, with the operations team deep in reporting and routing.
- VERTICAL
- Insurance, Debt Relief
- SCALE
- Inc. 5000 honoree, in-house call center
- ROLE IN CALL FLOW
- Seller & Buyer (hybrid)
- FEATURES USED
- Value ExtractionTurbo RoutingDuplicate Bid Management
- TIME ON CALLGRID
- Live since launch, daily use
"The best conversation we've had with a platform vendor."
How many calls did you pay for last week where no agent was actually ready?
Bidirectional agent availability ping
THE PROBLEM
Agents sit behind a dialer that knows availability, but on their previous setup a system pickup counted as a connect and started billing even when nobody was ready. Dozens of paid calls a week with nothing on the other end.
WHAT CHANGED
The publisher pings CallGrid, CallGrid pings every agent through the dialer's availability API, and if all agents are busy the call is rejected back to the publisher before any IVR pickup or billable second. A split parser read the dialer's non-standard response format with no rebuild.
THE RESULT
The billing leak is closed by design, not by dispute. Exact dollars saved land after the side by side window.
- VERTICAL
- Medicare (Insurance)
- SCALE
- Volume not published
- ROLE IN CALL FLOW
- Buyer
- FEATURES USED
- Bidirectional Agent Availability Ping
- TIME ON CALLGRID
- Live day one
How long does it take you to match a call record to the buyer's report? What if the answer was zero?
Source call ID tagging, per-creative number pools, group routing, open API with live Swagger docs
THE PROBLEM
Reconciliation on their previous platform required reverse engineering a buried join key that varied by buyer, roughly three days of work, on top of a messy account structure with duplicate sources and empty number pools.
WHAT CHANGED
CallGrid attaches a source call ID tag to every call sent to a buyer, so the join key is inherited automatically. The account was restructured into a single CTV source with one pool, every number tagged with its creative name, and group routing opened up split testing they did not have before.
THE RESULT
A multi day reconciliation chore is gone, and the migration is proceeding to full cutover.
- VERTICAL
- CTV
- SCALE
- 10-30 new creatives/wk
- ROLE IN CALL FLOW
- Buyer
- FEATURES USED
- Source Call ID TaggingPer-Creative Number PoolsGroup RoutingOpen API (Swagger)
- TIME ON CALLGRID
- Migrating to full cutover
"The fact that you even have Swagger docs is already huge."
When did you last A/B test your routing strategy instead of arguing about it?
Average RPC predictive routing with A/B testing, RPC-E and ACD reporting, native AI Agent (in evaluation)
THE PROBLEM
Wanted better routing performance and one platform that could also qualify calls, which they were running through an external AI tool for debt amount screening.
WHAT CHANGED
Average RPC predictive routing validated with A/B tests instead of opinions, reporting pinned to RPC, RPC-E, and ACD, and the native AI Agent is being evaluated to replace the external qualifier so the whole flow lives on one platform.
THE RESULT
Higher RPCs, margins, and conversion since the migration, with no negative team feedback.
- VERTICAL
- Debt Relief, Home Services
- SCALE
- ~16K calls/mo
- ROLE IN CALL FLOW
- Seller
- FEATURES USED
- Average RPC Predictive RoutingA/B TestingRPC-E & ACD ReportingAI Agent (in evaluation)
- TIME ON CALLGRID
- Ongoing, monthly training cadence
"Higher RPCs, higher margins, higher conversion rates across the board, with no negative feedback from the team."
What are the calls you can't sell worth? Right now, for most agencies, the answer is voicemail.
Routing-first plus bidding-first in one campaign, templated buyer setup, agent availability ping, DNI, conversion postbacks
THE PROBLEM
A category named 1-800 number generates roughly ten organic calls a day, most outside the agency's book of business. In-house calls needed to ring their own agents first, off-fit calls were going to voicemail. Two previous attempts at the architecture ended in three disconnected systems.
WHAT CHANGED
One campaign routes life insurance calls to in-house agents via availability ping, then falls through to category-matched paper call buyers built from templates, with circuit breakers per category, DNI ready for future paid traffic, and sold-policy postbacks attributed back to the original call.
THE RESULT
Calls that went to voicemail now produce revenue, three reports became one, and the playbook generalizes to any business holding a category named number.
- VERTICAL
- Insurance (Life)
- SCALE
- ~10 organic calls/day on the category number
- ROLE IN CALL FLOW
- Hybrid, in-house plus buyer network
- FEATURES USED
- Routing-First + Bidding-FirstTemplated Buyer SetupAgent Availability PingDNIConversion Postbacks
- TIME ON CALLGRID
- Live after one afternoon
"It didn't fit my routing-first use case anywhere else, so I built my own. Three systems later, this finally does both."
See what your numbers look like on CallGrid.
Month to month. No contracts. Bring one campaign and run it side by side.
† Customer reported, verification against platform data in progress.