Skip to main content

Mobile Incident View

Respond to incidents on the move with the mobile-optimised interface.

Incidents do not wait for you to be at your desk. CrownSync Playbooks provides a mobile-optimised interface that allows you to respond to incidents from your phone or tablet, ensuring you can take immediate action wherever you are. The mobile view retains the core functionality of the desktop experience while adapting the layout for smaller screens.

Accessing the Mobile View

The mobile view activates automatically when you access CrownSync Playbooks from a device with a smaller screen. There is no separate mobile application to install — simply open pb.crownsync.uk in your mobile browser and sign in as normal. The platform is a responsive web application that adapts to your screen size.

For the best experience on mobile, we recommend:

  • Using a modern browser such as Safari (iOS) or Chrome (Android)
  • Adding the site to your home screen for quick access during emergencies
  • Ensuring push notifications are enabled in your browser settings for real-time alerts

Checklist Mode

The most valuable mobile feature during an incident is checklist mode. When viewing a playbook in the context of an active incident, each section's action items are presented as a tappable checklist optimised for one-handed use.

In checklist mode:

  • Each action item displays as a large, touch-friendly row with a checkbox
  • Tapping a checkbox marks the action as complete and logs it to the incident timeline automatically
  • Completed items are visually distinguished but remain visible so you can track progress through the phase
  • You can swipe between phases rather than scrolling through the entire playbook

Add to home screen

For the fastest access during an incident, add CrownSync Playbooks to your phone's home screen. On iOS, tap the share button in Safari and select “Add to Home Screen”. On Android, tap the browser menu and select “Add to Home screen”. This creates an app-like shortcut you can reach in a single tap.

Quick Action Logging

The mobile interface includes a persistent Quick Log button at the bottom of the screen when viewing an active incident. Tapping this button opens a simplified action logging form with:

  • A text field for the action description
  • A toggle for marking the action as a key decision
  • A camera button to quickly take and attach a photo as evidence
  • A submit button that logs the action with the current timestamp

The quick log form is designed for speed. The timestamp is set automatically, and the “performed by” field defaults to you. For more detailed entries, use the full action logging form available from the timeline view.

Tap-to-Call Contacts

During an incident, you may need to contact key personnel, regulators, or third parties urgently. The mobile view displays contact information from your organisation profile and the active playbook as tappable phone links. Tapping a phone number initiates a call directly from your device.

Tap-to-call is available for:

  • The incident lead and response team members
  • Escalation contacts defined in your organisation profile
  • Regulatory body helplines (e.g., ICO breach reporting line, Action Fraud)
  • Your cyber insurance provider's incident hotline (if configured)
  • External forensic investigators (if listed in your playbook contacts)

What Is Different on Mobile

While the mobile view covers the essential incident response functionality, some features are better suited to the desktop experience:

  • Content editing— The split-view markdown editor is not available on mobile. Section editing is best done on a desktop or tablet.
  • PDF export— PDF generation is available but the preview is limited on smaller screens. Exports can still be triggered and downloaded.
  • Version history diffs— Side-by-side diff comparison requires a wider screen. On mobile, diffs are shown in a stacked layout.
  • Admin functions— Team management and organisation settings are accessible but optimised for desktop use.

The mobile view prioritises the actions most needed during an active incident: viewing playbook steps, logging actions, checking the timeline, and contacting key people.

Was this page helpful?