Can You Use One AI Agent Across Several Countries?

Short answer: yes. One AI agent can answer calls, WhatsApp and chat for customers in several countries, in their own languages, with one knowledge base and one memory of each customer. What needs planning is everything around it: a local number per country, calling hours that follow each country's rules and each customer's clock, knowledge that is clear about which prices and policies apply where, and the data region your workspace lives in. Split into separate agents when brands, scripts or legal wording differ by country.

What works the same everywhere?

• Channels: the agent answers phone calls, WhatsApp, website chat and Telegram, with one memory of each customer, matched by phone number.
• Languages: set the agent to match the customer and it replies in the language they use: 50 languages on calls, 37 in written replies. Arabic is voice-only.
• Knowledge: one knowledge base serves every language, so you do not translate it for each market.
• Handover: one shared inbox, where staff in any country can take over.

What changes by country?

How do time zones work?

• Your workspace has a clock. A new workspace starts in your own time zone. Holidays you skip are read in the business's time zone.
• Weekday rules follow the customer. Restricting campaigns to certain weekdays works in the customer's time zone.
• Calling hours follow the called person. You set each campaign's calling hours yourself, and they apply on the called person's clock. The product has no legal window of its own, so set hours inside each country's rules: for example, 8am to 9pm for US solicitations and 9am to 9pm for commercial calls in India.
• Callbacks stay inside calling hours. "Call me back after five" is scheduled against the workspace clock and kept inside the campaign's calling hours.

Practical rule: run one outbound campaign per country, with that country's hours and its own contact list, rather than one campaign that mixes everyone.

How do numbers work across countries?

Customers trust a local number, so give each country its own. Outside India you import numbers from your own Twilio, Telnyx or Plivo account; we do not rent US, UK or UAE numbers. One agent can call out from numbers on several providers and use a different one per call, so a US number can ring US customers and a UK number UK customers. If you use Telnyx, it only calls the countries switched on in your outbound voice profile, which is the US and Canada by default.

How do you keep the knowledge right for each country?

• Label anything country-specific in the knowledge base: "UK prices", "UAE opening hours", "US returns policy".
• Write into the instructions how the agent should tell which country a customer is in, such as from the number they rang or by asking.
• Test each country with its own questions, in its own language, from local staff.
• Keep currency in the knowledge base consistent with what you actually charge in each market.

Where does the data live?

A workspace is stored in one region, chosen when you sign up: London for international workspaces (US, UK, UAE and elsewhere), Mumbai for India. India workspaces are billed in rupees with GST invoices; international ones in US dollars. A business that sells in India and abroad and wants each market's data stored in its own region, or billed in its own currency, usually runs one workspace in each. See where your AI agent's data should be stored.

When should you use separate agents?

• Different brand names or tone in different countries.
• Different legal wording in greetings, such as recording notices required in some places and not others.
• Very different services, prices or opening hours, where one knowledge base would confuse more than help.
• Separate teams that should only see their own country's conversations.

Separate agents can still live in one workspace and share your contacts and inbox.

Your next step

Read the market pages for the US, UK, UAE and India, then see which languages work on which channel and how voice campaigns handle hours and retries.