Know which customers are slipping before renewal does

Health scores in most CRMs are stale. Someone updates them before a QBR or a renewal, and by then the signals are weeks old. The facts that matter (an angry email, a cluster of bugs, a champion who stopped joining calls, an integration request nobody logged) are scattered across transcripts, inboxes, the CRM and the ticket tracker.

The Account Health Autopilot fixes that. Every week at {RUN_TIME} your clone:

• sweeps the previous 7 days across four sources: call transcripts, email, CRM support signal (Salesforce Cases, or HubSpot notes/tasks/engagements) and the Linear tracker,
• tells "no results" apart from "lookup failed", so a broken connection never makes an account look healthy,
• verifies keyword hits by reading the source, so a customer named after a common word doesn't get false signals,
• grades each in-scope account on a 6-level health scale,
• drafts updates to three CRM fields: pain points, health grade and integrations needed,
• shows you the full proposed changes and writes only after you say yes,
• sends one weekly report with the health distribution, movers, silent-risk accounts and tracking gaps.

What you get:

Quick-start alternative: the prebuilt skill Weekly Account Health Update can be attached through the platform for a faster start. This card's custom skill gives you full control over the scale, the sources, the three fields and the approval flow.

• Customer Success teams who own health scores and renewals and want them current every week.
• Rev Ops who want health data in the CRM to be consistent, evidence-based and reportable.
• Leadership who want a weekly view of the customer base: distribution, movers and risks.
• Support leads who want case and ticket patterns reflected in account health.

It works for current customers (per your {CUSTOMER_DEFINITION}). Prospects, internal records and partner/referral records are skipped on purpose.

 ┌───────────────────────────────────────────────────────────────────┐
 │  Every week at {RUN_TIME} (scheduled task)                        │
 └───────────────────────────────┬───────────────────────────────────┘
                                 │
                                 ▼
 ┌───────────────────────────────────────────────────────────────────┐
 │  "Account Health Autopilot" skill                                 │
 │                                                                   │
 │  1. Build the account list ──►  {ACCOUNT_SCOPE}, minus            │
 │                                 {EXCLUSIONS}, with {NAME_MAPPINGS}│
 │  2. Sweep last 7 days (in parallel):                              │
 │       Transcripts · Email (name AND domain) ·                     │
 │       CRM cases (all statuses + text search) · Ticket tracker     │
 │     Each source: "results" / "no results" / "lookup FAILED"       │
 │  3. Verify hits by reading the source (no false positives)        │
 │  4. Grade health on the 6-level scale ({HEALTH_SCALE})            │
 │       quiet week ≠ grade change · flag silent risk                │
 │  5. Draft 3 fields per record ──►  pain points · health ·         │
 │                                    integrations needed            │
 │  6. Check {REQUIRED_FIELDS} ──►  blocked records listed, not      │
 │                                  guessed                          │
 │  7. Show proposed changes ──►  WAIT for your "yes"                │
 │       (first run = dry run, no writes)                            │
 │  8. Write in batches of 2–4 ──►  {WRITE_TARGET} in your CRM       │
 └───────────────────────────────┬───────────────────────────────────┘
                                 │
                                 ▼
 ┌───────────────────────────────────────────────────────────────────┐
 │  Weekly report ──► {REPORT_RECIPIENTS} and/or {TEAM_CHANNEL}      │
 │  updates · failures · distribution · movers · silent risk · gaps  │
 └───────────────────────────────────────────────────────────────────┘

#The health scale

The default scale has six levels. You can rename them or change the definitions with {HEALTH_SCALE}.

Two rules apply every week:

• A quiet week alone never changes a grade. No news is not good news or bad news by itself.
• Silent risk is worse than noise. An account with no cases, no emails and no calls because nobody is using the product is a bigger worry than an account filing bugs. The clone flags these separately.

Your clone matches these to the exact skill names in your workspace. Your clone will report the names it finds in your catalog.

Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.

• A failed lookup is not zero results. If the email or case search fails and is counted as "nothing found", the account looks quiet and healthy. The skill reports every source as results / no results / failed, and never grades an account as healthier because a source failed.
• Customers use personal email addresses. Contacts often write from gmail.com or outlook.com. That's why email is searched by company name and domain, plus known contact addresses.
• Cases get filed under the wrong account. Support cases are often logged against a parent account, a reseller or a placeholder. The skill runs a secondary text search on case subjects and descriptions to catch them.
• Company-name false positives. A customer named after a common word (think "Summit", "Apex" or "Bright") will match lots of unrelated emails and transcripts. The skill reads each hit to confirm it's really about that customer.
• Validation rules block saves. If your CRM requires certain fields ({REQUIRED_FIELDS}) before a record can be saved, the write will fail on records missing them. The clone never invents values; it lists the record as blocked so a person can fill in the gap.
• Overwriting can lose detail. The pain points field is overwritten each week. The skill carries forward unique detail that's still true and flags anything it plans to drop, so you can say no.
• A quiet week shouldn't change a grade. Holidays and slow weeks happen. Only real evidence moves a grade.
• Silent risk hides in plain sight. No activity at all can mean nobody's using the product. These accounts are flagged, not marked healthy.
• Field-level permissions. The CRM integration user (the account the clone's CRM operator signs in as) needs edit rights on the three fields specifically. A user who can edit the record but not the field gets a permission error. This is the most common first-week failure.
• Picklist values must match exactly. "Bright green" vs "Bright Green" can fail or create a stray value. Keep {HEALTH_SCALE} and the picklist identical.
• Name mappings drift. New products, acquisitions and renamed accounts break matching. Review {NAME_MAPPINGS} every quarter.
• The clone only sees what's shared with it. If transcripts live in a folder it can't open, or support is in a tool it isn't connected to, that source shows as failed or missing.
• Use exact skill/operator names as they appear in your skill catalog. The clone checks them during discovery.
• Read every instruction before saving it into a skill. You're responsible for what your clone does and what it writes into your CRM.