Grok Bot for support: hourly ticket sweeps, refunds approved in Stripe

You can give one Grok Bot your support inbox on an hourly schedule, let it answer from your playbook, and keep every refund behind a click you make in Stripe. This playbook follows Holly Helpdesk, Claire Vo's support Bot for ChatPRD, as she described it in a Sep 3 post. Holly also reads a week of tickets and suggests doc fixes. Her October posts still talk about Bots with jobs like support but don't name Holly, so read this as her setup in early September. It fits support leads at small software teams and founders who still answer tickets. It's her own account, on her own company's site, and we haven't run it.

Not tested: we have no helpdesk, support inbox or Stripe account to run it against.

Who runs it#

Claire Vo's X bio reads "building @cxodev @chatprd". She hosts the How I AI show, and her Sep 3 post says "I migrated our ChatPRD customer support agent, Holly Helpdesk, over to Grok Bot". In the same post she says she is "running about 30 agents at any given time".

Disclosure: Holly answers ChatPRD's own customers, and the post sits on ChatPRD's site, which sells ChatPRD. On Aug 30 she posted that "the grok @bot team has given me 50 ULTRA plan codes ($200 in usage) to give away". She shares her Bots as templates; the Holly page says "This AI bot was created by a third-party user, not by SpaceXSI." We found no staff role at Cursor, xAI or SpaceXSI in her bio or posts.

The support loop#

Her post lists five parts, quoted from her Sep 3 post:

1. Hourly sweep. "Every hour, Holly sweeps our Intercom and email inboxes."
2. Answers from the playbook. "Using our support playbook and tools, she manages refunds and technical support requests."
3. Refunds wait for her. "She is empowered to request refunds, but not to issue them unilaterally." When one is needed, "I get a notification with an “Approve” button. Clicking it takes me to an agent action in Stripe, where I can explicitly grant permission for that single transaction."
4. A weekly docs loop. "On a weekly basis, Holly analyzes the past seven days of support tickets and suggests items to add to our support playbook or public documentation to encourage more self-service."
5. The community Slack. "I’m not great at managing our community Slack, so I’ve given Holly access. She answers support questions, prompts engagement, and keeps the community active."

Her Aug 28 X post adds two jobs the blog leaves out: Holly "escalates bugs to cursor cloud agent to fix" and handles "human-approved stripe refund, bot managed dispute management".

Her Aug 19 post shows the Stripe card. The screenshot reads "Approve agent action" and "Create a refund", "Requested by Cursor · Aug 19, 2026, 5:49 PM" (no time zone shown), with the amount and customer blurred and Deny and Approve buttons. She wrote: "A+ would refund again".

The template describes the Bot as "Frontline customer support. Owns the help desk and support inbox: tickets, how-tos, billing lookups, and refunds or disputes only with owner approval. Signs as support and CCs the support alias on replies."

Why it matters at work#

Our read: small teams lose most support time on the hourly inbox check and on refunds that sit until someone opens Stripe. In her Sep 3 account, Holly took the check and the refund prep, and the money still moved only when a person clicked Approve. The weekly review turns repeat tickets into doc changes, so the same question should come up less often. She gives no ticket counts or time saved. Her one result is that "multiple customers ask where they can leave a review for our exceptional support. That has never happened before."

Set it up#

These steps are ours, built from her post and the docs. Her blog shows the jobs, not her prompts.

1. One Bot, one queue. Name it for the job. She says a Bot "often infers its purpose from the name."
2. Give it the playbook first. Point it at your support playbook and public docs before the first sweep.
3. Put the refund gate in Stripe. Stripe lets you require approval for "Refund is created", and you can add an amount condition. It also says "Stripe maintains default approval rules for the following sensitive actions taken by agent-tagged API keys", and refunds are on that list (Stripe Docs). She doesn't say which Stripe setting she used.
4. Add the hourly routine, then the weekly one. She warns: "I’ve found you need to be pretty explicit about setting up these routines". Name the inboxes, the hours and what counts as done.
5. Keep the community Slack last. Our read: public answers under your brand are harder to take back than a draft.

Starter prompt (ours, untested)#

You are our support Bot for [product]. Every hour, check [Intercom and support inbox] for new or unanswered tickets. For how-to questions, draft a reply only from [support playbook] and [public docs], and link the doc you used. If the answer isn't there, say so instead of guessing. For a refund, check it against our refund rules and tell me what you would refund and why. Only after I say yes, request it in Stripe so I approve it there; never issue a refund yourself. Every Friday, list the five most common ticket themes from the past seven days, each with ticket links and one suggested doc or playbook change. Send everything to me in this chat. Don't reply to customers, post in Slack or send anything yourself.

The hourly sweep, the playbook, the Stripe approval, the weekly review and the Slack job are hers. The drafts-only rule, the doc links, the no-guessing rule, the yes before any Stripe request, the five-theme list and Friday are ours.

Good to know#

• Intercom's MCP server lists no customer reply tool. Intercom's docs say the OAuth consent page sums up its access as "view conversations and add internal notes to them, view contacts and companies, view, create and update articles, and use Fin Operator", and the note tool "cannot send customer-visible replies" (Intercom). Workspaces with Fin Operator can also "ask Operator to do work inside your workspace" through it. She doesn't say how Holly connects to Intercom or sends replies. Her template says it "CCs the support alias on replies", which points to email (our read). Intercom also says "AU hosted workspaces are not yet supported."
• Replies from a routine may wait for you. Cursor's rule for email from the Bot's own address: "Email from a routine, an incoming message, or other work you didn't start with that request waits as a draft until you press Send". The exception: "When you ask for an email in chat, it goes out once Auto-review allows it." Approval cards raised by a routine expire "after 30 minutes" (Approvals help). She doesn't say which address Holly sends from.
• Stripe approvals have limits. "Approved actions are completed automatically; denied actions are discarded with no changes made." Requests that aren't approved "within 14 days expire automatically", and "A user can’t approve their own request" (Stripe Docs).
• Hourly runs cost usage. "An hourly schedule, a short interval, or a Slack trigger on a busy channel can use a week of usage in a day" (Routines help). Limit the sweep to your support hours if you can.
• Tests are real. "A test does real work" (Routines help). Test on a sandbox ticket, not a live customer.
• Her group chat note is out of date. On Sep 3 she wrote "You can’t yet add one to a group chat". Cursor's approvals help now covers group chats: "In a group chat, only the person whose message the Bot is answering can approve" (Approvals help).

What to watch#

• Numbers. She gives no ticket volume, reply time or refund count. Signal: a How I AI post or @clairevo X post with Holly figures.
• Whether Holly is still on Grok Bot. On Oct 7 she wrote "Bot == it has a job (support, sales, EM, etc)", and on Oct 29 she wrote that "Grok Bot functions as my chief of staff". Neither names Holly. Signal: the Holly template page going offline, or a post naming a new support tool.
• The reply path. Signal: an Intercom MCP update that adds customer-visible replies, or a post from her showing how Holly sends them.

Last checked: Oct 30, 2026, 12:10 to 12:12 PM ET. What changed: first published Oct 30.

Related#

• Grok Bot for support and customer success: drafted answers, quiet watches, and call prep
• Grok Bot for support: intake that a webhook or a Slack reaction starts

Sources#

• Claire Vo: Practical Grok Bot Agents and Workflows That Replaced OpenClaw (Sep 3)
• ChatPRD: How to Automate Customer Support with a 5-Star AI Agent (Sep 3)
• Grok Bot template: Holly Helpdesk by Claire
• @clairevo on X: Holly Helpdesk, the support Bot (Aug 28)
• @clairevo on X: the Stripe agent approval link (Aug 19)
• @clairevo on X: Ultra plan codes from the Grok Bot team (Aug 30)
• @clairevo on X: a Bot has a job (Oct 7)
• Claire Vo: Grok vs. Dot vs. Muse vs. Claude Duet (Oct 29)
• Stripe Docs: Set up two-party approvals
• Intercom Developers: Model Context Protocol (MCP)
• Cursor Help Center: Approvals and Auto-review
• Cursor Help Center: Routines