Call analysis for Arabic sales and support calls

Why Arabic calls need their own treatment

Arabic is not one spoken language on a sales call. A customer in Cairo, a buyer in Riyadh and a tenant in Dubai use different words for the same thing, pronounce the same words differently, and move between dialect and Modern Standard Arabic depending on how formal the conversation feels. English product names, figures and job titles are often dropped into the middle of an Arabic sentence.

Tools that were built for English and extended to Arabic later tend to treat all of this as one language. The transcript comes back in something closer to formal written Arabic than to what was said, names are misheard, and the summary reads smoothly while missing the point. For a manager who cannot listen to every call, that is worse than no summary at all, because it looks trustworthy.

Dialect is a setting, not a guess

Callens supports Egyptian, Saudi and Emirati Arabic, and English. The language is set per organization or per employee. A company with one sales floor in Cairo can set Egyptian Arabic once for everyone. A company with a support team in Riyadh and account managers in Dubai can set each employee to the dialect they actually speak on calls.

Setting it explicitly matters because the people on your team are known in advance. Your Saudi account manager will speak Saudi Arabic on Monday and on Thursday. Treating that as configuration, rather than something to be inferred from every recording, keeps the setting visible and easy to correct.

Named speakers, not "speaker 1"

A transcript is only useful if you know who said each line. In Callens every measure is attributed to a named person rather than an anonymous speaker label. Speakers are assigned by who greets like an agent, and when the roles come out wrong, one click corrects them.

That is what makes the numbers mean something. The 22 conversation measures, such as talk ratio, silence, interruptions, response speed and open questions, are computed from word-level timings and belong to a specific person, so a weekly view of an agent's calls is about that agent and not about whoever happened to be on the line.

Summaries in the call's language, with English beside them

Many teams in the region are run by managers who read Arabic and English, report to leadership in English, and coach agents in Arabic. Callens delivers summaries in the language of the call with an English rendering beside them, so the regional manager and the head office read the same call without a separate translation step.

Each call also gets five judgments: what the customer wanted, who decides, the budget, the timeline and the outcome. Commitments, meaning what was promised, by whom and by when, are lifted into one team queue. On an Egyptian real-estate call that might be a promise to send the payment plan by Sunday. On a Saudi support call it might be a promised callback once a technician visits.

Evidence you can check in Arabic

Every model-produced line is checked against a real segment of the transcript before it is stored, and every claim cites the second of the recording it rests on. A reviewer who doubts a line in the English rendering can jump to the Arabic moment and listen.

Search finds the moment something was said however it was phrased, which matters when the same objection can be voiced in several dialects. Chat answers questions across every call the user is allowed to open and says where each part of the answer came from.

• Pick real calls from each dialect your team speaks.
• Check that each line is attributed to the right named person.
• Open the cited second and confirm the summary matches what you hear.