Why Near-Real-Time Beats Real-Time Call Transcription (Full Transcript)

A pragmatic look at legacy integration risks, scaling needs, and how post-call analytics can still deliver fast anomaly detection in contact centers.
Download Transcript (DOCX)
Speakers
add Add new speaker

[00:00:00] Speaker 1: How do you make those design decisions between post-call versus real-time and how do you weigh off some of the trade-offs that you see there?

[00:00:06] Speaker 2: Yeah, so we have some demand from customers for real-time, but we haven't really gone there. So that layer down here that I talked about, which is the integration layer, this is a complex mess of horrible integrations to APIs on old legacy call systems that are pants. And they go down, they fail. And I was a technical founder, so I was involved in building a lot of this stuff at the start, and it's horrible. And asking the team to now, instead of downloading the call after the call, because normally we receive an event or we can run a report every two minutes for how many calls ended in the last two minutes. Okay, just give me those transcripts. That's a much easier loop. Then let's try and connect to the stream, transcribe it in real-time, and then actually get into our API in real-time. So for us, the gain wasn't enough to go down that thing. But what is important for us is we do have one of the large ins for us in high-volume contact centers is that we assess. We assess every call that's happened in the last 30 minutes, and then we compare it to every 30 minutes. So we have a 30-minute interval over the last 30 days, and we look at what are the themes appearing, and is there anything unusual? So we know that at half seven on a Wednesday evening, there'll be this many calls about cancellations and this many calls about password issues. But oh, hey, there's normally not some calls around this payment problem. And then we can build an alert around that and quantify that and get action fast. But that requires us to have the transcripts of the system as soon as possible after the call ends. So for us, the real-time is more around, we call it near-time. We call it real-time on our website, but really, you know, it's posted. First call, we hammer it at the API, and we need a response really quick. And then that can, often in those circumstances, there's an influx of calls. So then we need to kind of scale that up very quickly to transcribe all of those calls and get that result back to the user.

ai AI Insights
Arow Summary
Speaker 2 explains why they favor post-call (near-real-time) processing over true real-time transcription. Real-time streaming would require fragile, complex integrations with legacy call systems that frequently fail, and the added value doesn’t justify the engineering risk. Instead, they ingest calls immediately after they end, transcribe quickly, and use 30-minute rolling comparisons over 30 days to detect unusual call themes and trigger alerts—especially important for high-volume contact centers where rapid scaling is needed during call spikes.
Arow Title
Choosing Near-Real-Time Over Real-Time for Call Analytics
Arow Keywords
real-time transcription Remove
post-call processing Remove
near-real-time Remove
legacy integrations Remove
contact centers Remove
API reliability Remove
scaling Remove
theme detection Remove
anomaly detection Remove
30-minute intervals Remove
alerts Remove
transcripts Remove
Arow Key Takeaways
  • Real-time streaming transcription often demands complex, fragile integrations with legacy telephony systems.
  • Post-call ingestion (within minutes) can deliver most of the business value with far less engineering risk.
  • Near-real-time transcripts enable rapid monitoring and alerting without full real-time constraints.
  • Comparing call themes in 30-minute windows against historical baselines (e.g., last 30 days) helps detect anomalies like new payment issues.
  • Systems must scale quickly to handle spikes in call volume and return analyses fast after calls end.
Arow Sentiments
Neutral: The tone is pragmatic and technical, emphasizing reliability, integration complexity, and cost-benefit trade-offs rather than excitement or frustration (though legacy systems are described negatively).
Arow Enter your query
{{ secondsToHumanTime(time) }}
Back
Forward
{{ Math.round(speed * 100) / 100 }}x
{{ secondsToHumanTime(duration) }}
close
New speaker
Add speaker
close
Edit speaker
Save changes
close
Share Transcript