Mixed-language speech
Hindi–English code-switching is tested on real recordings rather than assumed to work. Language hints are stored per segment, so one meeting can hold more than one language.
Languages
Built for the way people really talk.
Meetings in India move between languages, accents and speeds. NeMeets preserves the language that was actually spoken and rejects the idea that one language model fits every room.
Language status
Two languages first. The rest only when accuracy is proven.
A transcript that is 90% right about names and numbers is a transcript someone has to rewrite. We would rather ship two languages that hold up than six that do not.
English First
Hindi First
Gujarati Next
More Indian languages Planned
The original is preserved
The transcript stays in the language that was actually spoken. Anything translated is labelled as a translation, not passed off as the source.
Drafts in the right language
Follow-up drafts are written in the language and tone of the conversation, and still require a person to approve them.
Evaluation
What we test before claiming a language works.
Melting pots of accents, background noise and overlapping speakers are the normal case, not an edge case.
Tone and speed
Fast speakers, quiet voices and rising intonation — measured on consented recordings, not studio audio.
Accents
Regional accents across English and Hindi, including speakers who switch mid-sentence.
Names
People and company names are the first thing to break in a transcript, and the first thing a reader notices.
Numbers and dates
Amounts, deadlines and quantities are checked explicitly, and uncertain values are flagged rather than filled in.
Overlapping speakers
Real meetings interrupt. Speaker turns are tested against people talking over each other.
Room conditions
Air conditioning, traffic, echo and distance from the speaker all change results. We test in rooms, not on a desk.
No accuracy figures yet
We do not publish word-error rates or accuracy percentages, because we have not finished measuring them on real meetings. When we do, the methodology and the conditions will be published with the number.
Adding a language
What has to happen before Gujarati ships.
- Record and transcribe enough real, consented meetings to see the failure patterns.
- Review names, numbers and mixed-language segments with native speakers.
- Fix the recurring errors, then re-run the same evaluation set.
- Publish the language as supported only after that evidence exists.
For teams that meet across languages
A meeting in Pune might open in English, move to Hindi for pricing and end in Gujarati for logistics. NeMeets stores language hints per segment so the record reflects that, instead of forcing the whole meeting into one language.
- Segment-level language hints
- Original-language transcript preserved
- Translated outputs labelled as translations