Azure RealtimevsCCascade

Cascade is more reliable, by 12.2 points. Azure Realtime passed 58 of 82 scenarios on all three runs, and Cascade passed 68. A scenario only counts when every run of it passed.

On reliability, no: the cascade passes more scenarios on every run. Cascade is ahead on reliability, success rate, agent responses, data accuracy and calls where the agent went quiet, and Azure Realtime on response time. The two tie on interruption. Both ran as the same agent, with the same prompt and tools.

Cascade, by 8.0 points. Azure Realtime saved everything exactly right on 86.1% of the calls that save data, and Cascade on 94.1%. On Booking calls, 94.2% against 98.8%. On Medicare calls, 65.2% against 81.8%. A call counts only when nothing is missing, wrong, extra or saved twice.

Yes. Azure Realtime starts replying 0.51s sooner at the median. Azure Realtime takes 1.66s at the median and 2.22s at p90; Cascade takes 2.17s and 2.51s. Both are measured on the call audio, from the caller finishing to the agent starting to reply.

They score the same. Azure Realtime scores 4.96 and Cascade 4.96 for how well the agent handled being talked over.

Cascade, by 3.3 points. The agent went quiet for 10 seconds or more on 4.1% of Azure Realtime calls and 0.8% of Cascade calls.

There is no verified per-minute rate for Cascade, so cost cannot be compared yet.

Cekura ran both as the whole agent in the same open-source Pipecat pipeline, with the same prompt, tools and connection. A simulated caller worked through all 82 scenarios on live calls, three times each, 3,198 calls across the benchmark. A call passes only when the agent said the right things and saved the right data. The cascade runs the same agent for reference and is never ranked.