How to Follow Up When a Japanese Business Contact Has Not Replied
More polite language does not automatically make a follow-up message in Japanese more effective. The recipient still needs to know what you need, why it matters, and when you need a response. This guide is for reminders to an existing customer, business partner, contractor, or colleague. Here, “first reminder” means your first follow-up in an existing business relationship—not a follow-up to a cold sales message. Start with the actual deadline, the action required, the operational reason, and what has happened since your previous message. Email and established work chat may require different levels of context. This guide does not cover legal notices, disputed liability, contract enforcement, or unapproved escalation to private contacts or senior leaders.
Plain-language answer
Do not let extra politeness obscure a real deadline. State the action you need, the operational reason, and the actual date or time. Use a softer ending when the timing is flexible, and a clearer request when the deadline is fixed.
This is a decision guide, not a message that fits every recipient unchanged.Why context matters
An existing customer, partner, contractor, or colleague does not need the same introduction as a stranger receiving a sales message.
A first reminder should leave room for oversight or workload; later reminders can state earlier dates and promises as neutral facts.
An email can include the matter, requested action, reason, deadline, and fallback. An established work chat message is usually shorter and places the requested action earlier.
The recipient's prior writing style and the team's normal practice are more useful than assumptions based on nationality, age, or company type.
This guide does not cover: Cold-sales follow-up, legal notices, disputed responsibility, and unapproved escalation to private contacts or senior leaders are outside this guide.
What to check first
- 01
Confirm that an existing business connection already exists.
- 02
Identify the one action needed: receipt, approval, an answer, materials, or a realistic response date.
- 03
Separate a fixed date and time, a date only, an approximate period, and no deadline.
- 04
State the real operational reason for the timing when it can be shared.
- 05
Check whether this is the first reminder, a missed promised date, or a later reminder.
- 06
If a time is specified across countries, name the timezone.
- 07
Check the recipient's established email or chat style before adding ceremonial language.
Decision framework
Use the observable conditions below to choose a direction. They are not a yes-or-no diagnosis of the other person.
No real deadline
Approach: Ask for a response estimate without manufacturing urgency.
Why: A false deadline or urgency word creates pressure without helping the recipient plan.
A date matters, but the request remains flexible
Approach: Give the reason and date, then use a softer ending such as ご確認いただけますと幸いです.
Why: The date stays visible while the ending leaves some room.
A fixed deadline is operationally necessary
Approach: Give the reason, exact date and any timezone, then use ご返信をお願いいたします or ご確認をお願いいたします.
Why: A mandatory deadline should not look optional.
A promised date was missed or reminders have repeated
Approach: State the earlier date as a fact and ask for either the answer or a realistic response estimate.
Why: Facts are clearer and less accusatory than emotional phrases such as 何度も.
A channel change or escalation is being considered
Approach: Use only an established business channel and obtain human approval before contacting private accounts or senior people.
Why: More channels can increase relationship and excessive-contact risk without producing better evidence.
Example messages
Copy the language only after checking that its stated conditions match the real situation.
Reason plus date
- Use when
- A real date matters, but no exact time is required.
- Channel
- Business email or an established email thread
- Strength
- Polite and specific
お忙しいところ恐れ入りますが、次の工程に進むため、〇月〇日（〇）までに〇〇をご確認いただけますと幸いです。Meaning and impression: Use a conventional softener, explain the next operational step, and request confirmation by a stated date.
Why this wording: The concrete reason makes the deadline easier to understand than a generic claim of urgency.
Avoid when: Do not use this softer ending if an exact time is mandatory or if there is no actual date.
Required date and time
- Use when
- The response is needed by a fixed time for a real operational reason.
- Channel
- Business email; shorten carefully for established work chat
- Strength
- Clear and firm
恐れ入りますが、〇〇の手配のため、〇月〇日（〇）日本時間〇時までにご返信をお願いいたします。Meaning and impression: Request a reply by a specific deadline in Japan Standard Time (JST) because a concrete arrangement depends on it.
Why this wording: お願いいたします makes the required action clearer than 幸いです while the reason prevents an unexplained demand.
Avoid when: Do not invent a time, omit the timezone in international work, or use it only because your internal team is impatient.
Ask only for the response estimate
- Use when
- A full answer may be difficult, or there is no fixed deadline.
- Channel
- Email or established work chat
- Strength
- Lower burden
先日お送りした〇〇について、確認のためご連絡いたしました。ご回答の見込み時期だけでもお知らせいただけますと幸いです。Meaning and impression: Follow up on the earlier item and ask for the expected timing of a response rather than requiring a full answer immediately.
Why this wording: A realistic response estimate can unblock planning without overstating urgency.
Avoid when: Do not use it when the exact answer is already contractually due or when consequences and responsibility require human review.
Short follow-up in established work chat
- Use when
- The recipient is a colleague or regular business contact, and the team already uses the chat channel for operational requests.
- Channel
- Established work chat
- Strength
- Concise and clear
〇〇の件、次の工程に進むため、〇月〇日（〇）までにご確認をお願いします。難しい場合は、確認できそうな時期だけでもお知らせください。Meaning and impression: Briefly state the item, operational reason, date, and fallback without adding an email-style introduction.
Why this wording: Established work chat usually benefits from placing the action and date earlier.
Avoid when: Do not use this as a first contact, in a channel that has not been approved for business communication, or for an important external relationship whose established style is more formal.
Expressions to avoid—or use carefully
お手すきの際に
Why it can be a problem: It can make the request look optional.
Problem conditions: It is too weak when a real deadline exists, the next step is blocked, a promised date has passed, or receipt is urgently needed.
When it may work: It can work when there is genuinely no deadline and the task is low priority or optional.
Safer alternative: Name the action and date: 〇月〇日までにご確認いただけますと幸いです。
至急／早急に
Why it can be a problem: It creates pressure without explaining what must happen or why.
Problem conditions: It is usually too strong for a first reminder, an undefined deadline, or urgency caused only by the sender's internal delay.
When it may work: It may be appropriate for safety, a major outage, or a formal same-day deadline when the reason and action are stated.
Safer alternative: State the operational reason, action, and actual deadline instead of using the urgency word alone.
ご確認いただけますと幸いです
Why it can be a problem: Several softeners in one sentence can hide a mandatory deadline.
Problem conditions: It becomes too weak when an exact response is required or repeated reminders have not produced action.
When it may work: It remains natural as one polite ending for a flexible request.
Safer alternative: For a necessary fixed deadline, use ご確認をお願いいたします after giving the reason.
何度もご連絡しておりますが
Why it can be a problem: It can foreground the recipient's failure to reply and make the message sound accusatory.
Problem conditions: It is risky when the purpose is only to express frustration or when the earlier contact history does not need to be restated.
When it may work: If the contact history is operationally important, refer to the actual dates or promised response instead of emphasizing the number of reminders.
Safer alternative: 〇月〇日にもご連絡した〇〇について、状況確認のため改めてご連絡いたしました。
Cultural context without stereotypes
Some formal emails to external business contacts use more framing, while some international or chat-based teams communicate more directly.
A short message is not automatically rude, and a long indirect message is not automatically considerate.
Do not try to make the message “more Japanese” in the abstract. Match the established thread, the recipient's earlier wording, and the team's normal way of working.
A phrase such as 進行の都合上 is not always wrong, but a specific process such as 次の工程に進むため is easier to act on when accurate.
When human review is recommended
Ask for review of the uncertain decision or high-risk clause—not necessarily a complete rewrite of every sentence.
- The message escalates to a manager, executive, or another department.Ask a reviewer to inspect the contact history, authority, escalation route, and the paragraph explaining the next step.
- A private phone number, personal social account, or several channels would be used.Confirm that the channel is authorized and that a single, limited follow-up is proportionate.
- The message mentions termination, payment hold, order suspension, public disclosure, fault, liability, or loss.Have a responsible person verify the factual basis, authority, consequence language, and whether legal review is needed.
- A major customer or strategically important relationship could be damaged.Review the full history and next action, not only the Japanese sentence.
Check the context before drafting
Identify which relationship, channel, timing, and next-step questions affect your situation. The current check does not analyze or rewrite the text of your message.