Audit CRM fields by fill rate, format, and use, and propose keep, fix, or retire for each.
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 for one object at a time, or for the fields behind a named report.
State the export date, object, filter, row count, and the list of fields included. If the export is partial or filtered, say so before any figure.
For each field record:
Flag fields that look filled but hold placeholders such as "n/a", "tbc", or a default date.
Label each field keep, fix, or retire, with one line of reason and the report it affects. For fix, name the smallest change: a picklist, a required rule, or a backfill from a named source. For retire, list what still reads the field.
Return the list for the CRM owner to approve.
Never fill a blank field with a guess, and do not change, hide, or delete a field or record yourself.
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.