Implementing Voice AI correctly in 5 steps

"Press 1 for Sales. Press 2 for Support. Press 3 for..."

No one likes hearing this voice from the phone anymore. 89% of service professionals say that conversational AI increases the self-service resolution rate (Salesforce State of Service, September 2025; n=6,500). By 2027, 50% of all service requests are expected to be resolved by AI, up from 30% in 2025 (Salesforce State of Service, September 2025).

The question is no longer whether Voice AI is coming. The question is how you introduce it without ending up operating two separate systems that know nothing about each other. This article shows five steps that determine success or failure.

1. Choose the right provider

The first step is choosing the right Voice AI solution. Four providers shape the German market in 2026, each with a different focus.

Pendura is a telephone solution for premium customer service and a direct branchly partner. Pendura takes care of the telephone side, call acceptance, routing, and customer interaction. The integration into branchly is fully aligned, meaning you do not need to set up a custom integration project. Pendura on the phone, branchly as the database and dashboard, and you are done. Particularly suitable for medium-sized businesses that want to manage their website AI and their telephone AI from a single source.

The Red Phone from London replaces rigid IVR menus with natural language routing. The mission is clear: to fix the first 30 seconds of every call. Native audio-voice model with under 600 ms latency, 99.9% uptime, 30+ languages. Integrations for ServiceNow, Twilio, Five9, Salesforce, Genesys. Suitable for companies with an existing contact center that want to end the IVR pain without switching the entire platform.

Fonio is the volume player in the German market. 9,500+ customers, 4.9 stars on Trustpilot, "#1 Software Tool of the Year 2026" by OMR among over 10,000 companies (OMR, 2026). AI telephone assistant for small and medium-sized businesses, setup in minutes. Own orchestration layer, servers in Nuremberg. Suitable for SMEs, self-employed individuals, and trades who cannot afford to miss calls but do not operate a contact center.

Newcall is an AI telephone assistant for tourist information offices and destinations in the DACH region. The AI assistant Mira answers guest inquiries 24/7 in 25+ languages, completely anchored in the destination's data. Servers in Germany, GDPR-compliant, EU AI Act taken into account. Official destination.one partner with direct DMS access. Go-live in one week, full-service including setup and ongoing optimization. Starting at €650 per month (new-call.de, 2026).

Which provider fits depends on your industry, your volume, and your existing infrastructure. What all four have in common: they are direct partners of branchly and can be natively connected to the branchly platform.

2. Avoid a duplicate database and set up a central knowledge base

The most common problem when introducing Voice AI is not the technology. It is the architecture. Companies buy a Voice AI solution, already operate a chat on their website, and end up running two systems side by side.

The problem: the Voice AI on the phone knows different information than the chat on the website. A customer asks for opening hours on the phone and gets a different answer than on the website because both systems feed from different sources. Every change to the knowledge base must be made twice. Every FAQ answer must be entered into both systems. This duplicate maintenance process costs time and leads to inconsistent answers. Compliance must be cleared individually for each system.

The solution is a central knowledge base. You set up your content once—website texts, FAQs, product data, PDFs, event calendars, external databases. This knowledge base then applies to every module: the website chat, AI Search, the Advisor, the Navigator, Forms, and the Voice Agent on the phone.

If you update an FAQ entry, it is immediately available on the phone and on the website. If you add a new product, the chat, the search, and the Voice AI know about it. One setup, six modules, one database. That is the difference between "buying Voice AI" and "introducing Voice AI strategically."

3. Ensure GDPR compliance right from the start

Voice AI in customer service falls under the scope of the EU AI Act, which has been in force since August 2024. High-risk system requirements will apply from August 2026, with penalties of up to 7% of annual turnover. BFSG/WCAG accessibility requirements have been mandatory for B2C services since June 28, 2025.

Not tacking these rules on retrospectively, but thinking about them from the very beginning, saves time and money. The questions you should clarify before the introduction:

Where is the data processed? US servers are a procurement blocker for DACH companies. GDPR, data processing agreements, Schrems II. Those who offer EU-native hosting win. Fonio has servers in Nuremberg, Newcall in Germany, Pendura in the EU, The Red Phone in the UK/EU with SOC 2. branchly hosts on Microsoft Azure EU for LLMs and OVH Cloud for user data. Nothing leaves the EU.

Is there a DPA? A data processing agreement must be in place from day one. If it is missing, data processing is not legal. branchly provides a DPA in accordance with Art. 28 GDPR.

Is the solution EU AI Act compliant? The Act requires transparency, logging, and human oversight. Anyone who cannot prove this risks penalties. branchly is EU AI Act ready.

Is the Voice AI solution WCAG compliant? Accessibility has been legally required for B2C services since June 2025. Not every tool provides this out of the box. branchly is WCAG 2.1 AA compliant, for all modules, out of the box.

4. Use call insights for content gaps

Calls are a source of data that most companies leave unused. Voice AI changes this, but only if the data flows into a central dashboard.

If 100 customers call in a month about opening hours, that is not a coincidence. It is a signal that your website does not provide this information prominently enough. Frequent call topics are candidates for FAQs. Instead of guessing what customers are asking, you see it in the data.

Callers say things they would never have written on the website. "Product X does not work with Y." "I wish there was Z." This is free market research material if you collect and evaluate it.

If callers are frustrated with a specific topic, the dashboard shows it. You can react before the issue becomes a complaint.

A prerequisite for these insights: the Voice AI data flows into a central dashboard that also aggregates the website data. Two separate dashboards will never show you the whole picture.

5. Connect Voice AI with your website AI via branchly

The final step is the connection. branchly does not offer its own Voice AI. branchly is the central database and dashboard that connects Voice AI solutions like Pendura, The Red Phone, Fonio, or Newcall with your website AI. The voice technology comes from the partner, the database and insights come from branchly.

All four providers are direct partners of branchly and can be natively connected to the branchly platform. The Voice AI on the phone then accesses the same knowledge base as the website chat, AI Search, Advisor, Navigator, and Forms.

You set up the knowledge base once in branchly. Create, structure, and index content. After that, it applies to every module:

• The website chat answers questions from the knowledge base.

• AI Search finds relevant content via hybrid search.

• The Advisor recommends matching products from the catalog.

• The Navigator guides visitors through processes.

• Forms intelligently pre-qualify inquiries.

• The Voice Agent delivers the knowledge base to the phone, via the integrated Voice AI solution.

What you get from this connection:

No differing information. Phone and website feed from the same knowledge base. A customer gets the same answer on the phone as in the chat. No contradictions, no outdated information on one channel.

No duplicate maintenance effort. You maintain one knowledge base, not two. Every update is immediately active for all channels.

One dashboard. All voice and web insights in one interface. What topics are asked on the phone? Which ones on the website? Where are the content gaps?

One compliance standard. GDPR, EU AI Act, WCAG, solved once, not per channel. One platform, one DPA, one audit trail. Microsoft Azure EU hosting for LLMs, OVH Cloud for user data. Nothing leaves the EU.

No double solution. You do not have to maintain two platforms, manage two contracts, and evaluate two dashboards. One platform, two interfaces, one database.

Summary

Successfully introducing Voice AI means more than buying a tool. It means choosing the right provider, avoiding a duplicate database, thinking about GDPR from the beginning, using call insights for content gaps, and connecting Voice AI with your website AI via branchly.

Anyone who takes these five steps is not running an island. They are running a platform that gets better with every interaction.