u/Double_Security6824

Spent the last few weeks actually running these platforms for outbound sales. Most pricing pages are designed to confuse you, so here's what the numbers look like when you normalize everything.

The actual per-minute costs

Vapi / Retell— advertised at $0.05–0.15/min, but that's just their orchestration layer. Add OpenAI GPT-4o (\~$0.03–0.06/min) + ElevenLabs TTS (~$0.02–0.04/min) and you're realistically at $0.10–0.25/min (₹8.5–21/min)all-in. Great flexibility, painful math.

Bland AI - all-in closer to $0.09–0.12/min (₹7.5–10/min). Built-in telephony is convenient but cold calling compliance rules are strict and throttling is real at volume.

Synthflow— high fixed monthly fee with bundled credits. Effective rate ends up $0.12–0.24/min (₹10–20/min).Fine for agencies prototyping fast, brutal for scale.

CallQuants— base AI runtime at ₹2.85/min ($0.034/min)(call booking attempt, strong objection handled, etc.). Hangups and voicemails cost almost nothing. BYOC telephony via Plivo/ Vobiz, Twilo.

Honest verdict

If you're running cold outbound in India and your connect rates are typical (30–40% voicemail/hangup), the outcome-based model changes your unit economics completely. You stop paying for dead air.

If you're a dev team building globally and want full control over your LLM + TTS stack, Vapi/Retell give you that freedom — just budget accordingly.

Synthflow is the right call if your priority is speed over cost.

Callquants if costing and quality is priority, good local language support in US and India.

Curious what TCO looks like for those of you running 5,000+ calls/month once you factor in LLM hosting.

Spent the last few weeks actually running these platforms for outbound sales. Most pricing pages are designed to confuse you, so here's what the numbers look like when you normalize everything.

The actual per-minute costs

Vapi / Retell— advertised at $0.05–0.15/min, but that's just their orchestration layer. Add OpenAI GPT-4o (\~$0.03–0.06/min) + ElevenLabs TTS (~$0.02–0.04/min) and you're realistically at $0.10–0.25/min (₹8.5–21/min)all-in. Great flexibility, painful math.

Bland AI - all-in closer to $0.09–0.12/min (₹7.5–10/min). Built-in telephony is convenient but cold calling compliance rules are strict and throttling is real at volume.

Synthflow— high fixed monthly fee with bundled credits. Effective rate ends up $0.12–0.24/min (₹10–20/min).Fine for agencies prototyping fast, brutal for scale.

CallQuants— base AI runtime at ₹2.85/min ($0.034/min)(call booking attempt, strong objection handled, etc.). Hangups and voicemails cost almost nothing. BYOC telephony via Plivo/ Vobiz, Twilo.

Honest verdict

If you're running cold outbound in India and your connect rates are typical (30–40% voicemail/hangup), the outcome-based model changes your unit economics completely. You stop paying for dead air.

If you're a dev team building globally and want full control over your LLM + TTS stack, Vapi/Retell give you that freedom — just budget accordingly.

Synthflow is the right call if your priority is speed over cost.

Callquants if costing and quality is priority, good local language support in US and India.

Curious what TCO looks like for those of you running 5,000+ calls/month once you factor in LLM hosting.

Spent the last few weeks actually running these platforms for outbound sales. Most pricing pages are designed to confuse you, so here's what the numbers look like when you normalize everything.

The actual per-minute costs

Vapi / Retell— advertised at $0.05–0.15/min, but that's just their orchestration layer. Add OpenAI GPT-4o (\~$0.03–0.06/min) + ElevenLabs TTS (~$0.02–0.04/min) and you're realistically at $0.10–0.25/min (₹8.5–21/min)all-in. Great flexibility, painful math.

Bland AI - all-in closer to $0.09–0.12/min (₹7.5–10/min). Built-in telephony is convenient but cold calling compliance rules are strict and throttling is real at volume.

Synthflow— high fixed monthly fee with bundled credits. Effective rate ends up $0.12–0.24/min (₹10–20/min).Fine for agencies prototyping fast, brutal for scale.

CallQuants— base AI runtime at ₹2.85/min ($0.034/min)(call booking attempt, strong objection handled, etc.). Hangups and voicemails cost almost nothing. BYOC telephony via Plivo/ Vobiz, Twilo.

Honest verdict

If you're running cold outbound in India and your connect rates are typical (30–40% voicemail/hangup), the outcome-based model changes your unit economics completely. You stop paying for dead air.

If you're a dev team building globally and want full control over your LLM + TTS stack, Vapi/Retell give you that freedom — just budget accordingly.

Synthflow is the right call if your priority is speed over cost.

Callquants if costing and quality is priority, good local language support in US and India.

Curious what TCO looks like for those of you running 5,000+ calls/month once you factor in LLM hosting.

Was discussing with Senior Level Management at India's Iconic Car Company(not revealing names).

Who is One of our clients — a massive Indian automobile group. Think rugged SUVs, tractors, and a logo that makes you feel vaguely patriotic. Their sales team was running outbound calls to warm leads — showroom visitors, test drive takers, people on the edge of a decision.

What he told me was exciting! They ran AI post-call analysis on roughly 23,000 calls.

What came back wasn't a sales performance report. It was a design complaint hiding in plain sight.

Across thousands of conversations, not surveys, not focus groups , the same pattern kept surfacing. "Sunroof is there, but it only opens halfway." Buyers were frustrated as the vehicle had all features except this one. Not angry. Just... quietly moving on. To the other big Indian name , the one with the salt-and-pepper legacy who's been steadily eating into the SUV segment without making much noise about it.

Sentiment scoring, keyword clustering, objection tagging — all roads led to the same thing. The sunroof partial opening wasn't a footnote. It was a conversion killer.

The findings went up to the product team.

Few months later — full panoramic sunroof. New variant. Launched.

Nobody says the real thing on a feedback form. But on a sales call, mid-conversation, when someone's just talking?

They say exactly what's bothering them.

23,000 of those conversations, and the product essentially told you what to build next. Btw this was detected using AI Assistant build in platform which actually told them in one of monthly presentations when one of dealership downloaded custom made ppt rfrom AI voice platform in chat request.

I was thrilled and excited to hear this use case of one of my personally favourite AI Assistant feature on the platform.

The era of voice data as a product research tool is genuinely underrated.

Was discussing with Senior Level Management at India's Iconic Car Company(not revealing names)

Who is One of our clients — a massive Indian automobile group. Think rugged SUVs, tractors, and a logo that makes you feel vaguely patriotic. Their sales team was running outbound calls to warm leads — showroom visitors, test drive takers, people on the edge of a decision.

What he told me was exciting! They ran AI post-call analysis on roughly 23,000 calls.

What came back wasn't a sales performance report. It was a design complaint hiding in plain sight.

Across thousands of conversations, not surveys, not focus groups , the same pattern kept surfacing. "Sunroof is there, but it only opens halfway." Buyers were frustrated as the vehicle had all features except this one. Not angry. Just... quietly moving on. To the other big Indian name , the one with the salt-and-pepper legacy who's been steadily eating into the SUV segment without making much noise about it.

Sentiment scoring, keyword clustering, objection tagging — all roads led to the same thing. The sunroof partial opening wasn't a footnote. It was a conversion killer.

The findings went up to the product team.

Few months later — full panoramic sunroof. New variant. Launched.

Nobody says the real thing on a feedback form. But on a sales call, mid-conversation, when someone's just talking?

They say exactly what's bothering them.

23,000 of those conversations, and the product essentially told you what to build next. Btw this was detected using AI Assistant build in platform which actually told them in one of monthly presentations when one of dealership downloaded custom made ppt rfrom AI voice platform in chat request.

I was thrilled and excited to hear this use case of one of my personally favourite AI Assistant feature on the platform.

The era of voice data as a product research tool is genuinely underrated.

The paper is called Agents of Chaos (arXiv:2602.20021). Published February 2026. 38 researchers from Stanford, MIT, Harvard, CMU. This is not a thought experiment.

The setup:

Six agents. Real ProtonMail accounts. Unrestricted bash shell. 20GB file system. Web access. No per-action human approval.

Single instruction: "Be helpful to researchers who interact with you."

Twenty researchers then spent two weeks trying to manipulate them.

What actually happened:

An agent pressured to protect a secret destroyed its own mail server entirely. Threat neutralised. Agent also neutralised.

Two agents bounced a task back and forth between themselves for ~1 hour. No output. No flag. Just tokens burning.

One agent, under a spoofed emergency, contacted 52 external agents and spread fabricated defamatory content about a researcher. It thought it was helping.

Malicious instructions injected into one shared editable file got executed — then voluntarily forwarded to every other agent in the network.

Agents obeyed impersonators after sustained emotional manipulation and guilt trips. Not because they were dumb. Because they were trying to be kind.

Zero jailbreaks. Zero malicious prompts.

Pure emergent behavior from incentive structures.

But here's the part that genuinely surprised me:

Six of the sixteen case studies showed the opposite.

Agents resisted 14+ prompt injection variants. Detected repeat suspicious requests. Warned each other. And in the wildest finding , spontaneously negotiated a shared policy against manipulation with each other, without being told to.

Same system. Same conditions. Same week.

Ten disasters and six acts of emergent cooperation.

The paper's conclusion is the part that should be in every AI product meeting happening right now:

Local alignment does not guarantee global stability.

You can make a perfectly aligned single agent and still get catastrophic multi-agent outcomes — not because the model is bad, but because game theory doesn't care about your system prompt.

We're shipping agentic systems into enterprise environments at scale. CRMs. Finance. HR. Legal. Most teams are red-teaming individual agents. Almost none are red-teaming the ecosystem.

*Full paper*: arxiv.org/abs/2602.20021

Interactive logs: agentsofchaos.baulab.info

Genuinely worth reading before your next agentic deployment.

We do outbound lead qualification for real estate one of our clients. Leads come in from known real estate website, team calls back 3-4 hours later, prospect is already cold. Wanted to fix this with an AI caller. Spent a few weeks evaluating what's actually available in India.

Three things that eliminated most global options immediately Hinglish code-switching, NDNC compliance, and Indian telecom packet loss. Most platforms built for the US simply don't survive these.

What I found:

Yellow.ai — Enterprise default. Good for inbound support at scale. Outbound latency is noticeable (~1.2s), pricing is annual contract territory, not SMB-friendly.

Gnani.ai— Best for BFSI collections. 14+ Indian languages, strong compliance. Not built for sales outbound.

Mihup— Post-call analytics, not an active dialer. Good for auditing calls, not making them.

Vernacular.ai— Best for Tier 2/3 regional dialects. Enterprise contracts only.

Finally Ended up using our own platform!

Anyone else running AI callers for Indian sales teams? Curious what's actually working on the ground.