Bilingual agents: serving English and Urdu callers

The language setting is one of the first real decisions in building an agent, because it determines how the agent listens and speaks for every call it ever takes. Get it right at the start and it rarely needs revisiting; get it wrong and every caller who does not fit the mode you picked has a worse experience than they should.

English only

Choose English only when you are confident your callers are comfortable in English for the entire call, business-to-business support lines, international customers, or a local business that has deliberately positioned itself as English-first. The agent will always speak and respond in English, and if a caller addresses it in Urdu, it will politely continue in English rather than switching. This is the right choice when consistency in one language matters more than meeting every caller in their preferred language.

Urdu only

Choose Urdu only when your customers are overwhelmingly Urdu-speaking and a caller using English would be unusual, a local retail shop, a neighbourhood clinic, a service business operating mainly in Urdu-speaking markets. The agent speaks clear, formal Urdu throughout, and if a caller opens in English, it gently responds in Urdu and continues there. This produces the most natural-sounding experience for a purely Urdu-speaking customer base, because the agent never has to decide which language to use, it only ever uses one.

Bilingual: English + Urdu

Choose the bilingual option, labelled "Bilingual — switches to match the caller" in the wizard, when your callers are a genuine mix, which in practice describes most consumer-facing businesses operating in Pakistan. A bilingual agent detects which language a caller is using from the first thing they say and responds in that language, and if the caller switches mid-conversation, the agent switches with them immediately and without commenting on it. It never mixes both languages in a single response unless the caller does so first. This is the mode that best matches how many Pakistani callers actually speak, opening in English and dropping into Urdu for specifics, or the reverse, within the same call.

Bilingual is a premium option

In the wizard, the single-language options sit under "One language" and the combined options sit under "Bilingual — switches to match the caller," with a "Premium" badge on the bilingual choices, meaning they require an upgraded plan. Factor this into your decision early rather than building an agent around a single language and discovering later that your customer base genuinely needed both.

What does not change between modes

Whichever mode you choose, the agent's name, its knowledge base, its FAQ entries and its voice selection on the Voices page are set independently of the language mode. Choosing bilingual does not automatically translate your existing English FAQ into Urdu, and it does not require a different voice than a single-language agent uses. What changes is how the agent listens and which language rule it follows when it speaks; what it can say in each language still depends on what you have written for it, which is why the rest of this guide covers preparing that material properly.

Picking the right mode is a five-minute decision with a lasting effect on call quality. The next section covers the first thing every caller hears regardless of mode: the opening greeting, and how to write one that works for a bilingual audience.

The first message is the single most-heard piece of writing your agent will ever use, and in a bilingual agent it carries extra weight: it is the first signal to a caller that they can continue comfortably in either language. A greeting that sounds confidently bilingual from the first sentence sets the tone for the whole call.

Keep the opening short and warm in either language

The same rule that applies to an English-only greeting applies here: keep it to one short, natural sentence, a name, the business name, and an offer to help. A bilingual greeting does not need to say everything twice; it typically opens in one language and lets the caller's own first response decide which language the rest of the call continues in.

A bilingual greeting, written out

Below is a first message written for a clinic's reception agent, shown first in English, then the same tone and content in Roman Urdu, then in Urdu script. Use whichever matches your team's comfort when drafting, both are the same greeting.

Notice the greeting uses "aap," the respectful form of "you," rather than the informal "tum." This matters enough that it gets its own section later in this guide, but it starts here, in the very first sentence a caller hears.

Should the greeting itself be bilingual?

For a bilingual agent, the opening line is usually best delivered in one language rather than both, typically whichever language is more common for your majority of callers, because the agent will switch the moment the caller responds in the other language anyway. A greeting that tries to say the same sentence twice, once in English and once in Urdu, back to back, tends to sound stilted rather than welcoming. Trust the switching behaviour described in the next section to handle the rest.

Tone words matter as much as vocabulary

The tone setting you choose when building an agent, professional, friendly, formal or casual, shapes word choice in Urdu as much as in English, but the safe default for Urdu business calls leans slightly more formal than the equivalent English tone, because Urdu speakers in a customer-service context generally expect more deference than the breezier tone common in English-language customer service. A friendly English greeting and an overly casual Urdu greeting can feel mismatched even when the words are a direct translation of each other.

A well-written bilingual greeting tells a caller, in the first five seconds, that they can speak however they are comfortable. The next section covers what happens after that opening line, when a caller actually switches language partway through the call.

Getting the big picture right, mode, greeting, code-switching, still leaves a layer of detail that determines whether an Urdu call sounds natural or slightly off: how the agent handles names, numbers, addresses and dates. These are small, mechanical things, but they come up on almost every call, so getting them right matters more than their size suggests.

Names: respectful forms matter

Addressing a caller by name in Urdu commonly pairs the name with a respectful suffix, "Sahib" or "Sahiba," particularly for a formal or older-skewing customer base ("James Sahib, aap ka appointment confirm ho gaya hai" rather than the bare "James, aap ka appointment confirm ho gaya hai"). Whether to use this depends on your business's tone, a younger, casual consumer brand may skip it, while a clinic, a bank-adjacent service or a formal professional practice generally should not. Decide this deliberately as part of your tone setting rather than leaving it inconsistent.

Numbers: say them the way your customers actually expect

Phone numbers, order numbers and confirmation codes are usually read back digit by digit regardless of language, "zero three zero zero" rather than "three hundred," and this holds in Urdu as well as English. Prices and quantities, by contrast, are more often spoken as whole numbers in natural Urdu phrasing, "do hazar rupay" (دو ہزار روپے) for two thousand rupees, rather than digit by digit. When you write prices or quantities into your knowledge base or FAQ for an Urdu-speaking audience, write the number the way you want it spoken, not just as a bare digit, if the natural reading matters to you.

Addresses: keep the structure, adapt the pronunciation

A Pakistani address read aloud in Urdu typically keeps proper nouns, area names, road names, landmarks, largely as they are (a road named after a person's name is not translated), while connecting words ("near," "opposite," "behind") are naturally spoken in Urdu ("Main Boulevard ke qareeb," قریب, "Main Boulevard کے قریب"). Write your business address and any directions in your knowledge base exactly as you want a human receptionist to say them, since that is effectively the standard to aim for.

Dates and times: match local convention

Days of the week and months are commonly said in English even within an otherwise Urdu sentence in Pakistani business speech ("Monday ko," "January mein"), while the surrounding grammar stays Urdu. Times are typically read in a mix as well, "subah 10 baje" (صبح 10 بجے) for 10 AM, rather than a fully translated or fully English phrasing. This mixed convention is itself a form of natural code-switching, covered in the previous section, and an agent built for bilingual callers should sound comfortable using it rather than insisting on a fully translated or fully English version of dates and times.

These details are easy to overlook because none of them, individually, feels important. Together, they are a large part of what separates an Urdu-language call that sounds like it was built for Urdu speakers from one that sounds like an English script read through a translator. The next section turns to the written material behind all of this: your knowledge base and FAQ, prepared properly for two languages.

A bilingual agent's language mode controls how it listens and speaks; it does not automatically translate the content you give it. Your knowledge files, your FAQ entries and your business instructions still need to actually contain the information in a form the agent can use in both languages, and that takes deliberate preparation, not just a language setting.

Your knowledge base does not translate itself

If your FAQ and uploaded files exist only in English, an Urdu-speaking caller's questions are still matched against English content, and the quality of the answer the agent gives back in Urdu depends on how well it can draw on that English material. The more reliable approach, and the one this section recommends, is maintaining core FAQ answers in both languages rather than relying on the agent to bridge the gap on its own every time.

Start with your highest-traffic FAQ entries

You do not need to duplicate your entire knowledge base into Urdu on day one. Start with the handful of FAQ entries that get asked most, hours, pricing, your two or three most common policy questions, and write an Urdu version of each alongside the English one. Add an agent-wide FAQ entry in Urdu for exactly the questions you already know matter most, rather than attempting a complete translation pass before launch.

Politeness forms: use "aap" everywhere, not just the greeting

The respectful "aap" form of "you" should run through every FAQ answer and every piece of knowledge material you write in Urdu, not just the opening greeting. This is the single most common slip when FAQ content is translated quickly: an answer that starts formally and drifts into the more casual "tum" partway through reads as inconsistent, even jarring, to a native speaker, because in real Urdu business conversation a shift in register mid-sentence signals something has gone wrong. Write every Urdu answer with "aap" throughout and have a native speaker check the whole set together, not entry by entry, specifically to catch this kind of drift.

Do not rely on machine translation alone

A quick machine translation of an English FAQ answer is a reasonable first draft, but it should never be the final version. Machine-translated Urdu frequently produces grammatically correct but unnatural phrasing, overly literal word choices, or an inconsistent politeness register, exactly the kind of small wrongness that a native Urdu-speaking caller notices immediately even if they cannot articulate why. Treat a machine translation as a starting point a native speaker edits, not a finished answer you upload directly.

Decision table: matching content to your language mode

Expanding over time

Preparing a fully bilingual knowledge base does not need to happen all at once. Launch with your highest-traffic questions covered in both languages, then use the "Couldn't answer" log on the agent's Knowledge pages the same way described for any knowledge base, watching for Urdu-phrased questions that come up repeatedly and adding Urdu FAQ entries for them specifically. Over the first month or two, this naturally grows your Urdu coverage toward exactly the content your real Urdu-speaking callers need, rather than guessing up front.

A bilingual language mode gives your agent the ability to meet callers in their own language; the content you prepare is what it actually says once it gets there. The final section covers how to confirm all of this works, with real native speakers, before your customers are the ones testing it.

Everything in this guide, the language mode, the greeting, code-switching, numbers and addresses, bilingual FAQ content, comes together (or falls apart) in an actual call. The only reliable way to know which one happened is to test deliberately, with real native speakers, before real customers do.

Why a native speaker has to be involved

You can review Urdu text on a page without being fluent, but judging whether a spoken Urdu response sounds natural, whether the "aap" form is consistent, whether a code-switch lands smoothly, genuinely requires a native or highly fluent Urdu speaker listening to real calls. If nobody on your immediate team fits that description, recruit someone, a bilingual friend, a family member, a part-time reviewer, specifically for this testing phase. This is not a step to skip or approximate.

Structure the test calls deliberately

Do not simply "try the agent out" informally. Work through a structured set of test calls that each check a specific thing: one call entirely in English, one call entirely in Urdu, and at least one call that deliberately switches language mid-conversation, ideally more than once, to confirm the agent follows naturally both ways. Within each call, ask at least one question from your FAQ, one question about pricing or a number, and one question the agent is not expected to know, to confirm its fallback behaviour sounds right in that language too.

What a failed test actually tells you

A test call that goes wrong in Urdu almost always points to one of a small number of causes covered earlier in this guide: the FAQ content genuinely does not exist in Urdu yet, a translated answer drifted out of the respectful "aap" form partway through, a number or address was written in a form that does not read back naturally, or the underlying instructions described behaviour that only makes sense in English phrasing. Treat a bad test result as a pointer back to the relevant section of this guide, not as evidence that bilingual mode itself is unreliable.

What to do next

Building a genuinely good bilingual agent is less about the technology and more about treating Urdu as a real, equal language in your preparation, not an afterthought translated quickly at the end. To put this guide into practice:

1. Decide your language mode honestly, based on your real caller mix, defaulting to bilingual if your customers are genuinely a mix of English and Urdu speakers.
2. Write (or rewrite) your first message for a bilingual audience, checked by a native speaker for both naturalness and the respectful "aap" form.
3. Review your core instructions to confirm they describe behaviour language-neutrally, since the bilingual mode already handles the actual switching.
4. Prepare your highest-traffic FAQ entries in both English and Urdu, paying particular attention to how numbers, names and addresses are written.
5. Run the full bilingual test-call checklist above, with a native speaker involved, before you consider the agent ready for real callers.
6. After launch, review the "Couldn't answer" log for recurring Urdu-phrased gaps and keep expanding your Urdu FAQ coverage over time.

A bilingual agent built this way, a deliberate language choice, a natural greeting, content genuinely written for both languages, and a real test-call process, sounds to a Pakistani caller like it was built for them specifically, rather than translated as an afterthought. For the knowledge base work referenced throughout this guide, see the knowledge base guide, and for the rest of the build process, the complete guide to building your first AI voice agent and deploying your agent.