Answering Enquiries in a Second Language: Tone, Templates and Translation

Writing in a second language isn't the problem. Writing in translated English is, and guests notice it in the first line.

Last updated: September 27, 2026

You can write a correct answer in your second language and still lose the booking, because the guest reads the tone before they read the details. It isn't a grammar problem. It's a distance problem, and it shows up in the first line, long before anything useful is said.

Key Takeaways

• Correct isn't the same as warm. A flawless sentence written in the register of a call centre still reads as a call centre.
• Templates are a starting point. Vary the opening and the close, keep the facts identical, and the reply stays yours.
• Some questions need you. Anything about safety, money, accessibility or a complaint gets written fresh rather than assembled.
• Name your second language. Saying it once removes the awkwardness, and guests are almost always kind about it.
• Shorter beats thorough. Two sentences that answer the question land better than five that explain why.

Why a translated reply reads as distance

Translation keeps the information and drops the rhythm. It moves the facts across and leaves the rest behind: the short answer first, the small aside, the willingness to say "yes" instead of "we would like to confirm that this is possible".

So you end up with something like: "Dear guest, regarding your inquiry, we kindly inform you that luggage storage prior to the check-in time may be arranged." The facts are right. The guest, reading it on a phone, hears a hotel front desk. What they needed was: "Yes — you can drop your bags from 10. I'll be there."

Formality isn't politeness, in English. It's the opposite more often than not. A host who writes "kindly be advised" sounds further away than a host who writes "sure, no problem". The second one isn't sloppy. It's how people actually write to each other when they expect to meet in a week.

A few habits push a reply toward that distance, and they're easy to spot once you look for them. Long openers that name the subject before answering it. Passive constructions where a person belongs. Apologising twice for the same delay. Literal versions of idioms that don't travel — the phrase that means "no worries" in your language can land as "it doesn't matter" in English, which is a different thing entirely.

None of that means your English is bad. It means the reply was assembled in one language and delivered in another, and the guest can feel the seam.

Building a template bank you vary rather than paste

A template is useful in the way a recipe is useful: it holds the facts steady while you cook. The mistake is pasting the whole thing, greeting included, so that a guest who writes twice gets the same words back twice. That's what makes a host feel like software.

Build the bank from real enquiries rather than from imagination. Look at the last twenty messages you sent and pull out the parts that never change: the address of the building, the check-in window, how the door works, the wifi details, the bin day, where to park. Those are facts, and facts should be identical every time.

Around the facts, leave room to write. Change the greeting so it matches what the guest actually said. Change the closing so it fits the conversation. If someone asked three questions, answer them in the order they asked, not the order your template keeps. A guest can tell whether their message was read.

Keep one more rule: read every template aloud before you save it. Anything you wouldn't say out loud to someone standing in front of you gets rewritten. It's a fast filter, and it catches the stiff phrases that only exist in written English.

Where do these enquiries arrive? If they come from Airbnb, they land in a single inbox, because that's the channel the inbox connects to. Enquiries from other places are answered where they arrive, which is worth knowing when you're deciding where to keep your facts.

Handling the questions no template can answer

Some enquiries shouldn't go anywhere near a template. A guest who mentions a smell in the hallway, a broken lift, a refund, a wheelchair, an elderly parent and a flight of stairs — those messages are asking whether you're a person worth trusting. A neat automated-sounding paragraph is the worst possible reply.

Write those by hand, and use a shape rather than a script. Acknowledge the thing they raised, in their words. Answer the part you can answer right now. Say what you'll check, and say it without inventing a promise you can't hold. Then stop. Padding a sensitive reply with reassurance makes it sound less honest, not more.

If a sensitive answer needs translating, translate it yourself or write it yourself in English, even badly. Machine translation flattens exactly the warmth you need here, and it can turn a careful sentence into a formal one. A slightly rough answer that sounds like a human being beats a smooth one that sounds like a form.

This is also where the small details of your setup help rather than get in the way. Language follows the property in LOCALSBNB — six languages, with English as the fallback when one is missing. The six are English, Chinese simplified and traditional, Japanese, Thai and Malay. The facts you keep once come back in the language your guest writes in. And your calendar of bookings across Airbnb, Booking.com, Agoda and Trip.com sits at localsbnb.com, which is often what an enquiry is quietly asking about.

Saying plainly that you are writing in a second language

There's a sentence most hosts avoid, and it works almost every time: something like "Excuse my English — it isn't my first language, so ask me again if anything's unclear." It costs one line and it changes how the whole message is read.

Said once, it turns a stiff phrase into an endearing one. The guest stops grading your grammar and starts reading for meaning. It also gives you permission to write more plainly than you would otherwise dare, which is a style advantage rather than a compromise.

Don't lead with it every time, and don't use it to dodge an answer. Put it at the end when the answer is simple. Put it near the top when the question is complicated and the stakes are higher. And if you don't understand a question, say so and ask — a clarifying question is cheaper than guessing wrong and having to undo it later.

One more thing worth saying: writing plainly is a skill you get to keep. Every short, clear reply you write teaches you a phrase you'll use again. That's a better use of your second language than reaching for the formal register you were taught in a classroom.

FAQ

Should I use machine translation for guest messages?

Use it to understand an incoming message, and be careful about using it for the reply. It's good at facts and weak at tone, which is exactly backwards from what a nervous guest needs. For anything emotional or complicated, write it yourself and keep it short. A small mistake you can explain beats a formal sentence that hides who's writing.

Will guests think less of me if I say English isn't my first language?

Almost never. Guests judge you on whether their question got answered clearly, not on whether your grammar was perfect. Naming it early tends to make people warmer rather than more critical, and it lowers the pressure on you to write something you'd never say out loud.

How many templates do I actually need?

Fewer than you'd think. Most enquiries are about access, timing, facilities or the area, and a handful of fact blocks covers those. The value isn't in the count, it's in keeping the facts consistent while the sentences around them change.

Answer like a person and the language stops being the story. Keep your facts in one place, vary the words around them, write the sensitive answers by hand, and say the one sentence that makes your second language a detail rather than a problem. The bookings your replies are about sit on one calendar at localsbnb.com, which is where the accurate answers start.

---

This article is general guidance for hosts on writing guest messages and isn't legal or platform policy advice; platform messaging rules and current terms prevail.