Reply window
Who was waiting, for how long, and whether automation stole the first useful minute.
Four layers between “delivered” and “still a conversation.”
The Engagement Atlas is the internal map Systemagentbase uses when a team asks for Messaging Engagement Analytics and arrives with a vendor screenshot. It is not software. It is the order in which we read a week of threads.
Why a map, not a score
A single “engagement score” hides the hour that mattered. The Atlas keeps four layers separate so a staffing problem is not reported as a creative problem, and a consent problem is not reported as agent laziness.
Students meet the Atlas in week one of Inbox Signal Lab. House Desk teams often ask us to apply it privately to one channel first—usually LINE OA in Thailand, sometimes WhatsApp care.
The four layers
Opt-in grain
Consent that still means “you may continue this thread,” not merely “you may broadcast.”
Thread health
Whether the next message has a job, or the queue is only generating noise for agents.
Quiet hours
Local calendars, shift maps, and the difference between respect and neglect.
How operators use it after class
The Atlas is meant to sit beside the vendor UI, not replace it. A weekly ritual looks like this: export the week, mark each layer in a ledger, write one sentence about what you will not send. That last sentence is the product decision.
Teams who skip layer two (opt-in grain) often look “engaged” in LINE statistics and still lose thread starts after a campaign reset. The journal note on opt-in fatigue walks through a Bangkok example.
If you want the Atlas taught rather than described, start with the programme list or write to the desk with a sample week attached.