We are now bringing two new home screen widgets. One shows who is on call right now and until when. The other shows your open incidents. Both work on iOS and Android, and you pick what each one tracks.
Inside the app, the incident page has a status timeline in the activity log. You can see who moved an incident from acknowledged to resolved and when they did it. Adding a note is much nicer now.
We also cleaned up dropdowns, animated how incidents move between states, and fixed a few activity log bugs that had been hanging around.
If you want a different app icon, there are new ones to choose from.
Notes are being used about ten times more than they were five months ago. You are writing more in them, and writing them with each other, so we rebuilt Notes around that.
The editor is rich text now and it takes Markdown. The writing area is much larger, so a long note stays readable while you write it.
Pin a note
You can pin a note to an incident. Open the incident and the pinned note is right there, so whoever picks it up next starts with the context instead of reading the whole thread for it.
Attachments
Incidents and notes now take attachments, in any file format. Most of what people wanted to add was a screenshot, and videos and documents come up often too, so all of it can go straight on the incident.
Reference other incidents
Reference an incident in a note with @ID and the two are linked. Open an incident and you can see every note that mentions it, which is how you find the last time this happened and what fixed it.
More improvements
Every note keeps its edit history.
You can delete a note.
Mention a teammate and they get a mobile notification, a Slack DM, and a Microsoft Teams DM.
Status pages now support nested components. Put a component under a parent and report an incident on exactly the part that is affected.
Take our own status page. Alerts is a component. Under it sit Phone alerts, SMS alerts, and Email alerts. When SMS delivery breaks, we mark SMS alerts as down. Phone and Email stay green.
Any component can be a parent, a child, or both. There is no limit, and you can reorder them.
When a child's status changes, the parent updates on its own.
Pick the affected child component when you publish an incident from Spike to your status page.
The status page API now carries the parent and child relationship on components.
We rebuilt the Slack app from the ground up. The headline is Spike AI: mention @Spike in any thread and run your incident response in plain language. Plus a leaner alert layout and richer link previews.
If your workspace is already connected, you need to reconnect. The new app adds Slack scopes, and reconnecting is how you pick them up. Head to the Slack connect page → to do it in a few clicks.
Here is everything new in the new app for Slack.
Spike AI, in any thread
This is the big one. Mention @Spike in any Slack thread and get things done in plain language. No slash commands, no syntax to memorize. It reads the thread and acts on it.
Declare an incident, or turn an existing thread into one.
Add or remove responders on the fly.
Add overrides when plans change.
Check who is on call and list open incidents.
Ask questions about your account and get an answer in the thread.
Spike AI turns any conversation into the place you run the incident from.
Incident alerts
Handle an incident without leaving the alert. Acknowledge, resolve, add a note, or spin up an incident channel right from the message. The layout is leaner, so the actions you reach for are front and center.
Fetch the activity log to see what happened and when.
Open the full incident payload inside Slack.
Create a Statuspage incident and link it back to the alert.
We also shipped a new template for incident alerts, so every alert reads clearly at a glance.
On-call alerts
Add an override straight from the on-call alert. If you cannot take a shift, hand it off in a click without opening the dashboard.
Link unfurling
Paste an incident link and Slack expands it into a rich preview. Everyone in the channel gets the context without clicking through.
You can change incident details from the preview too, so a link becomes a place to act, not just a reference.
When you open an incident, you'll find a cleaner layout focused on the title and message. All the key actions: acknowledge, unacknowledge, resolve, and escalate are at the top.
Add a resolution note and resolve in one action. Or add a note to an open incident and resolve it later.
Escalating an acknowledged incident now prompts you to unacknowledge and escalate in one click. Acknowledged incidents pause escalation alerts.
Improved view of how repeated and suppressed incidents were resolved previously.
Quick actions panel: resolve, change severity and priority, jump to the integration or escalation.
Create a status page incident with a custom message, make the incident public, start a conference call, or create a Linear or Jira ticket.
The payload view is redesigned. Copy any key, search with /, view as JSON, and copy the full payload. You can also add links to the incident.
The activity log has filters and sorting. Escalation alerts are grouped by level so you can see how far an incident escalated.
Comments and notes are merged into a single Note. Tag teammates with @name and link incidents with @ID.
Press Command+K to run common actions from the incident page.
On-call
The on-call page puts the calendar front and center. No more scrolling to reach it.
Switch between month, week, and day views using keyboard shortcuts.
Filter the calendar to show only your shifts.
Add overrides by clicking a shift to overwrite it, or drag across empty dates to create one. Remove overrides directly from the calendar.
Switch between on-calls with Command+K or by clicking the schedule name.
Open All Schedules to see everyone's shifts. Filter by your own shifts or by a specific schedule.
Layer configuration is in a compact panel. Open it to view layers, swap members, and reorder.
Connected escalations are accessible from the same view.
Contact the current on-call member via email or call.
Navigating to the right escalation policy is faster now. Use the left panel to switch between policies. Filter by on-call schedule, user, integration, or number of levels.
Editing is faster too. You can make changes easily. Undo or redo changes at any point, and a full history of edits is available.
Each level now shows how many minutes after trigger it runs, and the total escalation duration.
You can now use Change Integration in Alert Routing Rules to automatically route incidents to the right integration and team.
For example, an incident comes in under the API integration. But if its title contains "payments", Spike routes it to the Payments integration and alerts the payments team instead.
This way, the right team always gets paged with the right context. And over time, you can see which integrations receive the most incidents.
We also added two new routing conditions: Incident suppressed and Incident suppressed within a time window.
You can use these to switch integrations when an incident gets suppressed too many times.
For example, if an incident is suppressed 5 times, Spike can move it from the API integration to the Payments integration and start alerting the right team.
We added a new action in Alert Routing Rules called Route to other teams.
Now, when an incident comes in, you can automatically route it to the team that owns it.
For example, if Ops team picks up a security incident, you can route it to the Security team instead.
To set it up:
Toggle Route to other teams
Pick the destination team
Save the rule
You can also change the incident’s priority and severity while routing.
Once the incident is routed, the destination team’s escalation policies and alert rules take over, so the right people get alerted based on how that team works.
