By the Onsites AI team · Last updated · 5-minute read
LINE is not an app market in Japan, Taiwan or Thailand — it is the operating layer of daily life, including buying. Shoppers there follow a store's LINE Official Account the way other markets follow an Instagram, then do something Instagram cannot do: message the store directly and expect a reply. For a small shop this makes LINE the most personal marketing channel available — and the most dangerous to run from one person's phone. This guide covers the setup that scales, the split between conversation and broadcast, and how a free desk makes both sustainable.
The prerequisite is an official account, which takes an application through LINE's platform and your business verification; the LINE shared-inbox guide covers the application and the linking steps in detail. Once linked in Settings → Channels, every 1:1 message from every follower lands in the same shared queue as your email and website widget conversations — assigned like any ticket, timed by the same SLA, searchable alongside everything else. The difference between this and the native LINE app on one teammate's phone is the difference between support as a habit and support as a heroic act: shifts exist because the queue catches what phones miss. It is the same architecture as the WhatsApp playbook, tuned for a market where chat-app commerce is even more normal.
LINE Official Accounts let you message at followers in bulk — broadcasts — and that power is governed by strict monthly message limits on LINE's own plans, plus an unfollow reflex that punishes noise instantly. The discipline that keeps a store safe is a bright line: 1:1 conversation belongs in the shared queue; broadcasts are scheduled, capped and planned like emails. Never repurpose a support thread into marketing ("while you're here, here's our promo") inside the same chat without the customer asking; answer the question, then let the relationship invite the broadcast. The shop that answers stock questions in three minutes and broadcasts twice a month keeps its subscribers; the one that auto-spams "thank you + catalog" attachments trains people to block.
Concretely for a small shop: one planned broadcast per campaign — launch, seasonal sale, or restock of a famously limited item — written with the same care as your best email, and a queue standing by for the replies it generates. Because every reply lands in the desk with the customer's history attached, a broadcast's afterwave becomes the week's most productive support hours, not a flood of repeated copy-paste.
Followers tolerate information; they unsubscribe from frequency. A rhythm that survives contact with real audiences: one broadcast per two weeks maximum for a young account, rising to weekly only when opens and replies prove appetite; content that is useful before it is promotional (arrival dates for a known item, a restock notice the queue literally watched people ask for); a single clear action per message; and honest send times — evening local time, when LINE is actually read. Track per-broadcast: delivery, opens, replies-in-queue. The replies are the underrated metric: a broadcast that starts ten 1:1 conversations about one product is doing better field research than any dashboard.
Keep the broadcast calendar in the same plan as support seasonality: the five KPIs a small team tracks will show you the week after a broadcast — the queue's volume spike, the topics it created, the replies per conversation. That loop converts LINE from "a marketing app somewhere" into part of the desk's operating picture.
LINE commerce rarely starts with a cart; it starts with a question. A follower taps through a broadcast, opens 1:1, and asks "does this come in size L?" — that moment is the entire funnel, and its speed decides the sale. The desk-side pattern: stock and sizing questions deserve canned answers with live information (a one-line inventory check beats a link to a size chart), and anything not in stock becomes a restock-notification note attached to the CRM contact rather than a dead end. When the fan turns out to be a buyer — a corporate gift order, a wholesale inquiry — the same thread graduates into quotes and invoices without changing rooms, which is the chat-to-quote flow wearing a LINE jersey. The measure of the funnel is not followers; it is conversations that convert, and the desk counts them by the tag you set on the thread.
LINE shows every follower a store's response rate — and followers check it before writing. An account that answers in an hour all afternoon and goes silent at midnight trains exactly the wrong expectations. Set the desk's working hours honestly and let the auto-greeting carry the off-hours load ("the shop is closed now — we reply from 10:00"), because a polite immediate acknowledgement preserves the badge psychology even when the answer waits for morning. Never chase a 100% always-on score with midnight shifts; chase a stated, kept promise instead — the same one-number discipline the response-time benchmarks recommend everywhere else.
Beyond the obvious multi-person answering, the desk adds four things the native app structure fights. Language: translation at 3 credits per message keeps cross-border followers — tourists, international fans — inside one conversation instead of being shrugged to Google Translate. Auto-answers: the greeting message and the response rate LINE displays are team artifacts, not individual ones; the routing rules keep every reply owned within minutes even at midnight. History and compliance: what was promised to which follower is in the thread, exportable through the export ritual, not lost when a staff member changes jobs. Continuity: the LINE conversation attaches to the CRM record alongside email and widget threads, so "the customer who asked about this in March" is a lookup, not a legend told by whoever remembers.
And when the shop grows past social channels into a full store experience — order tracking, quotes for B2B fans, invoices for wholesale buyers — the same workspace they already chat through already carries those tools; that is the quiet argument for starting free rather than starting over.
Do we need a LINE Official Account to run LINE support?
Yes — the Official Account is the searchable, followable business presence buyers message; personal accounts cannot serve as a support channel. Link the account to a shared desk so every 1:1 message lands in one team queue with SLAs and assignment.
How often should a small shop broadcast on LINE?
Start with one planned broadcast per two weeks, rising to weekly only when opens and replies prove appetite. Broadcasts should be useful before promotional — restock notices, launch dates, member offers — with one clear action per message.
What is the biggest LINE-specific mistake small stores make?
Mixing broadcast spam into support: auto-replies stuffed with catalogs, marketing pushed into complaint threads, daily promotional blasts. LINE punishes noise with unfollows; keep 1:1 conversation fast and human in the queue and keep broadcasts scheduled and capped.
How do we keep LINE service running across shifts and staff changes?
Link the account to a shared inbox, set routing so every message is owned within minutes, and use auto-replies for off-hours acknowledgement. History then lives in the desk — exportable, searchable — instead of on one employee's phone.
Can we handle international followers who write in other languages?
Yes: the desk's Copilot translates replies for 3 prepaid credits per message, so cross-border followers get answers in their language and the conversation stays in one shared thread with full history.