WEBVTT

00:00:00.059 --> 00:00:03.480
Pending calls let dispatchers prepare a record before releasing

00:00:03.480 --> 00:00:05.010
it to selected responders.

00:00:05.389 --> 00:00:08.699
This walkthrough uses one clearly marked software exercise

00:00:08.699 --> 00:00:09.899
in a fictional department.

00:00:10.449 --> 00:00:12.579
Open Calls and choose New Call.

00:00:13.050 --> 00:00:18.360
Enter a recognizable Name and a concise Nature, then review Priority and Type.

00:00:18.809 --> 00:00:21.040
We select Routine and Investigation.

00:00:21.430 --> 00:00:25.309
The location and destination remain blank in this small example; for

00:00:25.309 --> 00:00:28.850
your own work, complete the fields your department requires and use an

00:00:28.899 --> 00:00:31.170
accurate, permitted incident location.

00:00:31.389 --> 00:00:34.709
Turn on Save as pending, do not dispatch yet.

00:00:35.199 --> 00:00:37.340
Read the explanation beside the switch.

00:00:37.840 --> 00:00:41.490
The call will be saved and numbered, with any selected recipients

00:00:41.490 --> 00:00:43.460
retained as a proposed dispatch.

00:00:43.849 --> 00:00:47.470
Saving a pending record and dispatching it are separate decisions.

00:00:47.829 --> 00:00:52.419
This is useful when a dispatcher needs to finish a nonurgent request or review

00:00:52.419 --> 00:00:54.589
its recipient list before releasing it.

00:00:54.759 --> 00:00:57.000
Open Select Recipients and search for

00:00:57.000 --> 00:00:59.000
Wallace Boden, our fictional member.

00:00:59.439 --> 00:01:02.040
Check his row and leave Everyone unchecked.

00:01:02.450 --> 00:01:04.220
The picker shows one selected.

00:01:04.659 --> 00:01:07.810
Choose Confirm to return that proposed selection to the form.

00:01:08.259 --> 00:01:12.199
At the bottom, verify one selected, the pending switch and the

00:01:12.199 --> 00:01:14.039
full Save Pending Call button.

00:01:14.480 --> 00:01:17.000
Check the exact title and description before

00:01:17.000 --> 00:01:18.480
choosing Save Pending Call.

00:01:18.810 --> 00:01:21.939
The member selected here is still part of the proposed list.

00:01:22.150 --> 00:01:24.869
The app opens the pending queue with a numbered row.

00:01:25.270 --> 00:01:29.049
Its narrow columns shorten the name and number, so open the row

00:01:29.049 --> 00:01:30.619
to read the complete identity.

00:01:31.059 --> 00:01:36.590
This example is F D fifty one, twenty twenty six, zero zero zero seven.

00:01:37.090 --> 00:01:40.319
Call Details says Pending, not yet dispatched.

00:01:40.760 --> 00:01:43.989
Open Dispatched and you can already see Wallace Boden.

00:01:44.440 --> 00:01:47.819
While the pending banner remains, that tab shows the proposed

00:01:47.819 --> 00:01:51.770
recipient; its title alone does not mean the call has been released.

00:01:51.959 --> 00:01:55.380
Return to Pending Calls and choose Dispatch for that record.

00:01:55.840 --> 00:01:59.200
Review the proposed member in Select Dispatch Recipients.

00:01:59.559 --> 00:02:04.420
Here we clear Boden once: the count becomes zero and Confirm is disabled.

00:02:04.800 --> 00:02:09.309
Select him again and verify one selected, with Everyone still unchecked.

00:02:09.690 --> 00:02:12.469
Review this final choice before pressing Confirm.

00:02:12.879 --> 00:02:15.960
This is the action that releases the waiting call to the selected

00:02:15.960 --> 00:02:20.010
recipient, so use the same care you would when making a new dispatch.

00:02:20.080 --> 00:02:22.099
Check the result in two places.

00:02:22.470 --> 00:02:25.360
The pending queue now says No pending calls.

00:02:25.699 --> 00:02:30.540
In the same saved call, Dispatched lists Wallace Boden, with Command as his

00:02:30.540 --> 00:02:32.779
group and User as the recipient type.

00:02:33.080 --> 00:02:37.149
The pending banner is gone, and Dispatch additional resources is available.

00:02:37.440 --> 00:02:39.159
We leave that separate action alone.

00:02:39.580 --> 00:02:42.930
These checks confirm the recorded dispatch state and selected

00:02:42.930 --> 00:02:44.409
recipient inside the app.

00:02:44.619 --> 00:02:49.659
To finish this exercise, check its title and number, then choose Close Call.

00:02:50.179 --> 00:02:53.980
Select Closed under Close Type and enter a Close Note that

00:02:53.980 --> 00:02:55.780
identifies the training activity.

00:02:56.179 --> 00:02:59.589
Turn off Notify everyone on the call for this local cleanup.

00:03:00.129 --> 00:03:03.670
Read back the type, complete note and switch before selecting

00:03:03.670 --> 00:03:05.310
the final Close Call button.

00:03:05.769 --> 00:03:09.689
Close only your exercise record; keep unrelated incidents and

00:03:09.689 --> 00:03:11.189
their command boards intact.

00:03:11.319 --> 00:03:14.440
The console returns to three active training calls, with

00:03:14.440 --> 00:03:16.299
zero pending and zero scheduled.

00:03:16.749 --> 00:03:21.120
Search for our exercise name: the call panel shows No active calls while

00:03:21.120 --> 00:03:22.950
the department total remains three.

00:03:23.300 --> 00:03:26.200
A warehouse search still finds the original incident.

00:03:26.559 --> 00:03:30.329
Our exercise record also remains readable in Call Details, with

00:03:30.329 --> 00:03:32.140
its Close Call action removed.

00:03:32.470 --> 00:03:33.880
Clear the search when finished.

00:03:34.220 --> 00:03:38.429
The same prepare and review pattern can serve fire and EMS, community

00:03:38.429 --> 00:03:42.810
care and mental health teams, search and rescue, security, wildland

00:03:42.810 --> 00:03:45.129
contractors, and industrial teams.

00:03:45.469 --> 00:03:50.000
This browser exercise confirms these application records; it does not establish

00:03:50.000 --> 00:03:54.230
notification delivery, a physical response or native device behavior.
