LINE is not a channel most Western CRM vendors take seriously, and that is exactly why it causes so much trouble. In Japan, Taiwan and Thailand it is not one messaging app among several. It is the messaging app, the one where customers expect to reach a business, and a company that cannot answer on LINE in those markets is functionally unreachable.
The gap is not awareness. Most teams know they need a LINE Official Account. The gap is what happens after they have one, when the conversations start arriving and there is nowhere sensible to put them.
This guide covers what a LINE Official Account actually gives you, where the native tools stop, the message economics that catch everyone out, and what to look for if you are trying to run LINE as a proper CRM channel rather than a separate inbox somebody checks twice a day.
What a LINE Official Account is, and what it is not
A LINE Official Account is a business account customers add as a friend. That friending step is the whole foundation of the channel, and it is worth stating plainly because it defines what is and is not possible.
You cannot message a LINE user who has not added you. There is no cold outbound on LINE. No equivalent of a cold email, no buying a list, no scraping. Anyone who tells you otherwise is describing something that breaks LINE's terms, and any tool built on it will eventually take your account with it.
What you can do is answer people who message you, and send messages to people who have already added you as a friend. That constraint is not a weakness. It means the audience you build on LINE is opt-in by construction, which is why LINE conversations tend to convert better than channels where anyone can be reached.
Where the native tools stop
LINE gives you the LINE Official Account Manager, which includes a basic chat view. For a single shop with one person answering, it is genuinely enough.
It stops being enough at the point where any of these become true:
- More than one person answers, and you need to know who said what and who is handling which customer
- A conversation needs to outlive the conversation, so the next person to speak to that customer knows the history
- You want to know which enquiries turned into revenue
- LINE is one of several channels, and the customer who messaged you on LINE last week is the same person who filled in a form today
- You want a reply to happen automatically, at the moment the message lands, rather than whenever someone opens the app
None of those are chat problems. They are contact record problems, and a chat tool does not have contact records. This is the same wall businesses hit with Instagram DMs and WhatsApp, and it is why messaging channels keep ending up inside CRMs rather than staying in their native apps.
The message economics nobody explains upfront
This is the part that surprises people three months in, and it is the single most useful thing to understand before you choose a tool.
LINE has two ways of sending a message, and they cost differently.
Reply messages are free. When a customer messages you, LINE issues a short-lived reply token. Answer using that token and the message costs nothing against your quota, no matter which plan you are on.
Push messages count against your quota. Once the reply token has expired, any message you send is a push message, and push messages are metered by your LINE Official Account plan.
The practical consequence is that answering quickly is not just better service on LINE, it is cheaper. A team that replies inside the window pays nothing for those messages. A team that lets threads sit and then follows up the next day pays for every one of those follow-ups.
Most tools do not expose this at all. When you evaluate a LINE CRM, ask directly whether it stores the reply token against the conversation and uses the reply endpoint before falling back to push. If the answer is vague, assume every message you send is a metered push message, and price accordingly.
What to look for in a LINE CRM
It uses the official Messaging API. LINE integrations built on unofficial clients or session replay get accounts banned. Check that the connection is made with a channel access token and channel secret issued from your own LINE Developers console.
You keep ownership of the Official Account. You should be pasting credentials you issued and can revoke. If disconnecting the tool would cost you the account or the followers, that is not an integration, it is a hostage situation.
Webhooks are signature-verified. Every LINE webhook carries an X-Line-Signature header, and each Official Account has its own channel secret. A tool that accepts webhook events without verifying the signature against the right channel's secret can be fed fake events by anyone who learns the URL.
Each account belongs to exactly one workspace. If you run several brands or several clients, a LINE account that is not scoped to one of them is visible and sendable from all of them. That is how one client ends up messaging another client's followers.
Groups stay separate from private chats. LINE conversations happen in one-to-one chats, groups and rooms. These should become separate threads. Collapsing them means a group enquiry can overwrite a private one.
LINE fires the same automation triggers as your other channels. If your qualification and routing rules have to be rebuilt from scratch for LINE, you will not maintain them, and they will drift out of sync with the rules you actually use.
Running LINE alongside Instagram and WhatsApp
For agencies and multi-market businesses, the real problem is rarely LINE by itself. It is that LINE is the fourth inbox.
A customer in Bangkok messages on LINE, a customer in London messages on Instagram, and a lead from a campaign arrives by form. If those live in three tools, nobody has a view of the pipeline, reporting has to be assembled by hand, and the same person can be worked by two staff members who do not know about each other.
The fix is not a better LINE tool. It is treating LINE as one channel in a system that already handles the others, so that a LINE conversation produces the same contact record, the same pipeline stage and the same reporting row as any other conversation.
That is how Inflowave's LINE integration is built. You connect an Official Account with your own channel secret and access token, inbound messages become conversations in the same shared inbox as Instagram, Facebook and WhatsApp, and every message fires the same message_received workflow trigger the other channels use. Reply tokens are stored against the conversation, so a reply from a person or from the AI agent uses the free reply endpoint before falling back to a metered push.
Frequently asked questions
Do I need a LINE Official Account before I can connect a CRM?
Yes. Create the Official Account in the LINE Official Account Manager, then create a Messaging API channel for it in the LINE Developers console. The CRM connects to that channel.
Can I send a promotional message to everyone who added me?
Yes, to friends of the account, as push messages counting against your quota. You cannot send to anyone who has not added you.
Does LINE work for B2B, or only consumer?
Both, in its home markets. In Japan especially, LINE is used for business communication in a way that has no direct Western equivalent. Treating it as a purely consumer channel is a common and expensive misread.
What happens to media like images and video?
Inbound non-text messages create the conversation and the message record so the thread stays complete. The media itself is retrievable from LINE for a limited retention window, which is why a CRM should fetch it rather than linking to it indefinitely.
Is a LINE chatbot the same as a LINE CRM?
No, and conflating them is the most common mistake here. A chatbot answers. A CRM remembers. You can have a bot that handles first contact beautifully and still have no idea which of those conversations became customers.
