Resilion · Communications

Who hears what, when, and why

Resilion keeps every party on a project on the right thread — the project owner, contractors, insurance liaisons, and government liaisons each get the notifications that match their role, the channels they can actually read, and a permanent audit trail that ties every notification back to the underlying record.

Talk to us about communications Disaster response →

Philosophy

Role-based, audit-ready notifications

Resilion treats notifications as part of the record, not as a side effect. Each message is tied to a specific asset, milestone, policy, or activation event; the recipient list is derived from the project party roles, not from ad-hoc mailing lists; and every send is logged in the audit chain so a reviewer can answer "who was told what, when" without chasing inboxes.

Tablet-to-phone dispatch handoff: a coordinator hands a hot briefing onto a contractor phone in the field.

Bundled stock — replace with client-authorized dispatch photo via /dashboard/media.

Tablet → phone

Briefing handoffs that the audit chain can read

The coordinator hands off a hot briefing to a contractor in the field. The handoff is logged on the audit chain with role, channel, and recipient — so the next reviewer can answer ‘who was told what, when’ without chasing inboxes.

Roles and what they get

Each project party receives notifications derived from their role. The mapping is published; the underlying queue is governed by the audit chain.

Project owner

The owner receives every noteworthy event on their project — captures, dispatch, scope changes, milestone closes, share approvals, escalations — so the project narrative stays coherent end-to-end.

When notified

Every project mutation; daily digest; milestone transitions; share approval requests; overdue inspections; escalation triggers.

Contractor

Contractors see only what is actionable for them: their dispatch assignments, scheduled windows, deadline risk tied to their scope, signature requirements, and post-event inspection sweeps.

When notified

Role-assigned dispatches and field assignments; signing documents; inspections due on enrolled assets; dispatch reassignments.

Insurance liaison

Insurance liaisons see claim-relevant events: estimated vs. actual reconciliation, milestone closures that affect the claim, deadline risk on claim milestones, exported claim packages.

When notified

Claim-package exports; milestone approvals affecting the claim; reconciliation deltas; FMIT pulls; deadline risk on claim-blocking milestones.

Government liaison

Government liaisons see compliance-relevant events on emergency access and grant deployments: activations opened/closed, grants approved or revoked, response activity in declared disaster regions.

When notified

Resilion Responds activations in their declared regions; grants approved or revoked on their activation; response activity summaries.

Channels

Each party reads from the channel they prefer — every channel rides the same audit-logged escalation.

In-app alerts

Persistent alerts inside Resilion that surface on the project dashboard, the asset timeline, and the user's inbox tab.

Always on, structured, sortable — no inbox search needed
Threaded on the underlying project / asset / milestone
Visible to other approved parties on the same record
Archived with the project for the full retention window

SMS escalations

Time-critical escalations (deadline risk, missed inspection, blocked milestone) route to SMS when the recipient is configured to receive them.

Escalation tone only — never the primary channel
Recipient opt-in per role; governed by the project preferences
Carries a deep-link back to the underlying Resilion record
Logged alongside the in-app alert in the audit trail

Email summaries

Daily and weekly digests plus ad-hoc alerts (share approval, signature needed, escalation) ship to the party contact on file.

Templates render in the recipient's preferred language
Each link points back to a specific record — no 'click here' ambiguity
Subject prefixes let operators route inbound replies
Delivered through the signed, audit-logged Resilion email proxy

Disaster response

Communications during a declared activation

When a major disaster is declared, Resilion Responds changes the comms tempo: free full-access accounts are activated for the affected municipalities, relief organizations, and government emergency managers; government liaisons on those activations see live response activity; insurance liaisons see claim-package exports against the activation's assets.

Resilion Responds →See Resilion pricing →

Comms tempo

Minutes, not days

During a Resilion Responds activation, government liaisons see live response activity and insurance liaisons see claim-package exports against the activation’s assets — every send pinned to the audit chain.

FAQ

Frequently asked questions

Who decides who receives each notification?

The party roster is set when the project is created and on every party change. Resilion derives each party's notification preferences from their role on the project — project owners see everything, contractors see their assignments, insurance liaisons see claim-relevant events, government liaisons see compliance-relevant events.

Can a project mute a notification type?

Per-project preferences let operators and project owners throttle digests and silence specific categories. Critical-path notifications (deadline risk, share approval, signature required) are never silenced — the audit chain requires they reach the responsible party.

Where do SMS escalations come from?

SMS is escalation-only — never the primary channel. Recipients opt in per role, governed by the project preferences. Every SMS log line is paired with the same record in the audit chain so reviewers can prove what was escalated and when.

How can I confirm what was sent during a response?

Open the project's audit log — every notification dispatched through Resilion (in-app, SMS, email) appears there with timestamp, recipient party, and template. The audit log is the source of truth for "who heard what, when."