The AI layer
Panic is unstructured. Your board isn't
In an emergency, information arrives as panicked free text and half sentences. Muster's AI layer turns it into structure, answers the commander's questions from live data, and writes the paperwork before anyone asks for it. Running on Claude, scoped to your tenant.
01 · SOS triageIn drills today
“my leg is pinned” is not a status code.
Nobody replies with clean keywords mid-emergency. Give the triage layer a fragmented reply and it pulls out intent, injury, and location, then lands it on the board as a structured needs-help flag.
This runs in drills today. A real inbound text is still matched on keywords, SAFE, OK, SOS, and putting triage on the live carrier path is the next piece of work.
- Injury
- leg pinned, cannot walk
- Location
- annex, east side
- Escalation
- responders notified
02 · Incident copilot
Ask the board. It answers from live data.
Mid-event, the commander types a question in plain language. The copilot answers through a read-only tool loop over the live event: the muster summary, the roster, the escalation state. It can see everything and change nothing, and it never leaves your tenant.
who is still missing at the north lot?
03 · After-action narrative
The report writes its own summary.
The moment you stand down, the resolved event gets a written narrative: what happened, how fast people responded, who needed help and how it was handled. The paragraph your insurer, your executives, and your OSHA log all want, as a side effect of resolving the event.
04 · Drafted instructions
The right words, under pressure.
One tap drafts the evacuation instruction, phrased to be read on a phone while walking. A real draft from the live system:
“Leave the building now by the nearest safe exit and do not stop to collect belongings. Go straight to your assembly point and wait there for a headcount.”
The honest part
Boundaries, stated plainly.
- Tenant-scoped, read-only. The copilot reads your event data through scoped tools and cannot take actions or see other tenants.
- Never trained on. Requests run through the Claude API, which does not train on API data.
- Never in the critical path. Alerts, check-ins, and escalation run without AI. If the AI layer is ever unavailable, the platform does not blink.
- Triage is not on the carrier path yet. Free-text triage runs in drills. A real inbound text is matched on keywords today, and connecting the two is the next piece of work. The copilot, the narrative, and the drafting are live now.
- Not on every plan. The AI layer is a module your instance has to have switched on, and it needs an API key configured on your own server.
Watch it run a drill, triage and all.
Fifteen minutes, phones out, no slides.