Production incident?

This route pages an on-call engineer directly, day or night.

Use this if

Your customers are seeing errors or an outage

Data is being lost, duplicated or corrupted

You suspect a security incident or exposed credential

Anything else — including things that are annoying but not urgent — belongs in normal support, which is faster than you would expect.

+31 10 421 8899

Quote this reference

ws_studioform · plan_scale

Europe · Rotterdam

On call right now

4 minutes

Average pickup, last 90 days

If it turns out not to be an incident, that is genuinely fine. We would rather be woken for a false alarm than read about a real one in the morning.

">

The prompt

Create an urgent support escalation panel with Tailwind CSS. Use a max-w-lg card with a red-tinted header strip holding a warning glyph, a heading reading "Production incident?" and a line stating this route wakes an on-call engineer. The body starts with a bordered checklist of three criteria that qualify — customer-facing outage, data loss risk, or a security incident — each with a check glyph, followed by a muted line asking people to use normal support otherwise, with a link. Then a phone number as a large monospaced link, a "Start a priority chat" dark button and a copyable incident reference in a bordered row. Under it, a two-column block giving the current on-call region and the average pickup time. Finish with a muted footnote about false alarms being fine and never held against anyone.

Paste it into Claude, Cursor, v0 or any AI coding tool. Prefer the finished markup? .

More contact prompts

All Contact prompts →