In Taiwan and across Southeast Asia, LINE is where customers live.
They ask questions, confirm orders, receive notifications, and even pay — all inside LINE. But most business websites and LINE Official Accounts (LINE OA) have no connection to each other. Customers have to manually switch between two systems, and each switch is a drop-off point.
There are three main architectural approaches to integrating LINE OA with your website. They differ significantly in engineering complexity and in what they're actually suited for.
Pattern 1 — Webhook Push Notifications
Complexity: Low / Best for: one-way alerts
The simplest integration: something happens on your website (order placed, appointment confirmed, form submitted), and LINE OA automatically sends the customer a message.
Technically: your backend calls the LINE Messaging API with the customer's LINE User ID. The prerequisite is that the customer has previously added your OA as a friend — that's the only way to obtain their User ID.
Good for:
- E-commerce order confirmations and shipping updates
- Appointment reminders (automated 24 hours before)
- Form submission acknowledgements
Limitation: This is one-directional. Customers receive the message but can't take action inside LINE (like rescheduling). If you need two-way interaction, pair this with a Rich Menu linking back to your site, or move to Pattern 2.
Common mistake: LINE User ID is not the same as LINE ID (the @username handle). User ID is a unique identifier generated when someone adds your OA — you can't guess it, and you can't retrieve it without having built an add-friend flow that captures it properly.
Pattern 2 — LIFF Embedded Flows
Complexity: Medium / Best for: bringing website functionality into LINE
LIFF (LINE Front-end Framework) embeds a web page directly inside LINE. When a customer taps a menu item or link, instead of jumping to an external browser, a web view opens within LINE itself.
This lets you:
- Complete a booking or reservation without ever leaving LINE
- Automatically capture the customer's LINE User ID and display name at form completion
- Return seamlessly to the LINE interface when done
Good for:
- Service bookings (clinics, salons, restaurants)
- Event registration and surveys
- Any flow requiring identity verification (member login)
Engineering reality: LIFF pages are essentially web pages, but with notable constraints. Safari's cookie restrictions are more aggressive inside LIFF — if your site uses session-based authentication, it will likely break on iOS. LIFF window height is also fixed, making complex multi-step interfaces feel cramped.
Building a complete LIFF booking flow with backend management typically takes 4–8 weeks from scratch.
Pattern 3 — Full CRM Integration
Complexity: High / Best for: automating the entire customer journey
The most complete approach: LINE OA, your website, and your internal systems (CRM, ERP, or even Google Sheets) all connected.
Customer sends a message in LINE → webhook triggers your server → intent is identified (inventory inquiry vs. order change) → your backend API is called → response delivered back to the customer, fully automated.
This architecture enables:
- Customers querying order status or loyalty points directly in LINE
- Automatic differentiation between new and returning customers
- Business events triggering LINE notifications (overdue payment, low stock)
- Conversation records written automatically into your CRM
Good for: Businesses with high customer volume, high-repetition interactions, and a genuine need for operations automation.
Engineering reality: This isn't a plugin you install. It requires backend development, API design, and willingness to expose your internal system's data to read/write operations from an external service. Integration scope ranges from 2 months to 6 months depending on system complexity. Pairing this with an LLM (like Claude) for intent recognition significantly improves automated response quality — but it's also one more layer to maintain.
Choosing the Right Pattern
You don't need the most complex approach:
| What you need | Best fit |
|---|---|
| Customers receive notifications | Webhook push |
| Booking / forms inside LINE | LIFF embedded flow |
| Full customer service automation | CRM integration |
For most SMBs, Webhook + LIFF is the right starting point. Push notifications handle the "inform the customer" use cases; LIFF moves your highest-frequency flows (bookings, registrations) into LINE. Full CRM integration is worth considering when manual handling genuinely can't keep up with volume.
Start with the simpler pattern. Get it running. Decide on the next step based on actual usage — rather than building a sprawling system upfront that stalls halfway through implementation.