Draft follow-ups to customers who asked for a feature once it ships
Once a feature ships, have Grok Bot find the customers who asked for it and save personalized Gmail follow-up drafts for your review.
What the agent did
Source-reported example · as described by Sebastian Röhl (@SebastianRoehl)
After shipping Quit Habits in HabitKit, an indie app developer asked Grok Bot to search HabitKit support emails for people who had wished for the feature and draft a personal follow-up for each, as Gmail drafts only.
Grok Bot found the relevant customers and saved 40 personalized Gmail drafts for his review. He had used the same approach earlier for a Notes feature.
Grok Bot found the relevant customers and saved 40 personalized Gmail drafts for review; his screenshot shows nothing sent during the documented run.
The author also reports happy replies and reviews; the posts don't establish how or when the messages were sent. He calls it two minutes of work; in the earlier Notes run he reported 34 users made happy in two minutes.
Limitations
Short X posts. Grok Bot only drafted: per the screenshot it found the relevant customers and saved 40 personalized Gmail drafts for review, and the screenshot shows nothing sent during the documented run. The posts don't establish whether, how or when the messages were sent.
'Happy' replies and reviews are the author's description. The Notes-run image is an illustration, not a record of the job. The author builds and sells the app being announced (disclosed under Commercial interest).
Try it in your business
What you'll need
Grok Bot connected to the mailbox where customers write in (author used Gmail), with permission to create drafts; a shipped feature and the words customers used to ask for it. How Gmail was connected and whether, how or when the drafts were sent are not disclosed.
Grok Bot read HabitKit support mail in Gmail and saved drafts there; how Gmail was connected isn't described and no custom code is described.
Author's original prompt
Go over ALL my HabitKit support emails and check for people who wished for a "Quit habits / Inverse habits" feature (where habits are checked on by default) in HabitKit. Draft a message for them that tell them that it finally landed in the app, apologize that it was a long time coming. Say that I would be super happy if they would check it out. Only drafts in my Gmail!
Optional starting prompt (ours, untested)
How ours differs from the original setup: Same Grok Bot execution agent and the same drafts-only rule as the author's prompt. Adds a checkable match list with request quotes and a skip rule for people who asked not to be contacted.
We just released [feature name] in [app]. Search my email history, including support emails, for every customer who asked for this feature or something clearly equivalent. List each match with the date and a one-line quote of their request so I can check it. Then draft a short personal follow-up for each person: tell them it's live, mention what they asked for, and say how to get it. Skip anyone who asked not to be contacted. Save the drafts for my review; don't send anything.
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
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.
Our suggested starting prompt — not the author's original · untested
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.
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.
Triage support tickets and draft replies with evidence
Get support messages checked against ticket history, with reported bugs reproduced and reply drafts ready for a person to review and send.
Our suggested starting prompt — not the author's original · untested
You'll need: The original setup uses custom support instructions, integrations with messaging and help-desk tools, and a test environment. The support skill's contents, specific chat and help-desk products, and costs are not disclosed.
Review today's support messages in [inbox or help desk]. Summarize each issue, check the customer's history and [known-issues document], and draft a reply using the evidence you found. For suspected bugs, reproduce the problem on [test site] if available and record the steps and result. Otherwise flag it for investigation. Save drafts for review and list refund requests separately. Do not send replies or issue refunds.
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.

