Everything the triage desk does in Trailwinds Dispatch, in the order a night actually happens: take the call, create the assignment, watch it accepted, handle the decline, and pull the numbers the next morning.
Four roles, and each one sees a different app. Roles are set by an administrator under Admin → Staff, and they are enforced on our servers — not just hidden on screen.
| Role | Where they work | What they can do |
|---|---|---|
| Triage | Web dashboard | Create assignments, reassign, re-page, defer, edit, cancel. Sees the live board, the staff roster, and reports. |
| Admin on call | Web dashboard + iPhone | Everything triage can do, plus setup: staff accounts and roles, the patient list, and the organization's escalation and response settings. |
| Field nurse | iPhone app | Receives assignments, accepts or declines, confirms arrival, completes the visit. The web dashboard shows a nurse-only account a pointer to the app. |
| Leadership | Web dashboard | The same live board, read-only — no action buttons — plus the full reports section. |
Every screenshot in this guide comes from a demonstration system. The patients, nurses, addresses, and phone numbers in it are invented — no real patient information appears anywhere on this page.
Access is invitation-only: an administrator adds your work email first, and there is no public sign-up. The first time you use a computer, you sign in with a code we email you.

One screen holds the whole night: the queue on the left, your service area in the middle, and the selected visit on the right. Nothing here refreshes on a timer — it changes the moment something changes.

The counters are the first thing to read: open is everything live, declined and escalated appear in red and amber only when they are not zero, and active and deferred sit quietly beside them. The teal button on the right creates a new assignment.


This is the screen you fill in while the family is still on the phone. It follows the order you already think in — who, where, what kind, how urgent, who goes — and the whole thing is one send.


The visit moves through the same five states every time, and every step is stamped with the second it happened.
| State | What it means | Who sets it |
|---|---|---|
| Assigned | Sent to the nurse; the acceptance clock is running. | You |
| Accepted | The nurse has it and is coming. | The nurse, one tap |
| En route | They are driving. | The nurse |
| Arrived | They are at the door. The phone may prompt when it detects arrival, but the nurse confirms it. | The nurse |
| Completed | Visit finished; the record closes and moves to History. | The nurse |
If nobody accepts, Trailwinds alerts your on-call chain at five minutes and again at ten — the exact numbers are yours to set under Admin → Organization. The card’s timer changes colour as each alert fires, the escalation is written into the visit timeline, and it stays on the report the next morning whether or not anyone remembers it happened.
A decline is not a failure — it is information arriving early. It lands back on your board immediately, with the reason attached.


Three smaller actions live under the panel's main button. Each one keeps the record honest about what happened.



Anything worth remembering about a visit belongs on the visit, not in a phone call nobody wrote down.
The dispatch board answers what is happening to the visits. This one answers who you have tonight and what they are carrying.

Everything here is an aggregate — counts and times, no patient details — which is why it is safe to put in front of a board or a surveyor.

Tonight and This weekend follow on-call windows rather than calendar days: tonight runs 5 PM to 8 AM, the weekend runs Friday 5 PM to Monday 8 AM. 30 days and Custom do what they say.
Every closed visit, searchable, with the full record behind each row.


Everything you set up once lives behind the dark Admin button: your people, your patients, and the numbers that govern escalation and response.



| Setting | Default | What it controls |
|---|---|---|
| First alert | 5 minutes | How long an unaccepted visit waits before the on-call chain is alerted. |
| Second alert | 10 minutes | The second, louder alert. |
| Response targets | 15 / 30 / 60 minutes | Reporting goals for immediate, urgent, and routine. They colour the metrics; they never block a dispatch. |
| Arrival prompt radius | 150 metres | How close a nurse must be before their phone offers to mark them arrived. |
| Ping every | 5–10 minutes | How often a phone reports its position while sharing is active. |
| Keep positions | 60 days | How long position history is kept before it is deleted automatically. |
| Tracking policy | Per your agency | Whether sharing follows on-call hours or runs continuously on company devices. |
| Remember a computer | 7 days | How long before a verified computer has to use an emailed code again. |
Personal settings hang off your initials in the top-right corner, not the main menu — they are yours, not a place you work.


A short list, because the things a dispatch platform refuses to do matter as much as its features.
Most of what goes sideways on a night shift has a two-line answer.
The iPhone side — accepting, declining, navigating, confirming arrival, and completing a visit — is covered in the nurse app guide, which is also available as a PDF to print or email to your on-call staff.
Still stuck? Your administrator is the fastest route; anything they cannot answer comes to us.