How OBD Calling Works in India: Technical Guide 2026

The Technology Behind OBD Calling

OBD (Outbound Dialer) calling is powered by a cloud telephony platform that sits between your contact database and India's telecom carrier network. Understanding how it works helps you configure campaigns better, interpret reports accurately, and troubleshoot issues when connection rates drop.

The Five-Layer Architecture

Layer 1 — Contact Database

Your list of phone numbers is the input. Before dialling begins, the platform runs three processes on the database: Deduplication: Removes duplicate numbers. Running the same number twice wastes budget and triggers TRAI complaints. DND scrubbing: The platform queries the TRAI National Do Not Disturb (NDNC) registry and removes all numbers registered on DND. For promotional campaigns, DND scrubbing is mandatory. For transactional campaigns (EMI reminders to existing customers), DND exemptions apply based on prior customer relationship. Number validation: Invalid numbers (wrong digit count, invalid prefixes) are filtered out before dialling begins.

Layer 2 — Dialler Engine

The dialler engine manages how and when calls are placed. Three dialler types are used in Indian OBD campaigns:

Predictive Dialler: Dials multiple numbers simultaneously, anticipating agent availability. Used when OBD campaigns include live agent transfer for hot leads. The algorithm predicts when agents will be free and places calls accordingly, minimizing agent idle time. Progressive Dialler: Dials one number per available agent slot. Slower but produces fewer abandoned calls. Used for high-value outreach where every connected call must reach an agent. Preview Dialler: Shows the agent the contact's details before dialling. Used for very high-value outreach (real estate, enterprise sales) where personalization matters.

For pure automated OBD (recorded message, no live agent on first contact), the platform runs as a blast dialler — placing calls to all numbers in the database simultaneously, without agent availability constraints.

Layer 3 — Carrier Network

When a call is placed, it routes through India's telecom carrier network. Two carrier types are used:

VoIP-to-PSTN: Your OBD platform sends digital call requests over the internet; the carrier converts these to traditional phone calls that ring any mobile or landline in India. Most OBD providers use this route. Call quality depends on the carrier's PSTN termination quality. Direct carrier integration: Some large-volume OBD providers have direct SS7 connectivity with Airtel, Jio, Vi, and BSNL. This route provides better delivery rates and call quality but requires higher volume commitments.

Layer 4 — IVR Response Collection

When a call connects, the pre-recorded message plays. At the end of the message (or during it), an IVR prompt captures the recipient's intent:

Single-level IVR (most common): "To speak with our admissions team, press 1. To receive information via SMS, press 2. To stop receiving calls, press 9." Multi-level IVR: "For JEE batch information, press 1. For NEET batch information, press 2." [After pressing 1:] "For classroom batches, press 1. For online batches, press 2." Voice response IVR: The system asks an open question and records the spoken response for later review by your team. Used for research campaigns or where key-press is impractical.

Layer 5 — Lead Handoff

When a recipient presses the interest key (typically Press 1):

Immediate transfer: The call is transferred in real time to a live agent at your call center or sales team. The agent receives the call with the contact's details visible on their screen. This is the highest-conversion option — the customer is actively interested at the moment of transfer. Callback queue: The interested number is added to a callback list. Your agents call back within a configured window (immediately, within 1 hour, within the day). Conversion is slightly lower than immediate transfer because the intent window closes. SMS/WhatsApp follow-up: An automated SMS or WhatsApp message is sent to the interested number with your details or a link. No agent required. Used for lower-value leads or when agent bandwidth is limited.

The Call Flow: Start to Lead in 90 Seconds

Database upload → DND scrub → Campaign start
↓
Dialler places call to [Number]
↓
CONNECTED → Message plays (20–45 seconds)
↓
IVR prompt: "Press 1 to speak with our team"
↓
[Recipient presses 1]
↓
Lead captured → Agent transfer / callback / SMS
↓
Your team follows up → Conversion

Not connected / No response → Retry logic (1–3 attempts over 24–48 hours) → Mark as unreachable

Reporting and Analytics

A well-configured OBD campaign produces these reports in real time:

Metric	What It Tells You
Dialled count	Total numbers attempted
Connected rate	% of calls answered (target: 30–45%)
Message completion rate	% who listened to the full message
IVR response rate	% who pressed the interest key (target: 2–8%)
Lead transfer rate	% of connected calls that converted to leads
Retry performance	How many leads came from 2nd and 3rd attempts
Time-of-day heatmap	Which calling windows produced highest connection rates