June 2026: Critical Communications - Safer setup and sending

What the update is and why it matters

We’ve improved the Critical Comms experience by making configuration issues easier to spot before send. Users now get clearer warnings when required settings are incomplete, and unsafe or incomplete communications can be stopped before they go out.

This matters because Critical Comms is often used in time-sensitive situations. Clearer validation helps teams move faster with more confidence, reduces avoidable mistakes, and improves trust in the sending process.

When to use this

Use this whenever you are:

• creating a new Critical Comms template

• reviewing settings before sending a message

• checking whether a communication is ready to go live

• training new users on Critical Comms workflows

How It Works (High-Level)

The system now checks Critical Comms configuration more clearly during setup and before send. If required settings are missing or incomplete, users see warnings explaining what needs attention. Where needed, the system prevents the communication from being sent until the issue is resolved.

Best practice tips

Review all template settings before relying on a communication in a live situation.
Treat warnings as part of your normal pre-send checklist.
Use a test or dry-run process when creating new templates for important communication types.
Keep template ownership clear so someone is responsible for ongoing review and maintenance.
Revisit older templates periodically to make sure they still reflect your current communication setup.