Channel-secret verified
Every inbound webhook is verified with the LINE channel secret HMAC. Tampered or replayed payloads are dropped at the edge before they reach Sonar.
Channel · LINE
LINE Official Account with AI-first handoff
OrcaLinq runs LINE OA as a first-class channel: AI answers fast, humans join when it matters, and quota usage is visible before you hit a paid threshold.
Why this channel
LINE is the channel for Japan, Taiwan, Thailand, and Indonesia
For teams operating in these markets, LINE Official Account is the primary inbound channel — often more important than email, web chat, or even WhatsApp. OrcaLinq treats it with the same routing, knowledge, handoff, and audit posture as every other channel.
AI-first answering
Routine questions answer in seconds with cited knowledge. Confidence threshold protects against guessing on tenant-specific facts.
Human handoff
Conversations route to the right human on their preferred endpoint. Agents on Telegram, the PWA, or LINE Works can all reply through the same Pod.
Quota-aware
Monthly message quotas tracked per channel. Matriarch policy can avoid exceeding paid thresholds without explicit permission.
Setup
Steps from LINE OA to live messaging
- 1. Create a LINE Official Account and Provider. In the LINE Developers Console.
- 2. Capture the channel access token and channel secret. Long-lived token preferred for production; rotation supported.
- 3. Add credentials to the dashboard. Stored encrypted, never returned via API.
- 4. Configure the webhook on LINE Developers. Use the platform's verify endpoint to confirm signature handling.
- 5. (Optional) Configure LIFF apps for richer in-LINE flows: intake forms, payment, document signature.
- 6. (Optional) Add a LINE Works endpoint if your agents prefer that to the PWA.
Limitations and tradeoffs
What LINE does well, what it doesn't
Strengths: dominant share in JP/TW/TH/ID — if you operate in those markets, you need LINE; rich Flex messaging for product cards, menus, and structured replies; LIFF for native-feeling in-LINE flows; built-in customer-identity handling via LINE user IDs.
Tradeoffs: monthly message quotas (with overage cost) are a real budget consideration on the higher-volume tiers; outbound outside the 24-hour reply window consumes quota; rich features are JP-first in documentation, sometimes ahead of localized examples; LIFF requires HTTPS-served apps and a non-trivial setup.
Best fit: ecommerce, retail, services, and consumer brands operating in JP/TW/TH/ID where customers expect to reach you on LINE.
Not ideal for: markets with no meaningful LINE adoption (Western Europe, US, India outside niche communities). Use WhatsApp, Telegram, or web chat there instead.
Security and credentials
How tokens, webhooks, and quotas are handled
- Channel access tokens encrypted at rest. Per-tenant key wrap; plaintext never logged or returned via API.
- Webhook signature verified on every inbound. Channel-secret HMAC validation is mandatory before Sonar runs.
- Tenant scoping at the data plane. Tenant-scoped state boundaries ensure no cross-tenant query path exists.
- Media stored in tenant-scoped buckets. Signed URLs with short TTLs; no public file links.
- Quota visible in real time. Podium shows monthly message usage against your plan; configurable alerts.
- Token rotation without downtime. Update the token in the dashboard; old token stops being used the same instant the new one is active.
Example conversation
A typical Japanese-D2C inquiry on LINE
Customer (LINE OA, 21:48 JST): "明日まで届きますか?注文番号 #4521" ("Will it arrive by tomorrow? Order #4521")
AI (live tool call to Shopify): "ご注文 #4521 は本日午後出荷済み、ヤマト運輸で配送中です。明日午前中に到着予定です。トラッキング: …" ("Order #4521 shipped this afternoon, in transit with Yamato. Estimated delivery tomorrow morning. Tracking: …")
Customer: "サイズが合わなかったら交換できますか?"
AI: "はい、未使用品なら7日以内に交換可能です。LIFFフォームでご希望サイズを選択してください→ [LIFF form]"
The customer fills the LIFF exchange form. The platform receives the structured form data, signed and verified, and routes it to the customer-service team's Den as a structured request — not just a free-text message. Wake captures the order number, the tracking lookup, the LIFF interaction, and the resolution.
LINE FAQ
Frequently asked questions
I'm in India — can I sign up for a LINE Official Account?
Not directly. LINE Business does not currently issue Official Accounts to merchants registered in India. To use LINE as a customer channel, the account holder must be registered in a LINE-supported region (Japan, Taiwan, Thailand, or Indonesia) and verify via that region's LINE Business Center. The platform supports LINE end-to-end once the OA exists — the regional gate is on LINE's side, not ours. Teams that want a chat presence for Indian customers usually start with WhatsApp Cloud API, Telegram, or the in-site widget, and add LINE later if/when LINE expands.
Does this work with LINE Official Account or LINE Personal?
LINE Official Account (the business product). Personal LINE accounts cannot be used as customer channels — that's a LINE platform restriction, not ours.
What about LINE Works for agents?
LINE Works (the enterprise variant) is supported as an agent endpoint. Signed, scoped, and auditable like every other agent endpoint. Convenient for teams already standardized on LINE Works internally.
Are rich messages supported?
Yes. Flex messages, quick replies, image and video carousels, sticker handling, and audio messages — all supported, subject to LINE's quota model and your account plan.
What about LINE message quotas?
LINE enforces monthly message quotas based on your plan. The platform tracks usage in near-real-time and surfaces it on the Podium with thresholds; you can configure routing to avoid exceeding paid tiers without explicit permission.
How does LIFF handoff work?
LIFF (LINE Front-end Framework) lets you open a custom URL inside LINE. The platform supports LIFF handoff for flows that need a richer form, a payment step, a document signature, or a structured intake form. The LIFF context (user ID, language, scope) is signed and verified by the platform.
Can I use multiple LINE accounts?
Yes. Each LINE OA is a separate channel binding with its own channel access token and webhook. Useful for splitting brand, region, or product lines without mixing inboxes.
What about push messages and broadcast?
Outbound is supported, subject to LINE's quota and consent rules. Push outside the 24-hour window may consume monthly quota; broadcast goes against the broadcast quota. Both are usage-tracked.
Related pages
Keep exploring
See LINE running on your own channel.
Bring a sandbox LINE Official Account. We'll connect it during the demo and show signature verification, Sonar reading intent, Matriarch routing, and a LIFF handoff end-to-end.