Features · Customers & CRM
Collaboration on the record — not in a chat that forgets
The customer's story shouldn't live in a group chat that scrolls away. In Flows, follow-ups happen on the customer or contract itself: log the call, @ the colleague who acts next, control who sees what — and the message center gathers what needs you.
01
Follow-up threads where the work is
Every customer and contract carries its own follow-up thread. Log the visit, the call, the promise — and the next person reads the whole story on the record, not a retelling. Handovers stop being an hour of oral history.
- Threads on customers & contracts
- Calls, visits, promises logged
- The record tells the story
- Handovers read, not retold
Customer — Bangkok Trading
@Somchai customer visit set for Thursday
Visible to the sales team only · full edit history
02
@ mentions that reach the right person
Type @ and a colleague's name and they're notified — 'please follow up period 3', right on the contract in question. The mention carries its context with it, so nobody asks 'which customer was this about?'.
- Notify by @ name
- Context travels with it
- On the exact record
- No which-customer confusion
Contract SC-2026-041 · Bangkok Trading
@Somchai please follow up period 3
Logged on the contract · visible to the team
03
Visibility control and the message center
A sensitive negotiation note can be visible to the whole company or only to the people involved — you choose per note. Meanwhile the message center's form activity feed and inbox collect the mentions and updates that need you, so following ten deals doesn't mean patrolling ten screens.
- Public or restricted per note
- Form activity feed
- Inbox & outbox for notices
- One place to catch up
Platform — system settings
API · data received from an external system
Button-level permissions on every action · fully logged
Inside the module
Real screens from Flows ERP — what your team will actually work in.
A follow-up thread
The customer's recent history — visits, calls, and @ mentions — in order, on the record.
The message center
Mentions and updates collected in one feed — the morning catch-up screen.
Why Flows
What makes Flows different
Not another generic ERP — a system built around how Thai SMEs actually buy, sell, and collect.
See how onboarding works →Priced per company, not per seat
One annual price, every module included. Add users freely within your tier — no feature gates, no seat fees.
Three languages with auto-translation
Thai, English & Chinese UI — and the data your team enters is translated automatically, so everyone reads the same records.
Your documents, exactly your format
Send us your invoice and receipt templates; our team configures them into Flows. Every document comes out looking like yours.
We walk you live — and stay
Five-step onboarding at no extra cost, then quarterly system stability reports. We don't disappear after go-live.
Spec sheet
What collaboration ships with — included in every plan.
Threads
On customers, suppliers, and contracts
Mentions
@ a colleague with notification
Visibility
Public or restricted, chosen per note
Message center
Form activity feed + inbox/outbox
History
Notes kept with the record, permanently
Edit log
Record changes tracked alongside the thread
Permissions
Access follows the record's permission layer
Scope
Works across every module's records
Frequently asked questions
How do follow-ups work in Flows ERP?
Each customer, supplier, and contract has a follow-up thread on its record. Team members log calls, visits, and progress there, so the full story stays with the record it belongs to.
What do @ mentions do?
They notify the named colleague and pull them into that record's thread — with the context already attached, since the mention lives on the customer or contract in question.
Can a note be hidden from some colleagues?
Yes — each note can be visible company-wide or restricted to the people involved. Sensitive negotiations stay in the right circle without leaving the system.
What is the message center?
Your catch-up view: a form activity feed with mentions and record updates that involve you, plus an inbox and outbox for internal notices — used much like email, but inside the system.
Does this replace LINE or email for the team?
It replaces the part that belongs on records: customer follow-ups, work handoffs, decisions about deals. General chat stays wherever your team likes it — Flows just stops business history from living there.
What happens to the threads when someone leaves?
Nothing — threads belong to the records, not to the person. The next owner reads the history and continues it, which is the whole point.
Put the conversation on the record.
Start a free one-month trial, or book a demo and watch a handover happen without a meeting.