All FAQs

Calls & Telephony

The call stack — routing, IVR, tracking numbers, and live transfer — and how much of it is ours.

17 questions answered

Is the call system proprietary?

Yes. It is our own call routing stack — IVR, dynamic number insertion, whisper prompts, call distribution, agent-presence and concurrency controls, and call dispositions — built on carrier-grade telephony infrastructure, plus an AI voice dialer with built-in TCPA compliance controls.

Related: Live Lead Transfer

What happens when a consumer dials one of my tracking numbers?

The call is matched to its campaign, partner and offer, optionally screened by an IVR menu, routed against your buyer contracts, and bridged to the winning buyer — with whisper, recording, billing and disposition all handled as one tracked lifecycle.

Related: Call Tracking Software

Can I put an IVR menu in front of routing?

Yes. You can play a menu, retry on invalid input with your own prompt, and then route the caller through the engine, transfer them straight to a number, or end the call. The caller’s menu selection is carried into routing as a filterable attribute.

Related: Call Routing Software

Do you support a whisper announcement, and can the agent decline the call?

Yes. The agent hears a whisper prompt built from that call’s own data and must press a key to accept, so the caller is only connected to an agent who is actually there — and a declined call moves straight on to the next buyer.

If the top-ranked buyer doesn’t answer, how many buyers will you try?

The call waterfalls sequentially through up to five ranked buyers, failing over on no answer, busy or rejection, and every attempt is written to the call’s routing trace.

Related: Call Routing Software

Do calls and form leads share the same buyer contracts, filters and caps?

Yes — calls run through the same contract, filter, schedule and cap engine as form leads, so one buyer setup governs both channels. Your spend caps apply across both, and volume caps can be shared or tracked separately per contract.

Related: Call Routing Software

Can a repeat caller be sent back to the buyer who bought them last time?

Yes. Caller and lead affinity route a returning caller to the buyer who handled them before, within a window you set, with a configurable fallback for when that buyer is unavailable.

Can I stop one agent from being sent a second call while they’re already on one?

Yes — agent-presence gating is always enforced: an agent on a live call is not sent another one, and a portal agent is only counted as available while their browser session is sending a live heartbeat. Configurable concurrency limits per buyer and per contract sit on top of that.

Do you support dynamic number insertion, and how is the number pool sized?

Yes. Each visitor is leased a tracking number from a campaign or shared pool that holds a minimum-available floor, buys more automatically when it runs short within your ceiling, and decays idle numbers back to the shared pool so you are not renting numbers nobody dials.

Related: Call Tracking Software

What visitor data follows the call into routing and reporting?

Marketing tags from the visitor’s URL and any declared form fields captured on the page ride with the call into routing, billing and reporting — and values flagged as personal data are encrypted at rest.

Related: Call Tracking Software

Do you record calls, and can recording be turned off for a specific number or buyer?

Recording is on by default with overrides at three levels — a per-number kill switch, a per-contract override, and a per-offer default. A consent announcement plays to the caller before the bridge and can be suppressed per offer for one-party-consent states.

How are calls billed, and where does the billable clock start?

Billing is per call, from prioritized rules supporting fixed, revenue-share and raw-call payouts against length, connected, dialed or postback conversion. Duration thresholds are measured from the anchor you choose: when the call arrives, when we dial the buyer, or when the buyer answers.

Can the price change based on the traffic source or the buyer’s reported disposition?

Yes. Billing rules match on call tags and on the disposition the buyer reports, so the same buyer can pay one price for a sold call and another for a quote — and rules layer at the offer, campaign or contract level.

How do buyers report what happened on a call?

From the buyer portal or through the API with a service token — both write through one shared path — using a post-connect vocabulary of sold, quoted, call back, voicemail, not interested and do-not-call, with wrap-up notes and a reported deal value.

Do you push real-time call events into our systems?

Yes. Ringing, accepted, missed and completed events dispatch to your endpoints as HMAC-signed webhooks, with personal data deliberately redacted from the ringing payload so an agent-alert integration never carries more than it needs.

Can agents take calls in a browser instead of a desk phone?

Yes — a browser softphone seat is available, and answering inside an authenticated portal session satisfies the whisper accept-gate. If the browser does not pick up the invite, the call moves on to the next buyer rather than stranding the caller.

What stops a buyer routing calls to a high-cost destination?

Destinations are classified as normal, premium, toll-free or non-US against live termination rates, and a premium destination carries a per-minute surcharge stamped onto the contract — so the cost of an expensive routing choice is attributed to the buyer who made it.

Still have a question?

Pricing is a flat plan plus published usage rates, and a build is configuration rather than custom development. Start where it makes sense for you.