WEBVTT

1
00:00:03.360 --> 00:00:06.399
In today's episode, Official API, less

2
00:00:06.399 --> 00:00:09.040
bans, more stability for your

3
00:00:09.040 --> 00:00:11.639
operation.

4
00:00:11.639 --> 00:00:13.599
Hello, once again, welcome

5
00:00:13.599 --> 00:00:16.320
to the videocast here at XMACNA. I'm

6
00:00:16.320 --> 00:00:18.560
Gustavo Fechus, and once again I'm here with

7
00:00:18.560 --> 00:00:21.080
my friend Daniel Valladares so we can

8
00:00:21.080 --> 00:00:23.359
talk about

9
00:00:23.359 --> 00:00:26.640
several aspects involving the

10
00:00:26.640 --> 00:00:30.000
provision of services, let's say, and

11
00:00:30.000 --> 00:00:33.079
solutions with artificial intelligence mediation.

12
00:00:33.079 --> 00:00:35.280
artificial. We are here in a

13
00:00:35.280 --> 00:00:38.280
very important campaign, right, Daniel,

14
00:00:38.280 --> 00:00:42.239
talking about this

15
00:00:42.239 --> 00:00:46.199
very complete XMACNA sales solution,

16
00:00:46.199 --> 00:00:49.039
which starts with an FD, with a digital

17
00:00:49.039 --> 00:00:51.640
employee, then goes through a

18
00:00:51.640 --> 00:00:54.280
conversation portal for managing all of the

19
00:00:54.280 --> 00:00:58.120
interaction in the FDs with the

20
00:00:58.120 --> 00:01:01.120
clients and leads. And also includes

21
00:01:01.120 --> 00:01:04.080
an automatic CRM, right, Daniel? Where

22
00:01:04.080 --> 00:01:06.560
we have all this record of

23
00:01:06.560 --> 00:01:08.920
information in great detail. If you haven't yet

24
00:01:08.920 --> 00:01:11.680
checked out this new feature, go back here to

25
00:01:11.680 --> 00:01:15.560
your feed and our channel, where you'll find

26
00:01:15.560 --> 00:01:17.159
all the episodes here from our

27
00:01:17.159 --> 00:01:18.680
videocast,

28
00:01:18.680 --> 00:01:21.479
our social media and website, everywhere

29
00:01:21.479 --> 00:01:23.360
we've been sharing this

30
00:01:23.360 --> 00:01:26.200
solution. But today, we are

31
00:01:26.200 --> 00:01:29.320
I proposed here to talk about a really

32
00:01:29.320 --> 00:01:32.640
important topic, which is a real and

33
00:01:32.640 --> 00:01:36.320
frequent pain for those who, let's say, use

34
00:01:36.320 --> 00:01:39.920
conversational technologies,

35
00:01:39.920 --> 00:01:42.399
right, Daniel? Especially for those

36
00:01:42.399 --> 00:01:46.119
who are not yet using the official API

37
00:01:46.119 --> 00:01:49.000
from Meta. And Daniel will have the opportunity

38
00:01:49.000 --> 00:01:50.320
to talk a bit about this for

39
00:01:50.320 --> 00:01:53.560
us. The big problem we are here

40
00:01:53.560 --> 00:01:57.439
talking about today is getting banned.

41
00:01:57.439 --> 00:01:59.920
Some of you, possibly, in this

42
00:01:59.920 --> 00:02:03.119
content, may have come here

43
00:02:03.119 --> 00:02:05.880
precisely because you have already gone through

44
00:02:05.880 --> 00:02:07.560
this

45
00:02:07.560 --> 00:02:09.599
unpleasant experience, right, Daniel, of

46
00:02:09.599 --> 00:02:14.360
having your number banned because you had

47
00:02:14.360 --> 00:02:17.400
a non-official connection, through

48
00:02:17.400 --> 00:02:21.560
an unofficial API. And these are

49
00:02:21.560 --> 00:02:24.160
real problems that make it much harder to

50
00:02:24.160 --> 00:02:26.720
operate and compromise service and the

51
00:02:26.720 --> 00:02:29.480
work of those already dealing with

52
00:02:29.480 --> 00:02:32.360
some kind of automation. So, Daniel,

53
00:02:32.360 --> 00:02:34.239
please talk a bit about this. I’d also

54
00:02:34.239 --> 00:02:37.040
like you, in your answer, to please,

55
00:02:37.040 --> 00:02:40.280
tell us how we here at XMACNA

56
00:02:40.280 --> 00:02:43.480
also have the

57
00:02:43.480 --> 00:02:46.760
solution to all these problems, OK?

58
00:02:46.760 --> 00:02:50.000
That's it. I remember that old phrase,

59
00:02:50.000 --> 00:02:51.640
"your problems are over," right?

60
00:02:51.640 --> 00:02:52.959
That's what I meant to say, but I

61
00:02:52.959 --> 00:02:54.720
I forgot. But I got the idea.

62
00:02:54.720 --> 00:02:55.720
of it.

63
00:02:55.720 --> 00:02:58.680
Yeah, I did get it. Well, guys, I think

64
00:02:58.680 --> 00:03:00.239
before anything else, thanks

65
00:03:00.239 --> 00:03:03.319
again for tuning in. For

66
00:03:03.319 --> 00:03:05.239
those of you arriving now, go ahead and

67
00:03:05.239 --> 00:03:08.560
consider liking this video, leave your

68
00:03:08.560 --> 00:03:11.120
subscribe to the channel to get

69
00:03:11.120 --> 00:03:14.920
more videos like this. And let's go to the

70
00:03:14.920 --> 00:03:18.440
message of the day here. So, man, it's,

71
00:03:18.440 --> 00:03:20.080
the thing, I think Meta has been

72
00:03:20.080 --> 00:03:22.120
working on this for a while now, right?

73
00:03:22.120 --> 00:03:26.000
to professionalize the tool in some way,

74
00:03:26.000 --> 00:03:28.480
and many people even

75
00:03:28.480 --> 00:03:31.000
I even saw Meta

76
00:03:31.000 --> 00:03:34.080
as the villain, but in the end I

77
00:03:34.080 --> 00:03:36.599
realize they're working to

78
00:03:36.599 --> 00:03:40.200
make WhatsApp, which is this

79
00:03:40.200 --> 00:03:43.120
powerful relationship and sales channel,

80
00:03:43.120 --> 00:03:46.239
not go through what

81
00:03:46.239 --> 00:03:49.360
emails went through in the past with

82
00:03:49.360 --> 00:03:52.360
a flood of spam, right? How many

83
00:03:52.360 --> 00:03:54.239
people out there—I myself have at least

84
00:03:54.239 --> 00:03:56.599
two or three email inboxes that

85
00:03:56.599 --> 00:03:59.720
got lost in time because I

86
00:03:59.720 --> 00:04:03.079
only get spam in those inboxes and

87
00:04:03.079 --> 00:04:06.000
they became irrelevant, right? So,

88
00:04:06.000 --> 00:04:08.400
Meta has been working to

89
00:04:08.400 --> 00:04:09.959
professionalize

90
00:04:09.959 --> 00:04:13.280
these business contacts inside

91
00:04:13.280 --> 00:04:17.160
WhatsApp, and with that, making the

92
00:04:17.160 --> 00:04:19.919
migration to the official API, where you

93
00:04:19.919 --> 00:04:22.360
have, you know, a cost per message sent,

94
00:04:22.360 --> 00:04:24.520
and there are some rules to

95
00:04:24.520 --> 00:04:28.120
follow regarding message templates.

96
00:04:28.120 --> 00:04:30.880
And even though I see this

97
00:04:30.880 --> 00:04:33.720
purpose as a noble one,

98
00:04:33.720 --> 00:04:37.080
going through this migration process isn’t

99
00:04:37.080 --> 00:04:40.120
such a simple process, right?

100
00:04:40.120 --> 00:04:43.039
Nowadays,

101
00:04:43.039 --> 00:04:45.160
many people have been going through

102
00:04:45.160 --> 00:04:47.160
temporary blocks, which are blocks

103
00:04:47.160 --> 00:04:51.400
of 24 hours, and then, the progression,

104
00:04:51.400 --> 00:04:53.280
you know, from that temporary block is actually

105
00:04:53.280 --> 00:04:56.440
the ban. And I myself went through a

106
00:04:56.440 --> 00:04:58.639
ban, I was offline for almost 15 days.

107
00:04:58.639 --> 00:05:02.360
I finally managed to

108
00:05:02.360 --> 00:05:06.720
register the official API, but in fact

109
00:05:06.720 --> 00:05:08.520
there are some points that I think are

110
00:05:08.520 --> 00:05:12.080
important for us to consider, right? And it's worth

111
00:05:12.080 --> 00:05:14.120
mentioning as well that the ban lasted

112
00:05:14.120 --> 00:05:17.960
15 days, not because of the service

113
00:05:17.960 --> 00:05:20.600
from XMACNA itself, but because of

114
00:05:20.600 --> 00:05:22.919
Meta itself, you know, the requests, the replies,

115
00:05:22.919 --> 00:05:25.720
right? Anyway, I should have migrated earlier.

116
00:05:25.720 --> 00:05:28.319
And here’s a message for those of you who still

117
00:05:28.319 --> 00:05:31.240
haven’t migrated. So, migrate. Let's talk a bit

118
00:05:31.240 --> 00:05:35.319
about how to do it, right? Hey,

119
00:05:35.319 --> 00:05:36.600
Gustavo, I think it's

120
00:05:36.600 --> 00:05:39.520
important. And even demystifying

121
00:05:39.520 --> 00:05:42.280
Another point I want to mention,

122
00:05:42.280 --> 00:05:43.800
I've heard some clients say:

123
00:05:43.800 --> 00:05:45.840
"Oh, I don't want to use AI because AI

124
00:05:45.840 --> 00:05:48.600
is banning accounts, right?" But actually,

125
00:05:48.600 --> 00:05:51.319
guys, the banning doesn't happen

126
00:05:51.319 --> 00:05:54.400
because of using artificial intelligence

127
00:05:54.400 --> 00:05:56.639
to manage your customer service on your

128
00:05:56.639 --> 00:06:01.199
WhatsApp, okay? This banning or

129
00:06:01.199 --> 00:06:03.360
even temporary blocks, they

130
00:06:03.360 --> 00:06:05.479
will happen even with human actions,

131
00:06:05.479 --> 00:06:08.639
as long as you send messages

132
00:06:08.639 --> 00:06:10.880
to a lot of people, sometimes

133
00:06:10.880 --> 00:06:13.360
the same messages. And 'a lot of people',

134
00:06:13.360 --> 00:06:15.680
quote-unquote, actually isn't as many

135
00:06:15.680 --> 00:06:17.960
as before. In the past, we said

136
00:06:17.960 --> 00:06:22.199
'a lot' was 400 or 300 people,

137
00:06:22.199 --> 00:06:25.199
per day, right? Nowadays, in the current

138
00:06:25.199 --> 00:06:29.120
scenario, 'a lot' sometimes means

139
00:06:29.120 --> 00:06:32.960
15, 20, 50. But definitely not more than

140
00:06:32.960 --> 00:06:36.720
50, for sure. So this is an

141
00:06:36.720 --> 00:06:39.880
important point. Anyway, what

142
00:06:39.880 --> 00:06:42.680
you need, so that you

143
00:06:42.680 --> 00:06:47.199
can manage to migrate to

144
00:06:47.199 --> 00:06:48.960
the official API, right? You will need to

145
00:06:48.960 --> 00:06:52.240
create an app inside the

146
00:06:52.240 --> 00:06:56.000
MetaDevelopers platform and set up a webhook there, okay?

147
00:06:56.000 --> 00:06:58.160
I'll go over this part

148
00:06:58.160 --> 00:07:01.319
quickly, because we

149
00:07:01.319 --> 00:07:05.240
can help you with that, right?

150
00:07:05.240 --> 00:07:09.479
If you are a XMACNA client. And the

151
00:07:09.479 --> 00:07:11.560
Besides that, what you actually need to

152
00:07:11.560 --> 00:07:14.240
have on hand, which can be important

153
00:07:14.240 --> 00:07:16.840
in this process is your company's documentation.

154
00:07:16.840 --> 00:07:18.599
So, you'll need your company's registration card,

155
00:07:18.599 --> 00:07:21.360
the CNPJ, and your personal documents

156
00:07:21.360 --> 00:07:23.000
if you are the administrator of this

157
00:07:23.000 --> 00:07:25.080
company, because you'll need to do

158
00:07:25.080 --> 00:07:27.840
a verification in the app in case

159
00:07:27.840 --> 00:07:30.240
you haven't done it yet. You will also

160
00:07:30.240 --> 00:07:32.400
need a credit card as well

161
00:07:32.400 --> 00:07:33.919
on hand, because you'll need to

162
00:07:33.919 --> 00:07:37.319
register your payment method right away.

163
00:07:37.319 --> 00:07:40.080
And another point that has been

164
00:07:40.080 --> 00:07:43.080
generating a lot of discussion is

165
00:07:43.080 --> 00:07:45.840
regarding the display name on

166
00:07:45.840 --> 00:07:48.960
WhatsApp, right? Because when you

167
00:07:48.960 --> 00:07:51.400
register on the official API, you need to

168
00:07:51.400 --> 00:07:53.440
insert the WhatsApp name there, which will

169
00:07:53.440 --> 00:07:56.319
be your company's name and should be a

170
00:07:56.319 --> 00:07:59.879
name that Meta will recognize and

171
00:07:59.879 --> 00:08:02.960
approve, just like Meta does

172
00:08:02.960 --> 00:08:06.479
also with the message templates,

173
00:08:06.479 --> 00:08:09.400
right? So, when you put the

174
00:08:09.400 --> 00:08:13.560
company name, many times you

175
00:08:13.560 --> 00:08:14.879
will face, for example—I'll give you

176
00:08:14.879 --> 00:08:17.120
an example from my own business

177
00:08:17.120 --> 00:08:19.960
here, which is Eventos Exponenciais. So,

178
00:08:19.960 --> 00:08:22.680
within Meta's naming guidelines,

179
00:08:22.680 --> 00:08:24.440
naming

180
00:08:24.440 --> 00:08:28.240
possible for Meta, it does not allow

181
00:08:28.240 --> 00:08:31.080
Adjectives and exponentials. In this case,

182
00:08:31.080 --> 00:08:33.640
it was recognizing it as if it were a

183
00:08:33.640 --> 00:08:36.919
adjective, but in reality, it isn't. And then

184
00:08:36.919 --> 00:08:39.560
I had to go through a whole process of

185
00:08:39.560 --> 00:08:41.159
rejections

186
00:08:41.159 --> 00:08:44.800
automatic rejections, so I could finally get

187
00:08:44.800 --> 00:08:46.560
after, I think, if I'm not mistaken, the

188
00:08:46.560 --> 00:08:49.160
third or fourth rejection, it unlocked

189
00:08:49.160 --> 00:08:52.440
an option for a, for a, for a

190
00:08:52.440 --> 00:08:55.720
manual review, right? So it's worth

191
00:08:55.720 --> 00:08:58.760
getting ahead, understanding the

192
00:08:58.760 --> 00:09:00.720
guidelines, how they work, right?

193
00:09:00.720 --> 00:09:02.920
What are the possibilities you have

194
00:09:02.920 --> 00:09:04.800
for putting the name there, for example,

195
00:09:04.800 --> 00:09:06.560
to make this process faster

196
00:09:06.560 --> 00:09:09.360
and register, you know, also think about

197
00:09:09.360 --> 00:09:11.399
the message templates you’ll use

198
00:09:11.399 --> 00:09:13.760
to start conversations, so you can

199
00:09:13.760 --> 00:09:16.440
also register them and wait for

200
00:09:16.440 --> 00:09:18.640
their approval, so that you

201
00:09:18.640 --> 00:09:22.680
can, as soon as the API is released

202
00:09:22.680 --> 00:09:25.480
actually use things the way you

203
00:09:25.480 --> 00:09:30.040
imagine, okay? Now, not everything is darkness

204
00:09:30.040 --> 00:09:34.640
and chaos in the official API environment. The

205
00:09:34.640 --> 00:09:36.959
moment you create the API,

206
00:09:36.959 --> 00:09:39.240
regardless of whether you have

207
00:09:39.240 --> 00:09:41.600
the name approval or not, template approval or not,

208
00:09:41.600 --> 00:09:45.680
you are able to use the

209
00:09:45.680 --> 00:09:49.040
official WhatsApp for incoming contacts, right?

210
00:09:49.040 --> 00:09:51.920
So, for those cases where there is a

211
00:09:51.920 --> 00:09:54.600
Good inbound flow, right? A good flow.

212
00:09:54.600 --> 00:09:56.720
Leads coming in and such, this doesn't

213
00:09:56.720 --> 00:09:59.360
have such a major impact. You just

214
00:09:59.360 --> 00:10:01.279
can't

215
00:10:01.279 --> 00:10:05.720
send out messages, right? Send, uh,

216
00:10:05.720 --> 00:10:08.079
start conversations, but you can

217
00:10:08.079 --> 00:10:10.120
still interact with the leads who

218
00:10:10.120 --> 00:10:13.680
are coming in, until the whole approval

219
00:10:13.680 --> 00:10:16.680
process is finished, and then you

220
00:10:16.680 --> 00:10:20.440
can, you know, move forward with your

221
00:10:20.440 --> 00:10:23.760
campaigns and everything else, okay? Now, um,

222
00:10:23.760 --> 00:10:26.000
this process, guys, I recommend that

223
00:10:26.000 --> 00:10:29.399
you don't do it the way I did,

224
00:10:29.399 --> 00:10:32.360
which is to wait until the very last moment, uh,

225
00:10:32.360 --> 00:10:34.880
when Meta forces you to do it

226
00:10:34.880 --> 00:10:38.000
and you end up having to do this process

227
00:10:38.000 --> 00:10:41.519
in a last-minute, less ideal way, or

228
00:10:41.519 --> 00:10:44.519
ideally, you need to stay ahead of things,

229
00:10:44.519 --> 00:10:47.920
because it could happen that you get

230
00:10:47.920 --> 00:10:49.760
a ban or a block, like

231
00:10:49.760 --> 00:10:51.440
it happened to me. That will leave you

232
00:10:51.440 --> 00:10:54.200
offline for much longer, right? If

233
00:10:54.200 --> 00:10:57.279
you do the migration properly, uh,

234
00:10:57.279 --> 00:11:00.160
without having a block or ban,

235
00:11:00.160 --> 00:11:02.160
without getting banned, you’ll be able to, uh,

236
00:11:02.160 --> 00:11:04.560
like I said, start using it right

237
00:11:04.560 --> 00:11:06.720
away for the incoming leads at least,

238
00:11:06.720 --> 00:11:09.680
the ones coming in and reaching out, right? And,

239
00:11:09.680 --> 00:11:12.519
then the approval time also ends up being

240
00:11:12.519 --> 00:11:14.079
faster, because you didn't have

241
00:11:14.079 --> 00:11:17.360
No account blocking, okay? So...

242
00:11:17.360 --> 00:11:20.959
It's worth taking precautions and already

243
00:11:20.959 --> 00:11:23.680
making this migration as soon as possible. If

244
00:11:23.680 --> 00:11:25.959
you're using it professionally,

245
00:11:25.959 --> 00:11:28.760
with broadcasts, with digital employees,

246
00:11:28.760 --> 00:11:32.399
with AI running there, it's really important.

247
00:11:32.399 --> 00:11:34.399
Actually, Gustavo, I think it's worth

248
00:11:34.399 --> 00:11:38.079
mentioning something else: “Oh,

249
00:11:38.079 --> 00:11:40.399
Daniel, but when I migrate to the official API

250
00:11:40.399 --> 00:11:44.760
there are costs and so on, right? But it's

251
00:11:44.760 --> 00:11:46.880
true, we do have a cost per

252
00:11:46.880 --> 00:11:49.800
message, right? And we tend to look

253
00:11:49.800 --> 00:11:52.279
at this cost, but in a way

254
00:11:52.279 --> 00:11:54.519
like, oh, this will make my

255
00:11:54.519 --> 00:11:57.079
business impossible, right? Because you're looking at it,

256
00:11:57.079 --> 00:12:00.279
if I send 10,000 messages, this

257
00:12:00.279 --> 00:12:03.160
times 40 cents is a significant amount.

258
00:12:03.160 --> 00:12:06.200
It's considerable. However, it's worth

259
00:12:06.200 --> 00:12:09.079
analyzing this from another perspective,

260
00:12:09.079 --> 00:12:12.240
which is: what is your average ticket?

261
00:12:12.240 --> 00:12:14.079
So, you have an average ticket

262
00:12:14.079 --> 00:12:15.959
let's say an average ticket

263
00:12:15.959 --> 00:12:17.720
on the lower end, where you have an average ticket of

264
00:12:17.720 --> 00:12:20.600
R$200, R$300 per customer.

265
00:12:20.600 --> 00:12:23.000
Let me just interrupt you on

266
00:12:23.000 --> 00:12:24.760
the next point before we do the

267
00:12:24.760 --> 00:12:25.680
calculation.

268
00:12:25.680 --> 00:12:28.240
There's that 24-hour window, right,

269
00:12:28.240 --> 00:12:28.680
within

270
00:12:28.680 --> 00:12:29.600
Exactly.

271
00:12:29.600 --> 00:12:31.519
>> Within which there is no cost at all.

272
00:12:31.519 --> 00:12:32.880
So, for example, if you have a

273
00:12:32.880 --> 00:12:37.000
automation made by XMACNA, which

274
00:12:37.000 --> 00:12:38.600
will obviously reply in

275
00:12:38.600 --> 00:12:41.079
seconds there, instantly, there is no

276
00:12:41.079 --> 00:12:43.800
need to worry about this cost, right?

277
00:12:43.800 --> 00:12:44.519
Right? Uh-huh.

278
00:12:44.519 --> 00:12:46.680
>> So, just a small contribution here

279
00:12:46.680 --> 00:12:48.440
because I think obviously we

280
00:12:48.440 --> 00:12:50.920
need to consider it, but let's go back to that.

281
00:12:50.920 --> 00:12:53.240
Suicide, man. This, this is important

282
00:12:53.240 --> 00:12:56.480
even before, right? Before getting back to the account,

283
00:12:56.480 --> 00:12:58.199
it's also important for the following

284
00:12:58.199 --> 00:13:01.240
reason, right? For those who have an inbound flow,

285
00:13:01.240 --> 00:13:02.920
which is what I

286
00:13:02.920 --> 00:13:06.480
mentioned a little earlier, let's

287
00:13:06.480 --> 00:13:08.000
suppose this person sends a message at a

288
00:13:08.000 --> 00:13:11.920
time when there is no human agent

289
00:13:11.920 --> 00:13:14.279
there to take the call.

290
00:13:14.279 --> 00:13:16.440
Let's suppose your business is a

291
00:13:16.440 --> 00:13:19.079
business that works from Monday to Friday

292
00:13:19.079 --> 00:13:22.959
and then on Friday at 7 PM, your company

293
00:13:22.959 --> 00:13:25.959
closes and someone sends a message. Those 24

294
00:13:25.959 --> 00:13:29.320
hours will run until Saturday, right? And

295
00:13:29.320 --> 00:13:30.880
you will contact them again on

296
00:13:30.880 --> 00:13:33.399
Monday. For you to contact this

297
00:13:33.399 --> 00:13:35.240
person again, that's when you have the

298
00:13:35.240 --> 00:13:37.839
cost, which is the opening message,

299
00:13:37.839 --> 00:13:41.040
right? And then you need the person to reply

300
00:13:41.040 --> 00:13:43.639
so you have 24 hours to talk

301
00:13:43.639 --> 00:13:46.560
with them. Yeah, but if you

302
00:13:46.560 --> 00:13:49.040
had answered at the moment they

303
00:13:49.040 --> 00:13:51.279
reached out, you would already have those 24 hours without

304
00:13:51.279 --> 00:13:53.680
any extra cost, right? Right? I think

305
00:13:53.680 --> 00:13:55.399
it's important to emphasize that,

306
00:13:55.399 --> 00:13:56.959
Gustavo, that sometimes those who aren't so

307
00:13:56.959 --> 00:13:59.560
used to it don't know these

308
00:13:59.560 --> 00:14:02.360
details, right? And that's important because

309
00:14:02.360 --> 00:14:04.680
if you have a cost of 40

310
00:14:04.680 --> 00:14:07.079
cents per message and your average ticket

311
00:14:07.079 --> 00:14:10.480
is R$ 200, even if you send,

312
00:14:10.480 --> 00:14:12.880
remember that this cost is for

313
00:14:12.880 --> 00:14:15.680
opening the conversation, okay? So it's a

314
00:14:15.680 --> 00:14:18.240
message where you will pay that amount

315
00:14:18.240 --> 00:14:20.680
to have 24 hours to talk to the

316
00:14:20.680 --> 00:14:23.800
person, okay? So, looking at this

317
00:14:23.800 --> 00:14:27.279
scenario, what are you going to do? Three,

318
00:14:27.279 --> 00:14:30.440
maybe four, at most, follow-ups with

319
00:14:30.440 --> 00:14:33.079
that person outside of that time window, right? Like

320
00:14:33.079 --> 00:14:35.199
the most, right? And from what I see, most

321
00:14:35.199 --> 00:14:37.279
of the clients I see here,

322
00:14:37.279 --> 00:14:38.839
tend to have a lower volume of

323
00:14:38.839 --> 00:14:41.920
follow-ups because, paid follow-ups,

324
00:14:41.920 --> 00:14:44.959
right? Because some of those follow-ups will

325
00:14:44.959 --> 00:14:48.079
happen within the open conversation window

326
00:14:48.079 --> 00:14:51.680
of those 24 hours, right? So look, even

327
00:14:51.680 --> 00:14:55.399
if you end up spending R$ 1, R$ 2 on

328
00:14:55.399 --> 00:14:58.480
cost with that person, when they

329
00:14:58.480 --> 00:15:02.199
convert, you'll earn R$ 200,

330
00:15:02.199 --> 00:15:04.720
right, on that average ticket value, for example.

331
00:15:04.720 --> 00:15:07.680
So, in fact, there is a cost to

332
00:15:07.680 --> 00:15:10.399
doing these openings, right, but

333
00:15:10.399 --> 00:15:12.680
when you look at your average ticket and

334
00:15:12.680 --> 00:15:15.440
how much you are investing in the lead,

335
00:15:15.440 --> 00:15:18.399
it's worth analyzing this, right? And if

336
00:15:18.399 --> 00:15:21.199
you are also investing a lot in

337
00:15:21.199 --> 00:15:23.320
sending messages that aren't giving you

338
00:15:23.320 --> 00:15:25.240
a return, it's a sign that you have

339
00:15:25.240 --> 00:15:28.000
a list that maybe doesn't make sense

340
00:15:28.000 --> 00:15:30.639
for you to make any effort with it.

341
00:15:30.639 --> 00:15:32.120
Even if it were free, you would be

342
00:15:32.120 --> 00:15:35.160
there wasting time, right, with a lead

343
00:15:35.160 --> 00:15:37.040
that really won't convert, with a

344
00:15:37.040 --> 00:15:39.959
lead that is disqualified, right? So,

345
00:15:39.959 --> 00:15:41.480
so

346
00:15:41.480 --> 00:15:45.920
When you have an AI there, right, to

347
00:15:45.920 --> 00:15:47.720
handle this service, to do this

348
00:15:47.720 --> 00:15:50.600
qualification, you can already, within

349
00:15:50.600 --> 00:15:54.279
that 24-hour window, even

350
00:15:54.279 --> 00:15:57.880
understand if that lead is qualified and

351
00:15:57.880 --> 00:16:00.399
would be able to receive other

352
00:16:00.399 --> 00:16:02.800
impacts, and maybe even paid impacts from

353
00:16:02.800 --> 00:16:05.639
your side to communicate something that is

354
00:16:05.639 --> 00:16:07.199
happening in your business, which will

355
00:16:07.199 --> 00:16:09.360
make that lead end up

356
00:16:09.360 --> 00:16:13.560
convert, right? I think I

357
00:16:13.560 --> 00:16:15.880
talked a lot here, let me pass it a bit to

358
00:16:15.880 --> 00:16:18.360
you, Gustavo, how do you

359
00:16:18.360 --> 00:16:20.920
see it, right, also from your point of

360
00:16:20.920 --> 00:16:24.040
view, this API issue

361
00:16:24.040 --> 00:16:26.920
Official, right? How has your

362
00:16:26.920 --> 00:16:28.399
experience been? I shared a bit of

363
00:16:28.399 --> 00:16:30.079
mine, and I’d also like to know how

364
00:16:30.079 --> 00:16:32.920
yours has been regarding these

365
00:16:32.920 --> 00:16:35.759
issues that have been happening.

366
00:16:35.759 --> 00:16:37.920
Alright, Daniel, thanks for the question.

367
00:16:37.920 --> 00:16:39.600
I think more than just saying how

368
00:16:39.600 --> 00:16:41.240
my experience with the API has been,

369
00:16:41.240 --> 00:16:43.519
it would be good to talk about how

370
00:16:43.519 --> 00:16:45.279
the experience with the unofficial API

371
00:16:45.279 --> 00:16:49.519
has been, right?

372
00:16:58.160 --> 00:17:00.120
Sometimes people have paid traffic

373
00:17:00.120 --> 00:17:02.319
campaigns, right, and automatic

374
00:17:02.319 --> 00:17:04.000
messages from Meta to

375
00:17:04.000 --> 00:17:05.640
WhatsApp don’t arrive. Anyway,

376
00:17:05.640 --> 00:17:09.640
web synchronization with the phone.

377
00:17:09.640 --> 00:17:11.839
So, there are many pieces in an

378
00:17:11.839 --> 00:17:14.720
unofficial puzzle that make

379
00:17:14.720 --> 00:17:18.319
us, at this moment, encourage

380
00:17:18.319 --> 00:17:21.480
strongly the migration to the official API.

381
00:17:21.480 --> 00:17:23.240
Basically, here’s the thing: Meta

382
00:17:23.240 --> 00:17:25.959
owns WhatsApp and is

383
00:17:25.959 --> 00:17:27.520
obviously working to make

384
00:17:27.520 --> 00:17:32.120
WhatsApp, besides being

385
00:17:32.120 --> 00:17:35.960
safe from the email effect, you know, from spam,

386
00:17:35.960 --> 00:17:38.160
which Daniel mentioned, that it

387
00:17:38.160 --> 00:17:41.919
also, obviously, is in

388
00:17:41.919 --> 00:17:43.679
control of this business rule, right?

389
00:17:43.679 --> 00:17:45.760
Making unofficial APIs

390
00:17:45.760 --> 00:17:49.760
always have, uh, uh, always have

391
00:17:49.760 --> 00:17:53.679
difficulties of, uh

392
00:17:53.679 --> 00:17:55.919
providing a service, of existing in the

393
00:17:55.919 --> 00:17:56.480
practice.

394
00:17:56.480 --> 00:17:58.760
Stability that matters to all of us,

395
00:17:58.760 --> 00:18:00.559
right? So, I think this is an

396
00:18:00.559 --> 00:18:02.720
important aspect and I wanted to, uh, already

397
00:18:02.720 --> 00:18:05.880
start wrapping up here, Daniel,

398
00:18:05.880 --> 00:18:08.440
to reinforce the fact that XMACNA clients

399
00:18:08.440 --> 00:18:13.360
of XMACNA who are interested, uh, in this

400
00:18:13.360 --> 00:18:16.520
topic and finally want, uh, this

401
00:18:16.520 --> 00:18:21.000
migration. Daniel, he was, uh, brief

402
00:18:21.000 --> 00:18:22.840
here in describing a path

403
00:18:22.840 --> 00:18:24.600
needed to make this migration.

404
00:18:24.600 --> 00:18:26.600
So, going solo,

405
00:18:26.600 --> 00:18:28.600
I can safely say that

406
00:18:28.600 --> 00:18:30.559
it's a lot of work. If you don't have a

407
00:18:30.559 --> 00:18:35.080
familiarity with this, uh, environment,

408
00:18:35.080 --> 00:18:37.440
it's worth leaving it to us. We

409
00:18:37.440 --> 00:18:39.640
do it, even for free

410
00:18:39.640 --> 00:18:41.520
for clients

411
00:18:41.520 --> 00:18:43.360
this migration, right? We follow the

412
00:18:43.360 --> 00:18:46.600
process, handle it, and deliver it to you

413
00:18:46.600 --> 00:18:49.320
with everything working. So, it's

414
00:18:49.320 --> 00:18:51.760
worth it. Obviously, we are also

415
00:18:51.760 --> 00:18:53.760
interested

416
00:18:53.760 --> 00:18:55.880
in this migration for the stability that

417
00:18:55.880 --> 00:18:59.159
this brings to both sides of the operation.

418
00:18:59.159 --> 00:19:01.520
So, I think it's a historic window

419
00:19:01.520 --> 00:19:03.840
that's important, right, Daniel, for us

420
00:19:03.840 --> 00:19:04.679
to be able to

421
00:19:04.679 --> 00:19:07.600
>> Making this process happen. And I

422
00:19:07.600 --> 00:19:11.159
honestly understand that it's like this

423
00:19:11.159 --> 00:19:14.039
currently it's 6 cents in dollars, right? The

424
00:19:14.039 --> 00:19:17.720
message that exceeds the 24-hour window

425
00:19:17.720 --> 00:19:20.240
hours, and there are different, uh

426
00:19:20.240 --> 00:19:23.559
possibilities for sending messages,

427
00:19:23.559 --> 00:19:25.400
including mass messaging.

428
00:19:25.400 --> 00:19:28.440
>> Uh-huh. But through the digital employee

429
00:19:28.440 --> 00:19:31.960
if the person made contact, they

430
00:19:31.960 --> 00:19:33.440
will reply immediately, so there won't

431
00:19:33.440 --> 00:19:36.840
be any charge for this

432
00:19:36.840 --> 00:19:38.440
operation, okay?

433
00:19:38.440 --> 00:19:40.159
from the perspective of how much the

434
00:19:40.159 --> 00:19:42.120
interaction costs and from the perspective of

435
00:19:42.120 --> 00:19:44.200
how much the migration itself costs,

436
00:19:44.200 --> 00:19:46.600
because we're in this campaign at this

437
00:19:46.600 --> 00:19:47.640
moment.

438
00:19:47.640 --> 00:19:50.120
>> Yeah, and I have to say I tried to do it

439
00:19:50.120 --> 00:19:53.240
on my own, by my own choice

440
00:19:53.240 --> 00:19:56.360
and honestly, it was at least

441
00:19:56.360 --> 00:19:59.240
traumatic, to say the least. So,

442
00:19:59.240 --> 00:20:01.799
it's really worth having all the

443
00:20:01.799 --> 00:20:04.120
support from our dev team at

444
00:20:04.120 --> 00:20:06.919
XMACNA for this task, you know?

445
00:20:06.919 --> 00:20:09.559
So, great. Daniel, thanks again

446
00:20:09.559 --> 00:20:12.039
for your courage in being with us. To

447
00:20:12.039 --> 00:20:14.559
you who stayed with us until now,

448
00:20:14.559 --> 00:20:16.159
please also share this content with

449
00:20:16.159 --> 00:20:18.400
anyone else who might be interested.

450
00:20:18.400 --> 00:20:20.720
A hug and see you next time.

451
00:20:20.720 --> 00:20:24.960
Thanks, everyone. See you later.

452
00:20:27.720 --> 00:20:28.000
เ