Templatizing communications



For this section, it helps to refer back to past examples of stakeholder communications that were considered effective and useful. Look for the patterns in those messages as a starting place for determining internal stakeholder messaging needs.

In order to be effective during an incident, internal stakeholder communications must be both accurate and fast. Templatizing and automating notifications ahead of a major incident can help you move fast and minimize errors.

For example, emails can be generated from templates that include: - Boilerplate language to use when talking to customers about an incident - Helpful resources that recipients can use to drill down for more information - Other information handy for helping them understand how to react to the incident.

Templates can include things like: - Links to incident details - Links to internal status pages - Information about how to join the incident response chat channel or call bridge.

Making communication templates may seem tricky to some because many incident details aren’t known in advance. For those unknowable details, create placeholders in your templates. Incident detail placeholders may include things like:

Other details relevant to internal stakeholders are known well in advance of an incident and these boilerplate items can be statically included in your templates. These details may change depending on the service, so you may have one template per service or per variation of known failure modes within a service. Templates can contain static details for items like:

The exact specifics for what belongs in your templates depends not just on the needs of your stakeholders, but also on the communication mechanism you've chosen to use for distribution. Some mechanisms, like SMS notifications, may have practical limits on message length. If you have to limit the length of notifications, let your stakeholders know where to go for more detailed information (email, status page, chat, etc).