1
00:00:00,059 --> 00:00:03,470
Chat keeps a team conversation with its
intended participants.

2
00:00:03,849 --> 00:00:07,019
Open the Chat button at the bottom of the
page where it is available.

3
00:00:07,449 --> 00:00:10,920
The widget shows department and group
channels, including the synthetic

4
00:00:10,920 --> 00:00:14,470
Command and Squad Three groups in our
Firehouse fifty-one department.

5
00:00:14,770 --> 00:00:18,920
Those names describe our training
organization; a search team can use team

6
00:00:18,920 --> 00:00:23,649
groups, a security company site groups, a
mobile response service operational

7
00:00:23,649 --> 00:00:29,139
teams, a wildland contractor crews, and an
industrial department facility groups.

8
00:00:29,530 --> 00:00:31,790
Review the channel audience before
sending.

9
00:00:32,110 --> 00:00:34,709
This is separate from the Assistant
button, which opens

10
00:00:34,709 --> 00:00:36,509
an A I assistance conversation.

11
00:00:36,950 --> 00:00:41,229
Chat availability depends on the deployed
chat feature and department access.

12
00:00:41,500 --> 00:00:44,520
In this lesson the training stack already
has it enabled.

13
00:00:44,880 --> 00:00:47,900
We do not claim that a learning choice or
a module label

14
00:00:47,930 --> 00:00:49,849
activates every rollout feature.

15
00:00:50,050 --> 00:00:52,450
New conversation opens a member picker.

16
00:00:52,880 --> 00:00:56,480
We select only the fictional Matthew Casey
and Kelly Severide.

17
00:00:56,960 --> 00:01:00,500
With multiple recipients, the action
changes to Create group

18
00:01:00,630 --> 00:01:01,930
and a name field appears.

19
00:01:02,340 --> 00:01:05,720
Enter Training, Field coordination, and
create the group.

20
00:01:06,170 --> 00:01:08,940
It appears as a conversation with the
current sender and

21
00:01:08,940 --> 00:01:10,280
the chosen participants.

22
00:01:10,649 --> 00:01:14,299
A department-wide channel and an
explicitly selected conversation

23
00:01:14,340 --> 00:01:15,959
are different audience choices.

24
00:01:16,299 --> 00:01:20,559
For a security site, consider whether the
whole site group needs the message or

25
00:01:20,590 --> 00:01:22,740
only the supervisor and assigned patrol.

26
00:01:23,159 --> 00:01:26,369
For mobile response, choose the actual
operational team.

27
00:01:26,729 --> 00:01:30,349
For search, wildland and industrial
response, choose the people

28
00:01:30,349 --> 00:01:32,159
coordinating the current assignment.

29
00:01:32,569 --> 00:01:36,159
Group creation is not a dispatch
assignment and does not change the

30
00:01:36,159 --> 00:01:38,549
members’ staffing or unit availability.

31
00:01:38,749 --> 00:01:41,100
Enter a concise coordination message.

32
00:01:41,529 --> 00:01:45,620
Our synthetic message says Team Alpha is
preparing for a staging-area

33
00:01:45,620 --> 00:01:49,509
exercise and explicitly separates the
message from dispatch.

34
00:01:49,940 --> 00:01:53,159
Send message adds it to the conversation
with Wallace Boden

35
00:01:53,159 --> 00:01:54,810
as sender and a timestamp.

36
00:01:55,209 --> 00:01:59,379
Reopening the saved conversation after
navigation retains the message.

37
00:01:59,730 --> 00:02:02,859
That proves the message was saved and can
be read in this view.

38
00:02:03,209 --> 00:02:07,519
It does not prove another device received
a push or that the participants read it.

39
00:02:07,970 --> 00:02:12,179
Emoji, G I F and image controls are
visible in the composer;

40
00:02:12,420 --> 00:02:15,699
attachments need their own approved
content and client test.

41
00:02:16,109 --> 00:02:20,650
Keep sensitive personal, clinical, client
and facility details within

42
00:02:20,650 --> 00:02:23,879
your organization’s approved record and
access procedures.

43
00:02:24,170 --> 00:02:28,249
A chat conversation is not a substitute
for an incident record, a roster

44
00:02:28,249 --> 00:02:32,060
declaration or a formal instruction that
needs a different workflow.

45
00:02:32,310 --> 00:02:36,649
For a message that needs an explicit
acknowledgment, select Send as urgent,

46
00:02:36,830 --> 00:02:39,220
requires acknowledgment, before sending.

47
00:02:39,859 --> 00:02:43,660
Our second message asks the two fictional
participants to acknowledge an

48
00:02:43,660 --> 00:02:46,000
accountability briefing for this exercise.

49
00:02:46,399 --> 00:02:51,770
The result displays U R G E N T and zero
of two acknowledged.

50
00:02:52,180 --> 00:02:55,449
Expanding the count in the widget shows
Matthew Casey pending

51
00:02:55,520 --> 00:02:57,360
and Kelly Severide pending.

52
00:02:57,780 --> 00:03:00,780
The count describes the expected
recipients and recorded

53
00:03:00,780 --> 00:03:02,350
acknowledgments for this message.

54
00:03:02,649 --> 00:03:06,730
It does not prove operational readiness,
completion of an assignment, or

55
00:03:06,730 --> 00:03:08,589
independent receipt by a device.

56
00:03:08,960 --> 00:03:12,359
Review how your department follows up when
someone remains pending.

57
00:03:12,789 --> 00:03:16,740
This recording leaves both recipients
pending; it does not simulate a

58
00:03:16,740 --> 00:03:20,629
recipient’s acknowledgment or claim
emergency notification delivery.

59
00:03:20,829 --> 00:03:25,240
Use Reply in thread on the urgent message
to keep follow-up with that message.

60
00:03:25,600 --> 00:03:29,150
The widget changes to Thread, shows the
original message, a

61
00:03:29,150 --> 00:03:31,300
Replies area and a composer.

62
00:03:31,699 --> 00:03:34,800
We add a synthetic clarification that area
Alpha is the

63
00:03:34,800 --> 00:03:36,730
practice sector, then send it.

64
00:03:37,099 --> 00:03:38,929
The thread now shows one reply.

65
00:03:39,429 --> 00:03:42,720
Close thread returns to the main
conversation, where the original

66
00:03:42,720 --> 00:03:47,080
message has a one-reply button and still
shows zero of two acknowledged.

67
00:03:47,470 --> 00:03:50,810
A reply does not perform the message’s
recipient acknowledgment.

68
00:03:51,099 --> 00:03:55,059
The original sender’s follow-up also
cannot stand in for either recipient.

69
00:03:55,450 --> 00:03:59,090
This distinction is useful when a patrol
supervisor clarifies a site

70
00:03:59,090 --> 00:04:03,860
instruction, a search leader clarifies a
sector, or an industrial coordinator

71
00:04:03,860 --> 00:04:06,009
clarifies a facility access point.

72
00:04:06,230 --> 00:04:09,019
Add reaction opens the quick reaction
choices.

73
00:04:09,380 --> 00:04:12,350
We select thumbs-up on the synthetic
urgent message.

74
00:04:12,710 --> 00:04:16,630
The live view did not immediately show the
reaction, so we reload the

75
00:04:16,630 --> 00:04:18,559
page and reopen the conversation.

76
00:04:19,040 --> 00:04:24,639
The saved result now shows one thumbs-up,
one reply and zero of two acknowledged.

77
00:04:24,979 --> 00:04:27,750
A reaction is separate from the
acknowledgment request.

78
00:04:28,119 --> 00:04:31,569
This build also displayed clock values
differently for live and

79
00:04:31,569 --> 00:04:35,500
freshly fetched messages; verify the
display before interpreting

80
00:04:35,500 --> 00:04:37,420
timestamps as local chronology.

81
00:04:37,889 --> 00:04:42,650
The full chat workspace was opened, but at
this normal viewport its message area was

82
00:04:42,650 --> 00:04:44,759
compressed and its thread pane was hidden.

83
00:04:45,079 --> 00:04:47,799
The widget provided a readable working
thread path.

84
00:04:48,090 --> 00:04:51,520
This recording uses that observed path and
leaves full-workspace

85
00:04:51,549 --> 00:04:54,560
layout and other-client verification as
follow-up work.

86
00:04:54,710 --> 00:04:58,489
For community paramedicine and mental
health response, coordinate the

87
00:04:58,489 --> 00:05:02,770
operational team and handover while
maintaining approved record boundaries.

88
00:05:03,219 --> 00:05:07,600
For search and rescue, use team and
staging conversations, with explicit

89
00:05:07,600 --> 00:05:09,820
follow-up for accountability instructions.

90
00:05:10,259 --> 00:05:13,570
For security companies, use site and
patrol groups with the

91
00:05:13,570 --> 00:05:15,420
intended supervisor audience.

92
00:05:15,810 --> 00:05:20,240
For wildland contractors, coordinate crew
and staging information and review

93
00:05:20,240 --> 00:05:22,349
connectivity and fallback procedures.

94
00:05:22,769 --> 00:05:27,640
For industrial emergency teams, coordinate
facility access, equipment issues and

95
00:05:27,640 --> 00:05:29,869
handover with the intended responders.

96
00:05:30,470 --> 00:05:35,090
Your practice exercise is to choose a
channel audience, create a small synthetic

97
00:05:35,090 --> 00:05:40,419
group, send an ordinary message, request
acknowledgment, record a focused thread

98
00:05:40,419 --> 00:05:42,640
reply and inspect the separate counts.

99
00:05:43,059 --> 00:05:45,790
Reopen the conversation to verify
persistence.

100
00:05:46,200 --> 00:05:50,829
Then test authorized recipients on the
actual devices and channels used by

101
00:05:50,829 --> 00:05:54,970
your organization, and record what the
training demonstration has not proved.