A customer messages your LINE OA on Tuesday asking about a service. A staff member answers, the conversation trails off, and by Friday nobody remembers who was supposed to follow up—because the only record of that conversation lives inside one phone, under one chat thread, owned by whoever happened to be on shift.
LINE had 56 million monthly active users in Thailand in late 2025, equal to 82.6% of the country's internet users, according to DataReportal's Digital 2026 Thailand report. For most Thai businesses, that makes LINE OA the default place customers show up—not a channel you chose, but the one your customers already chose for you.
It sounds like a customer-service problem: staff aren't replying fast enough, or someone dropped the ball. It's actually a record-keeping problem. LINE is built to carry a conversation extremely well. It was never built to tell a manager which of last week's forty conversations still need a next action, who owns each one, or what was promised. This piece walks through what LINE OA is genuinely good at, what breaks when a business treats it as the customer database too, and how to connect the two without losing the speed that makes LINE useful in the first place.
LINE carries the conversation. CRM carries the customer's context and next action. When only one person holds both in their head, the business doesn't have a customer record—it has a habit.
What LINE OA does well
LINE OA gives customers a channel they already trust, on an app they already have open. With the Messaging API enabled, events are delivered to a configured webhook whenever a user adds the account or sends a message, which is what makes automated greetings, quick replies, and rich menus possible. LINE Developers None of that is in question—LINE is genuinely excellent at conversation. The question is what happens to that conversation the moment it needs to become a customer record instead of a chat log.
Conversation Amnesia: why a chat thread forgets the customer every time someone new picks it up
Here's the pattern worth naming: Conversation Amnesia, the moment a customer's history, preferences, and open commitments vanish the instant the conversation changes hands—a new staff member, a shift change, a chat app reinstalled on a new phone. The conversation itself is still there, scrollable and searchable. What's gone is the *context*: why this customer messaged, what was already promised, whose job it is to answer next.
A single staff member with ten regular customers rarely notices Conversation Amnesia—they simply remember. The problem appears exactly at the point where memory stops scaling: a second staff member, a second shift, a second branch. LINE didn't get worse at that moment. The business just outgrew what a chat app was ever designed to remember on its behalf.
CRM adds a place for that memory to live outside any one person's head—connecting a person or company to their source, need, owner, sales stage, quotation, consent purpose, next action, and outcome, so a colleague can pick up a conversation without asking the customer to repeat themselves. If you're not yet sure what a practical setup should actually contain, our plain-language guide to CRM for Thai SMEs walks through it field by field.
Connect them with a clear identity rule
A LINE user ID is not automatically the same thing as a verified customer record. Ask for an appropriate identifier at a useful moment in the conversation, obtain the necessary permission, and avoid merging records based only on a similar display name—"Nong Ploy" is not a unique identifier in a country with several million of them.
LINE documents that profile information depends on user consent and may be unavailable in some webhook events, which means a business cannot assume it always has a name or picture to match against. LINE user consent
Build a handoff that survives a shift change
- Capture the new LINE conversation the moment it starts.
- Ask one or two qualification questions early, not five.
- Create or match the customer record carefully, using a verified identifier where possible.
- Assign an owner and a next action—not "someone will get to it."
- Store a useful summary of the conversation, not the full sticker-and-greeting transcript.
- Continue the relationship in LINE while the sales outcome updates in CRM.
Picture a hypothetical aesthetic clinic called Rin Clinic, running three branches in Bangkok and taking nearly all of its new enquiries through one shared LINE OA. Before it separated conversation from customer record, three front-desk staff were covering the same LINE account in rotating shifts, and a customer asking about a follow-up treatment had roughly even odds of reaching someone who had no idea a consultation had already happened. The fix wasn't a bigger team or a stricter shift schedule—it was making sure every new LINE conversation created one customer record that all three staff could see, regardless of who was on shift when the customer first wrote in.
The same handoff has to work whether a lead arrives by LINE, a website form, or a Facebook message—see how to capture leads from every channel in one place so LINE isn't the only door with a memory.
Avoid three common mistakes
Do not share one staff login across a whole team, blast promotional messages without clear permission, or assume that conversation volume equals sales progress—a busy LINE inbox can just as easily mean forty unanswered questions as forty happy customers. ETDA's CRM guidance for SMEs explicitly connects customer data handling with automated communication channels while reminding businesses to prepare for PDPA obligations as they do it. ETDA
Measure the connected journey, not the chat
Track LINE conversation to identified lead, identified lead to qualified opportunity, first-response time, repeated information requests, overdue follow-ups, and outcome. A rising follower count is useful marketing context, but it says nothing about whether this week's actual sales work got done.
Start with one LINE OA, one team, and a limited set of events. Reconcile customer matching weekly so mismatched records get caught early, not six months later. Expand to other channels only once staff can explain, in one sentence, where a customer's record lives and what happens when the LINE-to-CRM connection fails for a day.
The Conversation Amnesia Playbook
- Identity Before Merge—confirm a verified identifier before joining a LINE conversation to an existing customer record, never just a matching display name.
- One Owner, Always—every open conversation has exactly one named owner at any given time, visible to the whole team, not just to whoever answered first.
- Summary Over Transcript—store what a colleague needs to continue the relationship, not a copy of every message, sticker, and "ค่ะ/ครับ" exchanged.
- Weekly Reconciliation—once a week, check for LINE conversations with no matching customer record and close the gap before it becomes a pattern.
A dental clinic booking appointments mostly through phone calls faces the identical version of Conversation Amnesia every time a receptionist goes on leave and the next one has no record of who was mid-treatment plan—the mechanism is the same even though the channel is a phone line instead of a chat app.
Continuity: what this all comes down to
If there's one word for what actually separates a LINE inbox from a customer relationship, it's Continuity—not a bigger team, not a stricter reply-time rule, just a record that survives the moment one person stops being the only one who remembers.
So here's the question worth sitting with: if the staff member who normally answers your busiest LINE OA didn't come in tomorrow, would the next customer message still get a reply that shows the business remembers them—or would it start again from zero? If you're not certain, that uncertainty is exactly where Conversation Amnesia is already living in your business.
FAQ
Does every business that uses LINE OA need a separate CRM?
Not immediately. A single staff member handling a small, steady volume of conversations can often hold the context personally. The need becomes real the moment a second person, shift, or branch touches the same LINE account.
Can LINE OA data be connected to a CRM automatically?
Yes, within limits set by the platform and by user consent—LINE's Messaging API can deliver message events to a connected system, but profile details depend on what the user has agreed to share, so identity still needs a deliberate matching rule rather than an assumption.
Is a shared LINE login an acceptable substitute for a CRM?
No. A shared login means anyone can see the messages, but nobody specifically owns the follow-up, and there's no way to show a manager which conversations still need action without reading every thread manually.
What's the first thing to fix if LINE is our only system today?
Start by defining one customer record per contact and one visible owner per open conversation—before adding automation, connectors, or a second channel. Ownership visibility solves more of the problem than any integration does on its own.
Request a LINE-to-CRM workflow consultation to define identity, handoff, and follow-up before integration begins.