Why this matters
CSMs operate from notes, Slack, and stale dashboards. A book-of-business digest gives them a prioritized list every week without a BI analyst.
What you get
- Accounts needing outreach
- Expansion and champion signals
- Usage drops and support friction
- Suggested next action per account
Walk through it
You
Build this week’s digest for each CSM.
Agent
I’ll group account signals by CSM owner and write short action briefs.
POST /v1/projects/:project_id/analytics/query {
project_id: "default",
hogql: "SELECT properties.csm_owner AS csm, properties.account_id AS account, count() AS events_7d, max(timestamp) AS last_seen FROM events WHERE timestamp > now() - INTERVAL 7 DAY AND properties.account_id IS NOT NULL GROUP BY csm, account ORDER BY csm, events_7d DESC"
}The output
The agent returns one digest per CSM with high-signal bullets. It should avoid flooding the CSM with healthy accounts unless there is an expansion opportunity.
Setting it up
Emit account snapshot or usage events with account_id and csm_owner. Save each CSM’s preferred digest style with agent memory note.
Variations
- “Only show accounts with a health score drop.”
- “Create a version for the VP CS.”
- “Post this every Monday morning.”