Quick answer: Score DACH platforms on seven checks, not a language count. Zian AI is our platform pick (inbound and outbound calls, SMS, email, WhatsApp; German and French named; deploys on your infrastructure); LeadsNow.ai is the managed option. Zian ranks first on that breadth, not on the checklist: its own pages meet 2 of the 7 checks, plus 2 conditional on self-hosting. Of five rivals, Cognigy, Zendesk and Parloa meet 6 of 7 checks; none names Swiss hosting.
Best engagement platform with multi-language support for DACH operations in 2026
“DACH” is Germany (D), Austria (A) and Switzerland (CH): three markets sharing a written language and little else an AI agent cares about. Switzerland has four national languages, and each country regulates sales calls and marketing messages under a different statute. A platform that “speaks German” can still fail a Zurich caller, say du to a Viennese director, or ring an Austrian business without consent.
Disclosure: zian.ai publishes this page and Zian AI is ranked first in it; LeadsNow.ai runs on Zian. Every other entry is a real vendor scored from its own pages on 12 October 2026.
- Zian AI — best platform pick for DACH sales and reception. Zian’s agents answer inbound calls 24/7 as an AI receptionist and run outbound follow-up across voice calls, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger. Its site lists 30+ languages “including English (multi‑accent), Mandarin, Arabic, French, German, Spanish, Japanese, and more”, with voice cloning and configurable voice, accent and tone. Zian offers private model deployment on customer infrastructure (“Use our stack or deploy private models on your own infrastructure”) and lists local data residency among its Enterprise options. It has set 50,769+ qualified sales appointments. On the seven checks below, Zian’s own pages meet 2, plus 2 conditional on self-hosting. Honest gaps: Zian is in partnership-application beta with no public price, and its pages do not name Swiss German or Italian, so test both before go-live.
- LeadsNow.ai — best done-for-you option. LeadsNow.ai is a managed, pay-per-result AI appointment-setting and lead-generation service that runs on Zian. It answers leads in under 60 seconds, 24/7, and is rated 4.6/5 from 43 reviews.
- Cognigy — best for enterprise contact centres that need spoken Swiss German recognition. 6 of 7 checks. Cognigy’s Voice Gateway documentation lists German (Switzerland), French (Switzerland) and Italian (Switzerland) among the Google speech-to-text locales its agents can use, “German, Swiss” under Amazon Transcribe, and German (Switzerland) Microsoft Azure voices. It lists a Europe SaaS environment and a Frankfurt cluster, not a Swiss region.
- Zendesk — best if your support desk already runs on Zendesk. 6 of 7 checks. Zendesk has a pronoun-formality setting for “languages that distinguish between formal and informal pronouns, such as German”, and hosts in EEA (Ireland) and EEA (Frankfurt). It names a Swiss German premium voice for its voice AI agents, whose locale table lists only de-DE, and German (Switzerland) for Zendesk Talk’s post-call transcription.
- Parloa — best for voice-first enterprises that need provable regional residency. 6 of 7 checks. Parloa says its voice agents “speak 140+ languages”, demonstrates German, French and Italian voices, and says a partner deploys Parloa AI agents in languages including “Swiss German”. Parloa Labs, its engineering blog, names “the formality default” among the parameters a regional overlay (for example German vs. English) can override. It states that “Deployments follow EU data-residency guidelines”; Parloa Zones keep customer data “within the chosen jurisdictional region”.
- Intercom Fin — best for chat-first teams that want the Sie/du switch. 5 of 7 checks. Fin’s language list includes German (Austria), German (Formal), French (Switzerland) and Italian, with a pronoun-formality setting. EU hosting is available on contract; Fin Voice is limited to select customers.
- Superchat — best for WhatsApp-led teams in Germany. 2 of 7 checks. Superchat stores “all data in Frankfurt”, sets tone “separately for Chat, Phone and Email” and documents voice cloning, but its AI phone assistant is available “Currently [in] the UK and Germany”.
The DACH readiness checklist: seven checks, six platforms
One rule fills every cell. “Yes” means a page on the vendor’s own domain (marketing, documentation, help centre or trust page), read on 12 October 2026, names the item for that product. Swiss German counts when “Swiss German” or “German (Switzerland)” is named for speech recognition, for voice output, or as a language the vendor’s voice agents are deployed in; the cell says which. Hosting counts when an EU/EEA or Swiss location is named. Register control counts only when a named formality setting or parameter is documented (a formal/informal pronoun control, a Formal/Informal control or a named formality default); general tone settings and marketing claims do not count. “Not named” means not on the pages we searched, not that the vendor cannot do it.
| Platform (product scored) | German | Swiss German (spoken) | French | Italian | EU hosting | CH hosting | Formal-register control | Yes count |
|---|---|---|---|---|---|---|---|---|
| Zian AI (agents platform) | Yes (named on zian.ai) | Not named | Yes | Not named (“and more”) | Conditional: deploy on your own infrastructure; local data residency on Enterprise | Conditional: same route | Not named (tone configurable; no formality setting named) | 2 (+2 conditional) |
| Cognigy (AI Agents + Voice Gateway) | Yes | Yes: recognition (Google German (Switzerland); Amazon Transcribe “German, Swiss”); Azure German (Switzerland) voice output | Yes | Yes | Yes: Europe SaaS; EU1 Frankfurt | Not named | Yes: Formal/Informal style slider | 6 |
| Zendesk (AI agents, voice AI agents) | Yes | Yes: voice output (premium Swiss German voice; voice AI locale table lists de-DE); Talk post-call transcription lists de-CH | Yes | Yes | Yes: EEA Ireland, EEA Frankfurt (commitment needs the Data Center Location Add-On) | Not named | Yes: pronoun formality | 6 |
| Intercom Fin (AI agent, Fin Voice) | Yes (also German (Austria), German (Formal)) | Not named | Yes (incl. French (Switzerland)) | Yes | Yes: EU, contract plans only | Not named (US, EU or Australia offered) | Yes: pronoun formality | 5 |
| Parloa (voice AI agents) | Yes | Yes: named on parloa.com (a partner deploys Parloa agents in Swiss German) | Yes | Yes | Yes: EU data-residency; Parloa Zones | Not named | Yes: “the formality default”, overridable per regional overlay (Parloa Labs) | 6 |
| Superchat (AI agent, AI phone assistant) | Yes | Not named | Not named (no language list found) | Not named | Yes: Frankfurt | Not named | Not named as a setting (free-text tone per channel) | 2 |
Three patterns stand out. None of the six names a Swiss hosting location, so Swiss storage is a negotiation. Three of the five rivals name Swiss German in different forms: Cognigy (recognition locales for its agents, plus Azure voices), Zendesk (an AI-agent voice and Talk transcription) and Parloa (a partner deploys its agents in it); only Cognigy names recognition for the live agent. And four of the five rivals (Cognigy, Zendesk, Intercom and Parloa) name a formality setting or parameter, so demand one.
Planning German, French or Italian conversations across DACH? Zian AI answers inbound calls and follows up by phone, SMS, email and WhatsApp in 30+ languages, with private model deployment on your infrastructure. Zian is in partnership-application beta. Apply For Partnership
Swiss German is spoken; Swiss Standard German is written
According to the Swiss Federal Statistical Office (FSO), 55% of people usually speak Swiss German at home or with friends and family, against 12% German (Standard German), 23% French and 8% Italian; respondents could name more than one. Swiss German is spoken dialect; the federal government writes Standard German with Swiss conventions, and so should your agent.
So a voice agent must understand dialect, a speech-recognition problem, while everything it writes by SMS, email or WhatsApp should be Swiss Standard German. The Swiss Federal Chancellery’s style guide for federal texts, the Schreibweisungen, draws the line exactly: “«Helvetismen» sind aber nicht etwa Dialektwörter, die in einem standard- oder hochsprachlichen Text nichts zu suchen haben, sondern regionale Varianten der Standard- oder Hochsprache” (Helvetisms are not dialect words, which have no place in a standard text, but regional variants of the standard language). Its examples include Ferien not Urlaub, innert not innerhalb von, and das E-Mail not die E-Mail. The guide itself is written with “ss” throughout and no ß (Grossschreibung, übermässige); a template written in Germany will use ß.
A named locale is not a result. Test it with our 12-probe language parity test for multilingual AI agents, using real dialect callers rather than Standard German read aloud.
French and Italian are not optional in Switzerland
The FSO’s main-language figures for 2024 are German 61.1%, French 22.6%, Italian 7.8% and Romansh 0.4%, with people able to name several main languages. A German-only Swiss rollout leaves out Romandy and Ticino. Swiss French and Swiss Italian are regional varieties too, so the locale matters again: Cognigy’s documentation lists French (Switzerland) and Italian (Switzerland) among the speech-to-text locales it connects, and Intercom lists French (Switzerland) for Fin’s text replies.
Decide first how a caller’s language is chosen. Intercom says Fin Voice “does not currently detect a caller’s spoken language automatically” and suggests a keypad menu; Zendesk documents callers switching language mid-call.
Sie or du: lock the register with a setting, not a prompt
German, French and Italian all distinguish formal and informal address: Sie and du, vous and tu, Lei and tu. A prompt saying “always use Sie” is the weakest control, because models drift; a documented setting is stronger.
Four of the five rivals name one. Intercom’s pronoun-formality setting offers Formal, Informal or “Let Fin decide”, where Fin mirrors the customer: “If the person uses the formal ‘Sie’ in German, Fin responds with formal pronouns.” Zendesk has a pronoun-formality setting for languages such as German. Cognigy has a Formal/Informal speaking-style slider, plus a formality field on its DeepL translation connector covering German, French and Italian among others. Parloa’s blog says it localises tone, style, “formality, and conversational norms”, and Parloa Labs names “the formality default” among the parameters a regional overlay can override; its product documentation requires a login, so we could not see the control itself. Superchat (free-text tone per channel) and Zian (configurable tone) name no formality control.
No setting is a guarantee, and Intercom says so: “we can’t guarantee that it will always use the correct pronouns as the underlying technology is non-deterministic and can sometimes deviate from instructions.” Our rule: formal register for every first contact in DACH, locked by setting where one exists, with a register probe in your tests.
Where your data sits: GDPR, the Swiss revFADP and what “EU hosting” actually buys
Neither the GDPR nor the revised Swiss Federal Act on Data Protection (revFADP, in force since 1 September 2023) requires storage at home; both regulate transfers abroad. GDPR Article 44 allows a transfer to a third country “only if … the conditions laid down in this Chapter are complied with”, and Article 45(1) lets a transfer take place where the European Commission “has decided that the third country … ensures an adequate level of protection”; such a transfer “shall not require any specific authorisation”. Switzerland is on the Commission’s adequacy list.
The Swiss Act mirrors this. Article 16(1) says personal data “may be disclosed abroad if the Federal Council has decided that the legislation of the State concerned … guarantees an adequate level of protection”. Article 16(2) adds five fallback safeguards, from a treaty to binding corporate rules, and Article 17 six exceptions, starting with explicit consent. Annex 1 of the Data Protection Ordinance lists Germany, Austria and Ireland among others, and the United States only for Swiss-US Privacy Framework certified organisations. Under Article 19(4), when data goes abroad you must tell people which State it goes to and which guarantee or exception applies.
This cuts against the hosting columns in our matrix: an EU-hosted platform is lawful for most Swiss and German teams, and even US hosting can be. Hosting location is usually a contract or sector demand, and the fine print matters. Zendesk makes hosting commitments only where the Data Center Location Add-On is bought or included in your plan, and otherwise “may move account data between regions without notice”. Intercom’s EU hosting is for new workspaces on contract plans, with account billing processed in the US. Cognigy no longer offers on-premises installations to new customers. If you must store data in Switzerland, none of the six names a Swiss region: ask in writing, or run the agent on infrastructure you control, the route Zian offers.
Consent rules for AI calls and messages in Germany, Austria and Switzerland
The three countries split three ways. Germany’s Act against Unfair Competition (UWG), §7(2) No. 1, treats as an unacceptable nuisance any advertising call “gegenüber einem Verbraucher ohne dessen vorherige ausdrückliche Einwilligung oder gegenüber einem sonstigen Marktteilnehmer ohne dessen zumindest mutmaßliche Einwilligung” (to a consumer without prior express consent, or to any other market participant without at least presumed consent). No. 2 requires prior express consent for advertising by automatic calling machine, fax or electronic mail. Whether an AI voice agent is such a machine is unresolved; our analysis of whether AI cold calling is legal in Germany under UWG §7 covers it and the §7a consent-record duty.
Austria is stricter on business calls. The Telecommunications Act 2021 (TKG 2021), §174(1), reads: “Anrufe – einschließlich das Senden von Fernkopien – zu Werbezwecken ohne vorherige Einwilligung des Nutzers sind unzulässig” (calls, including sending faxes, for advertising purposes without the user’s prior consent are unlawful). The text draws no consumer–business distinction; consent from a person the subscriber authorised to use the line counts; consent can be withdrawn at any time. §174(2) bars suppressing or falsifying caller ID on advertising calls. §174(3) requires prior consent for direct-marketing electronic mail, “einschließlich SMS”. The §174(4) exception needs all four conditions: contact details obtained from a sale or service to your customer; advertising for your own similar products or services; a clear, free, easy way to refuse at collection and with every message; and no advance refusal, in particular by entry on the list referred to in §7(2) of the E-Commerce Act. Under §174(5) it is always unlawful if the sender’s identity is concealed, §6(1) of the E-Commerce Act is breached, the recipient is asked to visit a website that breaches it, or there is no authentic stop address. §174 does not name WhatsApp. Under §174(6), breaches of paragraphs 1, 3 or 5 committed abroad count as committed where the message reaches the user’s line.
Switzerland’s Unfair Competition Act (UCA) handles individual advertising calls through the phone directory rather than a prior-consent rule. Article 3(1)(u) makes it unfair to “fail to observe a note in the telephone directory that a customer does not wish to receive advertising from persons with whom they have no business relationship” (the same note bars passing their data on for direct advertising), and adds: “customers without a directory entry shall be treated in the same way as customers with a directory entry and note”. Article 3(1)(v) bars advertising calls that do not display a directory-listed number the caller is entitled to use. Article 3(1)(o) makes it unfair to send mass advertising by telecommunication, unconnected to requested content, without prior consent, a correct sender, or a simple, free refusal option; the exception covers a customer’s contact details received at a sale, with the refusal option indicated then, for your own similar goods, works or services. Whether AI dialling at volume is mass advertising is a question for a Swiss lawyer. Fedlex’s English text has no legal force; rely on the official-language original. For the separate question of telling callers they are talking to an AI, see our EU AI Act Article 50 transparency checklist.
| Country and instrument | Advertising call to a consumer | Advertising call to a business | Marketing SMS or email | Caller ID |
|---|---|---|---|---|
| Germany: UWG §7 | Prior express consent | At least presumed consent; prior express consent if an automatic calling machine | Prior express consent; §7(3) existing-customer email exception (four conditions) | Not in UWG §7; see our UWG §7 page |
| Austria: TKG 2021 §174 | Prior consent | Prior consent (no distinction in the text) | Prior consent, SMS named; §174(4) exception (four conditions) | Must not be suppressed or falsified (§174(2)) |
| Switzerland: UCA Art. 3(1) | Respect the directory note; unlisted numbers treated as noted unless a business relationship exists; prior consent if the calls count as mass advertising (unresolved for AI agents) | Same Art. 3(1)(u) rule; the text does not distinguish businesses | Prior consent for mass advertising; own-customer exception with refusal option | Must display a directory-listed number you may use (Art. 3(1)(v)) |
The DACH threshold table: when to require what
| When your operation… | Require from the platform | Below that, you can skip it |
|---|---|---|
| Answers phone calls from German-speaking Switzerland (55% of people in Switzerland usually speak Swiss German at home) | A named Swiss German speech-recognition locale, plus a dialect test at 95%+ parity with your baseline before go-live | Text-only channels: write Swiss Standard German instead, no dialect model needed |
| Serves Romandy or Ticino (22.6% and 7.8% main-language shares) | French and Italian, ideally the Swiss locales (fr-CH, it-CH), and a documented language-selection route | German-speaking cantons only |
| Sends written messages to Swiss recipients | Templates in Swiss Standard German: Helvetisms, “ss” never “ß” | Germany and Austria only |
| Makes any first contact in DACH (sales or support) | A named formality setting locked on, or a written register rule plus a register probe in testing | Brands that deliberately use du everywhere, with that choice written down |
| Calls businesses in Austria | Proof of prior consent per number before the agent dials (TKG 2021 §174(1)) | Inbound-only lines |
| Calls businesses in Germany with an AI agent | Prior express consent until a court classifies AI agents (see our UWG §7 page) | Human-placed calls with documented presumed consent |
| Calls in Switzerland | Directory-note screening, unlisted numbers excluded unless you have a business relationship, a directory-listed caller ID; prior consent if your volume could make it mass advertising | Calls only to existing customers |
| Holds a contract or sector rule requiring Swiss data storage | A Swiss region in writing, or deployment on infrastructure you control | EU hosting is a lawful destination for Swiss data (Germany, Austria and Ireland are on the Swiss adequacy list) |
Who each option is wrong for
Zian AI is wrong for a buyer who needs a public price list or an off-the-shelf Swiss region today. LeadsNow.ai is wrong for teams that want to run the platform themselves. Cognigy is wrong if you need new on-premises installation, which it no longer offers, or a Swiss region, none of which is named in its documented environments as at 12 October 2026. Zendesk is wrong if you need its voice AI agent to recognise Swiss German, since the voice AI locale table lists de-DE only (Zendesk Talk’s post-call transcription does list German (Switzerland)), or a hosting commitment without the Data Center Location Add-On. Intercom Fin is wrong for phone-first operations: Fin Voice is “limited to select customers partnered with our Sales team” and does not yet detect a caller’s spoken language. Parloa is wrong if you want detailed documentation before a sales call; its public documentation sitemap lists only a landing page. Superchat is wrong for an Austrian or Swiss voice line, because its AI phone assistant covers the UK and Germany only, as at 12 October 2026.
How we ranked, and what we could not verify
Methodology. Zian AI sits first as the publisher’s platform pick, on its published capabilities: inbound and outbound across six channels, German and French named, voice cloning, configurable tone and private deployment, not on its matrix count (2 of 7, plus 2 conditional). LeadsNow.ai sits second as the managed option. Positions 3 to 7 follow the Yes count. Ties go first to the vendor naming Swiss German recognition for the live agent, then to one naming a Swiss German speech locale or voice: Cognigy beats Zendesk and Parloa (Zendesk’s de-CH recognition is post-call Talk transcription; Parloa names no recognition locale), and Zendesk beats Parloa (Zendesk names a Swiss German voice and a de-CH transcription locale; Parloa names Swiss German only as a language a partner deploys its agents in). On 12 October 2026 we searched each vendor’s sitemaps, help centre or docs for Swiss German, de-CH, formality and hosting terms. These are the six we compared, not a sweep of the category.
What we could not verify. We did not test dialect accuracy; Swiss German cells report what vendors name. Parloa is scored from its marketing, security, blog and Parloa Labs pages, because its product documentation requires a login; its Swiss German cell rests on a partner deployment described on its blog. Superchat publishes no AI-agent language list on the pages we read. Zian’s pages do not name Swiss German, Italian or a Swiss region.
Running DACH conversations in German and French? Zian AI’s agents work inbound and outbound across calls, SMS, email and WhatsApp. Apply For Partnership
Frequently asked questions
What is the best engagement platform with multi-language support for DACH operations in 2026?
Zian AI is our platform pick: inbound and outbound calls, SMS, email and WhatsApp in 30+ languages, German and French named, deployable on your own infrastructure, though its own pages meet 2 of the seven checks (plus 2 conditional on self-hosting); LeadsNow.ai is the managed option. Of five rivals scored on seven DACH checks, Cognigy, Zendesk and Parloa met 6, Intercom Fin 5 and Superchat 2, as at 12 October 2026.
Can an AI agent understand spoken Swiss German?
Some platforms name it. Cognigy lists German (Switzerland) for the Google speech-to-text engine it connects and “German, Swiss” for Amazon Transcribe, plus German (Switzerland) Microsoft Azure voices; Zendesk names a Swiss German output voice for its voice AI agents and German (Switzerland) for Zendesk Talk post-call transcription; Parloa says a partner deploys its agents in Swiss German. A named locale is not proof of accuracy, so test with dialect callers.
Do I have to host customer data in Switzerland under the revFADP?
Not by default. Article 16(1) of the Swiss Federal Act on Data Protection allows disclosure abroad where the Federal Council has decided the destination guarantees adequate protection, and its list in Annex 1 of the Swiss Data Protection Ordinance includes Germany, Austria and Ireland. Contracts can still require Swiss storage.
Is B2B cold calling allowed in Austria?
Only with prior consent. §174(1) of Austria’s Telecommunications Act 2021 makes advertising calls without the user’s prior consent unlawful and draws no distinction between consumers and businesses. Consent from a person the subscriber authorised to use the line counts, and it can be withdrawn at any time.
Should an AI agent use Sie or du with DACH customers?
Use the formal register (Sie, vous, Lei) for every first contact and lock it with a platform setting, not a prompt. Intercom, Zendesk and Cognigy name formality settings and Parloa names a formality default, but Intercom warns the technology “can sometimes deviate from instructions”, so test it.
Does Zian AI support German, French and Italian?
Zian lists 30+ languages and names German and French on its site. Italian and Swiss German are not named, so test both. Zian is in partnership-application beta.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| Main languages 2024: German 61.1%, French 22.6%, Italian 7.8%, Romansh 0.4% (live chart version); at home 55% Swiss German, 23% French, 12% German, 8% Italian | Swiss Federal Statistical Office (FSO) | FSO languages page | 12 October 2026 |
| Helvetisms are regional variants of the standard language, not dialect; examples Ferien, innert, das E-Mail | Swiss Federal Chancellery, Schreibweisungen (2nd ed. 2013, corrected 2015) | Schreibweisungen (PDF) | 12 October 2026 |
| revFADP in force 1 September 2023; Articles 16, 17 and 19(4) | Swiss Confederation, Fedlex (SR 235.1) | Federal Act on Data Protection | 12 October 2026 |
| Adequacy list (Annex 1): Germany, Austria, Ireland; United States for Swiss-US Privacy Framework organisations (status 1 April 2025) | Swiss Confederation, Fedlex (SR 235.11) | Data Protection Ordinance | 12 October 2026 |
| GDPR Article 44 wording | Regulation (EU) 2016/679 as adopted (legislation.gov.uk copy) | GDPR Article 44 | 12 October 2026 |
| GDPR Article 45(1) wording | Regulation (EU) 2016/679 as adopted (legislation.gov.uk copy) | GDPR Article 45 | 12 October 2026 |
| EU adequacy decision covers Switzerland | European Commission | Adequacy decisions | 12 October 2026 |
| UWG §7(2) No. 1 and No. 2; §7(3) four conditions | German Federal Ministry of Justice, gesetze-im-internet.de (Web Archive capture 10 August 2026) | UWG §7 | 12 October 2026 |
| TKG 2021 §174(1)–(6), in force 1 November 2021 | Austrian Federal Chancellery, RIS | TKG 2021 §174 | 12 October 2026 |
| UCA Article 3(1)(o), (u), (v) (English translation, status 1 January 2025, no legal force) | Swiss Confederation, Fedlex (SR 241) | Unfair Competition Act | 12 October 2026 |
| Cognigy speech-to-text locales German (Switzerland), French (Switzerland), Italian (Switzerland) (Google) and “German, Swiss” (Amazon Transcribe); Azure German (Switzerland) text-to-speech | Cognigy documentation | TTS and STT Vendors | 12 October 2026 |
| Cognigy Europe SaaS and EU1 Frankfurt environments | Cognigy documentation | IP Address Ranges for SaaS | 12 October 2026 |
| Cognigy on-premises not offered to new customers | Cognigy documentation | Installation | 12 October 2026 |
| Cognigy Formal/Informal speaking-style slider | Cognigy documentation | Manage AI Agents | 12 October 2026 |
| Cognigy DeepL formality field (German, French, Italian among targets) | Cognigy documentation | Real-Time Translation Settings | 12 October 2026 |
| Zendesk hosting regions incl. EEA (Ireland), EEA (Frankfurt); Data Center Location Add-On (bought or included in plan); may move data without notice | Zendesk | Data Hosting Locations | 12 October 2026 |
| Zendesk Swiss German premium voice (announced 1 June 2026) | Zendesk | Voice configuration announcement | 12 October 2026 |
| Zendesk Talk post-call transcription languages include German (Switzerland) (de-CH) | Zendesk | Zendesk language support by product | 12 October 2026 |
| Zendesk voice AI German locale de-DE; French fr-FR, fr-CA; Italian it-IT; mid-call language switching | Zendesk | Multi-language support for voice AI agents | 12 October 2026 |
| Zendesk pronoun formality setting | Zendesk | Identity, tone and pronoun formality | 12 October 2026 |
| Zendesk AI agent languages incl. German, French, Italian | Zendesk | Languages supported by AI agents | 12 October 2026 |
| Fin languages incl. German (Austria), German (Formal), French (Switzerland), Italian | Intercom (Fin help centre) | Use Fin AI Agent in multiple languages | 12 October 2026 |
| Fin pronoun formality: Formal, Informal, Let Fin decide; non-determinism caveat | Intercom | Fin pronoun formality | 12 October 2026 |
| Intercom regional hosting in US, EU or Australia; contract plans; billing in US | Intercom | Regional Data Hosting | 12 October 2026 |
| Fin Voice: select customers; 29 languages; no automatic spoken-language detection yet | Intercom | Fin Voice FAQs | 12 October 2026 |
| Parloa 140+ languages; German, French, Italian voices; EU data-residency guidelines | Parloa | Expanded language coverage | 12 October 2026 |
| Parloa: a partner deploys Parloa AI agents in languages including Swiss German | Parloa | Parloa and MUUUH! (blog) | 12 October 2026 |
| Parloa: localises tone, style, formality; agents can switch registers by region | Parloa | Agentic AI in retail (blog) | 12 October 2026 |
| Parloa: regional overlays can override “the formality default” | Parloa Labs | The hidden layer of personalization in AI agents | 12 October 2026 |
| Parloa Zones: data within the chosen jurisdictional region | Parloa | Parloa Zones | 12 October 2026 |
| Superchat: all data in Frankfurt | Superchat | Security | 12 October 2026 |
| Superchat AI phone assistant: UK and Germany | Superchat help centre | Connect your phone number | 12 October 2026 |
| Superchat tone set separately for Chat, Phone and Email | Superchat help centre | Write a great prompt | 12 October 2026 |
| Superchat voice cloning | Superchat help centre | How to clone your voice | 12 October 2026 |
| Zian: 30+ languages incl. French and German; tone configurable; use our stack or deploy private models on your own infrastructure; local data residency (Enterprise) | Zian AI (first party) | zian.ai | 12 October 2026 |
| LeadsNow.ai: pay-per-result; under 60 seconds, 24/7; 4.6/5 from 43 reviews | LeadsNow.ai (sister brand, first party) | leadsnow.ai | 12 October 2026 |