Salesforce AI Research and UC Berkeley have unveiled BFCL Audio, a new benchmark designed to rigorously evaluate the precision of AI models in handling audio-native function calls. In an announcement on its blog, the collaboration detailed how this extension of the existing BFCL framework addresses critical challenges in real-world voice interactions, particularly for enterprise applications where accuracy is paramount.
The initiative stems from a recognized gap in evaluating AI models' ability to reliably execute zero-shot function calls, a problem the team first tackled in 2022 with the Gorilla OpenFunctions models. The original BFCL benchmark evolved through several versions, from AST-based evaluation to multi-turn and agentic settings, becoming a foundational tool for text-based function calling. BFCL Audio now extends this crucial evaluation to the voice domain, acknowledging that real-world products rarely operate in pure text.
Voice interfaces are ubiquitous, appearing in phone support, in-car assistants, smart homes, wearables, and accessibility tools. In these scenarios, AI agents must balance natural, low-latency dialogue with precise action execution. For enterprises, automating customer support and call centers demands flawless function calling; a misheard account number or incorrect appointment time can lead to significant customer frustration and financial loss.
The Precision Problem in Voice AI
The report highlights two primary architectural paths for voice agents: End-to-End (E2E) speech-to-speech systems and Cascaded ASR → LLM → TTS pipelines. E2E models offer natural prosody and low latency, unifying reasoning over acoustics and semantics. However, they often lack tool-call precision without additional structure and have limited model availability. Cascaded systems, while leveraging mature text LLM stacks and offering modularity, face a critical bottleneck: ASR errors. Even minor transcription mistakes can be catastrophic for function calling, where APIs demand exact matches. The LLM in a cascaded system never "hears" the waveform, losing crucial acoustic cues that could recover intent.
Audio introduces systematic shifts compared to typed input, including conversational fillers, acoustic artifacts, accents, background noise, and the challenge of homophones or named entities (e.g., "John" vs. "Jon," "final report.pdf" vs. "finalReport.pdf"). These factors contribute to non-trivial word error rates from ASR systems, directly impacting the reliability of subsequent function calls.
