Omilia raises $67M to scale its customer support platform

The Series B round, led by Expedition Growth Capital, adds $67 million to Omilia’s balance sheet after a prior $20 million raise in 2020. In the intervening period the firm grew its annual recurring revenue tenfold to $60 million, indicating strong market traction. This influx of capital is earmarked for scaling operations rather than product pivots, suggesting continuity in the current technology roadmap.

Omilia positions its platform as a toolbox that selects the simplest effective AI for each call, arguing that many support interactions only need basic data like account balances. By avoiding blanket deployment of large language models, the approach promises lower compute costs and tighter latency budgets for voice workloads. Engineers integrating the platform can expect APIs tuned for deterministic, information-retrieval tasks rather than open-ended generative dialogue.

The company already serves large financial institutions and has deployed voice ordering at over a thousand Taco Bell locations, highlighting its ability to handle high-volume, real-time voice traffic. A reported ordering glitch at Taco Bell was publicly disputed by Omilia, underscoring the importance of robust logging and monitoring in production voice AI. These client examples provide concrete integration scenarios for engineers looking to add voice ordering or account-info bots to existing services.

Omilia will use the fresh cash to open a new office in the United States, a market that contributes a sizable share of its revenue, and to bolster its go-to-market organization with senior hires such as a chief revenue officer and chief marketing officer. The expansion will likely increase the engineering headcount from roughly 500 to 600 by year-end, potentially accelerating feature development and support coverage. For partners, the U.S. presence may translate to faster response times and localized compliance support.

While the focus on lightweight AI yields cost advantages, it also means the platform may not cover use cases that demand deep generative language capabilities, such as nuanced conversational assistants. Teams requiring sophisticated, context-aware dialogue will need to supplement Omilia’s offering with additional models or services. Understanding this boundary helps engineers decide when to adopt Omilia versus a full-scale generative AI solution.