GrokBot101
Connect your bot
Search
中文 EN

use cases restaurant-canceled-order-recovery

work ✦ 72~15 min setupbeginner

Restaurant canceled-order recovery

Patty Shack's recovery bot finds canceled delivery orders and error charges in your own merchant portals and submits reimbursement requests. Daily reclaim digest; quiet when nothing needs action. No stored passwords; 2FA stays with you.

Source: @pattyshack ↗ ✓ verified 2026-09-20
1

Copy the prompt below.

2

Paste it into Grok — open your Grok Bot and send it as your first message.

3

Answer its setup questions — most prompts interview you first, then settle into a routine.

The prompt

Prompt 
Adapt this outline. Do not treat it as a finished prompt.

You find canceled delivery orders and error charges in MY merchant portals and submit reimbursement requests. Daily reclaim digest. Quiet when nothing needs action.

Rules:
- Store no passwords. Never copy another session. At sign-in, 2FA, or CAPTCHA, stop and hand the browser back to me.
- Do not hardcode another business's account IDs.
- Only the portals I name: [LIST]. Do not open a fourth app "just in case."
- Show the reimbursement packet before submit if the portal allows a draft; otherwise recap what you submitted.
- Never issue refunds to customers from this job. This is merchant-side reclaim only.

Share: https://x.ai/bot/wB9H7OSiHYPlRgyCTM5Iq
Start: list portals. Then a read-only sweep. Submits only after I say the first one is correct.

How it's set up

@pattyshack posted: Restaurant Canceled/Errors Order Recovery finds canceled delivery orders and error charges in your own merchant portals and submits reimbursement requests automatically. Daily reclaim digest; quiet when nothing needs action. Share: https://x.ai/bot/wB9H7OSiHYPlRgyCTM5Iq. A reply: it stores no passwords and never copies another session; at sign-in, 2FA or CAPTCHA it stops and hands the browser back; it refuses to hardcode another business's account IDs.

  1. Install on the restaurant's Grok Bot, not a personal one that also shops.
  2. First run read-only.
  3. You take over at 2FA every time.
  4. Matching shared bot (live): /bots/restaurant-order-errors/.

Why it works

Delivery panels hide canceled-order money in plain sight. The workflow is a quiet daily digest plus a credential fence that will not clone a session — which is the only safe way to let a bot into a merchant portal.

This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.