2026 Reference Report
The State of Multilingual Outbound Calling
A practical reference on the rules, languages, and technology behind outbound calling across 17 markets — calling hours, do-not-call registers, consent regimes, and answering-machine detection.
Key takeaways
Outbound calling rules differ sharply by market: the US allows 8:00–21:00 in the called party's local time, France restricts canvassing to weekday windows, and Germany and Spain are effectively consent-first. At least a dozen markets require scrubbing against a do-not-call register (US National DNC, UK TPS/CTPS, France's Bloctel, Italy's RPO, Spain's Lista Robinson, Mexico's REPEP, and GCC registries). A 3% abandoned-call limit is common in the UK and US. And answering-machine detection tuned only to US-English degrades elsewhere — language-aware, transcript-based AMD kept false positives below 3% in DialerBee's internal pilot conditions (vs 10–20% typical for beep detection). Results vary by campaign, list quality, carrier, region, and language.
Methodology & sources
This report compiles two kinds of information. The regulatory landscape (calling hours, do-not-call registers, consent regimes) is summarized from each market's public telecom and data-protection regulators — it is general guidance for planning, not legal advice, and rules change, so confirm the current position with the relevant regulator and qualified counsel. The performance figures (answering-machine-detection accuracy, throughput ranges) reflect DialerBee's internal pilot conditions and general industry ranges; they are illustrative and results vary by campaign, list quality, carrier, region, pacing, and language.
The multilingual reality
One operation, many languages and rulebooks
Outbound calling stopped being a single-language, single-jurisdiction activity long ago. A BPO in the Gulf may run Arabic, English, Hindi, and Urdu campaigns in the same shift; a European operation may span German, French, Italian, and Spanish; a nearshore center may serve both US-English and Latin American Spanish. Each language changes how customers answer, how voicemail greetings sound, and which scripts build trust — and each country changes the calling hours, consent basis, and do-not-call obligations that apply.
That combination is what makes outbound genuinely hard in 2026. The technology has to detect voicemail across dialects, agents have to speak the customer's language, and the platform has to apply a different compliance profile per destination — not one global setting. The rest of this report lays out the two moving parts that matter most: the country-by-country rulebook, and answering-machine detection across languages.
The rulebook
Outbound calling rules across 17 markets
General, publicly-documented positions for planning — not legal advice. Rules change; confirm the current position with each regulator.
| Market | Regulator(s) | Typical calling window | Do-not-call / opt-out | Consent basis |
|---|---|---|---|---|
| United Arab Emirates | TDRA | Sun–Thu, daytime; restricted on weekends/holidays | TDRA Do-Not-Call registry | Prior consent; PDPL |
| Saudi Arabia | CITC | Sun–Thu, ~9:00–21:00 | CITC DNC provisions | Prior consent; Arabic disclosures; PDPL |
| Qatar | CRA | Sun–Thu, daytime | DNC / opt-out | Prior consent; PDPPL |
| Bahrain | TRA | Daytime | DNC / opt-out | Prior consent; PDPL |
| Kuwait | CITRA | Sun–Thu, daytime | DNC / opt-out | Prior consent |
| Oman | TRA | Daytime | DNC / opt-out | Prior consent; PDPL |
| Egypt | NTRA | Sun–Thu, daytime; no calls during Ramadan fasting hours | NTRA DNC registry | Verifiable, withdrawable consent; Law 151/2020 |
| Jordan | TRC | Sun–Thu, daytime | DNC / opt-out | Prior consent; PDPL (2023) |
| European Union | GDPR + ePrivacy | Varies by member state | National registers vary | Opt-in or opt-out/soft opt-in — varies by state |
| Germany | BNetzA / UWG | Consent-first (no cold-B2C window) | — (consent is the gate) | Prior express consent; GDPR/BDSG; CLI must display |
| France | ARCEP / CNIL | Mon–Fri 10:00–13:00 & 14:00–20:00; not weekends/holidays | Bloctel (mandatory scrub) | Consent + Bloctel; frequency capped |
| Italy | AGCOM / Garante | Daytime | RPO (Registro Pubblico delle Opposizioni) | Prior consent; GDPR |
| Spain | CNMC / AEPD | Consent-first (Ley 11/2022, from 2023) | Lista Robinson | Prior consent or existing relationship; GDPR/LOPDGDD |
| United Kingdom | ICO / Ofcom | Daytime (UK time) | TPS / CTPS (mandatory scrub) | PECR — no calls to registered numbers without consent |
| United States | FCC (TCPA) / FTC (TSR) | 8:00–21:00 called-party local time | National DNC + state lists (scrub ~every 31 days) | Prior express written consent for autodialed/prerecorded |
| Mexico | IFT / PROFECO | Daytime (Central Time) | REPEP (do-not-call) | Consent + aviso de privacidad; LFPDPPP |
For a deeper per-country breakdown, see the DialerBee country guides linked at the end of this report. A 3% abandoned-call limit is a common threshold in the UK (Ofcom) and US (FCC safe harbor).
Answering-machine detection
Why beep detection breaks across languages
Traditional answering-machine detection (AMD) listens for a beep and for speech-timing patterns tuned to US-English voicemail. On other carriers, dialects, and greeting styles, that heuristic misfires — either dropping live people as "machines" (a false positive that silently kills contact rate) or leaving agents on voicemail. Commonly cited false-positive rates for beep detection fall in the 10–20% range.
The alternative is language-aware, transcript-based classification: the system transcribes the first seconds of the call and classifies a short human greeting versus a scripted machine message, per language. In DialerBee's internal pilot conditions this approach kept false positives below 3% with sub-second classification; results vary by list quality, carrier, region, and language. See the AMD benchmark methodology and the deep dive on how false positives erode contact rates.
9
languages with language-aware AMD & transcription
<3%
AMD false positives in internal pilot conditions
10–20%
false positives commonly cited for beep detection
Throughput
Dialing modes and what they trade off
The dialing mode sets the balance between agent-time efficiency and abandoned-call risk. These are general industry ranges — actual throughput depends on list quality, connect rates, talk time, and pacing.
| Mode | How it paces | Best for |
|---|---|---|
| Preview | Agent reviews the record, then dials | High-value, sensitive, or complex accounts |
| Power | Dials the moment an agent is free | Follow-ups and callbacks |
| Progressive | Controlled pacing, one call per free agent | Service- and compliance-sensitive campaigns |
| Predictive | Dials ahead of agent availability to lift talk time | Large campaigns — with abandon-rate guardrails |
Predictive dialing raises throughput but must stay within the abandoned-call limits above (commonly 3% in the UK/US). See the dialing-modes guide and the free abandon-rate estimator.
Key figures to cite
Reference this report
- US calling window: 8:00–21:00 in the called party's local time zone.
- France: canvassing limited to Mon–Fri 10:00–13:00 & 14:00–20:00.
- 12+ of 17 markets require scrubbing against a do-not-call register.
- Common abandoned-call cap: 3% (UK Ofcom, US FCC safe harbor).
- AMD false positives: <3% in DialerBee internal pilot conditions vs 10–20% typical for beep detection.
- DialerBee covers 9 languages across 17 markets.
Suggested citation
DialerBee, The State of Multilingual Outbound Calling — 2026 Reference Report. https://dialerbee.com/reports/state-of-multilingual-outbound-calling-2026 — figures reflect internal pilot conditions and public regulatory sources; not legal advice.
Frequently Asked Questions
What are the outbound calling hours by country?
Which countries require scrubbing against a do-not-call register?
What is the abandoned-call limit for predictive dialing?
Why is answering-machine detection harder across languages?
How many languages does multilingual outbound calling need to cover?
This report is for general educational and planning purposes and is not legal advice. Regulations change and vary by customer type, campaign purpose, and channel. DialerBee provides compliance-supporting controls; it does not provide legal advice or guarantee regulatory compliance. Performance figures reflect internal pilot conditions and results vary. Confirm the current rules with the relevant regulator and qualified counsel before launching campaigns.
See multilingual outbound in action
Language-aware AI AMD in 9 languages, per-market compliance controls, and BYOC SIP. View pricing.