“The Inbox Signal Lab made our LINE broadcast calendar look overconfident. We cut two weekly sends and first-hour replies actually rose. I still wish the homework used our live tags instead of sample CSVs.”Pimchanok Wattana · Head of CRM, regional beauty retailer
Bangkok · Messaging Engagement Analytics
The reply window is a product surface. We teach teams to read it.
Systemagentbase is a small studio on Krungthep-Nonth Road. We sit with CRM, CX, and lifecycle operators who already send on LINE, WhatsApp, and in-app chat—and still cannot explain why Tuesday’s thread died by Thursday.
“Arthit from Chiang Mai sat the Conversation Cadence Workshop and sent us a timetable, not a slide. That is rarer than it should be.”Arthit, Chiang Mai · independent lifecycle contractor
Seats currently open for critique
Each programme is built around Messaging Engagement Analytics: measuring whether a thread was actually held, not whether a campaign was merely delivered.
Inbox Signal Lab
A cohort that rebuilds your reply-window, opt-in, and thread-health dashboards from first principles.
Read the syllabus
Conversation Cadence Workshop
Short-form studio for teams who already have a tool stack and need a humane send timetable.
See all programmes
LINE & WhatsApp Cohort Desk
Regional channel work: quiet hours, OA blocks, and what “read” actually means across apps.
See all programmes
House method
We do not teach vanity funnels. We teach timetables.
Most messaging reports celebrate delivery. Our pedagogy starts later: after the customer has already received the ping. Students learn to annotate silence, not just clicks.
Cohorts meet in Bangsu or online. Critique is written, not theatrical. You leave with a ledger your ops lead can argue with, not a mood board.
Capabilities, written as notes rather than slogans
- Reply window First-hour, first-day, and abandoned-thread coverage, broken by agent desk and by automation.
- Opt-in grain Consent that survives a campaign reset, including LINE OA blocks and WhatsApp template fatigue.
- Thread health Whether a conversation still has a next useful message, or is only generating noise for the agent queue.
- Quiet hours Thai public calendars, shift patterns, and the difference between “do not disturb” and “do not bother.”
Journal
Recent studio notes
Reply latency is a product decision
Why first-hour coverage belongs on the roadmap, not only on the CX wallboard.
Read the note
Quiet hours on LINE OA in Thailand
A working calendar for Bangkok desks that still want to sound local after 21:00.
Read the note
Desk
Enquire
Bring a messy export. Leave with a timetable.
If your current report cannot tell you which threads were abandoned on purpose, write to the Bangsu desk. Seats are informational; there is no checkout on this site.