Dialpad and Ada Merger: What Small Businesses Should Do Now

What did Dialpad and Ada announce?

On November 4, 2026, Dialpad, a business phone and customer experience platform, and Ada, a company that builds AI agents for customer service, announced that they will combine. The companies expect the deal to close on or about November 12, 2026, and they did not disclose financial terms. Dialpad co-founder Craig Walker is set to lead the combined company, and Ada chief executive Mike Murchison becomes chief AI officer.

Dialpad runs its own voice network and its own speech and language models. Ada's agents answer customers by voice, chat, email and social channels, and Ada says they work in more than 130 languages. The stated plan is a single platform that joins phone calls, customer data and AI agents, starting with customer service and later reaching sales.

Existing customers of either company keep their current contracts, pricing, account teams and support channels, and existing integrations continue to run as configured. Roadmap details are promised for the coming months. One newspaper report put a value on the deal, citing unnamed sources. The companies have not confirmed that figure, so treat it as unverified.

Does this change anything for a small business today?

For most small businesses, not this week. The deal has not closed, and the companies say current plans and prices stay in place. If you already use Dialpad for calls or Ada for chat, nothing in the announcement asks you to act. The useful response is to find out where your own setup depends on either company.

One open question deserves attention. According to Ada's website, as summarized by one trade publication, Ada's agents currently pass conversations to human staff on other phone platforms such as Genesys, NiCE CXone, Amazon Connect and Aircall. Neither company has said how long that support will last after the merger. If your AI assistant hands callers to a person on one of those systems, ask your vendor about it directly.

A merger like this also tells you something about the market. Phone systems and AI agents are being sold as one product. That can simplify setup, and it can also make it harder to change one piece later without changing the other.

What should you ask your phone or chat vendor?

A short list of written questions will tell you more than a sales call. Send them to your account team and keep the replies with your contract.

You do not need a lawyer to send these questions. For anything that changes a contract, this is general information, not legal advice, and a short review by one is reasonable.

Should you rely on one vendor or keep your own connections?

A single platform is simpler to set up and has one company to call when something breaks. The cost is dependence. If your phone number, call logs, booking rules and customer records all live inside one vendor's product, a price change or a product change becomes your problem.

The alternative is a thin layer that you own. Your calendar, your customer records and your rules for when a caller should reach a person stay in your systems, and the phone or AI provider plugs into them. That takes more work at the start. It also means you can replace the provider without rebuilding how your business handles calls. An AI receptionist built this way books into your own calendar and writes to your own CRM, and an AI chatbot can draw its answers from content you approve.

Which path fits depends on how much you depend on the call. A business that gets a few after-hours calls a week may be fine with an off-the-shelf tool. A business that books most of its work by phone has more to lose from a surprise. Our guide to missed-call text-back versus an AI receptionist walks through that decision, and the AI receptionist cost guide explains what drives the price.

Example: a veterinary clinic with after-hours calls

This is a hypothetical example. A small veterinary clinic answers calls through a hosted phone system during the day. After hours, a separate AI assistant takes messages and offers appointment times. The clinic's calendar and customer records live in its own practice software.

When the clinic's phone vendor announces a merger, the owner asks four questions. Who owns the phone number? Where are the call transcripts stored? Does the AI assistant hand an urgent caller to the on-call technician, and on which system? What happens to the price at renewal? The answers decide whether the clinic can wait, or whether it should move bookings and records into a layer it controls before renewal.

Because appointments are written to the clinic's own calendar, and a confirmation is recorded only after the calendar accepts the booking, a change of phone or AI provider changes the voice on the line while the schedule stays put. That is the design goal, and it is also why the example is worth copying.

What should you do next?

Start with your own call flow. Write down who answers, what the AI assistant is allowed to do, and how a caller reaches a person at 8 p.m. on a Saturday. Then read your contract for term, renewal and number ownership.

If you want a second opinion on whether to keep your current setup or put your own connections between your phone, calendar and CRM, talk to us about an AI receptionist. The AI receptionist page shows how booking and human handoff work, and our guide to AI receptionist versus a website chatbot can help you choose where to begin.

Sources

News details in this article reflect the sources below as of November 5, 2026. Check each source for updates.

• Dialpad and Ada Combining to Build the Agentic Operating System for Customer Work (Business Wire release)
• Dialpad and Ada Merge to Put AI and Humans on the Same Call (CXM)