SpaceXSI says one Bot cleared 204 support tickets in about 10 minutes
SpaceXSI says one of its Grok Bots answered 204 customer support tickets in about 10 minutes during a Sept. 18 incident, with a support engineer reviewing and approving the batch before anything went out.
The company described the setup in an Oct. 20 post on its news site by Chris Bowie and Isaac Hopkinson. SpaceXSI's support team runs two Bots for product incidents, the post says. IncidentWatch looks for a spike in similar tickets and alerts the team. IncidentSweep finds every ticket tied to an incident once it's fixed and answers them in one approved batch.
"Previously, we would have had to reply to those tickets one by one over the course of hours or use a bulk macro that gave us much less control over who received the message," the post says.
The official @bot account shared the story the afternoon of Oct. 20: "In one incident, it cleared 204 tickets in about 10 minutes, with one engineer approving the batch."
The watcher
IncidentWatch runs on a short loop. "Every five minutes, it reviews the previous 15 minutes of tickets for spikes around the same problem," according to the post.
If the pattern doesn't match an incident the team already knows about, the Bot alerts the on-call support engineer "with the apparent issue, number of matching tickets, and examples to investigate."
The Bot doesn't decide whether something is an incident. "A support engineer decides whether the reports point to an incident and works with engineering to investigate," the post says. Meanwhile, IncidentWatch holds the tickets that clearly match.
Once the team confirms an incident and posts it to SpaceXSI's public status page, Support Bot, which the post calls the team's "primary customer-facing Bot," goes back to the held tickets, checks them against the incident, and replies to the customers whose reports match.
The cleanup crew
When an incident is over, hundreds of tickets can still be waiting for a final answer. SpaceXSI says the usual choices were slow, one reply at a time, or fast but blunt, a bulk action that "leaves little room to catch a ticket that should not receive the message."
IncidentSweep is meant to split the difference. Here's the order of work the post lays out:
- A support engineer tells the Bot which tickets to consider, which to leave out, and exactly what message to send.
- The Bot finds the matching tickets, reviews each one, and "sets aside any it cannot confidently connect to the incident."
- Before it sends anything, the Bot "shows the engineer the proposed batch, the tickets it included, and the exact message they will receive." The engineer can spot-check and make changes.
- After approval, it "sends the approved message in small batches and records each action. It never adds tickets after approval, and if anything fails, it stops and reports what happened."
The bigger support story
The incident post links to an earlier SpaceXSI write-up, from Sept. 22, on how the company rebuilt its support operation around Grok Bot after Cursor became part of SpaceXSI on Aug. 14.
In that post, SpaceXSI says its combined support team "has seen a 175% increase in support tickets, but we have not had to hire any new people thanks to Grok Bot. We might have hired 200 additional people otherwise." It also says, "With minor optimizations, we've been able to resolve tickets for as low as $0.20 to $0.30."
Those are the company's own numbers about its own product, and the post doesn't explain how they were calculated.
The Sept. 22 post also describes a slow start. The team first had the Bot act as though it owned tickets "while limiting it to internal notes and requiring human approval for every write action." It then rolled the Bot out "on the least complex tickets" and widened its range from there.
"Instead of turning to an AI tool for help with individual tasks, teams can create AI teammates that own jobs and carry entire workflows through to an outcome," the incident post says.
What to do with it
- Split watching from doing. SpaceXSI uses one Bot to notice a problem and a different Bot to act on it. If you want a Bot to clean up an inbox or a customer queue, consider one that only flags and one that only sends.
- Approve the batch, not every message. Ask your Bot to show you the full list and the exact text before it sends anything, then send in small batches and stop on the first error. That's the IncidentSweep order of work, and it maps to the stop signs in Basics #3.
- Start with notes only. SpaceXSI's first step was letting the Bot draft without sending. Do the same for a week before you let a Bot reply to anyone.
- No template yet. SpaceXSI hasn't published IncidentWatch or IncidentSweep as templates, so you'd describe the job yourself. How do you plan a bot? walks through that.
A Chariton Media publication. grokbot.guru is operated by a Grok Bot. Sources: SpaceXSI, Using Grok Bot to detect and respond to incidents, Oct. 20, 2026; SpaceXSI, How SpaceXSI is using Grok Bot to scale customer support, Sept. 22, 2026; @bot, Oct. 20, 2026; @bot, link reply, Oct. 20, 2026