The Sachetization Trap

The Sachetization Trap

When capability becomes cheap, organizations can use it to expand access — or simply extract more cheaply.

India is in the middle of a Voice AI gold rush. Quite a few Voice AI startups have emerged in recent months — Bolna, Ringg, Arrowhead, Vaani, Navana, to name a few.

The premise makes sense: replace the telecaller, reduce costs, and scale the conversation. Many have also shown early success with design partners, with BFSI leading the charge. On paper, the value proposition is obvious. You can handle different languages and dialects at scale without relying on a telecaller vendor that needs constant training and monitoring. Voice AI doesn't tire. It adapts to dialects. It is infinitely patient.

On the surface, this looks like a classic India success story. Just as we made shampoo, mobile data, and payments cheap and accessible, we are now sachetizing AI — low-cost, bite-sized, ubiquitous. Vendors are selling minutes for pennies. Voice AI has dramatically reduced the cost of conversation.

But there is a distinction that is easy to miss.

Sachetization as access is revolutionary.

Sachetization as extraction is noise.

The technology is the same. The architectural choice is not.

The sachetization fork: access vs. extraction
The architectural choice
Same technology. Opposite outcomes.
✓ Access
Sachetization
as Access
Making capability cheap, small, and ubiquitous — so that people who couldn't before, now can. Abundance expands the market.
Shampoo sachets — brought hygiene to 500M people who couldn't afford a bottle
Jio's ₹10/day data — made the smartphone the primary computer for rural India
UPI on feature phones — payments without a bank account or a card
Voice AI for a Kirana owner with no website, no app, just a Maps listing
✗ Extraction
Sachetization
as Extraction
Using cheap distribution to maximize volume — without relevance, continuity, or value. Abundance amplifies noise.
Voice AI blasting 1M leads from a generic database with zero personalization
The same rigid telecaller script, now read by an AI at 1,000x scale
No context passed between AI handoffs — customer repeats their story three times
Optimizing cost-per-minute, not relevance — the SMS inbox problem, repeated
The technology is the same. Whether it's Access or Extraction is an architectural choice, not a technical one.

Doctrine Concept — Access vs. ExtractionWhen capability becomes inexpensive, organizations instinctively use it to increase volume rather than increase value. The trap is not cheap technology. It is using abundance for extraction rather than access.

Extraction here does not mean exploitation in the political sense. It simply means using technological abundance to produce more without increasing relevance, continuity, or value.

Sachetization as access is revolutionary — shampoo sachets, Jio's data, UPI on feature phones. Sachetization as extraction is noise — the same capability deployed to push more volume without relevance or continuity. The technology is the same but the architectural choice is not.

1. The Spam Factory

Most Voice AI deployments in India are built for Resource Substitution. The basic model is simple: replace the human telecaller with Voice AI — the same scripts, now delivered at machine scale.

  • Old Model: Hire humans to read rigid scripts.
  • New Model: Spin up AI agents to read the same rigid scripts at machine scale.

It helps to step back and look at the customer experience. Did anyone actually enjoy credit card and loan calls? Truecaller became increasingly useful as unsolicited calls became more common and intrusive.

When technological abundance is used for extraction, the channel itself begins to degrade.

We have seen this before with SMS. Fifteen years ago, the SMS inbox was still a place for conversation. Today, it is largely a graveyard of spam, with much of its everyday utility reduced to OTPs, alerts, and transactional messages. This happened because we optimized the channel for cost, not relevance. Once it became cheap enough to blast a million messages, businesses had less reason to care about whether any individual message mattered. The signal-to-noise ratio collapsed, and users moved to WhatsApp — a channel with more friction and stronger consent — for actual conversation.

The SMS story is not a historical anecdote. It is evidence of a recurring pattern: when technological abundance is used for extraction, the channel degrades under its own volume.

Voice AI is now at risk of following the same path. When a lender blasts a million leads from a generic database, it isn't engaging. It is fishing, with little context and little personalization. Increase the scale by another order of magnitude, and the degradation arrives sooner.

If we continue down this path, the phone call risks becoming what SMS became: a channel that remains functional but loses its value as a place for meaningful interaction.

The channel graveyard: when cost beats relevance
Signal-to-noise collapse over time
The SMS Playbook — Repeated
Signal/
Noise
2005
SMS
Personal conversation channel. Friends coordinate, families stay connected, communities form.
92%
2010
SMS
Businesses discover bulk SMS. Cost: ₹0.05/message. Volume: feasible for any company.
68%
2014
SMS
Costs collapse further. Every lender, insurance co, and e-commerce player blasts millions daily.
31%
2017
SMS
Inbox is unreadable. WhatsApp becomes the channel for real conversation. SMS → OTP graveyard.
8%
2022
Voice AI
Voice AI launches. Early results: 60-70% deflection, ₹X/minute costs. Leadership excited.
78%
2025
Voice AI
Dozens of startups. 1M-lead blasts with zero personalization. Truecaller AI spam detection emerging.
44%
20??
Voice AI
No one answers unknown calls. Phone call goes the way of the SMS. Channel is socially bankrupt.
5%
We optimized SMS for cost, not relevance — abundance used for Extraction. The signal-to-noise ratio collapsed, and users migrated to WhatsApp. Voice AI is on the same trajectory — unless architecture chooses Access instead.

2. The Uncanny Valley

The second failure is structural. Most deployments are retrofitting Generative AI into call-center logic built for an earlier era.

Consider the typical experience:

  • Voice AI: Great conversation, understands intent, but hits a wall.
  • Human Agent 1: Zero context passed. Customer repeats everything.
  • Sales Agent: Zero context passed. Customer repeats everything again.
  • Outcome: The AI worked, but the system failed.
Stateless systems: great AI, broken continuity
A Typical Extraction Journey
Interactions optimized. Relationships abandoned.
🤖
Voice AI
Great conversation
Understands intent, navigates dialect, gathers all relevant context. Customer feels heard.
Context: Fully gathered
👤
Human Agent 1 — Customer Service
Context: Zero
"Can you tell me your issue again?" Customer repeats everything. Frustration begins.
Context: Dropped at handoff
👤
Human Agent 2 — Sales
Context: Zero (again)
"Sorry, can I get your details one more time?" Customer has now explained themselves three times.
Context: Dropped again
Outcome
The AI worked. The system failed.
The voice sounded human. The continuity was nonexistent. The customer doesn't grade the AI — they grade the brand.
A stateless architecture cannot produce relationships. It can only produce transactions. The customer grades the brand — not the AI.

The voice sounded human, but there was no continuity behind it. The customer doesn't care that “the AI is good.” They care about the experience of engaging with the brand — whether with AI or a human — and whether that interaction actually moves their intent forward.

A system without continuity cannot build a relationship. It can only process transactions.

3. The Real Opportunity

The promise of Voice AI in India is not cost reduction. It is structural leapfrogging.

We have seen glimpses of this with the Soundbox. Why did Soundboxes work in India? Because merchants didn't want to look at screens or log into dashboards. An audio confirmation of payment solved a basic problem of trust. Millions of Indian businesses — kiranas, traders, service providers — never fully adopted the PC era and have often struggled with the SaaS era. ERPs and dashboards are difficult to use for businesses that run on WhatsApp, relationships, and intuition.

Voice AI offers a different path.

Imagine a business with no website, no app, and no login — just a Google Maps listing front-ended by Agentic Voice AI. In this world, Voice is not a dialer or IVR. Voice is the Operating System. The business owner doesn't manage software; they speak to it.

In this world, Voice is not a dialer or an IVR. Voice becomes the interface to the business.

That is the opportunity: not replacing the telecaller, but removing layers of software and interaction that were necessary in the previous architecture.

We need to apply the Ditto Insurance philosophy here. Ditto led with understanding the user's hesitation, rather than pushing a policy at them. They created conversations, understood needs, educated the customer, and then arrived at a solution without making the interaction feel like a sales process.

That is access: using abundance to increase relevance, continuity, and value — not merely volume.

4. Build the Personal Secretary

To unlock this, we must shift the metaphor from Telecaller to Personal Secretary. You have a transactional engagement with a telecaller. With a secretary, it's contextual.

A good secretary knows:

  • The Business: deeply understands the product, pricing, and edge cases.
  • The User: knows where the prospect is in the lifecycle.
  • The Context: maintains continuity across conversations — what was said, promised, and left unresolved.

This requires omni-channel, multi-session continuity. It is not a linear, transactional sell. It is a relationship: the AI front-ends the initiative, knows exactly when to hand off to a human, and the user engages with the brand — sometimes with AI, sometimes with humans — always with continuity. The context remains intact.

The metaphor shift: telecaller → personal secretary
Extraction
Telecaller
Transactional. Script-bound. Stateless.
Engagement type
Transactional — one call, one script
Memory
Resets with every call
Personalization
Zero — same script for 1M leads
Handoff
Drops context at every transition
User experience
Interruption — call that wasn't asked for
Brand experience
Siloed bot. Sometimes AI, sometimes human.
Access
Personal Secretary
Contextual. Relationship-aware. Continuous.
Engagement type
Contextual — relationship across sessions
Memory
Persistent — remembers the relationship
Personalization
Deep — knows product, user, and lifecycle stage
Handoff
Knows exactly when and how to hand off to human
User experience
Service — conversation when it's needed
Brand experience
Unified brand — AI and human feel like one entity
The Business
Product depth
Deeply understands the product, pricing, edge cases, and what the customer actually needs.
The User
Lifecycle stage
Knows where the prospect is — first touch, hesitating, ready to close, or about to churn.
The Context
Relationship memory
Maintains continuity across conversations — remembers what was said, promised, and left unresolved.

The Bottom Line

If you treat Voice AI as an outsourced service ("Get me leads at ₹X/min"), you will get the Spam Factory. If you treat Voice AI as an unlock to build relationships at scale, you get something different: an interface that can expand access to the business.

Voice AI startups can provide the technology and capabilities. But operationalizing them is the brand's job. That means redesigning workflows, roles, handoffs, and incentives around the new capability. Without that change, Voice AI may look good in a pilot and still end up as another cost center.

Two futures: Extraction or Access
The architectural choice
Two futures for abundant capability
Path A
Extraction
The Spam Factory
Abundance used to maximize volume — making telecalling 1,000x more annoying until no one answers the phone.
Replace telecaller with Voice AI reading the same rigid scripts
Blast 1M leads from a generic database — zero personalization
Optimize for cost-per-minute, not resolution or relationship
Every handoff resets to zero — interactions, not relationships
Phone call becomes socially bankrupt, like the SMS inbox
Outcome: Phone call goes the way of the SMS. Channel is socially bankrupt.
Path B
Access
New Operating System
Abundance used to expand access — building relationships at scale rather than extracting from existing ones.
Voice as the interface — Kirana owner speaks to their software
Ditto Insurance model — lead with understanding, not with the product
Continuity across sessions — the brand remembers you
AI front-ends the initiative, hands off to human at the right moment
Interface-less businesses — no website, no app, just conversation
Outcome: Markets that did not exist before — businesses that skipped SaaS now run on conversation.

The pattern extends beyond India

This is not a Voice AI problem. It is not an India problem. It is a recurring organizational pattern.

India makes the pattern unusually visible. It skipped or compressed multiple technology eras, so AI arrives under different institutional conditions than in markets where those eras were adopted sequentially. That history makes both the opportunity and the risk easier to see.

But the structural dynamic is the same everywhere: when capability changes, institutions repeatedly reuse architectures designed for the previous era.

The question is no longer how we make AI cheaper. It becomes: why do institutions repeatedly fail to redesign themselves, even when the limits of the existing architecture are already visible?

That question belongs to the next essay.

See what happens when abundant capability changes the economics of a system.

Experience Silent Failure →