Azure RealtimevsGrok Voice 3.0

Grok Voice 3.0 is more reliable, by 11.0 points. Azure Realtime passed 58 of 82 scenarios on all three runs, and Grok Voice 3.0 passed 67. A scenario only counts when every run of it passed.

For a voice agent, Grok Voice 3.0, since it gets more scenarios right on every run. Grok Voice 3.0 is ahead on reliability, success rate, data accuracy, calls where the agent went quiet, interruption and response time, and Azure Realtime on agent responses. The two tie on cost.

Grok Voice 3.0, by 1.3 points. Azure Realtime saved everything exactly right on 86.1% of the calls that save data, and Grok Voice 3.0 on 87.3%. On Booking calls, 94.2% against 98.2%. On Medicare calls, 65.2% against 59.1%. A call counts only when nothing is missing, wrong, extra or saved twice.

No. Grok Voice 3.0 starts replying 0.32s sooner at the median. Azure Realtime takes 1.66s at the median and 2.22s at p90; Grok Voice 3.0 takes 1.34s and 1.62s. Both are measured on the call audio, from the caller finishing to the agent starting to reply.

Grok Voice 3.0, by 0.01 on a 0 to 5 scale. Azure Realtime scores 4.96 and Grok Voice 3.0 4.98 for how well the agent handled being talked over.

Grok Voice 3.0, by 4.1 points. The agent went quiet for 10 seconds or more on 4.1% of Azure Realtime calls and 0.0% of Grok Voice 3.0 calls.

They cost the same. Azure Realtime costs $0.080 a minute of call and Grok Voice 3.0 $0.080, at each vendor's published rates.

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.