For a communications platform like Dialpad, realtime messaging infrastructure is foundational to customer trust. Every call notification, message update, and live transcription depends on consistent, low-latency delivery across web, desktop, and mobile environments.
For Dialpad, reliability isn’t a feature; it’s a commitment customers depend on to run their businesses. As enterprise adoption increased and usage expanded globally, Dialpad’s engineering team reassessed whether their realtime messaging infrastructure was built to deliver the level of consistency customers expect at scale.
“Reliability comes first,” says Arnaud Budkiewicz, VP of Engineering at Dialpad. “Then it’s about experience. How responsive everything feels. How confident customers are that it will work, every time.”
Rather than waiting for reliability to become a problem, Dialpad chose to invest proactively in infrastructure designed for continuous uptime, predictable performance, and global scale. That decision led them to Ably.
The search: Finding a partner, not just a provider
With reliability established as a non-negotiable, Dialpad's engineering team took a deliberate and disciplined approach to selecting the realtime infrastructure partner. They evaluated every viable option, including building their own solution in house, through the lens of what enterprise customers would require at a global scale.
"We really looked at everything on the market. Build versus buy. We considered every option," says Arnaud. The criteria were clear: enterprise-grade reliability, global low latency, guaranteed message delivery with ordering, and the ability to scale alongside Dialpad's growing international customer base.
Beyond surface-level performance, Dialpad ran comprehensive benchmarks and architectural reviews, engaging directly with founders and CTOs to understand how each platform was designed. “We wanted to make sure the underlying architecture would truly work for us," Arnaud notes.
Through that process, Ably stood out for its reliability, performance, and architectural sophistication, particularly for the critical requirement of pub/sub communication between backend services and client applications.
