Crisis Communication Platform

Single composition interface for messages that will be sent across multiple channels simultaneously -- SMS, push notification via a registered public app, email, and social media posts. Channel-specific formatting within a single compose workflow: the message content adapted to the character limits and formatting conventions of each channel while maintaining a consistent core message. Channel selection per message -- some messages sent to all channels, some to responder push only, some to public SMS and social only -- configured at the point of compose without switching between systems. Sender identity management ensuring that messages sent from the platform appear to come from the organisation's established sender identity on each channel -- your short code for SMS, your verified account for social media, your domain for email. Scheduled message management for pre-planned communications -- the message composed in advance, scheduled for the planned send time, and released automatically or held for manual confirmation depending on the operational context.

Geographic message targeting enabling a message to be sent to all registered subscribers within a defined geographic area -- drawn on a map as a polygon, defined by a cordon radius, or specified by postcode sector -- without maintaining separate address lists for every possible combination of affected area. Dynamic area definition -- the affected area drawn on the map during the incident rather than selected from a pre-defined list, so the targeting reflects the actual incident geography rather than a pre-planned zone that may not match. Postcode sector targeting for situations where the communication needs to align with local authority ward boundaries, emergency planning zones, or postal sectors used in public-facing communications. Registered subscriber management for the public notification database -- how residents and businesses opt in to receive alerts for their area, how their location and channel preferences are stored, and how they opt out. Real-time recipient count showing the number of registered subscribers within the defined geographic area before the message is sent, so the communications team knows the expected reach before dispatch.

Template library of pre-approved message content for common incident types -- flooding, severe weather, road closures, utility outages, public health alerts, and evacuation notices -- each template reviewed and approved by the communications lead before an incident occurs, removing the drafting and approval burden during the incident itself. Template variable management enabling each template to include placeholder variables -- the affected area name, the duration of the restriction, the contact number for enquiries -- that are filled in at the point of use without amending the approved template text. Template versioning retaining previous template versions with their approval status and effective dates, so the template library reflects current approved content without losing the history of what was previously approved. Template categorisation by incident type, affected group, and channel, enabling the communications operator to quickly find the relevant template during an incident without searching through an uncategorised list. Template authorisation workflow for new and revised templates -- the draft reviewed by the communications lead and the legal or policy advisor, approved, and published to the library before it is available for incident use.

Acknowledgement tracking for messages sent to responder networks -- each responder's receipt and read confirmation recorded against the message, so the incident commander knows who has received the operational update and who has not. Unacknowledged recipient list accessible to the communications operator at any time after send -- showing the names of recipients who have not yet acknowledged, with the elapsed time since the message was sent. Chase functionality sending a reminder to unacknowledged recipients after a defined period -- reducing the need for individual phone calls to confirm that the operational message has been received. Role-group acknowledgement reporting showing acknowledgement rates by organisation, by role, or by operational sector -- so the incident commander can see whether a specific agency's responders have received the update rather than checking individual names. Acknowledgement audit log recording, for every message sent to responders, the complete list of recipients, the time each acknowledgement was received, and the device used -- the evidence base for post-incident review and for any subsequent inquiry into the adequacy of responder communication.

Stakeholder briefing record management for communications with elected officials, partner agencies, utility companies, transport operators, and other organisations with a role in the incident response or a need for regular updates. Briefing schedule management -- the planned times for media briefings and stakeholder updates defined at the start of the incident, with the briefing content prepared and reviewed before each scheduled briefing time. Media enquiry logging recording the enquiries received from journalists, the organisation that made the enquiry, the enquiry content, the person who responded, and the response given -- creating a complete record of media interactions for the post-incident communications review. Holding statement management for situations where the organisation is not yet in a position to provide a full statement -- the holding statement approved, distributed, and recorded, with the time of issue and the distribution list documented. Briefing pack generation assembling the current situation summary, the key messages, the supporting statistics, and the media line into a briefing document for the spokesperson in the format required for the briefing type.

Complete audit log of every message sent through the platform -- the message content, the send time, the channel used, the geographic targeting parameters, the number of recipients reached, and the sender. Delivery confirmation data from each channel carrier -- SMS delivery receipts, push notification delivery confirmations, email open and bounce data -- aggregated against the message record. Failed delivery reporting identifying where messages have not been delivered -- phone numbers that have been disconnected, email addresses that have bounced, push notification tokens that are no longer active -- for follow-up through alternative channels or for contact database maintenance. Regulatory compliance documentation for public emergency alerts where delivery evidence is required by the regulating authority -- the audit log provides the structured evidence of what was sent, to how many people, and at what time. Post-incident communication report generated from the audit log summarising the communications activity during the incident -- number of messages sent, total recipients reached, channel breakdown, and timeline from incident declaration to first public message.