Search blocks by description or jump to a page.
A left aligned header above five numbered phases in a horizontal stepper, each with a time chip and short note, plus a last incident line.
The source for every Marketing block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Incident Response Steps lays out what your company actually does when something breaks. A left aligned header frames the runbook honestly, then five numbered phases run across a horizontal stepper joined by hairlines: detect, contain, assess, notify, and publish. Each phase carries a time commitment chip and a single sentence of what happens, so the whole response reads as a timeline rather than a promise. A quiet line beneath cites the last time the runbook ran for real, which turns the process into a track record.
The five phases live in one typed array, and the connecting hairline is drawn between steps automatically, so adding or reordering a phase never breaks the stepper. Everything runs on theme tokens with no icons or images, which keeps the section light and consistent in light and dark mode.
Reach for this block when a buyer, especially an enterprise or regulated one, wants to know how you behave during an incident, not just how you prevent one. It belongs on a security or trust page, ideally right after the preventive controls, where a reviewer moves from what you protect to how you react when protection fails. The time chips make the section concrete, and the last incident line signals that you publish postmortems rather than bury them.
A natural flow around it on a Marketing Pro page:
Before
After
The obvious fit is your incident response runbook with per phase timelines. A few other ways to use the frame:
Tip: keep the last incident line real and specific. A concrete date and duration reads as confidence, while a vague reassurance reads as a company that has something to hide.