Z
Zappio Team
AI & Real Estate Experts · 6 July 2026 · 13 min read
Loading article...
Zappio Team
AI & Real Estate Experts · 6 July 2026 · 13 min read
The telephony stack is the infrastructure layer that physically connects an AI Calling Agent to the Indian PSTN. Every ASR engine selection, every TTS latency optimization, every prompt engineering refinement — none of it matters if the telephony layer introduces call drops, audio degradation, number blocking, or concurrency limits that cap the system's ability to operate at scale.
In the Indian real estate context, the telephony stack must satisfy five operational constraints simultaneously: PSTN audio quality at 8kHz/G.711 with under 150ms one-way latency, SIP trunk concurrency sufficient for outbound burst calling, a clean number pool that does not trigger carrier spam flags, regulatory compliance for commercial outbound calling, and cost-per-minute economics compatible with AI Calling's usage-based pricing model. This article compares Exotel, Twilio, Plivo, and Tata Tele Business Services across all five dimensions.
The telephony provider is the interface between the AI Calling Agent's software layer and the physical PSTN. In an AI Calling deployment, the telephony stack handles four distinct functions.
The telephony layer is stateless from the AI perspective — the AI pipeline receives an audio stream and sends audio back; the telephony provider manages PSTN routing complexity. But the quality and architecture of the telephony layer determines whether the AI pipeline operates on clean, low-latency audio or degraded, high-jitter audio that cripples ASR accuracy.
One-way PSTN audio latency from buyer speech to AI pipeline receipt should be under 100ms; round-trip latency should be under 800ms total. Each additional transcoding stage in the audio path adds 15–40ms latency and introduces codec artifacts that raise ASR Word Error Rate. A telephony provider that routes Indian calls through a US PoP before reaching the AI pipeline adds 180–250ms of round-trip latency — enough to make conversation feel unnatural.
Real estate developers running portal campaigns generate lead spikes — 200–500 new leads from a weekend Meta campaign drop require immediate outreach within minutes. The telephony stack must support concurrent outbound call bursts of 50–200 simultaneous calls without degradation. Some providers impose hard concurrency limits at the account tier level; provisioning higher concurrency requires advance notice, contracts, or enterprise tier upgrades.
AI Calling at scale generates call volume patterns that carrier spam detection systems flag as automated calling — high call frequency from a single number, short call durations, identical call attempt patterns. Spam-flagged numbers display as "Spam Risk" on buyer phones, triggering immediate hang-ups. Providers with limited Indian number pools cannot rotate caller IDs frequently enough to avoid spam flagging, and providers that share number pools across customers inherit spam reputation from other customers' calling patterns.
Commercial outbound calling in India requires compliance with the Telecom Commercial Communications Customer Preference Regulations (TCCCPR) framework managed by TRAI. The telephony provider must support scrubbing of call attempts against the National Customer Preference Register (NCPR) — formerly NDNC — to avoid calling registered DND numbers. DND scrubbing compliance is a carrier-level obligation of the real estate developer deploying the AI Calling system; the telephony provider's role is to support the API hooks needed for DND-scrubbed number lists to be passed through the dialing system.
At 10,000 call-minutes/month, the difference between ₹0.50/minute and ₹1.20/minute is ₹7,000/month — ₹84,000/year. At 100,000 call-minutes/month, the difference scales to ₹70,000/month. Telephony cost is the largest per-call infrastructure cost after LLM inference and must be optimized relative to call quality trade-offs.
India's largest cloud telephony provider by Indian enterprise customer count, built exclusively for Indian PSTN connectivity with PoPs in Mumbai, Bengaluru, and Delhi NCR. Audio latency: 40–80ms one-way, best of evaluated providers for India-to-India calls. Concurrency: 50 default, 200–500 enterprise. Number pool: 10,000+ Indian virtual numbers with proactive spam-flag retirement. Native NCPR/DND scrubbing built in. Pricing: ₹0.50–₹0.70/minute. Weaknesses: limited international number support, less mature documentation than Twilio, no global PoP network. Optimal use case: any Indian domestic real estate AI Calling deployment; primary recommendation for NCR, Mumbai, Hyderabad, Bangalore, Pune markets.
The global cloud communications leader with the most extensive developer ecosystem. Audio latency: 80–160ms one-way — routes Indian PSTN calls through Singapore PoP, adding 30–60ms vs. India-domestic routing. Concurrency: uncapped by default. Number pool: inconsistent spam reputation, customer-managed health monitoring. Streaming API (Media Streams) is the most mature bidirectional WebSocket API in the industry, with native integrations across most AI voice frameworks. No native DND/NCPR scrubbing. Pricing: ~₹1.08/minute, 40–50% higher than Exotel. Optimal use case: NRI call segments, international number provisioning, or when Twilio's ecosystem integrations justify the cost premium.
A US-headquartered provider with strong Indian infrastructure partnerships, positioned between Twilio (premium) and Exotel (India-native). Audio latency: 60–120ms, routing through Mumbai and Chennai PoPs. Concurrency: 100 default, 500+ enterprise. Number pool: limited variety, manual quality monitoring. Streaming API less mature than Twilio but functional. Basic DND filtering, no native NCPR integration. Pricing: ~₹0.71/minute. Optimal use case: hybrid deployments where a US headquarters manages global communications infrastructure but India-origin real estate is a secondary market, or as a budget-conscious alternative to Twilio for teams already using Plivo globally.
The enterprise division of Tata Communications, providing direct PSTN access via Tata's owned network infrastructure. Audio latency: 30–60ms — lowest of evaluated providers, as Tata carries Indian PSTN traffic as a licensed carrier with zero intermediate routing hops. Concurrency: 500–5,000 with proper enterprise provisioning. Number pool: carrier-grade, no shared reputation risk. Streaming API is less developer-friendly, typically requiring SIP expertise or a SIP-to-WebSocket gateway. Full NCPR/DND compliance built in at the network layer. Pricing: ₹0.35–₹0.50/minute, lowest of evaluated providers, with volume discounts above 100,000 minutes/month. Optimal use case: large-scale developers processing over 50,000 calls/month with dedicated SIP/VoIP expertise, where cost optimization justifies integration complexity.
| Dimension | Exotel | Twilio | Plivo | Tata Tele |
|---|---|---|---|---|
| Audio Latency (one-way) | 40–80ms | 80–160ms | 60–120ms | 30–60ms |
| Default Concurrency | 50 calls | Uncapped | 100 calls | 500+ calls |
| Max Concurrency | 500 (enterprise) | Uncapped | 500 | 5,000+ |
| Number Pool Quality | Large, monitored | Moderate, unmonitored | Limited | Carrier-grade |
| Streaming API Maturity | Good | Best | Adequate | Complex (SIP) |
| Native DND Scrubbing | Yes | No | No | Network-level |
| Developer Experience | Good | Best | Good | Enterprise-sales |
| Cost/Minute (₹) | 0.50–0.70 | 1.00–1.20 | 0.71–0.90 | 0.35–0.50 |
| Setup Time | Hours | Minutes | Hours | Days–Weeks |
| Best For | Mid-large India RE | NRI/Global/Enterprise | Hybrid/Global | Very large scale |
Primary: Exotel. API-key setup in minutes, native Indian infrastructure, DND scrubbing built in, developer-friendly documentation, lowest complexity for the first deployment. Cost: ₹2,500–₹3,500/month at 5,000 calls × avg 1 minute.
# Exotel WebSocket streaming connection
EXOTEL_STREAM_URL = "wss://api.exotel.com/v1/streams/{call_sid}"
async def handle_exotel_stream(websocket, call_sid: str):
session = CallSession(call_sid=call_sid)
async for message in websocket:
data = json.loads(message)
if data["event"] == "connected":
session.stream_id = data["streamSid"]
elif data["event"] == "media":
# Decode base64 μ-law audio → ASR pipeline
audio_bytes = base64.b64decode(data["media"]["payload"])
transcript = await asr_pipeline.process(audio_bytes)
if transcript:
response_text = await llm_pipeline.generate(transcript, session)
tts_audio = await tts_pipeline.synthesize(response_text)
await websocket.send(json.dumps({
"event": "media",
"streamSid": session.stream_id,
"media": {
"payload": base64.b64encode(tts_audio).decode()
}
}))
elif data["event"] == "stop":
await session.finalize_and_sync_crm()Primary: Exotel (retain for domestic Hindi-Hinglish calls). Secondary: Twilio (add for NRI callers, international number provisioning, or when using Twilio ecosystem tools).
def select_telephony_provider(lead: Lead) -> str:
# NRI leads → Twilio (international number, international routing)
if lead.country_code not in ["+91"]:
return "twilio"
# Premium English-first leads → Twilio (better English TTS/ASR ecosystem)
if lead.segment == "luxury" and lead.language_preference == "english":
return "twilio"
# Default Indian domestic → Exotel
return "exotel"Primary: Tata Tele (cost optimization and maximum concurrency). Secondary: Exotel (overflow, rapid provisioning, developer tools). Tertiary: Twilio (NRI/international).
At 100,000 calls/month × 1.2 min avg: Tata Tele at ₹0.40/min = ₹48,000/month vs. Exotel at ₹0.60/min = ₹72,000/month. A ₹24,000/month saving (₹2.88 lakh/year) justifies the SIP integration engineering investment.
One frequently overlooked telephony-layer configuration for Indian real estate AI Calling is answering machine detection (AMD). Buyer calls in India go to voicemail when the buyer does not answer — the AI must detect this within 3–4 seconds and terminate the call rather than running a qualification script against a voicemail system.
Without AMD configured, the AI will attempt to qualify voicemail systems, consuming LLM tokens and call-minutes, and generate false "no answer" dispositions in the CRM.
Disclaimer: Telephony pricing, concurrency limits, API features, and regulatory interpretations referenced in this article reflect market conditions and provider documentation as of Q2 2026. Provider specifications, pricing tiers, and regulatory frameworks evolve continuously. Actual per-minute costs depend on volume commitments, contract terms, and routing configurations. All financial estimates are provided for planning purposes only — verify current pricing directly with each provider before production deployment decisions. Regulatory compliance requirements must be validated with qualified legal counsel for your specific deployment jurisdiction and use case.