Dialpad and Ada combine: your AI support agent changes owners

Dialpad and Ada are combining, putting one of the best-known AI customer service agent vendors inside a cloud phone company. The joint announcement on November 4 says the deal should close on or about November 12. Dialpad's Craig Walker becomes CEO of the combined company. Ada CEO Mike Murchison becomes Chief AI Officer. If an Ada agent answers your customer chats, your AI support vendor now has a new owner and a phone network attached.

What actually happened

The official release confirms the leadership, the close date and one promise: current Dialpad and Ada customers "will continue with their current contracts, pricing, account teams, and support channels," and existing integrations keep working as configured. The two companies say they serve more than 50,000 companies together. Financial terms were not disclosed.

The Globe and Mail, citing two unnamed sources, reports an all-share deal that values Ada at about US$430 million. Ada's valuation was US$1.2 billion when it raised US$130 million in 2021. The Globe also reports that Ada cut half its marketing team in July and 25 more jobs the week before the deal. Treat these numbers as press reports, not confirmed terms.

The pitch is a single stack: Dialpad's voice network and speech models plus Ada's autonomous chat and service agents. Ada's FAQ says "Nothing changes as a result of this announcement."

Why it matters for your business

"Nothing changes today" is true on closing day. It does not stay true for long. Acquired AI vendors usually change in three steps: the roadmap moves toward the buyer's product, the pricing gets folded into a bundle, and the standalone SKU goes away at renewal. We saw the same pattern last month when Salesforce agreed to buy Cresta.

For a small business running Ada on Shopify, Zendesk or a custom help center, the risk is not that the agent stops working next week. The risk is that at renewal, the best price needs Dialpad phones too. Do these things now, while the contract is still in your favor:

• Write down your current terms. Price per resolution or per conversation, volume tiers, renewal date, and any notice period for price changes.
• Export your knowledge base and conversation logs. The answers your agent gives come from your content. Keep a copy outside the vendor.
• Keep the agent behind your own layer. If your help widget, order lookups and refund rules call your own API, you can switch the model or vendor without rebuilding the support flow.

Sources: Dialpad and Ada joint press release, The Globe and Mail, CMSWire.