Draft the weekly recap email to a client
Have Grok Bot write the weekly recap email to a client, then clean it up, as the author says he does.
What the agent did
Source-reported example · as described by Derek Riggs (@DerekatQuango), co-owner and account manager at Quango, a two-person web-first creative studio (per his X profile and Quango's site)
The author, Derek Riggs, co-owner and account manager at the web and advertising studio Quango, posted on X that he has Grok Bot write his weekly recap emails to one of his clients. He says the emails used to take him 30 to 45 minutes each week.
He says Grok Bot "has all the info it needs" and that it tends to already do most of the tasks for this account, or is at least aware of everything that goes on with them. He now cleans up what his Grok Bot sends.
The post gives no setup, steps, example email or prompt, and does not say what the recaps contain, how Grok Bot gets its information, or whether the email goes to him or straight to the client.
He says this saves him about 2 hours a month: the weekly email went from 30 to 45 minutes to "closer to 7-8 minutes a week" (his own figures; he does not say how they were measured).
Limitations
Short post with no setup details, steps, example or prompt. The times are the author's own estimates. It covers one client's weekly recap only.
The post does not say what the recap contains, how Grok Bot knows what happened on the account, whether Grok Bot sends the email itself or hands it to him, or what "clean up" involves, so we cannot say whether a person approves every email before the client sees it.
The model is not stated. One reply to the post exists and was not readable.
Try it in your business
What you'll need
Grok Bot with enough access to, or notes about, the week's work for the client (the post does not say which); your usual recap format or an earlier recap to follow; your own read-through and clean-up of each draft before it goes to the client.
The post says Grok Bot already knows what is going on with the account, which suggests it can see the account's work, but it does not say how. The label is our reading, not something the author states.
Starting prompt
The author didn't publish their prompt (read the full note_tweet text; no prompt or instruction is quoted; the one reply was not retrievable), so this is our adaptation.
How ours differs from the original setup: Same execution agent (Grok Bot). The author published no prompt, so this is our starting prompt based on his one-paragraph description. Where Grok Bot gets the week's information is a blank you fill in, because the post does not say.
It adds 'check' marks for anything uncertain and an explicit no-send, review-first instruction, because the post does not say whether the author reviews every email before the client sees it.
Draft this week's recap email to [client name]. Cover what we did for them from [date] to [date], what is in progress and what we need from them next. Use [where the week's work is recorded: notes, a task list or a folder I give you] and my last recap, [paste or attach], as the format and tone to follow. Where you are unsure whether something happened, mark it 'check' instead of stating it. Do not send anything to the client; give me the draft to review and edit.
Replace the [bracketed] parts with your own files and tools.
Get examples like this every Tuesday and Friday
Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.
Unsubscribe any time. Privacy policy
Related use cases
Check local prospects' email security and draft personalized outreach for your approval
Have Grok Bot research local businesses' public email-security records and draft personalized first-touch emails for your approval, the work the author says his AI team did.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot, or a Grok Bot team set up with roles like the author's; a list of the businesses to research (the post does not say whether the team found them or he supplied them); somewhere to keep the drafts and findings; your own approval of every email before anything is sent.
Here is a list of local businesses: [name, website, contact]. For each one, read only the DNS records the domain already publishes publicly and note whether it has SPF, DMARC and DKIM records and anything that looks missing or misconfigured. If you cannot tell (for example DKIM may depend on a selector you cannot see), write 'unknown' instead of guessing. Do not probe, scan or log in to anything. Then draft a short first-touch email to the owner, in plain English and in my tone, that names what you found for their domain and offers [my free check or service]. Put the findings in a table (business, domain, what you found, how sure you are) and save each draft with it. Do not send any email or contact anyone; give me the table and the drafts for my review and approval.
Triage customer support tickets and prepare fixes or replies for your approval
Have Codex triage incoming customer support tickets and prepare a reply or a proposed fix that waits for your approval before anything goes out.
Our suggested starting prompt — not the author's original · untested
You'll need: Codex access; a Linux machine with a dedicated user account per agent; email delivery into Maildir with a trigger that wakes Codex on new mail; scheduled wakeup timers; agent accounts in your support ticketing or bug-tracking system and CI; command-line tools or API access to those services; your own review and approval of each prepared fix or reply
You help me run customer support for my small software business. When a new support ticket or support email arrives [ticket system or mailbox], read it and any related history, then triage it: label it as a bug, question, feature request or duplicate, note its urgency, and link any existing ticket it matches. For questions, draft a reply to the customer. For bugs, investigate in the code repository [repo], reproduce the problem if you can, and prepare a proposed fix on a separate branch with a short explanation, without merging or releasing it. Put each draft reply and proposed fix in my approval queue [where] with a one-paragraph summary and anything you're unsure about. Do not send anything to customers, merge, deploy, close tickets or delete anything; I will review and approve every reply and fix myself.
Build an estimate and job-cost tracker connected to QuickBooks, email and OneDrive
Have Grok Bot build an estimate and job-cost tracker connected to QuickBooks, email and OneDrive, as the author says he did to replace his construction-management software.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot with access to your QuickBooks, email and OneDrive (the post does not say how it was connected); the estimate and job-cost categories your current software uses, ideally with a sample from one job; your own review of the tracker and of anything the bots prepare.
I want an estimate and job-cost tracker to replace [current software or spreadsheet]. Build it as a workbook saved in [OneDrive folder] with: an estimate sheet per job ([line items and cost codes]), a bills and actual-cost sheet per job, and a summary of budget against actual cost per job. Fill the cost data from QuickBooks ([company file]) and from bill emails in [mailbox or label], read-only: do not change anything in QuickBooks, send any email or delete anything. Match each bill to a job and cost code, and list the ones you cannot match, with the reason. First show me the structure and a sample for [one job] before you fill in the rest. For draws: when I ask, prepare the draw package for [job], draw number [n], using only invoices that were not in earlier draws, and list any issues from the last draw request. Save it as a draft and write a draft email to [bank contact]. Do not send anything to the bank; show me the package and the draft first.

