WEBVTT

00:00:00.000 --> 00:00:01.750
Start in Department Settings.

00:00:02.170 --> 00:00:05.969
Open Calls & Dispatch and choose Call & Dispatch Settings.

00:00:06.489 --> 00:00:10.069
This lesson follows the complete setup of a Personnel check-in rule,

00:00:10.340 --> 00:00:12.579
then tests it on one fictional call.

00:00:13.069 --> 00:00:17.120
Check-ins help coordinators organize agreed reporting updates, including

00:00:17.120 --> 00:00:20.360
community care visits and mental health response assignments.

00:00:20.770 --> 00:00:24.510
Department administrators configure the rules; operators use the

00:00:24.510 --> 00:00:26.270
resulting timers and history.

00:00:26.400 --> 00:00:28.329
Find Check-In Timer Settings.

00:00:28.820 --> 00:00:32.280
Auto-Enable Check-In Timers for New Calls controls whether new

00:00:32.280 --> 00:00:34.139
calls start with timers enabled.

00:00:34.549 --> 00:00:36.500
It is off in this training department.

00:00:36.799 --> 00:00:40.490
We leave it off and explicitly enable one practice call later.

00:00:40.799 --> 00:00:43.719
This separates department-wide enablement from the reporting

00:00:43.719 --> 00:00:47.979
interval and from the decision to use timers on an individual incident.

00:00:48.109 --> 00:00:52.440
Under Add New Default Timer, choose Personnel as the Target Type.

00:00:52.909 --> 00:00:56.930
Set Duration to thirty minutes and Warning Threshold to five minutes.

00:00:57.290 --> 00:00:58.819
Leave Enabled selected.

00:00:59.269 --> 00:01:04.450
Active States can restrict when a timer applies; leaving it empty uses All States.

00:01:04.819 --> 00:01:08.000
Review the values, then select Add Timer Config.

00:01:08.420 --> 00:01:12.409
Use intervals and state filters that your department has agreed for its work.

00:01:12.560 --> 00:01:17.239
Verify the saved Personnel row in Default Timer Configurations: thirty

00:01:17.239 --> 00:01:22.830
minutes, a five-minute warning threshold, Enabled Yes, and Active States All.

00:01:23.280 --> 00:01:27.219
This default applies when an enabled timer has no matching override.

00:01:27.690 --> 00:01:30.629
The warning threshold defines how close to the due time the

00:01:30.629 --> 00:01:32.469
server marks a timer as Warning.

00:01:32.859 --> 00:01:36.670
Here that window is the final five minutes of the thirty-minute interval.

00:01:37.070 --> 00:01:39.840
An overdue timer has reached its reporting deadline.

00:01:40.250 --> 00:01:43.789
Check the resulting behavior in the applications your department uses.

00:01:43.979 --> 00:01:48.320
Use Add New Override for a rule tied to a call type or priority.

00:01:48.700 --> 00:01:54.140
Here Call Type ID is Rescue, Call Priority is Any, Target Type is

00:01:54.140 --> 00:01:58.789
Personnel, Duration is forty-five minutes, and Warning Threshold is ten.

00:01:59.270 --> 00:02:02.729
We clear Enabled to save this example in a disabled state.

00:02:03.129 --> 00:02:04.629
Active States is empty.

00:02:05.010 --> 00:02:08.569
Select Add Override after reviewing the scope and values.

00:02:08.779 --> 00:02:11.539
Review Call Type / Priority Overrides.

00:02:11.970 --> 00:02:16.209
The Rescue row now shows forty-five minutes, ten warning minutes, and

00:02:16.259 --> 00:02:19.140
Enabled No, so that example is inactive.

00:02:19.520 --> 00:02:23.539
The existing Investigation Personnel rule is enabled for sixty minutes

00:02:23.610 --> 00:02:25.340
with a five-minute warning threshold.

00:02:25.740 --> 00:02:29.039
Matching enabled overrides take precedence over the default.

00:02:29.359 --> 00:02:32.879
We will use Investigation to test that sixty-minute rule while

00:02:32.879 --> 00:02:34.810
retaining the thirty-minute default.

00:02:34.960 --> 00:02:39.880
On New Call, enter a clear training Name and choose the intended Priority and Type.

00:02:40.349 --> 00:02:43.640
Our type is Investigation and the priority is Routine.

00:02:44.159 --> 00:02:48.149
The Call Identifier gives this exercise another recognizable reference.

00:02:48.489 --> 00:02:52.480
Keep the scenario fictional and identify it clearly so other operators

00:02:52.480 --> 00:02:54.289
can distinguish it from normal work.

00:02:54.660 --> 00:02:58.140
We use a supplied fictional location for this software exercise.

00:02:58.349 --> 00:03:01.820
In Personnel, select Wallace Boden for this practice call.

00:03:02.240 --> 00:03:06.559
Review the selected row rather than assuming a station, role, or group

00:03:06.559 --> 00:03:08.320
contains the intended recipient.

00:03:08.700 --> 00:03:12.530
For a real rollout, test with an agreed training audience first.

00:03:12.880 --> 00:03:17.070
A call may have several participants, so the recipient scope matters when you

00:03:17.070 --> 00:03:19.219
review which personnel timers appear.

00:03:19.430 --> 00:03:23.070
Near the bottom of the form, select Enable Check-In Timers.

00:03:23.430 --> 00:03:27.639
This is the per-call choice we planned while automatic enablement remained off.

00:03:28.009 --> 00:03:31.269
Review the rest of the call and its recipients, then choose

00:03:31.380 --> 00:03:32.950
Create and Dispatch Call.

00:03:33.370 --> 00:03:36.900
Saving timer configuration alone does not opt this call into

00:03:36.900 --> 00:03:41.019
timers; this checkbox makes that choice explicit for the exercise.

00:03:41.239 --> 00:03:44.090
Open the new call and inspect Check-In Timers.

00:03:44.580 --> 00:03:49.260
Wallace Boden has a Personnel timer, the state is OK, and Time Remaining

00:03:49.290 --> 00:03:51.050
is just under sixty minutes.

00:03:51.420 --> 00:03:54.880
This call uses the enabled Investigation override rather

00:03:54.880 --> 00:03:56.340
than the thirty-minute default.

00:03:56.800 --> 00:04:00.700
Open Show Check-In History to inspect the saved entries; this

00:04:00.700 --> 00:04:02.730
new exercise initially has none.

00:04:03.249 --> 00:04:07.109
This readback checks the effect of the configuration on an actual call.

00:04:07.350 --> 00:04:09.619
The Check In dialog provides a Note field.

00:04:10.149 --> 00:04:13.149
Enter a concise update under your department procedure,

00:04:13.459 --> 00:04:15.460
review it, and select Check In.

00:04:16.109 --> 00:04:20.059
Our note identifies a software practice check-in for this timer lesson.

00:04:20.420 --> 00:04:23.980
It makes no claim about physical arrival or device location.

00:04:24.429 --> 00:04:27.579
The note belongs to the check-in record, so it should explain

00:04:27.579 --> 00:04:30.870
the update clearly enough for another coordinator to understand.

00:04:31.110 --> 00:04:34.220
Review the timer and saved history after confirmation.

00:04:34.599 --> 00:04:38.550
The table shows Timestamp, Who, Type, and Note.

00:04:38.969 --> 00:04:42.779
Our new Personnel entry contains the exact practice note we entered.

00:04:43.130 --> 00:04:45.199
The timer has begun a new interval.

00:04:45.529 --> 00:04:48.749
Checking the saved history distinguishes a completed update

00:04:48.749 --> 00:04:50.390
from text left in a dialog.

00:04:50.810 --> 00:04:55.839
Keep status reporting, check-in reporting, and any physical safety verification under

00:04:55.839 --> 00:04:57.910
their appropriate department procedures.

00:04:57.999 --> 00:05:00.240
Finish the exercise through Close Call.

00:05:00.720 --> 00:05:05.570
Review Completed Type, Send Notification, and Completed Notes.

00:05:06.020 --> 00:05:10.649
We use Closed, leave Send Notification off for this local practice, and

00:05:10.649 --> 00:05:12.470
record a clear completion note.

00:05:12.890 --> 00:05:14.549
Then select Close Call.

00:05:15.010 --> 00:05:18.940
Review these choices for your own audience: the notification option

00:05:18.940 --> 00:05:22.329
changes whether the closing event is sent to the call participants.

00:05:22.479 --> 00:05:26.769
Verify that the call now shows Closed and the expected Completed Notes.

00:05:27.179 --> 00:05:30.229
Its saved check-in history remains available for review.

00:05:30.780 --> 00:05:34.879
The same configuration and verification habits apply to search and rescue,

00:05:35.120 --> 00:05:40.510
security companies, wildland contractors, and industrial response teams: choose

00:05:40.510 --> 00:05:44.299
the reporting target, agree the interval, test the matching rule,

00:05:44.559 --> 00:05:48.459
and check the resulting record before extending the setup to everyday work.
