Omnichannel Support: Phone, LINE, Email and Chat Together
How to run customer support across phone, messaging apps and email so customers never repeat themselves: one history, clear ownership, and consistent answers.
A customer asks a question on a messaging app, gets no reply in an hour, calls, and is asked to explain everything again. Then an email arrives from a third person with a different answer. Each channel worked as designed. The experience failed because the channels did not talk to each other.

Omnichannel support is the fix: not more channels, but connected ones. This guide covers what it means, how to build the foundations, how to decide which channels to offer and how to run them day to day, with a focus on phone, LINE and email, a combination common for businesses in Japan. It builds on Customer Support on LINE Official Accounts and Unified Inbox for Support.
Multichannel versus omnichannel
The difference in practice
| Multichannel | Omnichannel | |
|---|---|---|
| Channels | Several, each run on its own | Several, sharing one view of the customer |
| History | Separate per channel | One timeline across channels |
| Customer experience | Repeat yourself when you switch | Carry on where you left off |
| Answers | May differ between channels | Drawn from the same facts |
| Ownership | Each channel owns its messages | A case has one owner, whatever the channel |
Most small teams are multichannel by accident: a phone, a shared mailbox and a messaging account that different people check. Becoming omnichannel is mostly a matter of organisation, and tools help rather than replace the thinking.
The foundations
Four things you need
- One customer recordPhone number, email and messaging identity tied to the same person where possible.
- One timelineCalls, messages and notes in one list, newest first.
- One owner per caseA named person who is responsible until it is resolved.
- One source of factsHours, policies and prices kept in a single place that every channel uses.
Matching people across channels
The hardest practical problem is knowing that the person emailing is the same one who called. Phone numbers and email addresses are the usual links. Ask customers to give both once, and store them on the same record. Do not guess identity from similar names, and be careful with personal information: collect only what you need and tell people how you will use it.
Shared rules on timing
Agree response targets for each channel and publish them: for example, calls answered or called back the same day, messages replied to within a set number of hours, email within one working day. Customers forgive slower channels when they know what to expect.
Choosing the channels
More channels means more places for a message to be lost. Offer the ones your customers actually use and you can staff.
| Channel | Good for | Watch out for |
|---|---|---|
| Phone | Urgent, emotional or complex matters | Missed calls, peak queues |
| Messaging (such as LINE) | Quick questions, photos, bookings | Messages sitting unread, informal expectations |
| Detail, attachments, formal records | Slow replies, long threads | |
| Web chat | Questions while browsing | Needs staff or an agent online |
For businesses in Japan, a sensible starting set is phone, LINE and email. Elsewhere, replace LINE with whichever messaging app your customers prefer, such as WhatsApp.
Moving a customer between channels
Switching without friction
- Read the historyBefore replying, check what has already been said on any channel.
- Say you have it"I can see your message from this morning."
- Choose the right channelMove to a call for complex or emotional matters; move to chat for photos and links.
- Record the outcomeAdd a note so the next person sees what happened.
- Close the loopConfirm in writing what was agreed.
This is where templates help. Writing Reply Templates for Customer Messages shows how to keep tone and facts consistent across staff and channels.
Running it day to day
- Triage in one place. Staff see all new items in a single list, sorted by urgency or age.
- Assign promptly. Unassigned items are the ones that get missed.
- Keep notes short and factual. What was asked, what was done, what is next.
- Use summaries. Short call summaries make a phone conversation visible to colleagues who handle later messages.
- Review the oldest. Start each shift by looking at the longest waiting items.
Daily omnichannel routine
- Check overdue callbacks and unanswered messages first
- Assign every new item to a named person
- Update notes after each contact
- Close items only when the customer's issue is solved
- Flag recurring questions for templates or website changes
A worked example
Consider a hypothetical dental clinic that takes calls, LINE messages and email. A patient messages on LINE asking to move an appointment, and the reply asks for two possible dates. The patient then rings the next morning because they are not sure the message arrived. If the receptionist can see the LINE thread, they can say, "I see your message about moving your appointment; here are the options." If not, the patient must explain again and may lose patience.
| Without shared history | With shared history |
|---|---|
| Patient repeats the request on the phone | Receptionist opens the thread and continues |
| Two staff may offer different slots | The case has one owner and one set of notes |
| Nobody knows the message was already answered | Status shows resolved or pending |
| Email, chat and phone say different things | All use the same facts |
The clinic does not need a large system to achieve this. It needs a rule that every contact is logged in one place, a named owner for each request, and a habit of checking history before replying. Technology makes the habit easier, but the habit comes first. Teams that skip the habit and buy a tool usually end up with a more expensive multichannel setup.
Measuring whether it works
Channel-by-channel numbers still matter, but the omnichannel question is whether the whole journey improved.
- Customers who had to contact you more than once for the same issue.
- Time from first contact to resolution, across channels.
- Items with no owner or no reply past the target.
- Customer comments about repeating themselves.
Related measures are in First Call Resolution and Repeat Call Rate.
Start by connecting just two channels, usually phone and your main messaging app, and run them together for a month. The lessons from that small step, about ownership, notes and timing, will shape how you add anything else, and they cost far less than discovering the same problems across five channels at once.
Doing it in Call
Call puts phone and messages in one place. The inbox lists every message and phone inquiry in one view, with filters for open, pending and resolved items, a channel filter, an option to see only your own items and a search by name, number or words. A conversation opens as a thread with the customer's messages and your replies, and can be resolved or reopened. Phone calls appear in call history with a summary and transcript, and callbacks, voicemail and tickets for callers who asked for a person sit alongside. LINE and WhatsApp are channels the platform operator can connect with the credentials of accounts you already have, and a channel that cannot send is flagged so replies are not silently lost. Call does not send SMS unless an operator enables it. See Call Shared Inbox and Call CRM Contacts.
Frequently asked questions
What is omnichannel support?
Support in which several channels share one customer history, so the customer can switch channel without starting again.
Do I need every channel?
No. Offer the channels your customers use and your team can answer well. Two or three connected channels beat many separate ones.
How do I know a caller and an emailer are the same person?
Link them by phone number and email stored on one customer record, collected with the customer's knowledge. Avoid guessing from names.
What response times should I set?
Choose realistic targets for each channel and tell customers. Calls and messages usually warrant faster replies than email.
Is omnichannel the same as using one tool?
A single tool helps, but the real change is shared history, clear ownership and consistent facts.
How do I start?
Pick one place to see all new customer contacts, agree owners and response times, and keep one source for hours and policies.