How it works

Injects

Injects are the scripted events that drive the scenario forward — a customer email, a SIEM alert, a regulator's call. They're scheduled in advance and arrive on the clock.

What an inject is

Each inject is authored when the simulation is built. It has a trigger time (how many minutes into the exercise it fires) and a target— the role (or roles) it's addressed to. When its moment arrives, it's delivered to that target.

How injects reach you

Key rule

Injects arrive privately to the addressee. The war room is for central communication and shows the reaction — not the raw inject.

In other words: a scenario event lands with the person (or AI role) it's meant for, the same way a real email or alert would reach one desk first. What the rest of the team sees is how that person chooses to respond. This keeps the exercise realistic — information is distributed, not broadcast, and part of the challenge is deciding what to share and when.

Addressed to you (a human) — the inject appears in your private facilitator chat. You read it, then decide how to act in the war room.
Addressed to an AI role — the AI receives it and reacts in the war room. You see its response, not the original inject text.

Messages sent in your name

Some injects are written as if they come froma role. If that role is played by a human, the facilitator delivers the message to its recipients on that person's behalf and privately lets them know it went out in their name — so nobody is surprised by a message they didn't type.

What this means for you

If something lands in your facilitator chat, treat it as yours to handle. Decide what the team needs to know, and bring that into the war room in your own words.