The template
Ours Our version, based on what @OmarOuqfi described. He shared no prompt. Fill in the [BRACKETS].
Review one credit card for charges I might have missed, especially typo-looking amounts. Draft only. I send anything.
RULES
- Never send email, call a merchant, open a dispute or share card numbers, PINs or one-time codes.
- Sending, buying, posting, deleting and disputing always need my yes.
- Only use the transactions I point you at (a connected card or statements I upload). If you can't see a charge, say so.
1. REVIEW
- List each transaction with the date, merchant name as shown, amount and how I paid if that's visible (tap, chip, online).
- Flag amounts that look like a slipped extra digit or a shifted decimal (for example $222.20 next to a coffee shop that would more likely charge $22.20, or $199.99 vs $19.99).
- Also flag duplicates, charges I don't recognize, and merchants that don't match where I think I was that day.
- For each flag: why it looks off, what a more likely amount would be, and how confident you are (high / medium / low). Don't invent a "correct" price.
2. MERCHANT
- For flags I ask you to follow up on, search for the email or contact page of that specific location, not just the brand. Show the URL you used.
- If you can't find a contact for that location, say so. Don't guess an address.
3. DRAFT
- Write an email I can send: the charge date, amount, last four digits of the card if I give them, why I think it may be a typo, and a polite ask to check and refund the difference if it was a mistake.
- Leave a blank for any detail you don't have. I send it.
4. TALLY
- Keep a table: merchant, date, charged, suspected amount, difference, status (flagged / drafted / I sent it / refunded / no).
What they did
- He asked Grok Bot, while his car was driving itself, to review his credit card account for anything he might have missed.
- In a reply to Kyle, who asked whether the bot found the $222 charge on its own: "All I asked was to review the transactions on a specific credit card. I had no clue about that particular transaction."
- It flagged a $222.20 coffee-shop transaction from the previous February as most likely a typo instead of $22.20. He hadn't noticed it because he'd paid with tap.
- The bot found the email address of the specific location he had visited and put together an email with the details. He says he probably wouldn't have gone through that trouble manually.
- The next day the owner emailed to apologize and confirm the error. Omar picked up a $200 refund in person and was offered a coffee and an almond croissant.
- He writes: "Grok bot just pays for itself."
- Heads-up: he shared no prompt or template, and he didn't say how the bot read the card. In another reply he said that if Grok in a Tesla says it can't do something, you can ask it to check with your bots and it will hand the task off.
“I went to pick up my $200 refund and he offered me a coffee and an almond croissant while I was there.”— Omar Ouqfi (@OmarOuqfi), X
Summary written by Agent Cookbook. The amount is quoted as the creator stated it in their own public post or interview; we link it but can't see their accounts. See the original for full context. How we verify
Our notes
- What it takes
- Grok Bot and the transactions for one credit card, either through a connected account or statements you upload. He shared no prompt; ours is built from his post and a reply.
- Where it breaks
- Treating every oddly specific amount as a typo, emailing a brand inbox instead of that location, and counting a draft as money back. He did not say how the bot read the card. Other shops may not honor a typo claim.
- Human checkpoint
- The bot reviews, flags and drafts. You check each flag, send the email yourself, and you decide whether to visit, accept a refund or open a dispute.
- Tools involved
- Grok Bot, Transactions for a specific credit card (a connected account or statements you upload), A way to reach the merchant once you approve the draft
✓ Verified Source link checked and still live. Notes by Thomas, editor. How we verify
Approval rule
🛡
In our version the bot only reviews transactions, flags typo-looking charges and drafts the email. You send it yourself, and you decide whether to visit, accept a refund or open a card dispute. Sending, buying, posting, deleting and disputing always need a human.
Set it up
- Point Grok Bot at one card's transactions, the way he did, with a connected account or uploaded statements.
- Ask it to review those charges for anything you might have missed, especially amounts that look like a typo or an extra digit on a tap payment.
- Check each flag yourself against the real receipt or what you remember spending.
- If a charge looks wrong, have it find the specific location's contact details and draft an email. Send it yourself.
- If the merchant agrees, collect or accept the refund yourself. Don't let the bot open a card dispute without your yes.
Common failures
⚠
- Treating every oddly specific amount as a typo. Some coffee shops and restaurants really do charge $20-plus; check before you write.
- Emailing a brand's generic support instead of the location you visited. He said the bot found the specific shop's address.
- Counting a draft as money back. His $200 arrived after the owner confirmed the error and he picked it up in person.
- Letting the bot send the email or start a chargeback on its own.
Variations
- Run the same review after a trip, when tap charges from places you don't remember are easy to miss.
- Compare the flagged charge with your own receipt or the shop's menu prices before you write.
- If the merchant doesn't reply, you decide whether to follow up or open a card dispute yourself.
Get the next money recipe. Free.
New recipes every week, plus the top 10 agent setups pack.
Unsubscribe anytime. Privacy