1
00:00:00,050 --> 00:00:02,384
Todd Kane: Every MSP I talk to
is working out how much of the

2
00:00:02,385 --> 00:00:04,033
help desk to hand over to AI.

3
00:00:04,103 --> 00:00:08,359
My guest has spent two decades training
service teams, and he has the data

4
00:00:08,707 --> 00:00:11,990
on what happens when a customer
needs a person and can't reach one.

5
00:00:12,376 --> 00:00:16,526
Jeff Toister courses have been
taken by more than five million

6
00:00:16,528 --> 00:00:17,985
people on LinkedIn Learning.

7
00:00:18,220 --> 00:00:22,000
His new book, Human Service: The
Skills AI Can't Replace, is built

8
00:00:22,002 --> 00:00:27,778
on research from over 370,000 phone
calls, and he calls it a pro-AI book.

9
00:00:28,205 --> 00:00:32,269
We get into which tickets your
techs should hand, uh, handle,

10
00:00:32,297 --> 00:00:36,955
and what goes to a bot, and why
making a human easy to reach pushes

11
00:00:36,966 --> 00:00:38,926
more clients towards self-service.

12
00:00:39,050 --> 00:00:41,168
Jeff, welcome to the
Evolved Radio Podcast.

13
00:00:41,817 --> 00:00:42,998
Jeff Toister: Hey Todd, how are you?

14
00:00:43,569 --> 00:00:44,422
Todd Kane: I'm very well.

15
00:00:44,741 --> 00:00:45,318
Great to see you

16
00:00:46,038 --> 00:00:46,981
Jeff Toister: Good to see you as well.

17
00:00:47,351 --> 00:00:51,080
Which, it just strikes me as odd people
are listening and they're like, "I, I

18
00:00:51,083 --> 00:00:52,854
can't see either of you." But you should.

19
00:00:52,858 --> 00:00:53,782
You should be watching us

20
00:00:54,150 --> 00:00:54,427
Todd Kane: Yeah, yeah.

21
00:00:54,444 --> 00:00:55,069
Jeff Toister: your mind's eye

22
00:00:55,622 --> 00:00:59,102
Todd Kane: you can check out the, the,
the YouTube feed if you like, if you

23
00:00:59,102 --> 00:01:01,057
wanna see our smiley faces as well.

24
00:01:01,533 --> 00:01:05,051
Uh, but, uh, we… otherwise
we are in people's ears coming

25
00:01:05,051 --> 00:01:07,774
to them about AI and service.

26
00:01:07,792 --> 00:01:13,437
You, uh, you and I connected years
and years ago, uh, and we had sort of

27
00:01:13,439 --> 00:01:17,710
this common theme of, uh, you doing
a lot of the work in more enterprise

28
00:01:17,761 --> 00:01:21,923
space helpdesk to, and service, and
that's the space that I actually

29
00:01:21,924 --> 00:01:27,217
came from before I kind of found,
uh, the majority of my career in MSP.

30
00:01:27,578 --> 00:01:30,957
But I think a lot of this is incredibly
relevant because I've always felt

31
00:01:30,958 --> 00:01:35,949
that the work that I do in both the
operations that I did working inside

32
00:01:35,949 --> 00:01:41,019
of IT organizations and MSPs was really
lending from what I learnt in enterprise

33
00:01:41,048 --> 00:01:43,265
and trying to apply it in an SMB space.

34
00:01:43,643 --> 00:01:47,912
And I think, uh, the, the conversation
today is, is sort of a retreading of

35
00:01:47,912 --> 00:01:53,253
exactly that, is what are we seeing at--
we can learn at an enterprise level that

36
00:01:53,256 --> 00:02:00,576
should be applied at SMB and the MSP
space about the human and AI interface?

37
00:02:00,607 --> 00:02:04,568
This is, as I noted in the open, this is
something that's coming up a lot, right?

38
00:02:04,594 --> 00:02:09,041
Like I, I, I was initially a little
concerned at how slow the a- the adoption

39
00:02:09,383 --> 00:02:13,981
of AI was in MSPs, but it's starting
to come a little more fast and furious.

40
00:02:14,387 --> 00:02:17,948
But there's a lot of sort of
hand-wringing and consternation about

41
00:02:18,169 --> 00:02:19,768
what is the right approach here.

42
00:02:19,813 --> 00:02:23,385
And I've seen the tale of
two MSPs here, for example.

43
00:02:23,642 --> 00:02:27,225
One organization, you know,
we will not use any type of

44
00:02:27,225 --> 00:02:29,662
AI in user-facing activities.

45
00:02:29,993 --> 00:02:34,003
And then we had another MSP that I
saw, you know, e- they went to the,

46
00:02:34,030 --> 00:02:37,143
the full extent where, like, they
didn't even pick up the phone anymore.

47
00:02:37,178 --> 00:02:39,513
The AI was answering the phone
for them, and I was like,

48
00:02:39,804 --> 00:02:40,643
"How does that work for you?"

49
00:02:40,643 --> 00:02:43,460
And they're like, "Clients love it."
I was like, "Really?" Like, I was

50
00:02:43,460 --> 00:02:45,378
actually really surprised by that.

51
00:02:45,643 --> 00:02:49,564
So I find, like, the ground is
very shaky on this about, like,

52
00:02:49,569 --> 00:02:51,686
what people could and should do.

53
00:02:51,703 --> 00:02:55,362
So I'm, I'm excited to get your
perspective on this because you've

54
00:02:55,363 --> 00:02:59,349
got a lot of data, a lot of history
that, uh, I think informs this.

55
00:02:59,357 --> 00:03:03,141
So maybe, uh, all of that to say,
we can start with kind of your

56
00:03:03,143 --> 00:03:09,186
thesis on this of like the interface
between human service, and AI?

57
00:03:09,297 --> 00:03:13,228
Or, uh, maybe to start, what is h-
how do you define human service as

58
00:03:13,230 --> 00:03:14,690
the sort of the title of the book?

59
00:03:15,602 --> 00:03:17,607
Jeff Toister: So human service,
that's a good… I think that

60
00:03:17,607 --> 00:03:18,576
is a good place to start.

61
00:03:18,609 --> 00:03:22,564
It, it's, it's any service
in any environment that

62
00:03:22,577 --> 00:03:25,285
involves uniquely human skills.

63
00:03:25,649 --> 00:03:31,175
So a few examples of those would be
connection, that ability to just build

64
00:03:31,175 --> 00:03:34,509
rapport with someone that you're serving
so they like you and they trust you a

65
00:03:34,510 --> 00:03:36,953
little bit better, or understanding.

66
00:03:37,079 --> 00:03:41,263
A- and understanding goes beyond just,
let's say, finding the root of the issue.

67
00:03:41,487 --> 00:03:45,550
You know, "My computer's not working," but
it's understanding the intent behind it.

68
00:03:45,873 --> 00:03:48,493
"My computer's not working, and
I have a big client presentation,

69
00:03:48,550 --> 00:03:52,755
and I'm worried about not landing
the deal." And then advocacy.

70
00:03:52,880 --> 00:03:57,648
Advocacy means I'm working on your
behalf to try to get a result.

71
00:03:58,185 --> 00:04:00,496
A- and so those are things that humans do.

72
00:04:00,545 --> 00:04:06,070
Now, I think there is a very important
distinction between human service and

73
00:04:06,365 --> 00:04:11,091
people who are providing service, but
they're not using human qualities.

74
00:04:11,121 --> 00:04:13,187
So these are people who
are very transactional.

75
00:04:13,198 --> 00:04:16,960
They're, they're almost
trying to impersonate a robot.

76
00:04:17,014 --> 00:04:21,270
I mean, they're, they're trying to be
AI without the capability, and that's

77
00:04:21,485 --> 00:04:24,720
what I found writing the book is that
that's kind of the worst place to be.

78
00:04:25,301 --> 00:04:28,225
I, I don't want an
uncaring, inefficient human.

79
00:04:28,986 --> 00:04:32,329
So it's a better choice to say,
"Can I automate this and automate it

80
00:04:32,330 --> 00:04:39,087
effectively?" Or in these specific
situations, will a human add extra value?

81
00:04:41,210 --> 00:04:42,232
Todd Kane: I think this is huge, right?

82
00:04:42,234 --> 00:04:44,886
Because, uh, I think you get to the
heart of the problem that we see in a

83
00:04:44,888 --> 00:04:50,260
lot of tech industry is highly logical
people, you know, not terribly emotive.

84
00:04:50,350 --> 00:04:53,751
Em- empathy is something you sort of
have to, like, teach them and train them

85
00:04:53,751 --> 00:04:56,816
to some extent, and that- that's not--
that's a broad generalization, but I

86
00:04:56,818 --> 00:04:58,534
think it's also generally kind of true.

87
00:04:58,957 --> 00:05:03,251
Um, and, you know, this gets to sort
of the fundamental disconnect, I think,

88
00:05:03,256 --> 00:05:08,621
at a lot of service desks with around
IT is, uh, you know, I'm here to solve

89
00:05:08,621 --> 00:05:12,478
a problem, not to be your best friend,
and I think there is obviously a

90
00:05:12,490 --> 00:05:15,948
middle ground in that, especially when
you're doing, you, know, phone support.

91
00:05:16,369 --> 00:05:18,972
Uh, you're interacting with
someone, you're talking to them.

92
00:05:18,973 --> 00:05:22,105
There, there is obviously an
emotional and human connection

93
00:05:22,107 --> 00:05:23,619
because they're frustrated.

94
00:05:23,619 --> 00:05:26,422
Something doesn't work, and
most people are mystified by

95
00:05:26,426 --> 00:05:27,658
technology, and they kinda hate it.

96
00:05:28,042 --> 00:05:32,640
And the, the technical, uh, sort of wizard
on the other end of this is just like,

97
00:05:33,098 --> 00:05:34,680
uh, "Yeah, yeah, I know what this is.

98
00:05:34,682 --> 00:05:36,338
Hang on, let me get this
fixed for you right?

99
00:05:36,366 --> 00:05:39,945
And they, like, they're just not
interfacing with the humanity on the

100
00:05:39,945 --> 00:05:44,057
other end of the line here or sending
them an email and not recognizing how they

101
00:05:44,058 --> 00:05:48,900
come across, like what the, the implied
intonation in how you write something.

102
00:05:48,911 --> 00:05:51,568
Or the one that drives me the
most crazy is like, "Hey, did

103
00:05:51,568 --> 00:05:52,695
you call that client back?"

104
00:05:52,696 --> 00:05:54,949
They're like, "No, I don't have an
answer for them yet." Well, like,

105
00:05:55,401 --> 00:05:57,220
call them back and let them know that.

106
00:05:57,232 --> 00:06:00,107
Like, that's a part of this
communication that is necessary

107
00:06:00,107 --> 00:06:01,588
to service them as a human, right?

108
00:06:03,288 --> 00:06:06,983
Jeff Toister: I think you, you hit
upon a big challenge and, and it, it's

109
00:06:06,984 --> 00:06:11,125
made worse in a way because we're in a
world that thinks in terms of tickets.

110
00:06:11,651 --> 00:06:15,505
So we, we've taken the human almost out
of the equation because of the process.

111
00:06:15,506 --> 00:06:19,596
"Hey, can you help me with this?" "Yeah,
I don't see a ticket, so maybe I can't."

112
00:06:20,530 --> 00:06:26,632
But you also raise a good issue about that
disconnect between, you know, you know how

113
00:06:26,633 --> 00:06:29,005
to fix the issue so it doesn't bother you.

114
00:06:29,393 --> 00:06:33,291
And, and, and s- and you might
even be almost amazed that I

115
00:06:33,316 --> 00:06:34,581
don't know how to fix the issue.

116
00:06:34,601 --> 00:06:38,268
Like, it's so easy in your
mind, so tapping into empathy

117
00:06:38,268 --> 00:06:39,815
is, is extra hard there.

118
00:06:40,054 --> 00:06:42,983
One, one of the exercises I've
often asked teams to do is think

119
00:06:42,986 --> 00:06:47,107
about, you know, why is this person
really frustrated or anxious?

120
00:06:48,058 --> 00:06:51,779
And, and if they can get to that,
then ask yourself, h- have you

121
00:06:51,780 --> 00:06:53,633
ever f- had that same feeling?

122
00:06:53,650 --> 00:06:58,432
Like, you might not have been anxious
because your computer crashed right before

123
00:06:58,432 --> 00:07:02,641
the big presentation, but maybe your
car broke down on the way to work, and

124
00:07:02,641 --> 00:07:05,961
you knew you couldn't be late that day,
and you didn't know how to fix your car.

125
00:07:06,051 --> 00:07:08,778
You can fix a computer but not the car,
and now you're helpless and you're waiting

126
00:07:08,778 --> 00:07:11,811
for that mechanic, and you hope that
they're cool and they show up on time, and

127
00:07:12,058 --> 00:07:13,169
they don't make you feel like an idiot.

128
00:07:13,236 --> 00:07:19,607
Uh, I mean, it's a similar enough feeling
for then you can ask, "Well, what would've

129
00:07:19,607 --> 00:07:23,460
made me feel better in that moment?" Or,
"What did make me feel better in that

130
00:07:23,461 --> 00:07:27,793
moment?" And if you understand that, then
you can probably tap into empathy and say,

131
00:07:27,794 --> 00:07:31,587
"Okay, I can do the same thing for this
person I'm serving." But there's a lot of

132
00:07:31,587 --> 00:07:36,582
intention behind all of that, and it is
really easy just to be dismissive of it

133
00:07:36,841 --> 00:07:39,876
and say, "Look, it's another ID10T issue.

134
00:07:39,885 --> 00:07:42,253
Let me just get on it and away we go."

135
00:07:43,087 --> 00:07:43,296
Todd Kane: Yeah.

136
00:07:43,731 --> 00:07:47,481
Well, I guess, and that kind of
gets to, you know, um, what you're,

137
00:07:47,503 --> 00:07:50,890
you're noting here is sort of the
human in the loop, uh, in this.

138
00:07:50,926 --> 00:07:53,676
Because quite frankly, like
an AI can solve this stuff.

139
00:07:53,678 --> 00:07:57,265
Like we're getting to this place where,
you know, it can recognize what the

140
00:07:57,265 --> 00:08:02,344
issue is, it deploys a script, and
whoop-de-doo, like problem is resolved.

141
00:08:02,618 --> 00:08:05,995
So if that's where we're headed,
where is the human in the loop?

142
00:08:06,011 --> 00:08:12,105
What value does the human interaction, uh,
provide, uh, when s- a lot of this will

143
00:08:12,111 --> 00:08:17,092
start becoming sort of first contact or
first call resolution being done by a bot?

144
00:08:18,255 --> 00:08:21,692
Jeff Toister: There's a few
places where humans add, I

145
00:08:21,719 --> 00:08:23,586
think, some unexpected value.

146
00:08:23,820 --> 00:08:27,578
Um, and, and we'll go maybe
obvious to not so obvious.

147
00:08:28,306 --> 00:08:33,549
One of the obvious places is, is where AI
reaches the limits of its capabilities,

148
00:08:34,110 --> 00:08:35,200
and that's where we need a human.

149
00:08:35,200 --> 00:08:41,682
So those are more so edge cases or,
um, you know, we still rely on humans

150
00:08:41,693 --> 00:08:45,620
sometimes to document properly what's
actually going on and what they need.

151
00:08:46,235 --> 00:08:49,053
And, and, and sometimes we need a
human just to kind of suss that out.

152
00:08:49,794 --> 00:08:52,125
So that's the kind of more obvious.

153
00:08:52,636 --> 00:08:57,855
Um, there's a second where the human's
just not confident in the output.

154
00:08:58,752 --> 00:09:02,691
A- and there could be a lot of reasons for
that, but, you know, typically the higher

155
00:09:02,711 --> 00:09:06,688
the stress levels, the more urgency, the
more perceived complexity of the issue,

156
00:09:06,688 --> 00:09:13,665
the less tolerant we are of entrusting the
issue to automation or AI, especially if

157
00:09:13,665 --> 00:09:17,678
it doesn't feel highly competent or easy.

158
00:09:18,591 --> 00:09:23,844
But then the third area is, I think,
some of these unexpected places,

159
00:09:23,845 --> 00:09:28,924
let's say, where relationships
are really, really important.

160
00:09:30,059 --> 00:09:33,055
And it's more than just
troubleshooting an issue.

161
00:09:33,106 --> 00:09:37,337
It's more about providing confidence
that, hey, we're on it, and

162
00:09:37,338 --> 00:09:38,562
we're going to help with that.

163
00:09:38,618 --> 00:09:45,115
And in those cases, that's where a human
can really add a lot of extra value.

164
00:09:45,820 --> 00:09:50,438
So it's, it is a little bit of a
moving target, and A- AI is able

165
00:09:50,440 --> 00:09:51,977
to do more and more each day.

166
00:09:52,514 --> 00:09:57,353
Uh, but I think it's a mistake to
just we're gonna put everything

167
00:09:57,355 --> 00:10:02,838
on AI or we're never gonna touch
AI a- and, and it's all humans.

168
00:10:02,838 --> 00:10:07,246
I mean, AI, like anything else, is
a tool, and right tool, right job,

169
00:10:07,261 --> 00:10:08,708
you probably get the job done well.

170
00:10:10,339 --> 00:10:12,931
Todd Kane: So what about like,
uh, like first contact, right?

171
00:10:12,948 --> 00:10:16,047
Like, uh, 'cause I, I noted, you know,
the story that I heard about this

172
00:10:16,055 --> 00:10:21,049
MSP that just went pure AI answer,
uh, of phone calls, and I was shocked

173
00:10:21,083 --> 00:10:25,804
that the clients didn't, like, revolt
around this, uh, because that's what

174
00:10:25,804 --> 00:10:29,886
I tend to see is like, you know, uh,
we're of the generation, I suppose.

175
00:10:30,210 --> 00:10:33,730
Uh, I find a lot of this is generational
actually, because, like, the older

176
00:10:33,730 --> 00:10:38,174
generation than us, like the sort of
people in their 50s and 60s and beyond,

177
00:10:38,442 --> 00:10:39,737
they'll pick up, pick up a phone.

178
00:10:39,755 --> 00:10:42,277
Like, they wanna talk to a human,
and that's very much sort of a

179
00:10:42,278 --> 00:10:44,659
generational, uh, approach for them.

180
00:10:45,002 --> 00:10:46,636
Um, you know, I don't
know how old you are.

181
00:10:46,636 --> 00:10:48,081
You, you look like a young guy.

182
00:10:49,473 --> 00:10:52,592
But in those, in those 40s and
below type thing, um, that,

183
00:10:52,762 --> 00:10:54,808
Jeff Toister: No comment, and
definitely not 40s and below.

184
00:10:55,162 --> 00:10:55,568
Todd Kane: Okay.

185
00:10:56,589 --> 00:10:57,216
Well, you look great.

186
00:10:57,233 --> 00:10:57,894
You look great, Jeff.

187
00:10:58,282 --> 00:11:03,424
Um, that, you know, I'm, I'm there,
like mashing zero, like yelling agent

188
00:11:03,474 --> 00:11:08,272
into the phone when I'm stuck in a phone
tree, but I'm also the first one to go

189
00:11:08,302 --> 00:11:12,757
to the, the web and look for a chatbot
that can actually solve the problem for

190
00:11:12,758 --> 00:11:17,282
me, and then the generation below that
is just like, uh, either I will solve

191
00:11:17,282 --> 00:11:21,789
this myself, or, you know, maybe I can
send a text, or I can find a chatbot,

192
00:11:21,805 --> 00:11:26,188
but I am, I am absolutely not phoning
and talking to someone about this.

193
00:11:26,457 --> 00:11:31,194
So there is a bit of a generational split,
but, what would be your opinion about, you

194
00:11:31,195 --> 00:11:35,892
know, having that first line of interface
with a client being more agentic?

195
00:11:35,919 --> 00:11:38,350
Is that a good or a bad thing,
or is It circumstantial?

196
00:11:39,807 --> 00:11:41,929
Jeff Toister: It gets circumstantial.

197
00:11:42,252 --> 00:11:47,431
Uh, however, I, I think generally
there are some real advantages.

198
00:11:47,664 --> 00:11:52,865
So if we think about first line,
if I have to go to a human, I'm

199
00:11:52,871 --> 00:11:57,630
probably going to have to wait,
and if that wait time is tolerable

200
00:11:57,631 --> 00:11:59,603
because it's not urgent, that's okay.

201
00:12:00,218 --> 00:12:05,554
Um, but also one of the things where…
So AI can often answer this question

202
00:12:05,554 --> 00:12:07,163
immediately, especially simple stuff.

203
00:12:07,916 --> 00:12:09,810
You know, my, my internet is down.

204
00:12:10,277 --> 00:12:13,372
Okay, well, let's start,
let's start a process.

205
00:12:13,373 --> 00:12:15,881
We c- we can walk through a
troubleshooting process without waiting

206
00:12:15,881 --> 00:12:17,213
in a queue or submitting a ticket.

207
00:12:17,233 --> 00:12:18,326
That, that's an advantage.

208
00:12:19,750 --> 00:12:22,896
One of the other challenges e-
especially when we're reacting to

209
00:12:23,470 --> 00:12:28,798
issues is having the right amount of
information to diagnose the problem,

210
00:12:29,755 --> 00:12:32,668
and that is classically a challenge.

211
00:12:32,670 --> 00:12:36,726
But if we can have a conversation
with AI, it could probably guide us

212
00:12:36,737 --> 00:12:40,498
pretty quickly if it's programmed right
to provide the correct information.

213
00:12:41,201 --> 00:12:43,280
So there's definitely
some advantages there.

214
00:12:44,598 --> 00:12:50,074
I think when it exceeds complexity,
uh, or, or there's a level of urgency

215
00:12:50,076 --> 00:12:54,215
where I don't have the tolerance to
go back and forth with AI, especially

216
00:12:54,215 --> 00:12:58,669
if it doesn't initially seem to
understand me, that's where the

217
00:12:58,671 --> 00:13:00,885
human is, is gonna be more needed.

218
00:13:00,886 --> 00:13:04,525
So sometimes it's first contact is okay,
but do we have a clear escalation path?

219
00:13:05,409 --> 00:13:09,575
And, and, and what we're seeing it is
kind of all over the place, but AI is

220
00:13:09,575 --> 00:13:15,026
sometimes way too tenacious in terms of
holding onto the issue versus being able

221
00:13:15,061 --> 00:13:18,257
to recognize, "Oh, this is an edge case.
Let's get you to a human, and we're gonna

222
00:13:18,259 --> 00:13:20,020
send you to the human with context."

223
00:13:20,637 --> 00:13:24,085
Or, "Oh wow, you're super, uh,
this is super urgent. We're gonna

224
00:13:24,091 --> 00:13:28,505
get you to a human." Um, I think
you're probably right about there's

225
00:13:28,505 --> 00:13:29,700
some generational differences.

226
00:13:29,719 --> 00:13:31,403
I think there's also
some power differences.

227
00:13:31,425 --> 00:13:37,056
Your… Is your CFO or CMO going to
tolerate chatting with an AI, AI agent

228
00:13:37,315 --> 00:13:41,431
because they have a need that's urgent
or are they just going to talk to the

229
00:13:41,432 --> 00:13:45,156
person that they know is gonna help him,
help them right now versus I just started

230
00:13:45,156 --> 00:13:50,704
with this company, I don't know anybody
yet, and I'm trying to get my, you know,

231
00:13:50,704 --> 00:13:52,773
my, my workspace set up for day one?

232
00:13:52,821 --> 00:13:55,565
That's probably a different
level as well in terms of what

233
00:13:55,567 --> 00:13:56,639
people are willing to tolerate.

234
00:13:56,652 --> 00:13:59,953
So not a clear answer, but I think it's
good to think through those things.

235
00:14:00,685 --> 00:14:00,877
Todd Kane: Yeah.

236
00:14:00,963 --> 00:14:03,111
Well, let's, let's explore this
a little more then because,

237
00:14:03,252 --> 00:14:03,641
Jeff Toister: Yeah

238
00:14:03,698 --> 00:14:07,196
Todd Kane: examples that I find
frustrating in my interactions

239
00:14:07,196 --> 00:14:11,721
with, uh, with s- uh, help desks and
service desk in general, uh, it's

240
00:14:11,721 --> 00:14:15,489
funny how you become sort of critical
and you see this everywhere in your

241
00:14:15,490 --> 00:14:16,981
life when it's a part of your job.

242
00:14:16,986 --> 00:14:20,393
Like, I never thought much about,
like, phoning, uh, you know, an

243
00:14:20,405 --> 00:14:25,159
airline or, uh, support for a product
back in the day before I was in this

244
00:14:25,159 --> 00:14:29,440
industry, and now I'm keenly aware
of all of my interactions with some

245
00:14:29,441 --> 00:14:31,252
type of help desk or service desk.

246
00:14:31,677 --> 00:14:36,089
Um, and one of the things that I think
bothers me is there are lots of places

247
00:14:36,091 --> 00:14:40,939
where I almost feel like an interaction
with an AI that was sufficiently capable

248
00:14:40,986 --> 00:14:44,907
would be better than the human interaction
that we have to wait for in a lot of

249
00:14:44,907 --> 00:14:46,453
the enterprise environments, Right

250
00:14:46,758 --> 00:14:52,314
Like, you phone, uh, you get someone
who, uh, uh, you know, is potentially

251
00:14:52,337 --> 00:14:56,139
offshored, uh, they're doing their
best, But the part that bothers me

252
00:14:56,139 --> 00:14:59,724
about those interactions is that
they're incredibly scripted, right?

253
00:14:59,764 --> 00:15:03,576
And it's to the extent of, like,
the feigned empathy bothers me,

254
00:15:03,822 --> 00:15:06,818
of like, I tell them what my issue
is, and they're like, "Oh, I'm so

255
00:15:06,818 --> 00:15:08,786
sorry to hear that blah, blah, blah.

256
00:15:08,931 --> 00:15:10,855
That must be really frustrating for you.

257
00:15:10,878 --> 00:15:13,193
I'll see if I can help you with the
blah, blah, blah, blah, blah," right?

258
00:15:13,193 --> 00:15:15,508
And it's like you can tell they're
just reading from a script, and if

259
00:15:15,510 --> 00:15:18,609
you try to, like, break them out of
the script and interact with you in

260
00:15:18,609 --> 00:15:22,390
some way, like, it, it just, it's,
it doesn't derail the conversation.

261
00:15:22,395 --> 00:15:24,316
It just seems to, like,
go down the script.

262
00:15:24,316 --> 00:15:25,743
You can't break out of it, right?

263
00:15:25,744 --> 00:15:27,869
So, like, I may as well
be talking to a robot

264
00:15:27,892 --> 00:15:28,482
Jeff Toister: Right

265
00:15:28,859 --> 00:15:31,176
Todd Kane: The human
interaction is not additive.

266
00:15:31,187 --> 00:15:35,810
In fact, it's actually a detractor from
my experience in that interaction, right?

267
00:15:36,886 --> 00:15:38,810
Jeff Toister: But I think that
that's what I would consider

268
00:15:38,811 --> 00:15:41,224
to be, uh, not human service.

269
00:15:41,255 --> 00:15:43,270
That, that's, it's transactional service.

270
00:15:43,271 --> 00:15:47,455
It's, it… That person is impersonating
a robot by sticking to the script.

271
00:15:48,079 --> 00:15:50,967
They're not bringing their humanity,
so they don't add any value.

272
00:15:51,034 --> 00:15:52,044
And I, I think you're right.

273
00:15:52,044 --> 00:16:00,217
If, if I put that person up against a
capable, um, AI, um, AI is probably going

274
00:16:00,231 --> 00:16:03,438
to be just as charming or not as as…

275
00:16:03,837 --> 00:16:07,688
But, but it's probably going to, to
be a little bit faster at working

276
00:16:07,690 --> 00:16:09,222
through the issue, I hope, right?

277
00:16:09,222 --> 00:16:10,405
If it's programmed correctly.

278
00:16:11,230 --> 00:16:15,499
I, I think we have to look at places
where humans add the extra value.

279
00:16:15,502 --> 00:16:18,322
So, uh, let, let me give
you maybe two examples.

280
00:16:18,330 --> 00:16:24,421
One is I was about to start a webinar with
a client, and I, I desperately needed this

281
00:16:24,428 --> 00:16:26,337
webinar software to work, and it was not.

282
00:16:27,418 --> 00:16:35,172
And I was able to, to… I, I didn't
see a clear option to troubleshoot it.

283
00:16:35,174 --> 00:16:38,019
I didn't have time to go through
a whole script and, you know,

284
00:16:38,045 --> 00:16:41,599
Clippy, the AI bot, to tell me how
to reset the software and all that.

285
00:16:41,619 --> 00:16:43,577
I just needed a person
who could just handle it.

286
00:16:44,125 --> 00:16:46,929
And I fortunately got a person
right away, and they solved it.

287
00:16:46,931 --> 00:16:50,299
But then they did something
that AI just can't do yet.

288
00:16:50,850 --> 00:16:54,431
They understood the real source
of my anxiety was that I'm

289
00:16:54,432 --> 00:16:55,708
starting this client webinar.

290
00:16:55,732 --> 00:16:57,837
I'm worried about letting my client down.

291
00:16:58,643 --> 00:17:02,132
And I'll never forget, she
said, "I think we've solved it.

292
00:17:03,035 --> 00:17:05,956
But I know your webinar's about to
start, so I'm gonna stay on the line

293
00:17:05,958 --> 00:17:10,784
with you, and if anything goes wrong,
I will be right here to help fix it.

294
00:17:11,314 --> 00:17:14,948
And if it goes smoothly, which I think
it will, then I'll just quietly get

295
00:17:14,948 --> 00:17:19,416
off the line and you can facilitate
your webinar." That's a, that's a

296
00:17:19,473 --> 00:17:23,261
different level of understanding where
that person is adding value, and I

297
00:17:23,261 --> 00:17:30,035
was ready to cancel that service, and
I stuck with it for two more years,

298
00:17:30,036 --> 00:17:32,743
despite it being an inferior product.

299
00:17:32,753 --> 00:17:36,460
And then Zoom came along and, you
know, some other really good products

300
00:17:36,460 --> 00:17:37,744
and, you know, enough is enough.

301
00:17:37,746 --> 00:17:42,064
But they bought me two years
more of service from that person.

302
00:17:42,572 --> 00:17:45,633
Now, the flip side of this, the
other day I was trying to solve a

303
00:17:45,633 --> 00:17:50,711
problem that involved both payroll and
accounting, and it was after hours,

304
00:17:50,876 --> 00:17:53,183
so I, I didn't wanna wait for a human.

305
00:17:53,183 --> 00:17:54,849
It was, this was my time to get it done.

306
00:17:55,815 --> 00:18:03,074
And I first started with my payroll
provider's AI bot, and they had a

307
00:18:03,075 --> 00:18:05,945
hole in their documentation, which
means the AI bot couldn't solve it.

308
00:18:06,606 --> 00:18:10,008
And then I go to ChatGPT, which is
able to kind of source from multiple

309
00:18:10,008 --> 00:18:15,449
places, and I solved it on my time,
and it was a very helpful thing,

310
00:18:15,827 --> 00:18:17,471
without having to wait for a person.

311
00:18:17,474 --> 00:18:20,987
So I, I think, you know, there's
a, a case to be made for having

312
00:18:21,057 --> 00:18:22,631
both, and both have their place.

313
00:18:24,224 --> 00:18:27,222
Todd Kane: I think the, the, the
first example I think is what

314
00:18:27,222 --> 00:18:34,122
that reminds me of is that in, in
problems is almost some of your best

315
00:18:34,249 --> 00:18:36,712
options for creating loyalty, right?

316
00:18:36,712 --> 00:18:38,009
Like, I tell this story all the time.

317
00:18:38,010 --> 00:18:41,079
We're in an enterprise, uh,
consulting environment that I was in.

318
00:18:41,560 --> 00:18:46,446
Um, we made a huge error and deployed
like s- over 60 servers into the

319
00:18:46,446 --> 00:18:50,463
field for this very large client
with the wrong image on them, right?

320
00:18:50,534 --> 00:18:57,047
And like a huge i- issue because we paid,
you know, $400, $500 shipping to get

321
00:18:57,048 --> 00:19:00,465
these, all of these servers out and all
the work that had been done to build them.

322
00:19:00,911 --> 00:19:03,500
Um, and everyone's like, "Oh my
God," like, "This is such a problem.

323
00:19:03,501 --> 00:19:06,075
We're gonna-- Uh, we have to pull
them back." Like, "The price of the

324
00:19:06,076 --> 00:19:07,173
project is gonna have to go up."

325
00:19:07,179 --> 00:19:11,387
And the CEO is like, "Nope, this is our
error. We own this. We are not charging

326
00:19:11,387 --> 00:19:15,042
them any more, and we're gonna communicate
that to them." Two things about that.

327
00:19:15,052 --> 00:19:18,192
Like, um, one, owning it.

328
00:19:18,317 --> 00:19:22,279
Two, the fact that you own it and
that you're not charging them more.

329
00:19:22,279 --> 00:19:25,905
A lot of people will s- try to hide
these issues and, and sort of s- like

330
00:19:25,906 --> 00:19:30,618
circumvent to, to make themselves look
good when in a lot of cases, like how

331
00:19:30,619 --> 00:19:36,258
you handle an issue is far more i-
impactful than the issue itself, And

332
00:19:36,269 --> 00:19:39,625
they became an incredibly loyal client of
ours because of what we were able to do.

333
00:19:39,976 --> 00:19:41,126
Same thing for you, right?

334
00:19:41,126 --> 00:19:46,346
Like that person is probably incentivized
by their call handle time and the number

335
00:19:46,346 --> 00:19:49,692
of, uh, uh, tickets that they're able
to close through the course of the

336
00:19:49,692 --> 00:19:53,390
day, but they took that extra five to
10 minutes to hang on the line with

337
00:19:53,391 --> 00:19:54,975
you to make sure that you were okay.

338
00:19:55,228 --> 00:19:56,152
They didn't have to do that.

339
00:19:56,388 --> 00:20:00,014
But that simple action of rather
than saying like, "Looks like

340
00:20:00,017 --> 00:20:02,385
you're good, Jeff. Let us know
if you need any, any help in the

341
00:20:02,385 --> 00:20:04,050
future," and then click, right?

342
00:20:04,191 --> 00:20:07,842
Uh, they h- they held on, and that, that
created that sense of loyalty for you.

343
00:20:07,843 --> 00:20:08,804
So I think that's massive.

344
00:20:09,849 --> 00:20:13,377
Jeff Toister: And you're bringing up
a, an even broader issue, which is, you

345
00:20:13,378 --> 00:20:15,791
know, uh, taking ownership of mistakes.

346
00:20:15,795 --> 00:20:20,437
That's, uh, that's something that
does, it, it, it creates a s- a

347
00:20:20,438 --> 00:20:25,011
different set of trust and builds
a, a relationship with your clients.

348
00:20:25,159 --> 00:20:27,998
So, you know, I don't know that
a machine knows how to do it,

349
00:20:28,051 --> 00:20:30,414
but, uh, people certainly can

350
00:20:32,520 --> 00:20:32,750
Todd Kane: Yeah.

351
00:20:33,131 --> 00:20:36,658
And maybe we're sort of getting to
that, that state of the world as well

352
00:20:36,658 --> 00:20:41,543
is like when an AI does something
wrong, like how do they, how do

353
00:20:41,543 --> 00:20:43,154
they take responsibility for that?

354
00:20:43,154 --> 00:20:45,710
Where does the responsibility lie, right?

355
00:20:45,737 --> 00:20:48,692
Like this gets into some weird
spaces on, uh, you know, errors

356
00:20:48,693 --> 00:20:50,433
and omission, uh, insurance.

357
00:20:50,433 --> 00:20:54,918
Like our AI did something, uh, and it
went rogue and did something it shouldn't

358
00:20:54,924 --> 00:20:56,465
have in your client environment.

359
00:20:56,481 --> 00:20:58,433
Like that's something to consider as well.

360
00:20:58,436 --> 00:21:00,796
Like what's the scope of control
that you give these things?

361
00:21:00,797 --> 00:21:04,648
But also, you know, it can't really be
held responsible for the good and the

362
00:21:04,648 --> 00:21:08,777
bad things that, that, that it, it should
be doing or shouldn't be doing as well.

363
00:21:10,284 --> 00:21:10,562
yeah, this

364
00:21:10,584 --> 00:21:12,970
Jeff Toister: We've seen
a case already about this.

365
00:21:13,099 --> 00:21:17,574
Um, I, I, I'm, I'm not gonna, I'm
gonna get the details wrong, but I

366
00:21:17,595 --> 00:21:21,079
think there was a case, or maybe it's
going through the courts now about are

367
00:21:21,080 --> 00:21:23,118
we responsible for what our AI does

368
00:21:23,810 --> 00:21:24,045
Todd Kane: Mm-hmm.

369
00:21:25,072 --> 00:21:25,415
Yeah.

370
00:21:25,559 --> 00:21:26,570
No, I wouldn't be surprised.

371
00:21:26,570 --> 00:21:29,106
I think that's, that's
super, super relevant, right?

372
00:21:29,129 --> 00:21:32,070
Because e-especially as
they become more agentic.

373
00:21:32,564 --> 00:21:32,866
Jeff Toister: Ja

374
00:21:32,885 --> 00:21:34,559
Todd Kane: and we've seen
sort of the previous cases.

375
00:21:34,560 --> 00:21:38,057
I've personally not run into these
issues, but like when Clawbot and

376
00:21:38,057 --> 00:21:41,420
stuff s- first showed up on the scene,
and it would just sort of rip through

377
00:21:41,420 --> 00:21:43,126
and start deleting stuff for users.

378
00:21:43,135 --> 00:21:46,382
Like, "Hey, I'm cleaning up your
inbox. I'm deleting the 4,000

379
00:21:46,382 --> 00:21:49,747
emails that you've archived."
It's like, "No! Stop." All right?

380
00:21:49,757 --> 00:21:52,862
So I've never had an issue like this,
but you know, you could see that

381
00:21:52,874 --> 00:21:57,515
being an issue where, um, I don't
think it was an AI necessarily, but

382
00:21:57,560 --> 00:22:01,305
I've seen those i- the issues where
automation deleted all of the backups,

383
00:22:01,681 --> 00:22:01,861
Jeff Toister: Ja.

384
00:22:01,906 --> 00:22:05,017
Todd Kane: in order to make room
for, for, for the new backups.

385
00:22:05,018 --> 00:22:08,591
And it's like, well, no, like
we have a regulatory compliance

386
00:22:08,596 --> 00:22:10,258
requirement for keeping these backups.

387
00:22:10,258 --> 00:22:11,689
Like, you can't just go and delete them.

388
00:22:12,142 --> 00:22:14,930
Um, so there, you know, this
is maybe gets into those spaces

389
00:22:14,930 --> 00:22:17,649
of like, where is AI useful?

390
00:22:17,662 --> 00:22:21,507
Where is, you know, the, the, the
human in the loop needs to be required?

391
00:22:21,509 --> 00:22:25,596
So we've kind of touched on like
empathy being one that, you know,

392
00:22:25,911 --> 00:22:29,943
robots right now are not terribly good
at, and it's an important component

393
00:22:29,947 --> 00:22:32,048
for especially the service desk.

394
00:22:32,099 --> 00:22:37,174
I believe a lot of sort of the IT support
in the future will be back to the future

395
00:22:37,217 --> 00:22:41,449
of more consulting, a lot more human
interaction, because everything else on

396
00:22:41,449 --> 00:22:43,253
the back end is largely commoditized.

397
00:22:43,264 --> 00:22:47,235
Like I don't think having an
AI being able to resolve your

398
00:22:47,235 --> 00:22:50,571
client's issues for you actually
differentiates you in a lot of ways.

399
00:22:50,791 --> 00:22:54,835
It may make you more efficient, but I
don't think the clients particularly

400
00:22:54,836 --> 00:22:59,034
care about how the issues get resolved
as long as the experience that you

401
00:22:59,034 --> 00:23:01,649
create for them is, is positive, right?

402
00:23:01,650 --> 00:23:07,518
So I think that to this place of like,
what are the skills that humans are still

403
00:23:07,547 --> 00:23:13,044
highly adapted for that are necessary
in, you know, the IT future that, you

404
00:23:13,044 --> 00:23:17,070
know, for now, maybe the next, at least
the next year or next three years,

405
00:23:17,404 --> 00:23:21,306
uh, AIs are not particularly good at
taking on some of those tasks or being

406
00:23:21,310 --> 00:23:23,709
capable of doing those human activities.

407
00:23:23,710 --> 00:23:24,639
What would those look like?

408
00:23:25,780 --> 00:23:29,346
Jeff Toister: I think one of the biggest
things is, you know, go back to advocacy,

409
00:23:29,391 --> 00:23:35,666
that when something falls out of a
normal process or breaks, do you have

410
00:23:35,668 --> 00:23:38,584
a human who's available to run with it?

411
00:23:38,597 --> 00:23:45,720
So as an example, you hire a new
employee and you're counting on

412
00:23:45,721 --> 00:23:49,476
your MSP to make sure that that
employee is ready on day one.

413
00:23:50,556 --> 00:23:54,914
Whether or not they're ready is
critical for that day one to be a great

414
00:23:54,914 --> 00:23:58,270
experience, "Hey, I'm starting to learn
how to do this job and understand the

415
00:23:58,270 --> 00:24:01,887
culture," or, "My day one is spent
tracking down that computer they sent

416
00:24:01,889 --> 00:24:06,786
me and, uh, trying to get the right
credentials and log in." And so there's,

417
00:24:06,787 --> 00:24:08,396
uh, two very different scenarios.

418
00:24:09,104 --> 00:24:12,578
I think AI can help monitor and
run processes like that, but what

419
00:24:12,580 --> 00:24:13,753
happens if something goes wrong?

420
00:24:14,945 --> 00:24:20,208
Who's going to find that solution
that is not in your normal process?

421
00:24:20,407 --> 00:24:25,117
I mean, if that laptop you shipped
out got stuck in a, a shipping hub

422
00:24:25,138 --> 00:24:28,931
somewhere because of a snowstorm,
what are you gonna do about it?

423
00:24:29,711 --> 00:24:33,695
That-- And I think those are,
those things, humans are the ones

424
00:24:33,696 --> 00:24:35,158
that can find creative solutions.

425
00:24:35,481 --> 00:24:36,696
They can work around systems.

426
00:24:36,698 --> 00:24:38,939
They can work through
bottlenecks and limitations.

427
00:24:38,939 --> 00:24:42,467
They can think laterally at, at, at a
very different level and understand when

428
00:24:42,471 --> 00:24:44,558
a rule is a rule and more of a suggestion.

429
00:24:45,565 --> 00:24:51,517
A- and having a human available for
those more complicated scenarios or

430
00:24:51,518 --> 00:24:58,282
when something goes wrong is, I think,
a good way to use your human talent.

431
00:24:59,455 --> 00:25:03,818
It's okay to mo- to automate, you
know, a normal request, for example,

432
00:25:03,906 --> 00:25:07,542
that, but you still need somebody
to monitor that and fulfill it.

433
00:25:07,553 --> 00:25:12,300
So that's-- I think that's where
you, you run into challenges is where

434
00:25:12,354 --> 00:25:16,884
companies either go all in on AI and
forget that you still have to train

435
00:25:16,941 --> 00:25:19,459
and monitor it and have a fail-safe.

436
00:25:20,467 --> 00:25:24,529
But also, if we're just having humans do
all of that, that's inefficient as well.

437
00:25:24,540 --> 00:25:29,267
So there is a balance to be had, but those
edge cases are, to me, one of the biggest

438
00:25:29,267 --> 00:25:30,931
opportunities to have humans involved.

439
00:25:31,834 --> 00:25:32,012
Todd Kane: Yeah.

440
00:25:32,325 --> 00:25:36,309
You, you mentioned kind of the
advocacy, I would say, versus process.

441
00:25:36,377 --> 00:25:40,052
Uh, I think this is a, a big piece
that, that I'm fascinated by because,

442
00:25:40,505 --> 00:25:44,231
um, I often say that, um, critical
thinking skills is one of the

443
00:25:44,239 --> 00:25:47,763
hardest things to actually teach to
people, in my opinion, because so

444
00:25:47,763 --> 00:25:50,332
much of it is experiential, right?

445
00:25:50,365 --> 00:25:56,431
Like you can, you can give them sort
of, uh, value-driven judgments and, uh,

446
00:25:56,444 --> 00:25:59,740
give them as much process as you can,
but either they get stuck in following

447
00:25:59,835 --> 00:26:03,460
the letter of the law and like we talked
about of like, "I'm supposed to follow

448
00:26:03,461 --> 00:26:06,221
this script. If I go off script, I'm
gonna get in trouble, so I'm just gonna

449
00:26:06,222 --> 00:26:09,360
follow the script," and, you know, it
devalues the relationship that I have.

450
00:26:09,370 --> 00:26:13,422
Versus, you know, "Okay, I'm gonna go
off script here outside the scope of

451
00:26:13,422 --> 00:26:17,109
what I'm responsible for and do something
amazing for this client that may help

452
00:26:17,109 --> 00:26:21,289
them, make them a memorable experience
that they really value." But, you know,

453
00:26:21,289 --> 00:26:25,557
I also can't bury four hours on every
ticket that comes into me, and I think

454
00:26:25,567 --> 00:26:29,402
the judgment between these is really
difficult for people, and how you actually

455
00:26:29,414 --> 00:26:31,949
train that I find is quite tricky.

456
00:26:31,951 --> 00:26:35,748
Do you have any thoughts on sort of
like how you educate or give people the

457
00:26:35,748 --> 00:26:40,465
tools to figure out where should I draw
outside the lines and look for something

458
00:26:40,466 --> 00:26:45,291
creative and really bury some time on this
versus I just need to follow the process,

459
00:26:45,292 --> 00:26:48,621
and if the process is wrong, then I'll
tell my boss about it after this call?

460
00:26:49,559 --> 00:26:52,146
Jeff Toister: It's the system
and the culture that usually

461
00:26:52,155 --> 00:26:53,358
creates one or the other.

462
00:26:53,891 --> 00:26:56,293
A- and so I'll give you
a couple of examples.

463
00:26:56,824 --> 00:27:02,149
For the s- typical MSP, if you're
listening to this, a- ask yourself,

464
00:27:02,159 --> 00:27:07,576
have we collectively defined what
a great experience looks like?

465
00:27:08,722 --> 00:27:12,515
And the answer is no
for most organizations.

466
00:27:12,650 --> 00:27:14,668
A few have, and that's a huge first step.

467
00:27:14,685 --> 00:27:17,093
But if we haven't collectively defined it,

468
00:27:17,310 --> 00:27:18,163
yeah, Yeah

469
00:27:18,470 --> 00:27:21,150
Todd Kane: that they've
defined it is it's, "I want the

470
00:27:21,151 --> 00:27:22,932
customer to feel great," or, "I

471
00:27:23,066 --> 00:27:23,349
Jeff Toister: Right

472
00:27:23,374 --> 00:27:24,166
Todd Kane: customer outcomes.

473
00:27:24,166 --> 00:27:28,340
I want them to, you know, give us a
good, uh, CSAT or NPS score." Right

474
00:27:28,341 --> 00:27:30,226
Like, that's, that's
not really a definition.

475
00:27:30,242 --> 00:27:32,621
That's just sort of like, how do
we know that this is working or

476
00:27:32,621 --> 00:27:34,971
not, Right It, doesn't give you
the guidelines of what to do.

477
00:27:35,015 --> 00:27:35,256
Yeah.

478
00:27:35,317 --> 00:27:35,595
Go ahead.

479
00:27:35,778 --> 00:27:37,757
Jeff Toister: it, it, it's, it,
it has to be something like,

480
00:27:37,771 --> 00:27:40,414
what did you do for your client?

481
00:27:41,395 --> 00:27:44,840
And, and how did you… If you're
on a good day when your client

482
00:27:44,840 --> 00:27:46,052
is happy, what are you doing?

483
00:27:47,067 --> 00:27:47,895
And you can test that.

484
00:27:47,933 --> 00:27:51,632
Ask a group of employees at
random, and if they all give you

485
00:27:51,633 --> 00:27:53,300
the same answer, you're on target.

486
00:27:53,332 --> 00:27:57,843
But if they don't, what people probably
default to is process and procedure.

487
00:27:58,695 --> 00:28:04,205
And if you look closely at the process and
procedure, we're trained to follow them.

488
00:28:04,691 --> 00:28:12,599
So critical thinking is almost
pushed out by process or by procedure

489
00:28:12,615 --> 00:28:15,522
because, uh, you know, my boss is
gonna notice if I didn't follow the

490
00:28:15,524 --> 00:28:20,076
process, and maybe I'm gonna get in
trouble if I don't follow the process.

491
00:28:21,133 --> 00:28:26,931
So, uh, now, I don't even, I don't
even worry about going outside of that.

492
00:28:26,989 --> 00:28:31,435
But I, I will tell you that
I was lucky to learn a lot of

493
00:28:31,435 --> 00:28:34,603
lessons from, from customers and
clients, and years and years ago.

494
00:28:35,117 --> 00:28:40,393
I had a client, um, I, I, I had given this
client all kinds of excuses why I couldn't

495
00:28:40,394 --> 00:28:44,774
get something done, and it was all
because of process and procedure, and my

496
00:28:44,775 --> 00:28:46,427
client said something I'll never forget.

497
00:28:46,456 --> 00:28:52,946
He said, "Isn't that what they pay you
for?" And it just, it stuck with me.

498
00:28:52,982 --> 00:28:58,863
It like, wow, I'm adding no value here,
and I need to find a way to add value.

499
00:28:58,863 --> 00:29:03,184
And I worked for a big bureaucratic
company, but I've, I worked hard

500
00:29:03,438 --> 00:29:05,774
to find a way to get things done.

501
00:29:06,710 --> 00:29:09,764
And then I started visiting all
these other departments that I

502
00:29:09,779 --> 00:29:12,912
thought were holding me up and
realized they had challenges, too.

503
00:29:13,437 --> 00:29:16,510
And so instead of just saying, "You're
a jerk and you need to work harder for

504
00:29:16,517 --> 00:29:18,775
me," I realized that wouldn't land.

505
00:29:18,776 --> 00:29:22,005
I started asking them, "Well, what would
make it easier for you to get this through

506
00:29:22,007 --> 00:29:26,920
faster?" And they would say, "Well,
you know, this is how you do it, and I

507
00:29:26,920 --> 00:29:30,415
don't know why no one knows this." So I
start kind of documenting and building

508
00:29:30,415 --> 00:29:35,523
relationships, and eventually I'm able
to get more done, get more done quickly.

509
00:29:35,976 --> 00:29:40,143
But that took a lot of effort,
and none of it was encouraged.

510
00:29:40,153 --> 00:29:43,252
In fact, my boss actively
discouraged that kind of work.

511
00:29:43,252 --> 00:29:47,568
So I think as leaders, we have to
define what great looks like, make

512
00:29:47,568 --> 00:29:50,793
sure everybody knows it, and then
we need to make sure that all of our

513
00:29:50,805 --> 00:29:54,809
processes and procedures are aligned
with that definition of greatness

514
00:29:56,217 --> 00:30:00,112
Todd Kane: I love that example because
it's something that I see so commonly in

515
00:30:00,242 --> 00:30:05,293
companies writ large, MSPs in particular,
certain st- friction points between like

516
00:30:05,294 --> 00:30:09,801
sales or account management and tech, uh,
and let's say the owner and the service

517
00:30:09,801 --> 00:30:14,429
delivery teams or the administrative
group or, you know, the service team

518
00:30:14,431 --> 00:30:15,827
and the professional services team.

519
00:30:15,836 --> 00:30:18,360
Like, there's always sort of
this conflict between these

520
00:30:18,365 --> 00:30:20,239
groups, and I agree with you.

521
00:30:20,536 --> 00:30:25,777
Like, I would say 90% of those issues are
strictly communication and process, right?

522
00:30:25,777 --> 00:30:29,141
Like, we have not talked about what this
process looks like on both sides of the

523
00:30:29,141 --> 00:30:32,936
fence, and we keep on just pushing work
over to the other group and then, like,

524
00:30:32,937 --> 00:30:36,870
getting upset when it doesn't get done in
a timely fashion without any consideration

525
00:30:36,871 --> 00:30:38,603
as to like, could this be done better?

526
00:30:38,605 --> 00:30:42,074
Or if I just gave you these five
points of information before I

527
00:30:42,077 --> 00:30:44,620
shuttled this work over to you, all
of a sudden it's so much easier.

528
00:30:44,832 --> 00:30:47,154
It's just like, "Ah, why don't these
guys know what they're doing? How

529
00:30:47,155 --> 00:30:48,531
come they can't get this done," right?

530
00:30:48,902 --> 00:30:50,617
Uh, it's just so incredibly common.

531
00:30:50,618 --> 00:30:53,112
So I think that's, that's a
huge takeaway is just, you

532
00:30:53,112 --> 00:30:54,818
know, go over and investigate.

533
00:30:54,836 --> 00:30:58,046
Like, sit with them and understand what
their workflow looks like, and then I

534
00:30:58,046 --> 00:31:01,537
often tell people, like, um, if you're,
if you're having trouble interfacing with

535
00:31:01,537 --> 00:31:05,402
another department, build a form that,
like, says, "Hey, hey, here's all the

536
00:31:05,402 --> 00:31:09,548
information I need you to submit to me to
get this done, And I guarantee you the,

537
00:31:09,623 --> 00:31:13,463
the effort will be worth it because I'll
probably get this done like three X faster

538
00:31:13,464 --> 00:31:14,906
if you just give me this information."

539
00:31:15,141 --> 00:31:17,957
You get their buy-in on that, and then
all of a sudden everyone's winning, right?

540
00:31:18,427 --> 00:31:21,721
Jeff Toister: And you solved a problem
for them a- and you're right, now

541
00:31:21,721 --> 00:31:24,432
they're saying, "Okay, well now we're
on the same team. Let's, let's go."

542
00:31:25,032 --> 00:31:25,436
Todd Kane: Yeah.

543
00:31:25,708 --> 00:31:25,974
Yeah.

544
00:31:25,997 --> 00:31:28,949
It's, uh, it's, it's funny how so
many of these things are… I often

545
00:31:28,949 --> 00:31:31,972
describe, like, so much in business
is just back to basics, right?

546
00:31:31,972 --> 00:31:35,053
Like, we just do the simple things, and
then magic just starts to happen, right?

547
00:31:35,115 --> 00:31:35,194
It's

548
00:31:35,583 --> 00:31:36,359
Jeff Toister: It really does.

549
00:31:36,401 --> 00:31:39,736
But I, I think even when you think
about basics, like, you know,

550
00:31:39,748 --> 00:31:41,170
we could go the other extreme.

551
00:31:41,180 --> 00:31:44,417
Like I, I worked with a team where,
you know, they, they said, "Dude,

552
00:31:44,456 --> 00:31:48,897
take as much time as you need to
solve the problem." And that in

553
00:31:48,897 --> 00:31:50,416
a way became part of the culture.

554
00:31:50,465 --> 00:31:54,447
That the problem with that is that
if I take as much time as I need,

555
00:31:54,447 --> 00:31:57,239
you s- you'd see people in like tier
three that would just say, "Well, I'm

556
00:31:57,239 --> 00:32:00,656
just gonna focus on this one ticket
today," and they would ignore all

557
00:32:00,656 --> 00:32:02,195
this other work that would pile up.

558
00:32:02,351 --> 00:32:07,481
Or I, I saw this issue where everybody
was doing their own thing and there was

559
00:32:07,483 --> 00:32:11,233
a kind of a new issue that was taking
people on average 30 minutes to solve.

560
00:32:11,257 --> 00:32:15,335
But, but one person, Stephanie…
Stephanie figured out how to solve

561
00:32:15,335 --> 00:32:16,712
the same issue in five minutes.

562
00:32:17,647 --> 00:32:21,097
And Stephanie was frustrated because
she didn't have a mechanism to

563
00:32:21,097 --> 00:32:23,627
share her five-minute solution
with the rest of the team.

564
00:32:24,114 --> 00:32:26,430
So if, if you think about the
inefficiency of the rest of the

565
00:32:26,432 --> 00:32:30,010
teams, like, "Take as much time as
you want," it was killing their queue.

566
00:32:30,837 --> 00:32:34,687
And Stephanie's like, "Um, uh, how
do I share this?" And, and so even

567
00:32:34,693 --> 00:32:38,407
having this culture of do whatever
you want is… That's not it either.

568
00:32:38,407 --> 00:32:41,636
It's how do we constantly
serve our clients better?

569
00:32:41,646 --> 00:32:43,255
That's the culture we're trying to get to

570
00:32:44,268 --> 00:32:44,494
Todd Kane: Yeah.

571
00:32:44,669 --> 00:32:46,205
Uh, there's so many rabbit holes here.

572
00:32:46,205 --> 00:32:46,642
This is great.

573
00:32:46,663 --> 00:32:49,323
Like we could, we could jam on
this stuff all day 'cause what that

574
00:32:49,324 --> 00:32:53,961
reminds me of is, like I encourage
people, uh, to give positive feedback.

575
00:32:53,962 --> 00:32:56,761
I, I have this structure around
this of like five to one ratio.

576
00:32:56,774 --> 00:32:59,875
You wanna give five points of
positive feedback to every one point

577
00:32:59,875 --> 00:33:04,098
of negative feedback because quite
naturally we are, uh, adaptably

578
00:33:04,098 --> 00:33:06,052
evolved to have a negativity bias.

579
00:33:06,068 --> 00:33:09,862
It's so much easier to nitpick and find
things that are wrong in any business

580
00:33:09,862 --> 00:33:14,163
environment, and people just become
disheartened with this when, your example,

581
00:33:14,190 --> 00:33:16,961
if you had taken Stephanie and held her
up to the rest of the group and be like,

582
00:33:17,158 --> 00:33:18,833
"Stephanie, you're absolutely killing it.

583
00:33:18,919 --> 00:33:22,110
Like here are all the KPIs
that are 40% lower than all

584
00:33:22,115 --> 00:33:23,350
the other peers in your team.

585
00:33:23,585 --> 00:33:26,735
Can you tell us what you're doing
differently to be able to do this?"

586
00:33:26,777 --> 00:33:30,190
And then she does like a little dog
and pony show, does some cross-training

587
00:33:30,201 --> 00:33:33,430
with the team and every- all of a
sudden everyone is benefiting from what

588
00:33:33,430 --> 00:33:37,060
she figured out and, and you maximize
that across the team rather than just

589
00:33:37,061 --> 00:33:39,165
like, "You guys are doing terrible.

590
00:33:39,185 --> 00:33:40,206
I wish you would do better.

591
00:33:40,207 --> 00:33:42,270
This needs to improve."
Like, I'm trying to

592
00:33:42,270 --> 00:33:44,525
be constructive and tell you that
you should do better, but you're

593
00:33:44,526 --> 00:33:48,236
actually demoralizing the team
rather than using the positivity of

594
00:33:48,236 --> 00:33:51,488
a single person and promoting that
in some po- positive fashion, right?

595
00:33:52,616 --> 00:33:53,920
Jeff Toister: Oh,
that's, that's very true.

596
00:33:54,009 --> 00:33:59,562
Uh, or, uh, y- you just kinda
let it, let chaos slide, right?

597
00:33:59,862 --> 00:34:00,033
Todd Kane: Yeah.

598
00:34:00,721 --> 00:34:01,728
Jeff Toister: And then that's when we say,

599
00:34:01,797 --> 00:34:03,012
Todd Kane: I wish they were better, yeah

600
00:34:03,145 --> 00:34:05,868
Jeff Toister: now we need AI because
AI will be way more efficient."

601
00:34:06,436 --> 00:34:06,828
Todd Kane: That's right.

602
00:34:06,864 --> 00:34:07,375
Yeah, yeah.

603
00:34:07,637 --> 00:34:08,671
It solves all problems.

604
00:34:09,050 --> 00:34:09,633
Jeff Toister: That's right

605
00:34:09,752 --> 00:34:12,428
Todd Kane: the oth-the other one
I, I wanted to get your thoughts on

606
00:34:12,429 --> 00:34:14,197
is, uh, the reachability paradox.

607
00:34:14,206 --> 00:34:15,845
I find this really fascinating.

608
00:34:15,845 --> 00:34:20,634
I wanna hear a little more on this of
like, um, because, uh, the example of

609
00:34:20,635 --> 00:34:24,555
where I see this show up a lot is people
will ask me like, "Hey, you know, what's

610
00:34:24,555 --> 00:34:28,697
the best portal that I can use, uh, so
that my clients can enter their tickets

611
00:34:28,697 --> 00:34:32,392
and manage their tickets and see their
tickets?" Uh, and I'm like, Well, you

612
00:34:32,392 --> 00:34:35,641
know, the portal and portals in the
industry are okay at best, like none of

613
00:34:35,641 --> 00:34:39,084
them are great, but, you know, here are
your options." Before you spend a lot of

614
00:34:39,084 --> 00:34:43,267
time on this, is this something that a
client is specifically asking you for, or

615
00:34:43,267 --> 00:34:46,946
is this something that you want them to
use and you think it would be really cool?

616
00:34:47,174 --> 00:34:50,492
Because these two things
are very, very different.

617
00:34:50,738 --> 00:34:53,277
Most portals go largely unused.

618
00:34:53,312 --> 00:34:56,668
A little bit in enterprise, I think
there's some sort of general uptake

619
00:34:56,670 --> 00:34:59,526
of this and a, and an assumption
that these things will be utilized.

620
00:34:59,819 --> 00:35:03,362
In SMB, if you tell people to go
check a portal, I, I think you're,

621
00:35:03,459 --> 00:35:06,198
like you're, you're, you're kind
of pissing up the wrong tree.

622
00:35:06,200 --> 00:35:09,706
Like the-- people are just not gonna be
interested in this in general, unless

623
00:35:09,706 --> 00:35:12,730
you have maybe an IT director who
wants to actually monitor these things.

624
00:35:13,142 --> 00:35:17,771
Um, you, you know, we're talking a bit
about, you know, using some portals

625
00:35:17,771 --> 00:35:22,555
or maybe an AI entry point for these
things, but, you know, if we're directing

626
00:35:22,556 --> 00:35:26,430
them away from people, what is, what
is the impact on whether or not people

627
00:35:26,430 --> 00:35:32,288
actually feel that there is options to
use this and, you know, you're triaging

628
00:35:32,303 --> 00:35:38,038
on, on bots versus humans, um, and you
have an idea, uh, the, uh, of the more

629
00:35:38,038 --> 00:35:41,337
that you amplify these things, the
less that they have an adoption, which

630
00:35:41,340 --> 00:35:43,563
seems sort of counterintuitive here.

631
00:35:43,580 --> 00:35:45,266
So let you take it on that.

632
00:35:45,566 --> 00:35:47,548
Jeff Toister: let's start with one thing.

633
00:35:47,583 --> 00:35:53,308
Is, in this example, is the portal,
if people were using it, does

634
00:35:53,309 --> 00:35:58,025
it save their time or make their
experience better in any way?

635
00:36:00,733 --> 00:36:03,310
And I'm, I'm asking you
just generally, does it

636
00:36:04,096 --> 00:36:05,154
Todd Kane: Uh, I think it

637
00:36:05,194 --> 00:36:06,991
would give them better insight, right?

638
00:36:06,991 --> 00:36:09,761
So like one of the things I really
advocated for, we had some portals back in

639
00:36:09,761 --> 00:36:13,499
the day at the MSP that I ran, uh, and one
of the things that I really liked about

640
00:36:13,500 --> 00:36:17,375
it is it showed like this race car track,
and it would s- show like this is when

641
00:36:17,377 --> 00:36:21,393
the cr- the ticket was created, here are
all the time entry points of when it was

642
00:36:21,440 --> 00:36:25,278
updated, and here is when it was closed
or when it's predicted to be closed.

643
00:36:25,538 --> 00:36:30,701
And I think that that, that timeframe
of visualizing the life cycle of

644
00:36:30,703 --> 00:36:32,136
a ticket can be very beneficial.

645
00:36:32,504 --> 00:36:36,187
Problem is I think you're telling
people like to self-serve, like,

646
00:36:36,187 --> 00:36:39,100
"Go find the information yourself,"
and they're like, "Really?

647
00:36:39,100 --> 00:36:40,662
Like you're giving me homework?

648
00:36:40,672 --> 00:36:42,895
Can't you just tell me
like what's going on here?"

649
00:36:43,134 --> 00:36:45,730
And this is why like people
will do like the, the ticket

650
00:36:45,784 --> 00:36:47,462
m- the, the ticket messenger.

651
00:36:47,863 --> 00:36:50,395
Like they'll call the service desk
and be like, "Hey, I just opened a

652
00:36:50,395 --> 00:36:51,886
ticket. Do you guys have that ticket?"

653
00:36:52,314 --> 00:36:52,802
Jeff Toister: Right

654
00:36:52,863 --> 00:36:54,475
Todd Kane: "Yep, we got the ticket," Right

655
00:36:54,711 --> 00:36:57,292
'Cause they just don't trust that
anything's gonna happen unless

656
00:36:57,292 --> 00:36:59,939
they contact a person and are
able to chase someone down on it.

657
00:37:00,377 --> 00:37:02,129
Jeff Toister: Well, I think
you're, you're bringing up, I

658
00:37:02,148 --> 00:37:03,243
think the core issues, right?

659
00:37:03,244 --> 00:37:06,448
There's trust, and then we're also asking
people to change how they do things.

660
00:37:07,143 --> 00:37:12,151
And it's counterintuitive, but if, if
you have a system or a portal or anything

661
00:37:12,151 --> 00:37:17,078
else that actually can be beneficial
to the people who use it, even if it's

662
00:37:17,078 --> 00:37:21,881
in certain situations, one of the ways
to improve the adoption of self-service

663
00:37:21,908 --> 00:37:23,851
is by having a human readily available.

664
00:37:24,961 --> 00:37:28,564
And so at first it's a little more
labor-intensive, so maybe I'm talking

665
00:37:28,565 --> 00:37:33,240
to that person who checks on the ticket
and says, "Hey, um, I wanna show you

666
00:37:33,240 --> 00:37:37,354
something because if y- you have another
ticket and you wanna check on it, it's

667
00:37:37,488 --> 00:37:41,315
actually a very easy, faster way for you
to do it. Do you have a minute?" Right?

668
00:37:41,355 --> 00:37:44,894
And so that takes a little extra time,
but if the person says, "Oh, wow, this

669
00:37:44,894 --> 00:37:47,842
is super easy," and then you send them
a, you know, a message with a link

670
00:37:47,845 --> 00:37:52,374
to it, a couple of steps, that person
is more likely to try that again.

671
00:37:52,919 --> 00:37:58,626
There's also been multiple studies, I've
been part of some of myself, that just

672
00:37:58,638 --> 00:38:04,867
knowing a human is available if you need
it makes someone more likely to try it on

673
00:38:04,868 --> 00:38:08,459
their own and be happier with the outcome.

674
00:38:09,587 --> 00:38:14,116
And I think we have to design
that, you know, for humans.

675
00:38:14,118 --> 00:38:17,024
Often these, these things are designed
saying, "It's gonna save us more time

676
00:38:17,025 --> 00:38:21,088
if you don't contact us and you just go
to the portal." But we're not thinking

677
00:38:21,088 --> 00:38:23,099
about the person at the other end of that.

678
00:38:23,453 --> 00:38:25,993
A- and I'll give you two
ex- two quick examples.

679
00:38:26,623 --> 00:38:34,688
One, a CIO was getting a lot of flack
because his, his service desk was

680
00:38:34,690 --> 00:38:37,793
way behind on things like, you know,
they're setting up a new office in

681
00:38:37,793 --> 00:38:41,261
Europe and, you know, they're not
ready in time, that kind of thing.

682
00:38:42,557 --> 00:38:48,432
And he goes to investigate a- and the
issue is that executives in the home

683
00:38:48,433 --> 00:38:53,679
office would bypass the ticketing system
completely and just walk in and find an

684
00:38:53,679 --> 00:38:56,159
employee and say, "I need help with this."
And what are you, what are you gonna do?

685
00:38:56,169 --> 00:38:57,781
You're gonna tell the CFO no?

686
00:38:58,200 --> 00:39:02,121
I'm trying to set up this office in,
the network for this office in Europe.

687
00:39:02,544 --> 00:39:03,766
Get in line, buddy.

688
00:39:04,254 --> 00:39:05,814
Todd Kane: shoulder tapping is difficult.

689
00:39:05,876 --> 00:39:08,301
It's even more difficult
when it's an executive

690
00:39:08,685 --> 00:39:09,370
Jeff Toister: Exactly.

691
00:39:09,377 --> 00:39:15,041
So that's what was causing all the
problems, and it, it's, it's really

692
00:39:15,042 --> 00:39:16,764
not the employee's fault in this case.

693
00:39:16,846 --> 00:39:20,929
So… But the CIO just wanted to
give them some training or something.

694
00:39:20,930 --> 00:39:23,090
I mean, that, that process was broken.

695
00:39:23,601 --> 00:39:25,642
Another company, same issue.

696
00:39:26,457 --> 00:39:28,657
They said, "We're just gonna
recognize this is what happens."

697
00:39:29,253 --> 00:39:32,436
So each member of the executive
team was assigned a person.

698
00:39:32,986 --> 00:39:33,725
That's your person.

699
00:39:33,725 --> 00:39:37,055
You need help, you go to them because,
hey, that investor presentation's

700
00:39:37,067 --> 00:39:40,506
coming up, and you probably do need
someone to just make sure it happens.

701
00:39:41,929 --> 00:39:46,054
And then we're, we're just going to
acknowledge that, and by creating

702
00:39:46,055 --> 00:39:53,018
those, uh, relationships, having a
go-to person, it allowed the, the work

703
00:39:53,018 --> 00:39:56,196
for the entire team to be smoothed
out so that the shoulder tapping

704
00:39:56,197 --> 00:39:57,654
was a lot more predictable now.

705
00:39:58,107 --> 00:40:02,089
I just have to check on maybe one
person or two executives, and that's

706
00:40:02,090 --> 00:40:05,589
it, and the rest of it I'm going to
be working the queue like normal.

707
00:40:06,259 --> 00:40:11,121
And, and so just, it was acknowledging
this is how our humans are going to work,

708
00:40:11,121 --> 00:40:14,781
so let's design a system that's efficient
and works the way our humans work.

709
00:40:14,796 --> 00:40:16,756
It, it just ended up being
a way better solution

710
00:40:18,005 --> 00:40:21,042
Todd Kane: Yeah, I think, uh, that hits
on sort of the point that I rail against

711
00:40:21,042 --> 00:40:26,869
this is, uh, it has to be a full court
press of behavioral change and education

712
00:40:27,038 --> 00:40:30,173
if you're gonna get people to adopt this
stuff and change the way that they work.

713
00:40:30,407 --> 00:40:34,040
I like your suggestion of, um, you
know, you take the ticket and then

714
00:40:34,040 --> 00:40:37,160
at the end you're like, "Hey, by the
way, there's this cool tool that you

715
00:40:37,162 --> 00:40:40,953
could use in the future," and just
re-educate them on how to use that.

716
00:40:40,965 --> 00:40:42,035
You give them support.

717
00:40:42,057 --> 00:40:46,266
It's not just sorta, "We sent an
email last month about this portal,

718
00:40:46,266 --> 00:40:48,848
And no one's using it." Like,
no, of course they're not, right?

719
00:40:48,848 --> 00:40:52,172
Because, you know, you can
assume 70% of the people didn't

720
00:40:52,173 --> 00:40:53,984
even read the email, right?

721
00:40:53,986 --> 00:40:57,314
So, like, that's, not the extent of
communication, and I think making it

722
00:40:57,321 --> 00:41:02,442
more human of like, uh, uh, as you
said, like, "This… Here's how you

723
00:41:02,444 --> 00:41:05,360
can do this in the future because
you may have multiple tickets open.

724
00:41:05,546 --> 00:41:07,272
You don't have to wait to get ahold of us.

725
00:41:07,273 --> 00:41:09,844
You can just open this link, and then
you can check on the tickets yourself.

726
00:41:09,860 --> 00:41:11,837
Like, isn't that cool," right?
And they're like, "Oh, yeah, cool.

727
00:41:11,839 --> 00:41:15,797
Okay, I'll use that in the future,"
versus just quiet being frustrated by

728
00:41:15,797 --> 00:41:19,011
the fact that people are not using the
tool that you deployed but didn't really

729
00:41:19,011 --> 00:41:20,494
educate them on how to use, right?

730
00:41:22,070 --> 00:41:23,525
Jeff Toister: And that's
that's exactly it.

731
00:41:23,528 --> 00:41:25,571
The framing is this is how it helps you.

732
00:41:26,527 --> 00:41:30,059
And, and if people believe that,
then they're more likely to try it.

733
00:41:30,467 --> 00:41:33,752
A- and if they say-- and if you say, "Hey,
I think this will save you some time.

734
00:41:33,775 --> 00:41:37,336
You'll get an answer quicker." And
you can even add, "But if that doesn't

735
00:41:37,336 --> 00:41:39,495
work for you, I'm always here to help.

736
00:41:39,822 --> 00:41:42,602
It might just be a little delay 'cause
I'm working on some other issues."

737
00:41:42,911 --> 00:41:46,269
Now you've given people the option,
and you've opened the door for them to

738
00:41:46,270 --> 00:41:50,075
say, "Well, maybe I'll try it 'cause I
know I have to wait to get that person.

739
00:41:51,035 --> 00:41:52,767
Oh, hey, it's a good
experience, all right.

740
00:41:52,768 --> 00:41:53,325
This works

741
00:41:54,482 --> 00:41:54,860
Todd Kane: 100%.

742
00:41:55,586 --> 00:41:55,765
right.

743
00:41:55,784 --> 00:41:58,136
So Jeff, uh, this has been great.

744
00:41:58,177 --> 00:41:59,690
Really appreciate all your input.

745
00:41:59,727 --> 00:42:03,360
Uh, maybe we'll close out with,
uh, sort of an actionable here.

746
00:42:03,712 --> 00:42:09,057
If an MSP owner is like, "Cool, I think
I'm gonna start deploying some AI on

747
00:42:09,058 --> 00:42:14,452
my service desk next quarter with XYZ
tool," uh, what is one thing that they

748
00:42:14,453 --> 00:42:17,310
must protect in doing that, in your mind?

749
00:42:18,976 --> 00:42:20,442
Jeff Toister: Well,
that's a great question.

750
00:42:20,442 --> 00:42:22,179
I think you have to
protect the experience.

751
00:42:23,015 --> 00:42:26,886
And what I mean by that is
the goal is not to deploy AI.

752
00:42:27,870 --> 00:42:31,474
The goal is to create a better
experience for your client to do

753
00:42:31,476 --> 00:42:33,769
it efficiently and profitably.

754
00:42:34,542 --> 00:42:38,549
And if AI is a tool that can help
you do that really, really well

755
00:42:38,954 --> 00:42:42,290
and your client is happy with
that, then that's a good move.

756
00:42:43,117 --> 00:42:46,293
And if it's not the right
tool, then don't do it.

757
00:42:46,760 --> 00:42:51,974
So it's right tool for right job, but
think about the experience first and

758
00:42:51,976 --> 00:42:56,436
finding the right tool and the right way
to deliver that experience consistently.

759
00:42:56,999 --> 00:43:01,419
That should be the correct order of
thinking rather than, "Well, let's use AI.

760
00:43:01,525 --> 00:43:03,299
Oh, let's see, how do we make it work?"

761
00:43:04,620 --> 00:43:08,155
Todd Kane: Yeah, I like that, um, thinking
about it more holistically in the client

762
00:43:08,155 --> 00:43:12,179
experience and how that, that tool is
a component of the overall experience

763
00:43:12,179 --> 00:43:16,691
rather than the tool really being focused
on an internal deployment in order

764
00:43:16,691 --> 00:43:18,194
to make things more efficient, right?

765
00:43:18,232 --> 00:43:22,456
I think you kinda mentioned that earlier
as like thinking is not incorrect, it

766
00:43:22,457 --> 00:43:28,063
just, it, it, it, uh, it sort of loses the
forest through the trees essentially of

767
00:43:28,063 --> 00:43:32,224
like what is the ultimate thing that we're
trying to do here is to create a h- high

768
00:43:32,224 --> 00:43:37,570
value experience for our partners so that
they feel value in us as their IT partner

769
00:43:37,818 --> 00:43:39,585
and will continue to use us in the future.

770
00:43:39,588 --> 00:43:45,481
Not like, "Well, we shaved, uh, you
know, 14 calls off of our, our queue

771
00:43:45,544 --> 00:43:48,657
today, and therefore that's a win,"
despite the fact that we don't know

772
00:43:48,657 --> 00:43:50,116
if the clients liked it or not, right?

773
00:43:51,694 --> 00:43:52,397
Jeff Toister: Exactly.

774
00:43:52,448 --> 00:43:57,111
I, I think the real easy way to think
of like customer or client-facing AI

775
00:43:57,735 --> 00:43:59,913
is it, it should meet three conditions.

776
00:43:59,922 --> 00:44:04,741
One is confidence, that your end user is
confident using it, so they probably will.

777
00:44:04,823 --> 00:44:06,150
If they're not confident, they won't.

778
00:44:06,826 --> 00:44:10,286
It's routine, so in other
words, we have enough process

779
00:44:10,290 --> 00:44:12,252
procedure to be able to train AI.

780
00:44:12,284 --> 00:44:13,468
This is how to do it correctly.

781
00:44:13,489 --> 00:44:14,933
This is not how to do it correctly.

782
00:44:15,551 --> 00:44:16,462
And it's predictable.

783
00:44:17,010 --> 00:44:20,944
Uh, we have to be able to get
the same result every single time

784
00:44:20,947 --> 00:44:23,835
we run the same procedure, and
if we're not getting predictable

785
00:44:23,836 --> 00:44:25,023
results, it's not working for us.

786
00:44:25,034 --> 00:44:28,174
So the, it, it's confident,
routine, and predictable.

787
00:44:28,203 --> 00:44:29,160
That spells CRAP.

788
00:44:29,743 --> 00:44:34,059
We're just gonna automate the crap
that our clients don't want to have

789
00:44:34,060 --> 00:44:37,301
to wait for a human for, and frankly,
our humans don't wanna deal with.

790
00:44:37,364 --> 00:44:40,214
And if you can focus on that
first, I think you'll be okay

791
00:44:41,463 --> 00:44:41,829
Todd Kane: That's awesome.

792
00:44:42,291 --> 00:44:43,426
All right, Jeff, this has been great.

793
00:44:43,489 --> 00:44:49,258
Uh, I'll link to your LinkedIn profile,
your book, and, uh, any other fantastic

794
00:44:49,260 --> 00:44:50,708
links to check out your content.

795
00:44:50,708 --> 00:44:54,221
Anything else that you would call
people to or, or ask them to, to check

796
00:44:54,223 --> 00:44:55,782
out if they wanna see more from you?

797
00:44:56,503 --> 00:44:58,403
Jeff Toister: I think the
book is a good place to go.

798
00:44:58,772 --> 00:45:02,846
Uh, it's, it's human service,
so humanservicebook.com.

799
00:45:03,266 --> 00:45:06,919
And also, I, I know a lot of MSPs,
a lot of help desks, et cetera, uh,

800
00:45:06,920 --> 00:45:08,816
subscribe to my, uh, newsletter.

801
00:45:08,816 --> 00:45:11,558
It's my customer service tip of
the week, and you can find that

802
00:45:11,558 --> 00:45:14,723
at toystersolutions.com/tips.

803
00:45:15,067 --> 00:45:18,982
One email once per week, one
very specific tip you can use

804
00:45:19,044 --> 00:45:20,353
to help your clients this week

805
00:45:22,292 --> 00:45:23,499
Todd Kane: Links in
the show notes as well.

806
00:45:23,578 --> 00:45:24,322
Jeff, this has been great.

807
00:45:24,420 --> 00:45:24,944
Thanks for your time

808
00:45:25,492 --> 00:45:25,877
Jeff Toister: Thank you.

809
00:45:25,878 --> 00:45:26,561
I really appreciate it.

810
00:45:26,564 --> 00:45:27,078
It's been fun