AI Chat Summary
LINE conversations become a clean ledger of what was actually agreed.
A LINE OA is where most Thai sales conversations actually happen. AI Chat Summary captures that traffic, scopes it to the right customer, and gives your team a daily ledger of agreements and open questions.
If a sales conversation happens in chat and nobody summarises it, did the deal really move?
Why scope matters
The AI side-panel is scope-aware: at /crm/customers/[id] it answers about
that customer; at /inventory it answers about stock. It does not pull
context from sibling pages or other modules unless explicitly granted —
the scope tag is set on the conversation and is immutable after the first
turn.
Auditable by design
Raw webhook events are persisted. Approval state is logged. The activation
code carries through active / claimed / approved without resets, so an
auditor can reconstruct who connected what, when.
LINE OA ingestion
One reusable activation code works across many LINE groups. Signed webhooks; raw events persisted; auditable end-to-end.
Per-group, per-customer summaries
Each group's daily summary lands on the linked customer record. Sales teams see what was promised without scrolling chat history.
Approvals + room mapping
Pending groups surface in an Approvals page with refreshed names from LINE. Once approved, every summary is tagged to the right customer.
Scope-aware AI side-panel
Page / Module / Global scope. Ask the panel a question on /crm/customers and it knows it's a CRM question, not an Inventory one.
CRM
Customers as a first-class object, not a row in a spreadsheet.
See the moduleVoice Summary
Record once. Search the spoken word forever.
See the moduleProjects
The work, the people, and the conversations — on one timeline.
See the moduleWhat about WhatsApp and Facebook?
Connectors page already lists Facebook and WhatsApp as upcoming. LINE is the production target for the Thai SME segment.
Can the AI panel write back into the data?
Yes, through tool-use endpoints — but only within the user's tenant, role permissions, and active scope. RBAC is checked on every tool call.
Is there a way to keep an old summary out of the AI?
Yes. Summaries can be archived; the AI's retrieval layer respects the same archived/deleted flags as the UI.