Page, the incident comms Grok Bot
Incident communication Grok Bot template. Writes the status page update and the customer email during an outage: what broke, who is affected, what you are doing, next update at a stated time.
About this engineering Grok Bot template
Page is the incident communication Grok Bot for what customers read while something is broken. The first update goes out within minutes rather than when the cause is known, because silence is the most damaging thing in an incident and a nearly empty update beats a complete one an hour later.
It writes impact in what somebody cannot do rather than in internal terms, says what is still working since in most incidents most things are, gives the workaround at the top if there is one, and states the next update as a clock time and then keeps that promise even when there is nothing new. At resolution it answers the question every update forgets: what happened to anything in flight, lost or queued or duplicated. Afterwards it writes the note with a timeline, what made the incident last as long as it did, and specific commitments with dates, never blaming a person and never promising it will not happen again.
Use Page the moment an incident starts, before the cause is known. Repro and Diff are the Grok Bots for the engineering side, and Desk for the tickets the incident generates. The first update going out in minutes rather than when you have answers is the single decision that decides how customers remember an outage, and it is the one teams get wrong under pressure.
Mentioned above: Diff Code Review Bot, Repro Bug Bot, Desk Support Bot. Or see every Engineering Grok Bot.
What to ask it
- Write the first status update. We do not know the cause yet.
- Nothing has changed. Write the update anyway.
- We are fixed. Write the resolution, including what happened to queued jobs.
- Write the post incident note without blaming anybody.
- Give support one line to use so twelve people do not improvise twelve.
How to install this Grok Bot template
- Copy the template. You get the name, the description and the instructions.
- In Grok Bot, choose New, then Create new agent.
- Open Bot actions, then Edit Profile, and paste the name and the description.
- Paste the instructions.
- Switch on Web browsing. It needs no routines.
Or skip all five: add Page Incident Bot to Grok Bot in one click, using Grok Bot's own share as template link.
Questions about this Grok Bot
When should the first status update go out?
Within minutes, before the cause is known. This incident Grok Bot writes what is not working, who is affected, that you are investigating, and the clock time of the next update.
What if there is nothing new to say?
You post anyway. No change yet, next update at 15:30 is a real update and it keeps the trust that silence destroys.
Will it speculate about the cause?
Never in public before it is confirmed. A wrong cause published in an update is remembered longer than the outage.
What does the post incident note include?
A timeline in clock times, what broke, what made it last as long as it did, and specific changes with dates. Never human error as a cause, and never a promise it will not recur.
Design templates for your tool
Page Incident Bot works alongside the vibe coding tool you already build in, and the same licence covers the design templates for it: Lovable templates, Bolt templates, Replit templates, Claude Code templates, ChatGPT Codex templates, Cursor templates, Windsurf templates, Framer templates, v0 templates and Cline templates.
Included in the BrowserMoon licence, alongside every design template and all 51 Grok Bot templates. One licence, unlimited projects, including work you sell.
More Engineering Grok Bot templates
View allDiff, the code review Grok Bot
Findings ranked by blast radius
Repro, the bug report Grok Bot
Reproduces it, writes the report, stops
Query, the SQL Grok Bot
A query that runs, with the assumption named
Probe, the QA Grok Bot
The paths a human would miss, as a checklist that can fail
Browse Grok Bot templates