Conversational AI Companies · Code-Switching ASR
Code-Switching ASR Data for Conversational AI Companies
Voice-bot and chat-plus-voice platforms deploying into Indian markets, where the gap between demo accuracy and live accuracy is a code-mixing problem. Recognising speech that switches between an Indian language and English several times per sentence.
- Buyer
- Conversational AI Companies
- Use case
- Code-Switching ASR
- Metric
- Switch-point accuracy
Where the two meet
Bots trained on clean single-language data fail on real switching mid-utterance That is a code-switching asr problem, and it is solved by data shaped like this:
- Genuinely code-mixed spontaneous speech
- Per-token language ID labels
- A fixed rule for script of English tokens
Your evaluation criteria
- Does the data include overlap, interruptions and backchannels?
- Are utterances collected over the same channel conditions as production?
- Is intent labelling done against your live taxonomy?
Metrics
- Switch-point accuracy
- Mixed-utterance WER
- Language ID token accuracy
Pitfalls
- Concatenating monolingual data and calling it code-mixed
- Leaving script conventions to individual annotators
Contract points
- Scenario confidentiality
- Right to reuse across bot versions
- Delivery in a format that drops into an existing pipeline
Frequently asked
What does a first engagement look like?
Usually a scoped pilot: one language, an evaluation set plus a first training batch, delivered in three to five weeks, followed by the full programme.
Can you match our existing vendor's schema?
Yes. Working to your schema avoids a conversion pass and keeps deliveries comparable across vendors.
How is provenance documented?
Per-item contributor records and consent mapped to IDs in the manifest.
Send your requirement
Language, volume, metric, deadline.