Vai al contenuto
Tecnologia November 7, 2026 10 lettura minima

Arabic TTS for Numbers, Dates and Prices in Voice Agents

How Arabic voice agents should say prices, times, dates and phone numbers, why Gulf callers expect dialect forms, and how SSML say-as and text rules help.

D
November 7, 2026

Risposta rapida

Arabic text-to-speech mishandles numbers unless you plan for it. Number words change with the gender of the noun counted, and spoken times and prices differ from formal Arabic. The safest approach is to convert numbers into the exact spoken words in your own text before synthesis, use SSML say-as only as a hint where the engine supports it, and listen to read-backs on real calls.

A voice agent that gets a price, a time or a phone number wrong has failed at the one thing the caller came for. Arabic makes this harder than English, because numbers interact with grammar, and because the Arabic taught in school and heard on the news is not how most customers speak on the phone. This guide covers where Arabic number reading goes wrong, what Gulf callers tend to expect, two techniques for controlling the output (text normalisation and SSML say-as), and a way to test the result.

The linguistic examples below are illustrative and simplified. Native speakers should review every phrase you put into production, in the dialect of your callers.

Why numbers are hard in Arabic speech

Gender agreement runs the opposite way

In Arabic, the numbers three to ten take the opposite grammatical gender to the noun they count, a feature grammars call polarity. A system that reads digits mechanically can pair the wrong form with the noun, and a native listener hears it as an error at once. The same text, "3 appointments" or "3 services", needs a different number word depending on the gender of the noun. A voice agent therefore needs to know what is being counted, not just the digit.

The counted noun changes form

Two has its own pattern built on the dual form of the noun. After three to ten, the noun is plural. From eleven to ninety-nine, it is singular. A price such as "twenty dirhams" and "five dirhams" need different forms of the word for the currency. Currency names matter for this reason: dirham, riyal, dinar and their sub-units each follow these patterns.

The order of units and tens

From 21 to 99, Arabic says the unit before the ten ("one and twenty"), the reverse of English. Text that has been machine-translated or written by a non-native author sometimes uses English order, which sounds foreign.

Digits themselves come in two styles

Arabic text uses both Western digits (0 to 9) and Eastern Arabic-Indic digits, and callers and databases mix them. Make sure your text processing treats both as numbers, so one style is not skipped or read as a symbol.

Times: formal and spoken forms

Formal Arabic gives the hour as an ordinal ("the second hour"). In everyday speech, many dialects use the plain number instead ("the hour two"), and that dialect form is what a customer says and expects to hear. Both are Arabic a listener understands, but one sounds like a newsreader and the other sounds like a person.

ArticoloFormal styleEveryday spoken style (illustrative)
2:00الساعة الثانية (ordinal form)الساعة اثنتين / اتنين (plain number, depending on dialect)
Half pastوالنصفونص
Quarter pastوالربعوربع
Quarter toإلا ربعًاإلا ربع

Two further points for scheduling flows. First, callers often use a 12-hour clock with a part of the day ("two in the afternoon"), not a 24-hour clock. If your system stores 14:00, convert it to the spoken form with the right part of the day before it reaches the voice. Second, read back the time and ask for confirmation, since a misheard "two" and "twelve" in a noisy call is easy to make.

Dates: Gregorian and Hijri

Business appointments are usually given in the Gregorian calendar, while religious occasions and some official documents use the Hijri calendar. Callers can use either, and may name months in different forms: the Aramaic-derived names used mainly in Iraq, Syria, Jordan, Lebanon and Palestine, Latin-derived names such as يناير, used in Egypt and Sudan, or simply the month number, which is common in Gulf countries. Decide which calendar your agent speaks by default, speak the weekday together with the date ("Tuesday the 12th"), and be ready to accept a Hijri date from the caller without converting it silently. If you convert, say so back to the caller.

Prices and currencies

Prices are where a mistake costs money, and where voice agents should be most conservative. Points to settle in your text rules:

  • Currency names and sub-units. Each currency has its own sub-unit and its own divisor, and the spoken name of the sub-unit differs by country. Check the exact names with your finance team and native reviewers. Decide whether the agent says the sub-unit at all, or rounds to whole units.
  • "And a half". A price of 12.50 is often said as "twelve and a half" followed by the currency, rather than a decimal reading. Decide the rule and apply it consistently.
  • Rounding. State the price exactly as in the catalogue. Do not let the speech layer round it.
  • Ranges and "from". "From 200" and "200 to 300" need clear wording so a range is not heard as a fixed price.
  • Large numbers. Thousands, and the word for "thousand" with its own agreement rules, are a frequent source of error. Test amounts such as 1,200, 2,500 and 12,000.

Phone numbers and reference IDs

People do not read a long number as one quantity. They group digits. Many callers read phone numbers in groups of two or three, and read reference codes character by character, mixing letters and digits. Pick a grouping, apply it consistently, and make the voice pause slightly between groups. Letters in references (such as a booking code) need a decision: spell them in Latin letter names or in Arabic letter names, matching how your callers say them. Always offer to repeat the number.

Text normalisation before TTS versus SSML say-as

There are two ways to control how a speech engine reads a number.

Option 1: text normalisation (spell it out yourself)

Before the text reaches the engine, replace digits with the exact Arabic words you want spoken. The rule engine knows the context: that this is a price, that the noun is feminine, that the time is 14:00 and the caller is Gulf. The advantage is control, because the speech engine receives words and cannot guess wrong. The cost is that you must write and maintain the rules, and test them for each dialect.

Option 2: SSML say-as (hint the engine)

Speech Synthesis Markup Language (SSML) has a say-as element that tells the engine what kind of content it is wrapping. In the W3C SSML 1.1 specification, say-as has an interpret-as attribute naming the content type and optional format and detail attributes. Two details matter in practice. SSML 1.1 defines the element and attributes but does not list the allowed values; a separate W3C note, published in 2005 as a Working Group Note (not a Recommendation), suggests values such as date, time, telephone, characters, cardinal and ordinal, with formats like hms12 and hms24 for time. And the specification says that if the engine does not recognise a value, it renders the text as if the attribute were absent.

That means say-as is a hint, not a guarantee. Engines differ in which values they support, and Arabic support varies, so check your engine's documentation and test. Note also that the note does not define a currency value, so prices are better handled by normalisation. A reasonable policy is: normalise anything that carries money or agreement (prices, counted nouns, times), and use say-as for simple cases such as telephone numbers and characters where your engine is proven to handle it.

Testing: read-back lists and listening on real calls

  1. Build a read-back list. Prepare 50 to 100 test sentences covering each number type: prices with and without halves, times on the hour and half hour, dates, phone numbers, reference codes and the numbers three to ten with masculine and feminine nouns.
  2. Have native speakers listen. One reviewer per dialect you serve. Ask them two questions per line: is it correct, and does it sound like something a person would say?
  3. Record the fixes as rules and re-run the whole list after every change, since fixing one case can break another.
  4. Listen on real calls. A line that sounds fine from a speaker in the office can sound different over a telephone line. Review sample calls end to end, and give the caller a way to ask for repetition.
  5. Put a human fallback in place. If the caller disputes a figure, hand off rather than argue with the synthesis.

Come si inserisce DialerBee

Several DialerBee features speak numbers to callers. The agente vocale basato sull'intelligenza artificiale quotes only prices from your catalogue (a price-truth guard), books appointments after a calendar check, and treats Arabic as dialects rather than one flattened language. The Arabic AI voice agent page describes an agent that has run on live calls in Arabic and English, and suggests exactly the test above: ask it to read back a phone number, a date and an amount, and listen. For other languages, test on a demo first. Fixed prompts are handled by voice packs, sets of prompts in a language shared by the IVR, queues and surveys, and the Creatore di IVR lets a caller choose a language. For menu wording and tone in Gulf calls, see IVR design for Gulf callers.

Domande frequenti

Why does Arabic text-to-speech read numbers wrongly?

Arabic number words agree with the gender of the thing counted, the counted noun changes form, and the same digits can be read in formal or dialect style. A system that converts digits mechanically cannot get all of this right, so it needs context-aware rules.

How should a voice agent say the time in Gulf Arabic?

Most callers expect the everyday spoken form, using the plain number for the hour and short forms for half and quarter, with a part of the day, not the formal ordinal and a 24-hour reading. Have a native speaker from your callers' region approve the exact phrases.

Does SSML say-as work for Arabic?

It can, but it is a hint. SSML 1.1 defines say-as but does not list its values, and the W3C note that suggests values is a Working Group Note, not a standard. Engines may ignore values they do not recognise, so test your engine and normalise important text yourself.

Should a voice agent read digits or whole numbers for phone numbers?

Digits, in groups, with short pauses. Reading a phone number as one large quantity confuses callers. Choose a grouping that matches how your callers say their numbers and offer to repeat.

How do I handle Hijri and Gregorian dates?

Choose a default calendar for your agent, usually Gregorian for appointments, say the weekday with the date, and accept a Hijri date from the caller. If you convert between calendars, read the converted date back so the caller can confirm it.

Can DialerBee's voice agent be trusted with prices?

The agent speaks only prices that exist in your service catalogue, so it does not invent a figure. As with any voice system, we suggest you test read-backs of prices on a demo with your own catalogue before going live.

Fonti

Note: The Arabic examples are simplified and illustrative, and usage varies by dialect and speaker. Have native speakers review any phrase before it goes live. SSML support differs between speech engines.

Letture correlate

Letture correlate: Writing Prompts for an Arabic Voice Agent · What Is Text-to-Speech (TTS)?

Pronti a vedere DialerBee in azione?

Richiedi una demo dal vivo di 15 minuti oppure avvia una prova gratuita di 14 giorni: niente slide, nessun impegno. Le chiamate partono quando il tuo trunk SIP o PBX è collegato e approvato.

Prova gratuita di 14 giorni · credito IA gratuito · senza carta · 11 lingue · BYOC · controlli a supporto della conformità

Visualizza il sito completo in inglese →