Service
Call Centre Speech Data in India
Simulated and consented real-world contact-centre audio in Indian languages, recorded over telephony-grade channels so it matches the bandwidth your production system actually sees.
- Turnaround
- 3-6 weeks for 100-250 hours.
- Languages
- 14 Indian languages + Indian English
- Delivery
- Dual-channel call audio
What you get
- Dual-channel call audio
- Verbatim transcripts
- Intent, outcome and sentiment labels
- Scenario coverage matrix
Technical specification
Every parameter below is written into the statement of work before recording begins. If your pipeline needs different values, they replace ours rather than being converted after delivery.
| Parameter | Standard |
|---|---|
| Channel | 8 kHz narrowband telephony plus 48 kHz reference where required |
| Codec | G.711 / Opus simulated to match your stack |
| Structure | Agent and customer on separate channels |
| Scenarios | Billing, delivery, KYC, recharge, collections, support, sales |
| Emotion | Neutral, frustrated and escalated variants on request |
How the work runs
- Scenario library built from your call taxonomy
- Agent-side speakers briefed on your script and tone
- Recording over the specified codec path
- Transcription with intent and outcome labels
- Delivery with per-scenario counts
Quality control
Narrowband is simulated at capture time, not by downsampling clean studio audio, which would leave unrealistic artefacts.
QA failures are remedied by re-collection, not by editing the delivered files. Repaired audio introduces artefacts that survive into your model.
Speaker and contributor sourcing
Speakers with and without prior contact-centre experience, mixed to the ratio you specify.
Consent is captured per participant and mapped to file IDs, so provenance survives an external audit of your training data.
Timeline
3-6 weeks for 100-250 hours.
Staged delivery is available: first batches ship while later batches are still recording, so training can start early.
The numbers we hold ourselves to
- 100% of delivered files pass automated technical QA for SNR, clipping, duration and silence
- 5-25% of files pass a second native-speaker content review, stratified by city, dialect and transcriber, and escalating to 100% on any batch that fails the agreed threshold
- Accepted yield runs 85-90% for scripted speech, 60-70% for spontaneous, 55-65% for conversational and 50-60% for telephony
- Default cohort quotas: 50/50 gender, with age bands at 30% (18-25), 40% (26-40) and 30% (41-60)
- 48 kHz / 24-bit capture, delivered as 16-bit PCM WAV, with studio sessions held below a -50 dBFS noise floor
- First response within one working day; a scoped, fixed quote within two to three
These are the figures a delivery is measured against, not aspirations. A batch that misses them is re-recorded at our cost rather than repaired.
Commonly used for
- Contact-centre AI
- Call analytics
- Agent assist
- Voice bots
Frequently asked
What is the minimum volume for call-centre speech?
Programmes typically start around 50 hours or equivalent units per language. Smaller pilots are accepted when they lead into a larger build, because most of the setup cost is in specification and recruitment rather than recording time.
Can you work to our schema instead of yours?
Yes. Manifest fields, file naming, directory structure and label schema are set by you. Working to your schema from the start avoids a conversion pass that usually loses metadata.
Who owns the delivered data?
You do. Deliverables come with a perpetual, transferable licence and participant consent that covers model training and distribution of the resulting model.
How is pricing structured?
Per delivered hour or per unit, quoted against a written specification. Quotas, recording conditions and QA thresholds all move the price, which is why we quote from a spec rather than from a price list.
Get a quote for call centre speech data
Send the specification you already have, or the rough shape of it, and you get a scoped quote with a timeline.