Messaging and channels

Reply Templates for Customer Messages: Writing Polite Japanese

How to build a library of reply templates for customer messages in Japanese and other languages: structure, politeness levels, variables, review, and upkeep.

Call editorial team · Published · 5 min read

Every support team sends the same few replies again and again: hours, delivery, rescheduling, how to cancel, how to apply. Typing them from scratch wastes time and produces inconsistent answers. A template library fixes both, provided the templates are good.

A support agent drafting a reply on a laptop with a list of saved templates beside it
Illustrative image

This guide is written for businesses writing to customers in Japanese, though most principles apply to any language. It covers how Japanese business messages are usually structured, how to choose a level of politeness, how to design the templates and their variables, and how to keep the library healthy. It pairs with Customer Support on LINE Official Accounts and Omnichannel Support.

Why templates help, and where they hurt

Good templates and bad templates

HelpsHurts
SpeedStaff reply in a minute instead of fiveStaff send without reading and get details wrong
ConsistencyEvery customer hears the same policyReplies feel robotic or ignore the question
QualityWording reviewed once, used many timesOld wording lingers after the policy changes
OnboardingNew staff learn the house style quicklyStaff rely on templates and never learn the reasons

The goal is to speed up the repeatable part and leave room for the human part. A template is a starting point, not a script to paste blindly.

The shape of a Japanese business message

Japanese customer messages follow a familiar order. Following it makes a message feel proper even when it is short.

A typical structure

  1. GreetingThanks for contacting the business, and often the sender's name.
  2. AcknowledgeBriefly recognise the customer's request or concern.
  3. AnswerThe substance, in clear steps or a short statement.
  4. Next stepWhat the customer should do, or what you will do and when.
  5. ClosingA courteous close and an invitation to ask again.

Choosing the level of politeness

Japanese has several levels of politeness. Customer-facing messages normally use respectful and humble forms, and the right level depends on the customer and the industry. A luxury hotel will use a more formal tone than a casual café. Two traps to avoid: forms that are over-stacked and hard to read, and forms that are too casual for a first contact. Decide a house style, write it down with a few sample sentences, and have a native-level reviewer check the templates before launch.

Designing the templates

One template, one purpose

A template that tries to cover several situations ends up vague. Make each one answer a single question: opening hours, change of address, cancellation, delivery status, a request for more information.

Use variables for the details

Fill in names, dates and order references with variables rather than typing them by hand. It reduces mistakes and keeps the template readable. Make sure a missing value is obvious, for instance by a visible placeholder, so nobody sends a message with a blank in it.

What to put in a template library

  • InformationHours, location, access, services, how to apply.
  • ProcessCancellations, changes, returns, delivery questions.
  • Apology and recoveryDelays, errors, complaints, with room for specifics.
  • Closing the loopConfirming a task is done and inviting follow-up.
  • Out of hoursAcknowledging a message and stating when you will reply.

Adapting to the channel

The same answer may need different wording on email, chat and a messaging app. Email can be longer and more formal. Messaging apps expect shorter text, often without a long preamble. Keep the courtesy but shorten the form. Do not send more than the customer needs on a small screen.

ChannelLengthStyle notes
EmailMedium to longFull greeting and closing, clear subject line
Chat or messaging appShortBrief greeting, one or two points per message
Reply after a phone callShortRefer to what was said on the call, and confirm the agreed next step

If you send messages in more than one language, translate by meaning and have a speaker of each language review them. Machine translation is useful for a first draft but should not go out unreviewed, particularly where tone matters.

A sample template, step by step

Here is a hypothetical reply to a customer asking to change a booking, shown in English so the structure is clear. The Japanese version follows the same order, with the polite forms suited to your business.

Variables sit in square brackets here. Notice that the template never promises that the new date will be available, and says when the customer will hear back. Both are habits worth building into every template: do not promise what you cannot confirm, and always tell the customer what happens next.

Mistakes to avoid

Keeping the library healthy

Template governance checklist

  • Every template has an owner
  • Each has a purpose line saying when to use it
  • Facts such as hours and policies live in one place
  • Templates are reviewed on a schedule
  • Retired templates are removed or marked
  • Staff can suggest improvements
  • Drafts are kept separate from approved templates

Mark templates as draft until they are approved, and only let approved ones appear in staff's everyday tools. After policy or price changes, search the library for the old wording. Track which templates are used most and which are never touched; the second group can usually be deleted.

A good library also saves time for reviewers: once a wording has been approved, later replies can reuse it with confidence instead of being checked line by line each time.

Doing it in Call

Call has a Message templates area where you can keep templates for chat and SMS-style messages. You can switch between your own templates and read-only samples in Japanese and English, filter by business type, channel, language and purpose, copy a sample into your library as a draft, write your own, duplicate one, or ask for three drafts created with AI. Owners, administrators and managers can mark a template active so it is offered to staff in the inbox and campaign composers, or draft so it is not. A template only fills the message box, so staff can adapt it before sending. Call does not send SMS by default; sending by text depends on an operator enabling it, so your templates are most useful in the inbox and chat channels first. See Call Message Templates and Call Shared Inbox.

Frequently asked questions

Should staff send templates exactly as written?

Not blindly. Staff should check the details and adapt the opening or closing to the customer. The template saves the typing, not the thinking.

How many templates do we need?

Start with the ten or so questions you answer most often and add as patterns appear. A small, well-kept library beats a large neglected one.

How polite should Japanese customer messages be?

Use a respectful, humble style that fits your industry and customer. Write a house style with examples, and have a native-level reviewer check it.

How do I avoid errors in variables?

Use clear placeholders and a final read-through before sending, so no message goes out with a blank or the wrong name.

Can I use machine translation for templates?

As a first draft, yes. Have a speaker of the language review before use, especially for tone.

How often should I review the library?

At least every few months, and straight after any change in policy, hours or services.

Build a template library for your inbox in Call

In the demo console you can try incoming calls in a simulation.

Related guides