204 Support Tickets Answered in About 10 Minutes: SpaceXSI's Grok Bot Spots Outage Spikes and Clears the Backlog After a Human Approves
- Level Advanced
- Setup1–3 hrs (estimated)
- Evidence Some evidence
- CostNot stated in source
- No-codeNo
What they did
Can a bot answer the flood of tickets after an outage? SpaceXSI's support team runs two Grok Bot teammates. IncidentWatch checks the last 15 minutes of tickets every 5 minutes for a spike around one problem, alerts the on-call engineer and holds the matching tickets. After the fix, IncidentSweep finds the related tickets, sets aside any it isn't sure about, and shows the engineer the exact list and message before sending in small, logged batches. In a September 18 incident it cleared 204 tickets in about 10 minutes, work that used to take hours.
How it went
Early warning on ticket spikes, and one approved reply sent to every affected customer.
Worth knowing
- SpaceXSI's own blog about its own product (Oct 20, 2026); one incident, one batch, no accuracy data. A person still decides it's an incident and approves every send.
Prompt
Cleaned version rewritten from the source — not a direct quote.
Every 5 minutes, look at support tickets from the last 15 minutes. If several describe the same problem and it isn't a known incident, alert [on-call person] with the issue, the ticket count and 3 examples, and tag the matching tickets. When I tell you an incident is fixed, find every related ticket, set aside any you're unsure about, and show me the list and the exact reply I give you. Only after I approve, send it in small batches, log each one, and stop if anything fails.
Recommended
Try it in Grok Bot
- Copy the prompt (button below).
- Open Grok Bot chat and paste it. Replace any [bracketed] placeholders.
- Connect the listed tools (as needed) as connectors when Grok Bot asks.
- If the task repeats, ask: "Make this a daily routine."
Alternatives: the same prompt works in Claude, ChatGPT Agent, OpenClaw.
Set it up
Stack: Grok Bot + support ticket system + status page
- Read the original source for full context.
- Connect the tools your agent needs.
- Paste the prompt and replace [bracketed] placeholders.
- Run once manually and check the output before scheduling it.
Generic suggested steps, not from the source.
Evidence
Vendor blog post with one example (Sep 18 incident, 204 tickets in ~10 min with engineer approval)
Source: Web · 2026-10-20 · Verified by us: not yet · Report broken or outdated