Skip to content

Weekly account health (skill)

From official docsAuthor: @JeffShanCha

Written to the official six parts of a good skill: when to use, inputs and access, steps, validation, output, approvals. Run the task by hand once, then send this to the Bot to save it.

Save the following process as a skill called "Weekly account health":
When to use: every Monday, or when I say "check account health".
Inputs and access: <CRM view link>, product usage dashboard, support ticket system, billing system; all read-only.
Steps:
1. Read every account in the portfolio
2. Combine the last 30 days of usage change, support escalations, renewal timing and stakeholder activity
3. Score risk using these definitions: <e.g. usage down more than 30%, renewal within 90 days and no active stakeholder>
4. Rank into a watch list
Validation: every conclusion needs a source link; list accounts with missing data separately, do not guess.
Output: a table with account / risk level / evidence / why it matters / suggested next step.
Approvals: any action that contacts a customer needs my approval first; do not edit the CRM.

The official docs suggest putting risk thresholds in the Bot’s description so weekly results stay consistent and comparable.

Sources