Skip to main content
July 3, 2026 · By Piyush Sahoo · Updated November 3, 2026 ASR transcription is the automatic conversion of speech into written text by a machine-learning model. ASR stands for automatic speech recognition, also called speech-to-text. On a phone call, the model receives digitised call audio, either live or from a recording, and returns words that software can search, analyse, or act on. This guide follows one phone call from microphone to transcript. It then shows how to read accuracy claims, what published research says about 8 kHz audio, why Indian calls need their own test, and which Vobiz path suits each job.
Key takeaways
  • Treat any accuracy figure as a test result. One model in a 2023 Hindi study scored 7.6% on one test set and 26.8% on telephone-quality audio.
  • 8 kHz does not doom a transcript. Heavy compression, noise, and the wrong model can matter as much as the missing high frequencies.
  • Upsampling does not restore detail. Send the format your engine recommends, and avoid processing that the engine advises against.
  • Score the words you act on. A transcript can have a respectable overall error rate and still get the amount wrong.
  • Test Indian calls separately for each language mix. Hinglish, Tanglish, and single-language speech behave differently, and so do the engines.

What do ASR, STT, and transcription each mean?

ASR and speech-to-text name the same technology. The other terms around them describe different jobs, and mixing them up leads to the wrong product choice. On a live AI call, ASR is the listening step. Its text goes to a language model, and a text-to-speech service speaks the reply. See how a voice API connects these parts for the wider call flow.

What happens between a phone call and a transcript?

A transcript is the last step of a chain. Each stage can remove information or add errors before the next stage sees the audio. Five stages from a phone call to a transcript: caller and handset, network and codec, telephony media layer, ASR engine, and post-processing, each listing what decides quality at that stage. Five stages from a phone call to a transcript: caller and handset, network and codec, telephony media layer, ASR engine, and post-processing, each listing what decides quality at that stage.

The audio becomes features

A model does not read raw samples directly. It usually reads a compact picture of how energy moves across frequencies over time. OpenAI’s Whisper offers a concrete example: it resamples all audio to 16,000 Hz and computes an 80-channel log-Mel spectrogram over 25 ms windows, moving 10 ms at a time.

The model maps features to text

Older systems combined separate parts for sounds, pronunciation, and word sequences. Connectionist Temporal Classification (CTC) helped change that, because it trains a neural network on unsegmented audio without a pre-aligned label for each moment. Whisper goes further with an encoder-decoder transformer trained on 680,000 hours of labelled audio. Model architecture matters, but training data matters too. A model cannot be expected to handle speech it rarely saw in training, as the Indian results below show.

The decoder picks the likely words

Sound alone is often ambiguous. “Fifteen” and “fifty” can sit close together on a poor line, and so can “by” and “buy”. The decoder weighs acoustic evidence against what is likely in context, so a model tuned to banking language can make a better choice on banking calls.

Post-processing makes the text usable

Raw output still needs work. Later steps can add punctuation, turn spoken numbers into digits, label speakers, and redact personal data. These steps also change how accuracy gets scored, as the WER section below explains.

Should you transcribe during the call or after it?

Choose by when your software needs the words. The accuracy cost of live transcription comes from a basic limit: a streaming model cannot wait for audio that has not arrived. Research puts a figure on that limit under clean conditions. One 2023 paper compares models on LibriSpeech, a set of read speech. Its streaming model scored 3.90% and 8.21% WER, while its non-streaming counterpart scored 2.42% and 4.35% on the two test sets. Those numbers show the direction, not what you will see on phone calls. Live engines work around the limit by revising themselves. Deepgram’s documentation shows the pattern: interim transcripts are guesses that improve as more audio arrives, and endpointing finalises text when a voice activity detector finds a long enough pause. Your application must then decide when to act on words that may still change. You do not have to choose only one. One workable design streams audio for the live conversation, then runs a batch engine over the recording to produce the record that people review.

How do you measure ASR transcription accuracy?

Word Error Rate (WER) is the standard measure. Align the machine’s text with a correct reference, count the substitutions, deletions, and insertions, then divide by the number of reference words. Lower is better. An eight-word reference sentence aligned with a machine transcript. One substitution, one insertion, and one deletion give a Word Error Rate of 37.5 percent, and only the substitution changes the amount owed. An eight-word reference sentence aligned with a machine transcript. One substitution, one insertion, and one deletion give a Word Error Rate of 37.5 percent, and only the substitution changes the amount owed. WER is useful for comparison, but it can mislead in three ways: WER can even pass 100%, because insertions count against the same denominator. A model that invents words during silence can score worse than one that writes nothing.

Why the digits deserve their own score

Small error rates grow when a business depends on a long exact value. As an illustrative calculation, suppose an engine gets each digit right 98% of the time, independently. A 10-digit account number would then come through fully correct only about 82% of the time, because 0.98 raised to the power of 10 is 0.817. That means roughly one in five account numbers needs a fallback, even though a 2% digit error rate sounds excellent. For payment, identity, or consent steps, confirm the value with the caller or collect it another way, such as keypad input.

What accuracy can you expect on phone audio?

Expect a range, not a number. Quote no percentage without its test conditions, because the audio and the test method can move the result more than the headline suggests. The authors of the 2020 call-centre study help explain the gap. Their engines scored 10.2-11.6% on the Switchboard evaluation subset, about twice the best published figures at the time. They attribute this partly to testing on whole audio chunks with speech detection, and to general language models, where research systems often get prepared segments and models built for the data. The chart below shows how much the test set alone can matter. It uses one model, one language, and seven benchmarks. Bar chart of IndicWhisper Word Error Rate on seven Hindi test sets, from 7.6 percent on IndicTTS to 26.8 percent on telephone-quality Gramvaani audio, from the 2023 Vistaar study. Bar chart of IndicWhisper Word Error Rate on seven Hindi test sets, from 7.6 percent on IndicTTS to 26.8 percent on telephone-quality Gramvaani audio, from the 2023 Vistaar study. The Vistaar authors found that results on one benchmark can be a poor guide to another. Two of their test sets showed a negative correlation of -0.26 in how they ranked 14 systems. So a leaderboard tells you little until its audio resembles yours. These published figures are also dated, and engines have moved on. Use them to understand the size of the spread, not to rank any vendor today.

Does 8 kHz audio limit ASR accuracy?

It limits what the audio can contain, but it does not set a fixed error rate. An 8 kHz sample rate can only represent frequencies up to 4 kHz, half the sample rate. Fricatives such as “s” and “f” show significant energy between 5 and 10 kHz, so that part of the signal never reaches the model. Frequency map from 0 to 10 kHz. The telephone band ends near 3.4 kHz, 8 kHz sampling stops at 4 kHz, 16 kHz sampling stops at 8 kHz, and fricative energy sits between 5 and 10 kHz. A narrowband call in a 16 kHz stream is empty above 4 kHz. Frequency map from 0 to 10 kHz. The telephone band ends near 3.4 kHz, 8 kHz sampling stops at 4 kHz, 16 kHz sampling stops at 8 kHz, and fricative energy sits between 5 and 10 kHz. A narrowband call in a 16 kHz stream is empty above 4 kHz. That sounds fatal, yet the evidence is more mixed. The strongest recent data for Indian speech comes from a June 2026 preprint from ARTPARK and the Indian Institute of Science. It degraded Hindi audio in controlled ways before running current models on it: Read the 8-bit row with care. The study reduced amplitude precision directly, while G.711 stores eight bits per sample after logarithmic scaling. The result does not transfer to phone calls one for one.

What should you actually do with the audio?

Follow your engine first, because engines differ. Whisper resamples everything to 16 kHz, while Google Cloud’s guidance gives this advice for its own service:
  • Keep the native rate. Google prefers capture at 16,000 Hz or higher where you control it. It also says to avoid resampling, and to send telephony audio at 8,000 Hz if that is its native rate.
  • Prefer lossless encoding. FLAC or LINEAR16 is recommended, because mu-law and other lossy codecs may reduce accuracy.
  • Leave the audio alone. Google advises against automatic gain control, and says noise reduction before the service typically reduces accuracy.
Prevent mixed voices as well. When two people talk at once on one channel, Google warns that the recogniser may treat them as noise. Stereo recording avoids this, because a multichannel request transcribes each channel independently and each party has a track of their own.

Why do Indian calls need their own test?

Indian calls often combine three difficulties: mixed language, regional speech, and telephone audio. Systematic analysis for Indian languages is still limited, so a global benchmark tells you little about your own calls.

Code-switching breaks one-language assumptions

Researchers estimate that more than 250 million people in India use code-switched speech, especially blending English with Hindi. The hard form is a switch inside a sentence, where no pause marks the change. A speaker might say “aapka payment fail ho gaya, please retry karo”, and an engine that fixed on one language at the start must now handle both. Model choice has a large effect here. On a 2025 Hinglish corpus recorded at 16 kHz, three baseline models scored 16%, 31%, and 38% WER on adult speech from the same test audio. The same paper’s audio was clean by telephone standards, so expect a phone line to add difficulty.

Language coverage is uneven

Published Indian results vary widely by language and model. The Vistaar benchmark spans 59 test sets across 12 Indian languages, and its authors fine-tuned Whisper on 10,700 hours of Indian speech to get the lowest WER on 39 of those sets. For you, the lesson is simple: a good Hindi result says little about Tamil or Bengali, and each language pair needs its own evaluation.

Domain words carry the business value

Terms such as EMI, UPI, and NEFT come up constantly on Indian fintech calls, yet general training sets rarely contain enough of them. Some engines, including Deepgram’s, let you boost expected terms at request time. Add your product names, branch names, and local place names to your test.

Transcripts carry privacy duties

A call transcript can hold names, account numbers, and health details in searchable form. India’s Digital Personal Data Protection Rules, 2025 were published on 13 November 2025, with most operative rules starting 18 months later, in May 2027. February 2026 law firm commentary reports that MeitY proposed faster timelines for Significant Data Fiduciaries. We found no notified change to that timeline as of this update, so check the current Gazette. Plan for these three now:
  • Rule 3, notice. The notice must itemise the personal data and state the specific purpose.
  • Rule 6, safeguards. Minimum measures include encryption, obfuscation, or masking, along with access controls and logs.
  • Rule 8, retention. Rule 8(3) requires a Data Fiduciary to keep personal data, traffic data, and processing logs for at least one year, then erase them unless another law requires longer.
Call-recording consent and retention depend on your sector and role, so take legal advice for your case. For calling rules, see the India calling regulations guide.

How do you choose and test an ASR engine?

Run a small test on your own calls before you commit.
  1. Collect real audio. Use de-identified calls with the correct consent, spread across languages, regions, handsets, and busy hours.
  2. Write the reference by hand. Set one rule for numbers, punctuation, and script before you score anything.
  3. Send it the way production will. Use the same codec, sample rate, and channels, and do not test with a cleaned-up copy.
  4. Score in layers. Report overall WER, then accuracy on amounts, dates, names, and consent phrases.
  5. Split the results. Compare single-language speech, sentence-level switching, and mid-sentence switching separately.
  6. Measure the live path. For streaming, log time to first text, time to final text, and how often interim words change.

How does Vobiz handle transcription?

Vobiz gives you several ways to get words from a call. Your choice depends on timing, language, and how much of the speech stack you want to own. Decision map. During a call, short expected answers suit Gather speech input and open conversation suits Stream with your own engine. After a call, English calls can use Record Calls transcription, and other needs suit a stereo recording with a batch engine. Decision map. During a call, short expected answers suit Gather speech input and open conversation suits Stream with your own engine. After a call, English calls can use Record Calls transcription, and other needs suit a stereo recording with a batch engine. The table below lists the Vobiz controls for the live and built-in paths, plus the settings available on a SIP trunk. For <Gather>, check the supported languages list, which includes en-IN, and consider the phone_call speech model for call audio. Record Calls transcription covers English calls from 500 ms to 4 hours and under 2 GB. It delivers the result through webhooks (callbacks) to your transcription_url, and the Console’s Recordings page can show transcripts with speaker labels. For other languages, send the audio to a specialist engine. You can stream to it live, or download your recordings for batch processing. The Deepgram guide bridges a <Stream> to Deepgram’s India region, and Vobiz also powers the Rent from Sarvam telephony option. See the integrations hub for other options.

Which stream format should you choose?

Set the inbound format that matches your engine. Vobiz supports three inbound formats, and each media frame covers 20 ms of audio. The data rates below are our own arithmetic for one mono track, before WebSocket framing and Base64 encoding. Decode each payload using start.mediaFormat, not a rate you assumed in code. As the Vobiz docs note, a higher declared rate does not improve audio by itself. When bidirectional is true, the stream carries the inbound track only, so use a one-way stream with audioTrack set to both if your engine should hear both parties.

Which recording settings help transcription?

Set record_channel_type to stereo when you plan to transcribe. Stereo places the caller and callee on separate channels, so you avoid mixed voices at overlaps. Choose wav when your batch engine prefers lossless input, or mp3 when file size matters more. The Recordings page keeps recordings for 30 days. If your policy needs a longer period, export them to your own storage first. See how compliant recording pipelines fit together and how post-call analytics works for the next steps. Recording, transcription, and calls use your own credentials and are billed to your account. Confirm the numbers, the consent, and the current pricing before you run a test on live calls.

Frequently asked questions

ASR stands for automatic speech recognition. In transcription, it means a machine-learning model converts spoken audio into written text without a human typist. You will also see it called speech-to-text or STT.
In practice, yes. Both names describe software that turns speech into text, and vendors use them interchangeably. Transcription is the broader word, because a person can also produce a transcript. Speaker recognition is different, because it identifies who spoke and not what they said.
No single figure holds. Published phone-audio results range from 5.1% on a research benchmark to 16.5-19.2% on real call-centre recordings. Hindi telephone audio scored 26.8-59.9% across six systems in a 2023 study. Measure on your own calls, and separately score amounts, names, and dates.
Often, yes. Research systems have reached low error rates on telephone speech, and a 2026 Hindi study found a simulated 3.4 kHz band stayed close to the 16 kHz original. Compression, noise, and model fit can matter as much. Send the format your engine recommends, then test it.
It cannot restore detail that was never captured. A 2026 Hindi study measured moderate loss from classical upsampling, and neural restoration made error rates worse. Google advises sending telephony audio at its native 8,000 Hz. Some engines resample input themselves, so check your engine’s documentation.
Yes. Gather recognises caller speech during a call, and the Record Calls API can transcribe English calls after recording. You can also stream inbound call audio to an ASR engine you choose, or send stored recordings to a batch engine. Use your own credentials, and check pricing first.

Further reading on Vobiz

Sources

Build on Vobiz

Provision a number and stream direction-labelled call audio to your ASR engine.