Report CRM health for a period with counts, trends, owners, and the next fixes.
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 weekly or monthly, from dated exports compared with the last report.
Open with the export dates and row counts, then give each count against the last period:
Say which change matters most and which report it affects.
Break the counts down by object and by owner. Show where problems cluster and whether they are new or old. Keep the tone neutral; the aim is to fix the data, not to rank people.
List three to five fixes in order, each with the count it would clear, the report it helps, the owner who must approve it, and a suggested date. Note fixes from the last report that are still open.
Never guess a missing value to improve a count, and do not hide records to make a trend look better. Do not merge, delete, reassign, or edit CRM records yourself; the owners make each change.
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.
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.
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.