Skip to guide content
Browse all guides
Mobile appResponders

Mobile field basics

Sign in on iPhone, choose the right department, handle notifications, and understand offline queues.

7 minVerified guidanceReviewed Jul 13, 2026Synthetic examples only
Procom mobile app sign-in screen running on an iPhone simulator
The mobile app uses the same Procom account and department access.View full size(opens in a new tab)

Sign in with your Procom account

Use the same individual account as the web application. Confirm the active department before opening field information.

Procom mobile app sign-in screen running on an iPhone simulator
The mobile app uses the same Procom account and department access.View full size(opens in a new tab)

Allow operational notifications

When prompted, allow notifications if your department uses Procom for dispatch or shift alerts. Opening a supported notification routes to the related incident, PCR, protocol, or schedule view.

Understand offline data boundaries

Cached protocols and queued submissions are isolated to the signed-in user and active department. Keep the app open long enough to sync when connectivity returns.

Let queued submissions retry safely

Do not recreate an execution simply because the first submission occurred offline. Procom keeps a stable submission identifier and retries the queued item in order.

Protect shared devices

Sign out before handing the device to another person. Signing out clears user-scoped protected and offline state.

Keep support material free of protected information

These examples use synthetic records. Never capture or send patient information, passwords, API keys, access tokens, or real incident details when asking for help.