xAI says its AI support bot cleared 204 tickets in about 10 minutes

xAI says an AI support bot cleared 204 customer tickets in about 10 minutes during a September 18 incident, with a support engineer reviewing and approving the batch. In an October 20 disclosure, the company explained how it uses Grok Bot to spot possible incidents and handle the customer-response backlog, while keeping key decisions with people.

The result comes from IncidentSweep, one of two incident-focused bots described by Chris Bowie and Isaac Hopkinson in the company’s post. The other, IncidentWatch, looks for clusters of customer complaints that may signal a problem. Together, they cover two different jobs: noticing a possible incident and making sure affected customers receive a response after it is resolved.

xAI says its previous options were to answer those tickets individually over several hours or use a bulk response with less control over who received it. IncidentSweep is designed to combine batch sending with ticket-level screening. The September result is a company-reported example, not an independently verified performance measure.

Customer complaints become an early warning

The detection side starts in the support queue. xAI says customers sometimes report problems before its internal engineering alerts fire. IncidentWatch checks the previous 15 minutes of tickets every five minutes, looking for a spike in reports about the same issue. Its input is the pattern across customer reports, not a declaration that an incident has occurred.

When the pattern does not match a known incident, IncidentWatch alerts the on-call support engineer. The alert includes the apparent problem, a count of matching tickets and examples to investigate. A support engineer decides whether the reports indicate an incident and works with engineering to investigate; the bot does not make that decision.

Meanwhile, IncidentWatch holds tickets that clearly match the issue. Once the team confirms the incident, it posts the problem to its public status page. Support Bot, the company’s main customer-facing bot, then checks the held tickets against the confirmed incident and replies to matching customers. It can return with updates as the incident progresses.

One approval, a defined set of customers

IncidentSweep takes over the backlog work after an incident is resolved. A support engineer first specifies which tickets to consider, which to exclude and exactly what message to send. That gives the bot a defined selection job and a supplied response, rather than leaving it to choose both the audience and the wording on its own.

The bot finds matching tickets and reviews each one. It sets aside any ticket it cannot confidently connect to the incident, then presents the proposed batch and the exact outgoing message. Before anything is sent, the engineer can spot-check included tickets and make changes.

After approval, IncidentSweep sends the message in small batches and records each action. If anything fails, it stops and reports what happened.