WEBVTT

1
00:00:03.320 --> 00:00:05.520
In today's episode, when AI takes over

2
00:00:05.520 --> 00:00:10.000
customer service and sales skyrocket.

3
00:00:12.120 --> 00:00:14.120
Hello, everyone. Once again, welcome

4
00:00:14.120 --> 00:00:17.880
to the XMACNA podcast. I'm

5
00:00:17.880 --> 00:00:20.640
Gustavo Fechus. Today, we have here with us

6
00:00:20.640 --> 00:00:23.119
Daniel Valladares so we can talk

7
00:00:23.119 --> 00:00:26.039
about a very important topic

8
00:00:26.039 --> 00:00:30.720
that has to do with this relationship, the

9
00:00:30.720 --> 00:00:35.640
interaction between AI and humans. After all,

10
00:00:35.640 --> 00:00:39.040
when a DF, a digital agent,

11
00:00:39.040 --> 00:00:42.480
is operating in the sales funnel,

12
00:00:42.480 --> 00:00:45.840
providing service, it's common for us

13
00:00:45.840 --> 00:00:49.680
to notice some doubts about

14
00:00:49.680 --> 00:00:53.199
how this transition happens, right, Daniel, from

15
00:00:53.199 --> 00:00:56.480
the machine to the person, right? After all,

16
00:00:56.480 --> 00:00:58.359
we're talking here about a

17
00:00:58.359 --> 00:01:01.440
full replacement of the human salesperson

18
00:01:01.440 --> 00:01:03.000
in this initial stage of customer service,

19
00:01:03.000 --> 00:01:05.439
or, on the contrary, can we

20
00:01:05.439 --> 00:01:07.640
find a way to combine these two

21
00:01:07.640 --> 00:01:09.200
technologies?

22
00:01:09.200 --> 00:01:13.200
And how would that work? I also think

23
00:01:13.200 --> 00:01:15.240
Daniel, we can also

24
00:01:15.240 --> 00:01:18.479
include in this discussion

25
00:01:18.479 --> 00:01:21.320
the participation of a special product that

26
00:01:21.320 --> 00:01:23.159
we have here at AMPDEX XMACNA, which

27
00:01:23.159 --> 00:01:25.520
is the smart call feature. In other words, how

28
00:01:25.520 --> 00:01:28.439
do we make the jump from WhatsApp

29
00:01:28.439 --> 00:01:30.320
to a phone call, right, to an

30
00:01:30.320 --> 00:01:33.000
AI-powered call as well, which can

31
00:01:33.000 --> 00:01:34.840
Schedule an appointment for a

32
00:01:34.840 --> 00:01:37.920
human salesperson. Anyway, there are several

33
00:01:37.920 --> 00:01:41.240
flows, there isn't just one, right?

34
00:01:41.240 --> 00:01:43.799
And we are very sensitive to the

35
00:01:43.799 --> 00:01:46.119
customer's process so that we can

36
00:01:46.119 --> 00:01:48.880
together with XMACNA, build an

37
00:01:48.880 --> 00:01:53.000
actually effective and positive proposal

38
00:01:53.000 --> 00:01:56.360
for the funnel. So thank you very much

39
00:01:56.360 --> 00:01:57.920
for your participation, Daniel. We're already

40
00:01:57.920 --> 00:01:59.360
wrapping up here, right? We

41
00:01:59.360 --> 00:02:01.399
just finished

42
00:02:01.399 --> 00:02:04.840
with a self-explanatory introduction,

43
00:02:04.840 --> 00:02:09.000
mentioning several of the topics that

44
00:02:09.000 --> 00:02:10.200
we'll have the chance to go deeper into

45
00:02:10.200 --> 00:02:12.080
here together with

46
00:02:12.080 --> 00:02:13.879
your participation. So, over to you,

47
00:02:13.879 --> 00:02:16.239
choose where you want to continue.

48
00:02:16.239 --> 00:02:19.000
>> Very well, awesome. Thanks again

49
00:02:19.000 --> 00:02:21.640
for the opportunity to be here. And,

50
00:02:21.640 --> 00:02:24.840
thanks also to our audience out there.

51
00:02:24.840 --> 00:02:27.080
Remember to subscribe to the channel if

52
00:02:27.080 --> 00:02:29.800
you aren't already, and leave a

53
00:02:29.800 --> 00:02:32.440
like so we can get this

54
00:02:32.440 --> 00:02:34.599
content further, right? Every

55
00:02:34.599 --> 00:02:37.239
week here, content about digital workers,

56
00:02:37.239 --> 00:02:39.400
artificial intelligence and how

57
00:02:39.400 --> 00:02:43.040
to make your business more productive. Having said

58
00:02:43.040 --> 00:02:43.319
that,

59
00:02:43.319 --> 00:02:45.080
>> Here's your tip, Daniel. Next

60
00:02:45.080 --> 00:02:47.120
time you can give out our Pix keys.

61
00:02:47.120 --> 00:02:49.080
Alright? I think this makes things easier.

62
00:02:49.080 --> 00:02:50.519
We get straight to the point.

63
00:02:50.519 --> 00:02:53.800
That's true, that's true.

64
00:02:53.800 --> 00:02:55.840
No, but I leave that one to Hermes,

65
00:02:55.840 --> 00:02:57.239
our employee. That’s

66
00:02:57.239 --> 00:02:58.800
exactly. We’d feel a little

67
00:02:58.800 --> 00:03:00.159
awkward about it, right?

68
00:03:00.159 --> 00:03:02.000
That's true.

69
00:03:02.000 --> 00:03:04.440
By the way, speaking of hybrid service,

70
00:03:04.440 --> 00:03:07.440
right?

71
00:03:08.120 --> 00:03:09.480
That's it.

72
00:03:09.480 --> 00:03:11.200
So, guys, what I

73
00:03:11.200 --> 00:03:13.400
see, right? When I started my

74
00:03:13.400 --> 00:03:15.840
journey there with digital employees,

75
00:03:15.840 --> 00:03:17.360
and especially when bringing

76
00:03:17.360 --> 00:03:18.920
digital employees into another

77
00:03:18.920 --> 00:03:20.440
business I have, which is Aurora,

78
00:03:20.440 --> 00:03:23.599
my virtual salesperson. I had, I

79
00:03:23.599 --> 00:03:26.040
noticed that it’s normal, right, for the

80
00:03:26.040 --> 00:03:27.760
customer to go through some moments,

81
00:03:27.760 --> 00:03:29.680
some phases of adaptation.

82
00:03:29.680 --> 00:03:32.239
The first moment is when

83
00:03:32.239 --> 00:03:34.879
you want to control everything

84
00:03:34.879 --> 00:03:37.920
and you’re really concerned about what

85
00:03:37.920 --> 00:03:39.799
that employee is going to say. After all,

86
00:03:39.799 --> 00:03:41.560
you’re handing over your business's key

87
00:03:41.560 --> 00:03:45.120
to a robot, basically.

88
00:03:45.120 --> 00:03:47.879
Then you think: "Man, what if it burns

89
00:03:47.879 --> 00:03:50.680
everything down here, what’s going to happen,

90
00:03:50.680 --> 00:03:53.200
right?" So this is the first

91
00:03:53.200 --> 00:03:54.959
Ready, also already have the number for the

92
00:03:54.959 --> 00:03:56.519
fire department, right?

93
00:03:56.519 --> 00:03:58.040
Exactly. Precisely.

94
00:03:58.040 --> 00:03:59.959
It might come in handy. In fact, we

95
00:03:59.959 --> 00:04:01.760
can already integrate it through

96
00:04:01.760 --> 00:04:05.480
integration, if necessary.

97
00:04:05.480 --> 00:04:08.120
Automations for different purposes.

98
00:04:08.120 --> 00:04:11.000
Exactly. So this is the

99
00:04:11.000 --> 00:04:13.599
first step, right, Gustavo? We

100
00:04:13.599 --> 00:04:15.439
try to figure out, wow, will it

101
00:04:15.439 --> 00:04:18.440
talk nonsense? Maybe it won't? And then

102
00:04:18.440 --> 00:04:21.239
cut to a few days later, at the

103
00:04:21.239 --> 00:04:23.479
moment when you hardly even look

104
00:04:23.479 --> 00:04:25.440
at that phone anymore, when you hardly

105
00:04:25.440 --> 00:04:28.360
even check each message that's

106
00:04:28.360 --> 00:04:30.320
coming in, because you're too

107
00:04:30.320 --> 00:04:33.280
busy doing your sales meetings and

108
00:04:33.280 --> 00:04:34.880
mainly selling. And it's not just

109
00:04:34.880 --> 00:04:36.840
selling a little, it's selling a lot,

110
00:04:36.840 --> 00:04:37.520
right?

111
00:04:37.520 --> 00:04:39.400
Working with hot leads, right?

112
00:04:39.400 --> 00:04:41.560
Working with hot leads. And why

113
00:04:41.560 --> 00:04:43.520
does this happen? I think

114
00:04:43.520 --> 00:04:45.800
there's a bit of mystique here too. Could it

115
00:04:45.800 --> 00:04:48.400
be that this happens because of the

116
00:04:48.400 --> 00:04:50.039
digital employee? Just because it

117
00:04:50.039 --> 00:04:53.080
joined the business, something magical

118
00:04:53.080 --> 00:04:55.560
is going to happen, some kind of fairy dust

119
00:04:55.560 --> 00:04:57.840
that will make sales go up

120
00:04:57.840 --> 00:04:59.600
automatically?

121
00:04:59.600 --> 00:05:03.160
No. But the point is, right, the

122
00:05:03.160 --> 00:05:05.880
digital employee will make

123
00:05:05.880 --> 00:05:09.680
you or your sales team talk

124
00:05:09.680 --> 00:05:12.639
more times throughout the day with qualified leads

125
00:05:12.639 --> 00:05:14.639
So think about it: everyone

126
00:05:14.639 --> 00:05:16.919
who would call, everyone who

127
00:05:16.919 --> 00:05:18.960
messaged you on WhatsApp, let's say you have 50

128
00:05:18.960 --> 00:05:21.319
WhatsApp conversations, let's suppose that

129
00:05:21.319 --> 00:05:26.160
out of those 50, 10 actually make sense, right? But

130
00:05:26.160 --> 00:05:28.720
you'd have to go through all

131
00:05:28.720 --> 00:05:32.080
50 until you get to those 10. Maybe

132
00:05:32.080 --> 00:05:35.520
by the time you get to those 10, it's already

133
00:05:35.520 --> 00:05:37.639
too late and that lead has already gone to

134
00:05:37.639 --> 00:05:40.360
another place because they were so hot that

135
00:05:40.360 --> 00:05:42.680
your slow response made them

136
00:05:42.680 --> 00:05:45.479
look for another solution, right? Uh-huh.

137
00:05:45.479 --> 00:05:48.199
So, what does the digital employee

138
00:05:48.199 --> 00:05:51.039
actually do, whether it's over the phone,

139
00:05:51.039 --> 00:05:53.919
right, like Gustavo mentioned, we have the

140
00:05:53.919 --> 00:05:55.639
possibility of making smart calls

141
00:05:55.639 --> 00:05:59.400
or on WhatsApp—well, it

142
00:05:59.400 --> 00:06:02.479
will respond to everyone in record time

143
00:06:02.479 --> 00:06:04.759
and do a qualification to ensure

144
00:06:04.759 --> 00:06:07.319
that those hot leads who need

145
00:06:07.319 --> 00:06:09.560
a human touch, who need

146
00:06:09.560 --> 00:06:12.759
a meeting with you, with your team,

147
00:06:12.759 --> 00:06:15.240
get that right away.

148
00:06:15.240 --> 00:06:18.520
The right time, right? And that way, your

149
00:06:18.520 --> 00:06:21.120
team only talks to qualified people or

150
00:06:21.120 --> 00:06:22.479
most of the people

151
00:06:22.479 --> 00:06:25.720
qualified leads. And that alone increases

152
00:06:25.720 --> 00:06:27.759
conversions. So, it's not magic, it's

153
00:06:27.759 --> 00:06:31.199
science, right? This is math and

154
00:06:31.199 --> 00:06:34.240
it makes the business, by itself,

155
00:06:34.240 --> 00:06:36.639
start to become more successful. And then,

156
00:06:36.639 --> 00:06:39.479
obviously, this generates a virtuous

157
00:06:39.479 --> 00:06:42.120
cycle, right, Gustavo? After all, if

158
00:06:42.120 --> 00:06:44.080
you have more sales coming in, if you're

159
00:06:44.080 --> 00:06:46.160
converting more, the tendency is that

160
00:06:46.160 --> 00:06:48.319
you will invest more or less in the

161
00:06:48.319 --> 00:06:51.919
business, right? And by investing in the business, the

162
00:06:51.919 --> 00:06:53.880
trend is that you generate more or fewer

163
00:06:53.880 --> 00:06:57.360
leads, right? So, this ends up creating

164
00:06:57.360 --> 00:07:00.879
a cycle that really supports

165
00:07:00.879 --> 00:07:03.240
the growth of the business, right?

166
00:07:03.240 --> 00:07:05.560
Yes. Daniel, I just wanted to add

167
00:07:05.560 --> 00:07:08.120
a point here, because we're

168
00:07:08.120 --> 00:07:10.520
not talking about a single business,

169
00:07:10.520 --> 00:07:12.879
specifically, but trying to build a

170
00:07:12.879 --> 00:07:17.039
concept that applies to any

171
00:07:17.039 --> 00:07:20.800
businesses, to any operations. And

172
00:07:20.800 --> 00:07:24.360
it seems important to highlight that

173
00:07:24.360 --> 00:07:26.840
it's part of our service protocol

174
00:07:26.840 --> 00:07:30.080
to have a deep understanding

175
00:07:30.080 --> 00:07:33.039
of how this operation works and how we

176
00:07:33.039 --> 00:07:36.479
can introduce an FD there to

177
00:07:36.479 --> 00:07:39.440
do the best possible job. That being

178
00:07:39.440 --> 00:07:41.440
said, there is a possibility that the

179
00:07:41.440 --> 00:07:45.639
FD itself, if your business allows it,

180
00:07:45.639 --> 00:07:47.759
could also do the checkout, isn't that right?

181
00:07:47.759 --> 00:07:50.599
I mean, if there's no need

182
00:07:50.599 --> 00:07:52.520
for human mediation in the middle of this

183
00:07:52.520 --> 00:07:55.280
process, the FD can start from the beginning and

184
00:07:55.280 --> 00:07:57.960
finish at the end, right? On the other hand, if

185
00:07:57.960 --> 00:08:00.560
necessary, for example, if we

186
00:08:00.560 --> 00:08:03.199
have evidence that the

187
00:08:03.199 --> 00:08:04.879
appointments

188
00:08:04.879 --> 00:08:09.159
are more successfully made through

189
00:08:09.159 --> 00:08:11.599
a phone call, we can

190
00:08:11.599 --> 00:08:13.639
move from WhatsApp to a phone call, to

191
00:08:13.639 --> 00:08:15.319
a smart call. And when we

192
00:08:15.319 --> 00:08:18.120
say this in a sentence, it doesn't fully express

193
00:08:18.120 --> 00:08:19.919
the complexity and the quality

194
00:08:19.919 --> 00:08:22.280
of the conversation that the smart call

195
00:08:22.280 --> 00:08:24.039
delivers, right? So that the person on the

196
00:08:24.039 --> 00:08:26.400
other end doesn't even realize they're

197
00:08:26.400 --> 00:08:29.120
talking to an AI. So, from this

198
00:08:29.120 --> 00:08:31.080
phone call to an appointment that could

199
00:08:31.080 --> 00:08:33.839
be a human appointment and

200
00:08:33.839 --> 00:08:36.159
in-person, although not necessarily,

201
00:08:36.159 --> 00:08:39.360
anyway, there are many possible variations

202
00:08:39.360 --> 00:08:41.760
in this funnel. But what we can

203
00:08:41.760 --> 00:08:43.640
guarantee is that we will have

204
00:08:43.640 --> 00:08:46.440
an understanding of the client's process and at the

205
00:08:46.440 --> 00:08:49.880
same time the best solution, whether

206
00:08:49.880 --> 00:08:53.360
via WhatsApp or via smart call

207
00:08:53.360 --> 00:08:55.560
to transfer this service to

208
00:08:55.560 --> 00:08:58.720
a human or not, or even redirect it

209
00:08:58.720 --> 00:09:01.680
to checkout. So, regardless of the

210
00:09:01.680 --> 00:09:05.279
type of business and their current flow,

211
00:09:05.279 --> 00:09:07.360
Support operations, we

212
00:09:07.360 --> 00:09:10.160
can, it's

213
00:09:10.160 --> 00:09:12.920
modify, right? Maximize the results

214
00:09:12.920 --> 00:09:15.800
for conversion in every one of these steps

215
00:09:15.800 --> 00:09:20.320
very quickly and,

216
00:09:20.320 --> 00:09:21.760
anyway, man, because, actually, our

217
00:09:21.760 --> 00:09:24.160
data is so, right, striking,

218
00:09:24.160 --> 00:09:25.279
Daniel, when it comes to this

219
00:09:25.279 --> 00:09:26.440
transformation.

220
00:09:26.440 --> 00:09:26.839
— Uh-huh.

221
00:09:26.839 --> 00:09:29.000
— It might sound a bit cocky, right? It sounds

222
00:09:29.000 --> 00:09:31.760
self-congratulatory to keep saying, 'wow, how do we'

223
00:09:31.760 --> 00:09:34.160
do it? But it's like, we

224
00:09:34.160 --> 00:09:37.279
get into the processes, understand them

225
00:09:37.279 --> 00:09:39.279
first of all, and there are implementations that

226
00:09:39.279 --> 00:09:41.880
are very effective, right? So I think

227
00:09:41.880 --> 00:09:44.519
that's important for the

228
00:09:44.519 --> 00:09:47.240
end client to understand, right? Regarding

229
00:09:47.240 --> 00:09:49.600
how their own business could be, um,

230
00:09:49.600 --> 00:09:51.279
boosted using these

231
00:09:51.279 --> 00:09:53.680
automations we offer, and also for the

232
00:09:53.680 --> 00:09:56.480
partner themselves, right? The ones who are

233
00:09:56.480 --> 00:09:59.519
with us today, handling a good share of the

234
00:09:59.519 --> 00:10:02.000
representations for XMACNA, right? Because sometimes

235
00:10:02.000 --> 00:10:05.079
the partner's client has these

236
00:10:05.079 --> 00:10:07.360
same questions, because they're the questions

237
00:10:07.360 --> 00:10:09.560
that reach us too, right? I think it's

238
00:10:09.560 --> 00:10:11.800
important that the person who is

239
00:10:11.800 --> 00:10:14.720
mediating that sale also, um,

240
00:10:14.720 --> 00:10:17.519
understands the various possibilities, the

241
00:10:17.519 --> 00:10:19.920
Possible models we work with

242
00:10:19.920 --> 00:10:22.120
here. Maybe you could

243
00:10:22.120 --> 00:10:23.519
expand on this

244
00:10:23.519 --> 00:10:25.760
topic, Daniel, please. No, and

245
00:10:25.760 --> 00:10:28.560
there was even a point, right, Gustavo, where it reached

246
00:10:28.560 --> 00:10:29.959
something interesting, we had

247
00:10:29.959 --> 00:10:32.680
a case here recently where a

248
00:10:32.680 --> 00:10:35.240
client reached out to us

249
00:10:35.240 --> 00:10:36.920
desperately, saying: "Guys,

250
00:10:36.920 --> 00:10:39.320
"I need you to turn off

251
00:10:39.320 --> 00:10:42.560
the digital employee immediately."

252
00:10:42.560 --> 00:10:45.800
So obviously, we already thought,

253
00:10:45.800 --> 00:10:48.360
"Oh my God, what happened to

254
00:10:48.360 --> 00:10:50.240
this employee? Is it saying something

255
00:10:50.240 --> 00:10:53.320
crazy? Then, when we

256
00:10:53.320 --> 00:10:55.079
understood what was happening,

257
00:10:55.079 --> 00:10:57.720
he said: "Man, sales increased so much

258
00:10:57.720 --> 00:11:00.440
that our order flow is way more than we can

259
00:11:00.440 --> 00:11:02.720
handle, and I need to

260
00:11:02.720 --> 00:11:04.760
restructure my company here,

261
00:11:04.760 --> 00:11:07.440
bring more people into the team so we can

262
00:11:07.440 --> 00:11:10.480
keep up, because this really is a new

263
00:11:10.480 --> 00:11:12.959
reality, right? And that was something

264
00:11:12.959 --> 00:11:16.320
totally new in the company's

265
00:11:16.320 --> 00:11:18.480
history. It's a business that's been

266
00:11:18.480 --> 00:11:22.240
around for many years already, right?

267
00:11:22.240 --> 00:11:25.079
>> There was another situation, this one

268
00:11:25.079 --> 00:11:26.519
happened a little further back, where the

269
00:11:26.519 --> 00:11:30.200
person needed, on the weekend,

270
00:11:30.200 --> 00:11:32.440
a different kind of service, right?

271
00:11:32.440 --> 00:11:34.639
Because his operation wasn't, uh, uh...

272
00:11:34.639 --> 00:11:37.600
available there on the weekend. So...

273
00:11:37.600 --> 00:11:39.360
that also happened, but let's...

274
00:11:39.360 --> 00:11:41.360
turn it off on the weekend, even though we

275
00:11:41.360 --> 00:11:43.440
can, with a prompt adjustment, actually

276
00:11:43.440 --> 00:11:45.120
make it reply one way

277
00:11:45.120 --> 00:11:47.160
during the week and another way

278
00:11:47.160 --> 00:11:49.760
on weekends, guiding

279
00:11:49.760 --> 00:11:52.519
that lead to business hours.

280
00:11:52.519 --> 00:11:54.800
Anyway, there are many possibilities, but

281
00:11:54.800 --> 00:11:56.320
what seems really

282
00:11:56.320 --> 00:12:00.480
important, Daniel, is that we, uh,

283
00:12:00.480 --> 00:12:03.600
offer both to the client and to the

284
00:12:03.600 --> 00:12:06.720
partner who's in this mediation

285
00:12:06.720 --> 00:12:08.160
the chance to try it out, right?

286
00:12:08.160 --> 00:12:10.800
That's really easy; it's

287
00:12:10.800 --> 00:12:13.160
part of our protocol too. And I

288
00:12:13.160 --> 00:12:15.440
feel like the revolution starts there, when the

289
00:12:15.440 --> 00:12:18.360
person understands what it's about, because

290
00:12:18.360 --> 00:12:20.320
if I just hear about it, we don't have

291
00:12:20.320 --> 00:12:22.600
the same sense of the experience, right?

292
00:12:22.600 --> 00:12:24.959
When you see the guy talking, the guy

293
00:12:24.959 --> 00:12:28.959
me, right, the FD speaking in your tone of voice,

294
00:12:28.959 --> 00:12:31.920
right? Representing your brand and

295
00:12:31.920 --> 00:12:35.720
following a script that is

296
00:12:35.720 --> 00:12:37.920
anyway, any human would be much

297
00:12:37.920 --> 00:12:40.480
more likely to make mistakes than the script

298
00:12:40.480 --> 00:12:42.079
you set up with the system there,

299
00:12:42.079 --> 00:12:44.199
right? This digital worker, it's

300
00:12:44.199 --> 00:12:46.000
highly skilled.

301
00:12:46.000 --> 00:12:47.959
To be able to, in an absolutely

302
00:12:47.959 --> 00:12:49.959
organic way. It's not an experience of

303
00:12:49.959 --> 00:12:52.040
chatbot, it really is.

304
00:12:52.040 --> 00:12:55.240
It's about conducting this service in a

305
00:12:55.240 --> 00:12:58.160
more prepared way, right? So, this

306
00:12:58.160 --> 00:13:00.880
is unbeatable. And it's interesting because

307
00:13:00.880 --> 00:13:04.720
when I'm dealing, you know, there in

308
00:13:04.720 --> 00:13:07.079
talking with clients or

309
00:13:07.079 --> 00:13:10.160
prospects, potential future clients of XMACNA,

310
00:13:10.160 --> 00:13:13.320
sometimes there's a big concern

311
00:13:13.320 --> 00:13:15.440
about this particular point

312
00:13:15.440 --> 00:13:18.160
that you mentioned, which is about

313
00:13:18.160 --> 00:13:23.240
humanization of service. And

314
00:13:23.240 --> 00:13:25.079
when we think like this: 'Oh, I'm

315
00:13:25.079 --> 00:13:27.839
going to put in a robot, it'll make it less human, right? A

316
00:13:27.839 --> 00:13:29.880
digital employee will make the

317
00:13:29.880 --> 00:13:31.399
service less human. We have a

318
00:13:31.399 --> 00:13:33.279
service here that we like to

319
00:13:33.279 --> 00:13:35.880
stay close to the client, right? I've already heard

320
00:13:35.880 --> 00:13:39.800
that a few times. And when we

321
00:13:39.800 --> 00:13:43.279
look at the subtlety of

322
00:13:43.279 --> 00:13:45.240
a digital employee's service

323
00:13:45.240 --> 00:13:48.600
that even goes as far as, for example, a

324
00:13:48.600 --> 00:13:51.279
client who sends something like 'God bless you'

325
00:13:51.279 --> 00:13:54.320
and it replies: 'Thank you, same to you.'

326
00:13:54.320 --> 00:13:57.720
Right? So the client who sends 'Happy

327
00:13:57.720 --> 00:13:59.399
Easter', it will also reply:

328
00:13:59.399 --> 00:14:01.120
'Happy Easter to you and your

329
00:14:01.120 --> 00:14:03.199
family.' Wow, this level of

330
00:14:03.199 --> 00:14:05.880
semantic understanding is really impressive.

331
00:14:05.880 --> 00:14:07.880
happen, right? Because the guy says a

332
00:14:07.880 --> 00:14:09.759
thing there that's absolutely

333
00:14:09.759 --> 00:14:11.800
incorporated into the context of the interaction,

334
00:14:11.800 --> 00:14:12.279
right?

335
00:14:12.279 --> 00:14:14.440
Exactly. And man, when we talk, right?

336
00:14:14.440 --> 00:14:17.279
And here we... I do training

337
00:14:17.279 --> 00:14:20.360
also with sales teams, and when I

338
00:14:20.360 --> 00:14:23.040
go there, there's a lot of talk about SPIN,

339
00:14:23.040 --> 00:14:25.519
a lot is said about a series of techniques and

340
00:14:25.519 --> 00:14:28.079
sales methodologies, and there's one in

341
00:14:28.079 --> 00:14:30.639
particular that's very important, and that

342
00:14:30.639 --> 00:14:32.519
often goes unnoticed, which is

343
00:14:32.519 --> 00:14:35.199
rapport, which might even be the most

344
00:14:35.199 --> 00:14:37.279
important of all, which is the power

345
00:14:37.279 --> 00:14:39.360
to connect with the person on the

346
00:14:39.360 --> 00:14:40.959
other side, right?

347
00:14:40.959 --> 00:14:44.560
And in this, as incredible as it may seem,

348
00:14:44.560 --> 00:14:47.399
digital employees really teach us,

349
00:14:47.399 --> 00:14:49.440
right?

350
00:14:49.440 --> 00:14:51.040
They, for example, wouldn't reply

351
00:14:51.040 --> 00:14:52.880
"thank you" to a message like "God bless you"

352
00:14:52.880 --> 00:14:54.800
like you did. They would reply

353
00:14:54.800 --> 00:14:55.639
"amen."

354
00:14:55.639 --> 00:14:56.800
Amen.

355
00:14:56.800 --> 00:14:59.639
Ah, so

356
00:14:59.639 --> 00:15:01.360
the listener, come back here so you

357
00:15:01.360 --> 00:15:03.040
can notice this difference.

358
00:15:03.040 --> 00:15:07.600
That's true. It's true. So I

359
00:15:07.600 --> 00:15:09.759
realize that.

360
00:15:09.759 --> 00:15:12.600
So it really is, indeed, very

361
00:15:12.600 --> 00:15:15.639
Subtle, right? And like that, we notice the

362
00:15:15.639 --> 00:15:18.839
adaptive power it has to understand

363
00:15:18.839 --> 00:15:21.639
the way that lead wants

364
00:15:21.639 --> 00:15:23.839
to be treated. If it's a lead, sometimes, that

365
00:15:23.839 --> 00:15:25.480
or a client who wants to be approached in a

366
00:15:25.480 --> 00:15:27.360
more direct way, it will be handled

367
00:15:27.360 --> 00:15:29.440
a bit more directly. If it's someone who

368
00:15:29.440 --> 00:15:31.440
wants to chat more, it will engage

369
00:15:31.440 --> 00:15:34.319
more too. So it really delivers

370
00:15:34.319 --> 00:15:36.319
what is needed at that

371
00:15:36.319 --> 00:15:37.560
moment, right?

372
00:15:37.560 --> 00:15:39.079
Great, Daniel. Look, I think we've

373
00:15:39.079 --> 00:15:41.319
had the chance here to talk a bit

374
00:15:41.319 --> 00:15:44.920
about, well, the various

375
00:15:44.920 --> 00:15:47.279
possibilities of building an

376
00:15:47.279 --> 00:15:49.000
automation, right? Uh-huh.

377
00:15:49.000 --> 00:15:51.360
With artificial intelligence in several

378
00:15:51.360 --> 00:15:53.319
parts of the process, but also in

379
00:15:53.319 --> 00:15:55.800
the customer service of a business,

380
00:15:55.800 --> 00:15:59.240
of a company. And at the end, we leave our

381
00:15:59.240 --> 00:16:01.959
renewed invitation for everyone who's

382
00:16:01.959 --> 00:16:05.519
been with us so far to check out the site

383
00:16:05.519 --> 00:16:07.399
of XMACNA.

384
00:16:07.399 --> 00:16:09.519
Chat with Hervis, you'll definitely be

385
00:16:09.519 --> 00:16:11.480
surprised. He's our digital

386
00:16:11.480 --> 00:16:13.839
employee, our SDR who's there

387
00:16:13.839 --> 00:16:15.880
available for customer support. You can even

388
00:16:15.880 --> 00:16:17.759
have an interaction with him

389
00:16:17.759 --> 00:16:19.279
saying: 'Hey, can you

390
00:16:19.279 --> 00:16:21.000
call me, please?' so you can have the

391
00:16:21.000 --> 00:16:22.720
the smart call experience

392
00:16:22.720 --> 00:16:25.440
also. Call and you'll have the chance to

393
00:16:25.440 --> 00:16:28.959
really talk and already feel

394
00:16:28.959 --> 00:16:30.639
in practice what the experience of this

395
00:16:30.639 --> 00:16:31.600
product is like.

396
00:16:31.600 --> 00:16:33.839
Yeah, and here's a really

397
00:16:33.839 --> 00:16:35.600
interesting thing about Hermes, right? Which is the

398
00:16:35.600 --> 00:16:38.920
following: sometimes, as AI,

399
00:16:38.920 --> 00:16:41.720
even though it's trending and being talked about a lot,

400
00:16:41.720 --> 00:16:44.680
sometimes we still have doubts about

401
00:16:44.680 --> 00:16:46.480
how AI can really be

402
00:16:46.480 --> 00:16:48.240
implemented in my business, because

403
00:16:48.240 --> 00:16:50.160
we know every business has its

404
00:16:50.160 --> 00:16:52.720
own particularity, right? So, ask

405
00:16:52.720 --> 00:16:55.560
Hermes something like: 'Look, Hermes, here I do X

406
00:16:55.560 --> 00:16:58.560
thing, my company sells ping-pong balls,

407
00:16:58.560 --> 00:17:00.759
how can you help me?

408
00:17:00.759 --> 00:17:02.800
And you'll see that he'll

409
00:17:02.800 --> 00:17:06.000
give you many real and

410
00:17:06.000 --> 00:17:08.679
concrete options for how to implement it.

411
00:17:08.679 --> 00:17:10.640
Very good. So, Daniel, I thank you again

412
00:17:10.640 --> 00:17:13.959
for being here with us, and to

413
00:17:13.959 --> 00:17:16.199
you who stayed with us until now,

414
00:17:16.199 --> 00:17:17.839
you're also invited

415
00:17:17.839 --> 00:17:20.520
to share this content with anyone else

416
00:17:20.520 --> 00:17:22.520
who might be interested in it. Thank you

417
00:17:22.520 --> 00:17:24.280
and see you next time.

418
00:17:24.280 --> 00:17:28.439
Thanks, everyone. See you later.

419
00:17:28.960 --> 00:17:31.960
เฮ