Loading
Because arrival order is not urgency, and the distinction matters more than in most support operations. A shared mailbox has no priority, no clock and no owner, so what gets answered first is what was seen first.
And the alternative — giving every agent full visibility so they can judge — creates a data-access problem that is worse than the triage one.
Priorities and routing rules act on the request rather than on its arrival time, so urgent categories reach the right queue immediately with their own clock.
Permissions are per field: an agent handling an appointment query sees what the query needs, and every access to a restricted field is recorded permanently.
It is not a clinical triage system and must not be used as one. Its priorities are operational categories that you define.
And it holds no clinical record — it references the account, deliberately, and does not become a second store.
The same platform runs internal HR and IT queues through Nest's HR helpdesk and Desk's service management, on the same permission model rather than a second tool with second rules.
Escalations keep their history, so a case that moves between teams does not restart.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
It holds none. Access to any restricted field is per field and recorded.
No. Priorities are operational categories you define, and it must not be used clinically.
Yes, on the same permission model, with Nest's HR helpdesk.
Half an hour on your own numbers is usually enough to say whether Desk is the right place to start.