How a small business can answer customers in several languages

Your customers do not all write in the same language. One week you might get an enquiry in English, the next in Chinese, Vietnamese, Arabic, Hindi or Spanish, sometimes in the same afternoon. You probably run the business in one or two languages yourself, and you cannot be at your desk every hour. This guide looks at how a small business can answer customers in several languages, what it takes, and where the honest limits are.

Where language gets in the way

Most of the problem is not your whole website. It is a handful of moments when a customer wants one specific answer, quickly. If they cannot ask in their own language, some will simply try the next business, and they will rarely tell you that is why.

The first enquiry

A new customer lands on your site with one question: do you take walk-ins, do you deliver to my suburb, is there a class starting soon? If they cannot ask in their own language, the conversation ends before it starts.

Prices and policies

Cost, deposits, cancellations, warranties and refunds are where wording matters most. A wrong answer causes real damage: a missed booking, a bad review, a refund argument. They are also the questions you repeat most, which is why they should be written down once and reused.

Bookings

A booking is a two-way exchange. The customer needs a time; you need a name and a phone number. If either side misunderstands, someone turns up on the wrong day or the slot is wasted.

Follow-up calls

You get the enquiry, you call back, and nobody answers, or the person on the line cannot explain the details. The message arrived in one language; the conversation needs another.

None of these moments needs a fully translated website. They need correct answers to specific questions, in the language the customer actually used.

Four ways to handle it

Small businesses usually land on one of four approaches. Each has a place, and most use a mix.

The first three options are about people or pages. The fourth answers the question that was actually asked, at the moment it was asked. A bot built with Botsmith replies in the language the visitor writes in, whether your site is in English, Chinese, or anything between. It answers only from your content, pulling the relevant text from your pages and uploaded files. Ask something outside that content and it says it is not sure, rather than inventing a price or a policy. Every bot gets its own link and QR code that opens straight into the chat. If you are weighing up costs, you can compare options on the pricing page.

Keep one source of truth

If you keep separate translated price lists and policy pages, they drift apart. You update the English version in a rush, the others quietly become wrong, and a customer quotes you the old price. The fix is unglamorous but effective: write each fact once, in your main language, in one place. The bot reads that one version and answers in the visitor's language, so there is nothing to keep in sync.

In practice, that means one page or file per topic: services, prices, opening hours, booking and cancellation terms. If a fact appears twice, make one copy the real one and point the other at it. When something changes, you change it once. If your prices live in a spreadsheet or your policies in a PDF, upload them: the bot answers from PDF, Word, Excel, PowerPoint and CSV files alongside your pages. Our guide on what to put in a chatbot knowledge base covers choosing those pages and files, and the guide on writing instructions for your support bot explains how to tell the bot to use them. If you are unsure which questions a bot should handle, read what a website support bot should answer.

Where translation can go wrong

Automatic translation is useful, but it is not perfect. Knowing where it struggles keeps the mistakes away from your customers.

• Names. People and place names get mangled, especially when typed in the original script. A name that comes back wrong is a poor first impression.
• Technical and legal terms. Industry words carry exact meanings; a visa category or a building term is not something to guess at.
• Numbers and dates. Prices, phone numbers, dates and times must come back exactly as you wrote them. A digit in the wrong place is simply wrong.
• Tone. A short reply in one language can read as rude in another. Plain, polite wording survives translation better than jokes or slang.

Two habits protect you. First, tell customers up front that important details will be confirmed in writing:

Important details will be confirmed in writing.

That one line sets the right expectation. Second, decide which questions a person must answer. Legal, medical, migration and financial advice belongs with qualified people, in a language the customer understands, and the bot should hand those straight to you. If you run a migration agency, case questions need a registered agent; see how this works for migration agents. The same applies to dental clinics and tutoring providers, where health details and enrolment terms need a human.

What to do when a person has to reply

Sooner or later a customer needs you rather than a bot. Set that path up before you need it.

With Botsmith, when a visitor leaves a name, phone number or email, you get an email within seconds with the full transcript attached. Read the conversation in the customer's own words, and paste it into a translation tool if you need to. Reply in plain, short sentences; long, complicated replies translate badly in both directions.

When the matter is sensitive, offer a bilingual staff member or an interpreter. A short call is often easier than a chain of misunderstood messages. And when the bot could not answer something, that question is collected for you automatically. Answer it once in your knowledge base and the bot knows it from the next message on. That loop is how the setup improves without extra work each week.

A one-hour test before you rely on it

Do not rely on a setup you have not tested. Block out an hour and work through this list.

1. Write down your ten most common questions, the ones you answer every week.
2. Ask each one in two or three languages, the way a customer would type it, mistakes and all.
3. Check that prices, policies, dates and opening hours come back exactly as written, not close enough.
4. Ask something the bot cannot know, such as a price you never published, and check it says it is not sure instead of inventing one.
5. Have a friend who speaks the language read the replies and flag anything that sounds off.
6. Fix whatever the test exposes, then run it again.

A test like this tells you more than any sales pitch. If the bot passes, switch it on. If not, you know exactly which content to fix first. The same setup works overnight, when most language gaps go unnoticed; see how to handle after-hours enquiries. If customers ask about privacy, read the notes on AI chatbot privacy for small business first.

This guide describes general practice for small businesses. It is not legal, migration or professional translation advice.