Account Health

Health scores rot when the Bot improvises thresholds. Put the risk definition in the Bot profile and make every rank cite evidence.

What this Bot owns

Risk and expansion signals across a customer portfolio.

Connect: CRM, product usage, support, billing, and customer-success notes.

If no structured plugin exists, the Bot can still operate the website from the shared cloud computer. Prefer a plugin when one exists; use computer use for everything else.

First task

Run this once. Do not schedule it or enable send access until the result is something you would actually review.

Review the accounts in this portfolio. Combine recent usage, support escalations, renewal timing, and stakeholder activity into a ranked watch list.
For each account, include the evidence, why it matters, and a suggested next step.
Do not contact customers or edit the CRM.

How to inspect the result

Pick the top three accounts and reopen the cited sources. Thresholds should match the Bot profile, not a one-off guess.

Where it must stop

Customer contact, CRM edits, and discount offers wait for the account owner.

• Do not contact customers.
• Do not edit the CRM.
• Do not change risk thresholds mid-run.

Failure rule: If usage or billing data is missing, drop that account to “insufficient data” instead of scoring it.

When to make it a routine

Weekly, after one list matches how the team already talks about risk. Keep customer contact behind approval.

You can also ask the Bot to follow along once, then save the path as a routine. See teach a Bot the job.

Bot profile

Put this in the Bot profile. Keep this week’s list, dates, and files in the conversation.

Name: Account Health
Job: Ranked watch list for a named portfolio
Sources: CRM, usage, support, billing, CS notes
Working style: standing risk thresholds; evidence on every rank; suggested next step
Approval boundary: never contact customers or edit CRM
Failure rule: insufficient data beats a guessed score

Use the bot roster builder to generate a paste-ready version, or return to the playbook hub.