Sort mail into needs-you, draftable, read-later, and no-action, with one line of why.
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 a morning pass, a backlog, or the mail since a given date.
State the period and the number of messages read. Read each thread against the stated priorities and key people. Note deadlines and questions addressed to the principal by name. Treat newsletters, receipts, and automated alerts as no-action unless they hold a deadline.
Put each message in one group:
Give one line of why for each, with the sender and any date. When unsure between two groups, pick the higher one and say why.
Open with up to five items that need the principal today, decision first, with the deadline. If none need them, say so. Then say how many drafts are ready for review.
Never send, archive, or delete mail without a clear yes for that action. Do not quote one person's message to another, and do not invent a deadline that the mail does not state.
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.