Client work stalls less from disagreement than from messages that go missing: an email lands in spam, a reply goes to the wrong app, nobody confirms who acts next. The fix is a short set of rules agreed at the start of a relationship. Make sure your email is set up so it reliably arrives, keep conversations to as few channels as possible, acknowledge every message that needs action, and schedule calls rather than taking them at random. None of this needs new software. It needs someone to set it up properly and both sides to follow it.

Why do more communication tools make client work harder?

I work with directors, specialists and founders who are excellent at their jobs and still lose track of client conversations. The reason is rarely effort. It is that every tool arrived by default. A professional in Japan might have Slack for the internal team, Teams for a corporate client, WhatsApp for an overseas partner, LINE for local contacts, Chatwork for a supplier and email for everyone else. Each is reasonable on its own. Together they scatter the context of a single project across six places.

The practical consequences are familiar. A client sends an updated brief on LINE while the project thread lives in email. A decision is agreed on a call and never written down. A document goes to the wrong version because two people were working from different attachments.

For internal teams, I cover choosing between tools in LINE, Chatwork, Slack and Teams in Japan. Client relationships add a complication: you cannot dictate the other side’s tools, so the rules have to be simple enough to agree in one conversation.

Is your business email actually reaching clients?

Email remains the backbone of client communication in Japan, especially for anything formal, contractual or involving an invoice. It is also the channel people most often assume just works.

Set up SPF, DKIM and DMARC

These three DNS records tell receiving mail servers that a message really came from your domain.

SPF lists the servers allowed to send mail for your domain, such as Google Workspace, Microsoft 365, your newsletter tool and your invoicing system.

DKIM adds a cryptographic signature to each message so the receiver can check it was not altered.

DMARC tells receivers what to do when a message fails those checks, and sends you reports on who is sending mail using your domain.

Since 2024, Google and Yahoo have required authentication from bulk senders, and unauthenticated mail from small businesses is increasingly filtered too. A company that has never set these up may find quotes, invoices and replies landing in spam without anyone noticing. It also leaves the domain easier to spoof in phishing emails aimed at your clients.

Setting them up takes access to your DNS (at your domain registrar or DNS host) and to each service that sends mail for you. The common trap in Japanese SMEs is that nobody knows who controls the domain: it was registered years ago by a web agency or a former employee. The Google Workspace adoption guide covers domain ownership and mail setup, and it is one of the first things I check in a Diagnostics review.

Use a company domain, not a free address

Sending client work from a personal Gmail, Yahoo or carrier address looks less trustworthy and leaves the business without the records when people leave. Every person dealing with clients should use an address on the company domain, managed by the company.

How should you handle chat apps with clients?

Keep client chat to one channel per client where you can, and agree it at the start. If a Japanese client works in Chatwork or LINE WORKS, joining their room may be the easiest route. If a corporate client uses Teams, accept the guest invitation. What matters is that everyone knows which channel is the record for that project.

For my own client work I keep things to two channels wherever I can: properly authenticated email for anything that needs a record, and Signal for quick messages, because it is end-to-end encrypted by default and does not mix work into a social feed. Not every client can work that way, and some Japanese businesses run almost entirely on LINE. The principle still holds: fewer channels, agreed in advance, with the formal record in one place.

A few rules help whatever the tools are.

Move decisions out of chat. When something is agreed in chat or on a call, send a short email or update the shared task list so there is one record.

Keep files in a shared folder. Link to a document in Google Drive or SharePoint rather than attaching copies, so everyone works from the current version.

Do not use personal accounts for client data. Personal LINE and WhatsApp are convenient, but the company cannot archive them or recover them when staff leave.

Why acknowledging messages matters

A lot of communication breakdown is silence. Someone sends a draft for review and hears nothing, so they cannot tell whether it was seen, is being read or was lost. Several people end up waiting without knowing who should act.

Agree that any message needing action gets an acknowledgement within one working day, even if the full reply takes longer. “Received, I will come back by Thursday” is enough. In Japanese business email, a short 確認しました or 承知しました serves the same purpose and is expected in many companies anyway. Combine that with a clear owner for each open item and small gaps stop turning into delays.

Should you answer calls from unknown numbers?

I do not pick up calls from numbers I do not recognize, and I rarely take unscheduled calls at all. An unexpected call interrupts whatever work is in progress and usually leaves no written record. Scam and sales calls to Japanese mobile numbers have also become common enough that many people now screen them by default.

That is not the same as being unreachable. Clients can email or message and get a reply, and when a conversation is better by voice or video, we book it. A scheduled call has an agenda, the right people attend, and someone writes up what was decided. If you want to reduce the back and forth of arranging those calls, a booking page helps; I compare the options in Calendly, TimeRex and Google Calendar booking pages.

For genuinely urgent issues, agree a phone route in advance, so a call signals urgency rather than habit.

How do you set communication rules with a new client?

Cover it in the first meeting or the engagement letter. A short list is enough:

Formal channel: email, between named addresses on each side.
Quick questions: one agreed chat channel.
Files: one shared folder, with links rather than attachments.
Response times: acknowledgement within one working day; urgent issues by phone.
Calls: booked in advance with an agenda, followed by a written summary.

Write it down and share it with everyone who joins the project later.

These rules sound basic, and they are. The value is in actually setting up the email records, choosing the channels and sticking to them. If your company’s email setup, domain ownership or client channels need sorting out, I can do the setup with your team, or provide continuing support through Ongoing Stewardship.

Further reading: scheduling emails across time zones · choosing between LINE, Chatwork, Slack and Teams