Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this when an account wobbles or a quarterly business review (QBR) looms: read the health signals, run the success plan, and prep the review from evidence.
You need the account record (usage, tickets, renewals), the health signals and renewal-risk owners from prefs, and the last QBR or success plan.
Read usage trend, open P1/P2s, repeat themes, sentiment, sponsor changes, and days to renewal. Score 0-100 weighted roughly 40% usage, 30% support health, 30% outcomes: green 80-100, yellow 50-79, red under 50 — with the deciding signal quoted. A score with no quoted signal is UNKNOWN. Threshold crossings trigger the save play.
Draft the plan: the risk in one line, the two fixes that matter, an owner and date per fix, and the save draft when renewal is at risk. Plans go to the owner for yes before any customer sees them.
Build the deck outline from evidence: wins with numbers and dates, issues with resolutions, health score with trend, and asks of the customer. Every number carries its source and period; a number you cannot source is cut, never estimated.
Draft the exec summary in five lines: health, top win, top risk, plan, ask. Offer the full talk track once the outline is approved.
Deliver the health score with evidence, the staged success plan or QBR outline, and the account log line. Log health, plan state, and QBR date on the account, and offer to watch the risk signals in the Monday pulse until green.
No usage or ticket access means a signals-UNKNOWN read naming the missing source, not a guessed score. Never present a guessed health color to a customer.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
The English summary is being prepared. Showing the original description.