1. Set up
Connect your tools
Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access(opens in new tab).
Add a connector(opens in new tab) for each tool you want Claude to use.
Set your working folder
Drag the files you'll use (the usage export, the success plan, the latest NPS responses) into one folder on your machine, then give Claude access to it(opens in new tab) in the Claude desktop app. Claude reads from the folder and writes the health summary back to it. If you track this account ongoing, create a project(opens in new tab) from that folder so your health criteria, instructions, and memory stay attached.
2. The prompt
Copy this into Claude
From the usage data, open Zendesk tickets, NPS responses, and success plan for Northwind, write the account health summary to the account folder: call it red, yellow, or green with the reason in one or two sentences, then the two actions to take this week.
Why this works
Give a fixed set of answers. "Red, yellow, or green" makes Claude commit to one status instead of hedging, and "with the reason" means the call is defensible when leadership asks.
Say how many items you want. "Two actions I should take this week" keeps the output to what you'll actually do before Friday, not a backlog of everything that could help.
Name the sources to weigh together. Naming usage, tickets, NPS, and the success plan together means health is weighed across product, support, sentiment, and goals, not just whichever dashboard you checked last.
Include the goals to measure against. The success plan and usage export sit in the working folder, so the health call is measured against the goals you actually agreed with the customer.
Get a better draft
Add an example to match. Drop an example you like into the folder and Claude matches your structure and voice.
Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.
3. Make Claude work for you
Tell Claude your own rules for this task, such as your usage thresholds and your risk rules, then save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.
Make what we've done in this task so far into a skill called /account-health.
Review the skill, and save it if Claude hasn't already.
4. Make it repeatable
Run it across your book every week
Health should be tracked, not checked when something breaks. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and /account-health writes a fresh summary for every account in your book each week.
Set up a scheduled task for every Monday at 7am: run /account-health for each account in my book and write the summary to the matching health folder under Accounts. Put the red accounts first in one digest.
Runs /account-health for every account in your book and writes the summary
to its health folder, with red accounts first in one digest for you to confirm.
To use a folder on your computer during a scheduled task, keep your computer on and awake with the Claude desktop app open so Claude can access it.
5. Share with your teammates
Your /account-health skill now carries your usage thresholds, your risk rules, and your summary format. Share it so every CSM scores health the same way, and the red/yellow/green means the same thing across the whole book.