9:41●●● 100%

‹

Notes and Escalation WO-000046-1

🎤

Save

Notes

Create action

History

Capture what changed, who needs to know, and whether work can continue

Voice-ready Route to dispatcher

Note summary

Customer had a party on the weekend and system usage was unusually high.

Route to

Dispatcher queue▾

Impact on job

Informational only▾

Recent activity

📝

Technician note recorded

Created by Maxwell Baker · 4 minutes ago

📣

Dispatcher review requested

Waiting on acknowledgement

Save note and continue

Create follow-up action

Mobile adaptation — Notes, Exceptions, and Escalation

The original activity model is CRM-like, but the technician should not experience it as administrative overhead. This screen keeps notes short, voice-driven, and tied to operational routing decisions such as whether dispatch or the back office needs to intervene.

What this screen simplifies

One note form with routing and impact is enough for most field exceptions.
Operational routing is built into the same action, not split across note creation and task creation.
The technician can save and continue instead of getting trapped in a secondary process.

Voice examples

🎤"Customer says the issue got worse after the weekend party, route this to dispatch as informational."

🎤"Create a follow-up action for sales to review replacement options."

Wireframe · Step 36 — Notes, Exceptions, and Escalation

Mobile adaptation — Notes, Exceptions, and Escalation

What this screen simplifies

Voice examples