Templates

Communication

Draft incident updates that are clear and safe

Use Template

By Nalvin

Use Template

Description

Nalvin helps you draft incident updates that are clear, consistent, and safe to share. Based on current incident facts and available ticket/support context, it produces an update with impact, mitigation, and next steps. You can choose to post it in Slack/Teams, draft an email, or publish it to a docs page—always with a review step before sending.

Supported Integrations

Templates are flexible by default. Nalvin automatically picks the right integrations based on what you’ve connected.

HelpDesk

Freshdesk

Asana

ClickUp

Outlook Email

Gmail

Monday

Trello

Google Docs

Zendesk

Intercom

Notion

Email

Shortcut

Linear

Microsoft Teams

Confluence

Jira

Slack

How to best use this template

Below are a few tips & tricks from the Nalvin team to get the most out of this template.

Separate facts from hypotheses

Incidents evolve quickly. Ask Nalvin to label confirmed facts vs best-effort hypotheses so the message stays trustworthy.

Focus on impact and mitigation

Customers and stakeholders care about impact, workarounds, and ETA expectations. Keep the update centered on those, not internal debugging details.

Set an explicit update cadence in the message

Even if the template is on-demand, the update should say when the next update will happen. This reduces inbound pings and anxiety.

Keep a single source of truth link

You can level this up by linking to the incident ticket or doc page. This prevents conflicting narratives across channels.

Never send without review

Have Nalvin draft first, then confirm recipients and channel before posting/sending. This protects against mistakes in high-pressure moments.

Separate facts from hypotheses

Incidents evolve quickly. Ask Nalvin to label confirmed facts vs best-effort hypotheses so the message stays trustworthy.

Focus on impact and mitigation

Customers and stakeholders care about impact, workarounds, and ETA expectations. Keep the update centered on those, not internal debugging details.

Set an explicit update cadence in the message

Even if the template is on-demand, the update should say when the next update will happen. This reduces inbound pings and anxiety.

Keep a single source of truth link

You can level this up by linking to the incident ticket or doc page. This prevents conflicting narratives across channels.

Never send without review

Have Nalvin draft first, then confirm recipients and channel before posting/sending. This protects against mistakes in high-pressure moments.