1
00:00:00,070 --> 00:00:04,079
The Assistant opens a conversation with
the system, while Chat opens

2
00:00:04,079 --> 00:00:06,059
conversations with department members.

3
00:00:06,570 --> 00:00:08,850
Use the Assistant button where it is
available.

4
00:00:09,439 --> 00:00:13,590
In this synthetic department, Wallace
Boden asks where to configure custom

5
00:00:13,590 --> 00:00:17,370
unit statuses and how their labels differ
from their base meanings.

6
00:00:17,920 --> 00:00:22,180
Reopening the saved conversation shows the
original question and a reply

7
00:00:22,180 --> 00:00:26,010
saying the command was not understood,
with a suggestion to send HELP.

8
00:00:26,500 --> 00:00:28,270
That is the behavior we observed.

9
00:00:28,729 --> 00:00:32,770
It is not an answer to the configuration
question and does not demonstrate

10
00:00:32,770 --> 00:00:34,630
natural-language A I guidance.

11
00:00:35,200 --> 00:00:39,020
A system can expose an Assistant entry
point without every provider,

12
00:00:39,049 --> 00:00:41,069
feature or model being available.

13
00:00:41,529 --> 00:00:45,360
Start with the supported help path, and
inspect the owning configuration

14
00:00:45,360 --> 00:00:47,479
screen before acting on guidance.

15
00:00:47,670 --> 00:00:50,449
Open Assistant Settings from Department
Settings.

16
00:00:50,869 --> 00:00:53,869
The page separates ordinary department
controls from the

17
00:00:53,869 --> 00:00:55,660
bring-your-own-provider section.

18
00:00:56,070 --> 00:00:59,770
Enable Assistant controls whether
department members may interact with it.

19
00:01:00,259 --> 00:01:04,509
Allowed Platforms accepts a
comma-separated list, with an asterisk

20
00:01:04,540 --> 00:01:06,350
allowing all listed platforms.

21
00:01:06,720 --> 00:01:10,499
The page lists WebChat alongside external
messaging platforms.

22
00:01:10,819 --> 00:01:14,690
Selecting a name does not configure that
platform’s credentials, connect

23
00:01:14,690 --> 00:01:16,870
a bot or prove message delivery.

24
00:01:17,270 --> 00:01:21,289
In this lesson we use WebChat only in the
isolated training stack.

25
00:01:21,629 --> 00:01:25,769
A search organization might begin with a
browser-based coordination exercise,

26
00:01:26,050 --> 00:01:30,030
while a security company might review its
site communications channels separately.

27
00:01:30,419 --> 00:01:34,509
Choose the scope that your organization
can configure and verify, rather

28
00:01:34,509 --> 00:01:37,590
than assuming every channel is available
from this one field.

29
00:01:37,789 --> 00:01:41,870
We enable Assistant, set Allowed Platforms
to WebChat and

30
00:01:41,870 --> 00:01:43,999
enable Confirm Status Changes.

31
00:01:44,350 --> 00:01:48,919
We leave Allow Dispatch via Assistant off,
Confirm Phone Linking on

32
00:01:49,129 --> 00:01:51,270
and Proactive Notifications off.

33
00:01:51,669 --> 00:01:54,190
Save produces the saved-settings banner.

34
00:01:54,509 --> 00:01:56,659
Reloading the page retains the values.

35
00:01:56,979 --> 00:01:59,880
That verifies persistence of these
department settings.

36
00:02:00,350 --> 00:02:03,680
Confirm Status Changes is intended to
require explicit

37
00:02:03,680 --> 00:02:07,669
confirmation before destructive or
status-changing actions; this

38
00:02:07,669 --> 00:02:09,710
recording does not run such an action.

39
00:02:10,140 --> 00:02:14,050
Confirm Phone Linking relates to an S M S
account-linking confirmation,

40
00:02:14,269 --> 00:02:15,699
which we do not exercise.

41
00:02:16,079 --> 00:02:20,160
The per-user and per-department
message-rate fields remain blank, so the

42
00:02:20,160 --> 00:02:22,489
screen says the system default applies.

43
00:02:22,809 --> 00:02:24,410
We do not measure those limits.

44
00:02:24,800 --> 00:02:29,000
Review access, confirmations and rate
policy before broader rollout,

45
00:02:29,289 --> 00:02:32,710
and test the actual behavior with approved
synthetic actions.

46
00:02:32,939 --> 00:02:37,610
The bring-your-own-provider section says
Enhanced A I is required to connect

47
00:02:37,640 --> 00:02:41,369
a department’s provider subscription or
compatible model endpoint.

48
00:02:41,829 --> 00:02:44,730
In this stack, the add-on could not be
confirmed and the

49
00:02:44,730 --> 00:02:46,449
provider controls are disabled.

50
00:02:46,850 --> 00:02:48,449
No provider key is stored.

51
00:02:49,000 --> 00:02:52,720
The visible endpoint guidance calls for H
T T P S and a public

52
00:02:52,720 --> 00:02:56,910
address, and the model field asks for the
provider’s exact model name.

53
00:02:57,330 --> 00:03:01,519
Those are configuration requirements, not
evidence of a working connection.

54
00:03:01,990 --> 00:03:06,069
Connecting a provider can change where
department messages are processed, so the

55
00:03:06,069 --> 00:03:09,880
account owner must review the intended
data flow and provider agreement.

56
00:03:10,330 --> 00:03:14,630
This lesson does not verify provider
connectivity, data routing, paid

57
00:03:14,630 --> 00:03:17,330
entitlement or an A I-generated answer.

58
00:03:17,729 --> 00:03:21,549
Record those prerequisites explicitly
instead of treating the department

59
00:03:21,549 --> 00:03:23,780
enable switch as proof that they are met.

60
00:03:23,920 --> 00:03:26,320
Send HELP in the Assistant conversation.

61
00:03:26,769 --> 00:03:31,800
The saved reply says to text a command or
HELP followed by a topic for details.

62
00:03:32,230 --> 00:03:39,470
Its listed topics are status, staffing,
calls, messages, units, shifts, calendar,

63
00:03:39,680 --> 00:03:42,010
personnel, departments and stop.

64
00:03:42,479 --> 00:03:45,559
This gives a supported command vocabulary
for this deployment.

65
00:03:46,079 --> 00:03:49,899
Read topic help before any command that
can change a state, send a

66
00:03:49,899 --> 00:03:52,149
communication or create an assignment.

67
00:03:52,719 --> 00:03:55,909
In this recording the live message
remained marked Sending,

68
00:03:56,179 --> 00:03:59,489
so we closed and reopened the widget to
inspect saved history.

69
00:03:59,920 --> 00:04:02,620
The question and reply then appeared with
timestamps.

70
00:04:03,010 --> 00:04:05,820
That verifies the saved help response in
this view.

71
00:04:06,129 --> 00:04:11,129
It does not verify another device, another
platform or a future command’s result.

72
00:04:11,579 --> 00:04:14,710
Keep the supported vocabulary and any
client limitation

73
00:04:14,710 --> 00:04:15,949
visible in the walkthrough.

74
00:04:16,159 --> 00:04:19,400
Send CALLS, the read-only topic listed in
help.

75
00:04:19,929 --> 00:04:24,109
After reopening the conversation, the
Assistant returns Active Calls for

76
00:04:24,109 --> 00:04:28,489
Firehouse fifty-one, Training Department,
with the three seeded training calls.

77
00:04:28,939 --> 00:04:32,479
Each entry includes a call number and
shortened title and description.

78
00:04:32,879 --> 00:04:35,950
The completed dispatch-settings exercise
is not listed.

79
00:04:36,430 --> 00:04:40,469
This is an observed operational query
against the synthetic department; it

80
00:04:40,469 --> 00:04:42,559
does not create or dispatch a call.

81
00:04:42,950 --> 00:04:46,469
Inspect the underlying call record when
you need full text, current

82
00:04:46,469 --> 00:04:48,360
assignment or supporting evidence.

83
00:04:48,790 --> 00:04:52,889
The widget also retained an Assistant is
typing indicator after the reply

84
00:04:52,889 --> 00:04:56,579
was visible, so do not interpret that
indicator as a reliable

85
00:04:56,579 --> 00:04:58,470
completion signal in this recording.

86
00:04:58,880 --> 00:05:00,930
The saved content is the evidence.

87
00:05:01,349 --> 00:05:05,759
Natural-language reasoning and an external
messaging channel remain separate tests.

88
00:05:05,910 --> 00:05:09,429
For community paramedicine and mental
health teams, a supported

89
00:05:09,429 --> 00:05:13,600
query can help locate operational response
information; the Assistant

90
00:05:13,649 --> 00:05:15,709
is not clinical decision support.

91
00:05:16,230 --> 00:05:19,980
Search and rescue leaders can inspect
active search calls and then open the

92
00:05:19,980 --> 00:05:22,419
source record for full assignment details.

93
00:05:22,829 --> 00:05:26,829
Security supervisors can inspect active
site activity and verify

94
00:05:26,860 --> 00:05:29,200
access and scope before wider use.

95
00:05:29,600 --> 00:05:33,469
Wildland contractors can review active
assignment information while checking

96
00:05:33,469 --> 00:05:35,669
connectivity and current source records.

97
00:05:36,020 --> 00:05:39,209
Industrial teams can find response
activity and verify

98
00:05:39,209 --> 00:05:42,639
facility procedures and equipment evidence
on the owning screens.

99
00:05:43,189 --> 00:05:48,110
Your exercise is to choose one verified
platform, save and reopen a bounded

100
00:05:48,110 --> 00:05:53,029
configuration, run HELP, run an authorized
read-only query and compare

101
00:05:53,029 --> 00:05:54,670
the reply with the source records.

102
00:05:55,049 --> 00:05:59,049
Document provider prerequisites, client
behavior and every action

103
00:05:59,049 --> 00:06:00,790
still awaiting a separate test.