This is taking longer than expected.

Try againBrowse the library
AI Blocks

All AI specialists

Hire an AI customer renewal risk reviewer

Review account usage and support signals. Find slipping patterns, upcoming renewals and one proposed next step for each account.

What you give

  • Last week's usage per account, with the actions that matter and the renewal date
  • Open and closed support tickets per account (advised)
  • Survey answers, review lines or call notes from the week (optional)

What you get

  • A health score for every account, against last week
  • Slipping accounts with the likely cause and one idea each
  • Renewals at risk in the next 60 days, at the top
  • An escalation brief for any account that needs another team

An example

You have customers on plans, subscriptions or retainers and find out about cancels when they happen.

You ask: “Review account usage and support signals. Use the material I attach and ask for anything essential that is missing.”

You get back:

  • This week. One line with accounts scored, how many fell, how many recovered, and renewals at risk in 60 days.
  • Renewals at risk. Each at-risk account renewing within 60 days, with score, cause and the proposed touch.
  • Slipping accounts. Last three scores, progress on the leading sign, the likely cause and one idea for each.

An example, not your task.

Hire this specialist

It is free and needs no account. Download the pack, give it to your AI and tell it the job. Your AI asks for anything it is missing, then does the work and checks it.

Download the specialist

Related specialists

Skills and workflows for this job: Keep customers coming back

Details

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

  • A health score for every account, against last week
  • Slipping accounts with the likely cause and one idea each
  • Renewals at risk in the next 60 days, at the top
  • An escalation brief for any account that needs another team
  • A thank-you note and keep-in-touch plan for healthy and recovered accounts
  • A weekly check on your leading sign of success

How it does the job well

  • Check the current policy and the customer's order or account facts before replying.
  • Answer the actual question in the first two lines, then explain.
  • Match the customer's tone. Acknowledge the problem once, without grovelling.
  • Hand refunds outside policy, legal threats and safety issues to a person.

Mistakes it avoids

  • Messaging an account because its score dipped once.
  • Offering a discount as the first idea. Find the cause first.
  • Treating a quiet healthy account as safe forever.
  • Proposing three touches to the same person in a week.
  • Promising refunds, dates or fixes the policy does not allow.
  • Copy-paste replies that ignore what the customer said.

What a good result looks like

An example, not your task: You have customers on plans, subscriptions or retainers and find out about cancels when they happen.

  • This week. One line with accounts scored, how many fell, how many recovered, and renewals at risk in 60 days.
  • Renewals at risk. Each at-risk account renewing within 60 days, with score, cause and the proposed touch.
  • Slipping accounts. Last three scores, progress on the leading sign, the likely cause and one idea for each.
  • Escalations. A brief for each account with a problem another team must fix.
  • Touches to send. Thank-you notes and keep-in-touch plans for healthy and recovered accounts, as drafts.
  • Leading sign check. How many new accounts did the key action within the set number of days this week.

How the work is checked

  • Every slipping account shows scores from at least two weeks.
  • Each at-risk account has one cause and one idea, not a list of ten.
  • No touch was proposed for an account touched in the last 14 days unless it is slipping.
  • Renewals within 60 days are at the top.
  • States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Mark Roberge and Dale Carnegie would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

  • Set the leading sign once. Picks one early sign of success in the form "P percent do event E within T days", and re-checks it each quarter.
  • Read last week. Opens the saved scores and notes which touches were sent.
  • Score every account. Scores health, churn risk and upsell room from usage and support data, and adds the row to the history.
  • Sort each account. A slide two weeks running gets a cause and one idea. An unfixable problem gets an escalation brief. A healthy account gets a thank-you.
  • Watch the renewals. Lists renewals in the next 90 days with risk, and puts at-risk ones inside 60 days at the top.
  • Log and hand back. Saves the scores and touches, then stops for your yes.

How the role works

  1. Checks your task, context and available tools.
  2. Picks the methods needed and prepares a work plan.
  3. Carries out supported tasks, with each method's limits and review gates.
  4. Checks the real deliverables and corrects supported faults.
  5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id weekly-customer-health-watcher only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/weekly-customer-health-watcher/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

  • Last week's usage per account, with the actions that matter and the renewal date
  • Open and closed support tickets per account (advised)
  • Survey answers, review lines or call notes from the week (optional)
  • A read-only connection to your account tool (optional)
  • Last week's history file, once it exists

Helpful context (optional)

  • A note when a customer's main contact changes
  • Which accounts carry most of your revenue, so their slide rule can be tighter

Tools and access

  • Claude Code: It can keep the account and touch files between weeks and run every Monday.
  • Your billing or CRM tool: Export usage, plan and renewal date per account. A read-only connection lets the renewal step read them directly.
  • A spreadsheet: Counting how many customers did an action by day is simple in a sheet and easy to check.
  • Any good chat AI: Comparing two groups and writing the sign is text work any strong chat AI does well.
  • A contact or spreadsheet tool: Keep the buyer record and the dates in one place.
  • Any good chat AI: Short notes and schedules are simple text work.

Functions and deliverables

  • Customer renewal risk reviewer: Review account usage and support signals. Find slipping patterns, upcoming renewals and one proposed next step for each account.
    • A health score for every account, against last week
    • Slipping accounts with the likely cause and one idea each
    • Renewals at risk in the next 60 days, at the top
    • An escalation brief for any account that needs another team
    • A thank-you note and keep-in-touch plan for healthy and recovered accounts
    • A weekly check on your leading sign of success
  • Customer success milestone planner: Describe what buyers do after purchase. Pick one early success sign and a deadline to track it.
    • A comparison of what retained and lost customers did early
    • One sign written as a percent, an action and a time limit
    • How to measure it by cohort in 30 to 60 days
    • A check of lifetime value against cost to win
  • Customer health and churn scorer: Share account data. Get health scores, churn-risk tiers and expansion signals for each customer.
    • A health score per account
    • A churn risk rating with reasons
    • An expansion opportunity score
    • Ranked lists for follow-up
    Source: Alireza Rezvani.
  • Customer cancellation risk finder: Share usage, support, billing and engagement data. Get account risk scores, warning signs and possible next steps.
    • A risk score per account
    • Four risk tiers
    • Key signals for each account
    • A recommended action per tier
    Source: Burhan Sebin.
  • Escalation brief writer: Turn a stuck support issue and ticket history into an escalation brief with impact and a clear ask.
    • An escalation brief that opens with a clear ask
    • Reproduction steps for bugs
    • An impact summary covering who is hit, how badly and for how long
    • A suggested team to send it to
    • A deadline and next steps
    • Offers to draft a customer update or set a follow-up
    Source: Anthropic.
  • Post-sale follow-up planner: Plan your post-sale follow-up: give it what you sell and a buyer's details. You get a thank-you note, a dated contact schedule and a referral ask.
    • A personal thank-you note
    • A dated contact schedule
    • A list of what to record about the buyer
    • A plan for a problem and a referral ask
  • Renewal watch planner: See which renewals are coming up, which look risky, and where you can raise the price. Works as a renewal tracker from your CRM or a contract file.
    • Renewal calendar by date
    • Risk flags per account
    • Price uplift estimates
    • Prep actions for each renewal
    Source: Anthropic.
  • Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
    • A folder of eight plain files, from a start file for your AI to a claims list and a change log
    • A tag on every fact, and every claim marked approved, pending or banned
    • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
    • A short slice for your next step, if you name one
  • Mark Roberge: Review sales hiring or growth using Mark Roberge’s recorded approach. Check customer retention, clear measures and the behaviour your pay plan rewards.
    • Your problem worked on the way Mark Roberge would: their questions, their method, their push-back
    • The answer or the work, in Mark Roberge's voice, using their ideas by name
    • Anything that goes beyond their public record, marked
    • One suggested next step
  • Dale Carnegie: Rewrite a tense message or prepare a people conversation using Dale Carnegie’s recorded approach. See the other side, give sincere credit and ask clearly.
    • Your problem worked on the way Dale Carnegie would: their questions, their method, their push-back
    • The answer or the work, in Dale Carnegie's voice, using their ideas by name
    • Anything that goes beyond their public record, marked
    • One suggested next step

Tasks you can use it for

  • You have customers on plans, subscriptions or retainers and find out about cancels when they happen.
  • Renewals come up without anyone knowing whether the account is healthy.
  • You want one early sign that tells you, in the first month, whether a customer will stay.

Limits to check before starting

  • You only want to know who has already cancelled: use the Subscriber cancellation and retention reviewer.
  • You sell one-off orders with no plan or renewal: use a simple repeat-buyer list in a spreadsheet instead.
  • You have under about 4 weeks of usage data: wait and gather it first, because there is no trend to read yet.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

  • Start a chat with the agent. In Claude Code, add it as a skill or save it in .claude/agents, then ask it to run this week.
  • Export last week's usage per account from your product or billing tool. Put it in one folder, or attach it in the chat.
  • On the first run, tell it what customers do after they buy. It sets the leading sign and saves it.
  • Read the list. Send the touches you agree with, then tell the agent which went out.
  • Run it again next Monday. It adds the new scores and looks for the trend.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/weekly-customer-health-watcher for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.