WEBVTT 1 00:00:00.000 --> 00:00:03.000 Hello, 2 00:00:03.274 --> 00:00:05.294 [music] 3 00:00:07.859 --> 00:00:09.879 [music] 4 00:00:17.800 --> 00:00:19.800 everyone. Once again, very 5 00:00:19.800 --> 00:00:23.560 welcome to the XMACNA podcast. I am 6 00:00:23.560 --> 00:00:26.679 Gustavo Fechus and I am pleased to 7 00:00:26.679 --> 00:00:30.039 once again welcome Daniel Valladares, 8 00:00:30.039 --> 00:00:33.760 who leads the project, 9 00:00:33.760 --> 00:00:37.879 and the partners group here at XMACNA. So, 10 00:00:37.879 --> 00:00:40.000 Daniel, thank you once again for your 11 00:00:40.000 --> 00:00:41.480 time and the chance for us to 12 00:00:41.480 --> 00:00:45.239 have this conversation. Today, I wanted to suggest we 13 00:00:45.239 --> 00:00:47.840 go a bit deeper. I think 14 00:00:47.840 --> 00:00:51.239 it's always worth considering a bit 15 00:00:51.239 --> 00:00:55.120 about our 16 00:00:55.120 --> 00:00:57.640 digital employee. Well, I think our 17 00:00:57.640 --> 00:01:01.359 conversation today will be about 18 00:01:01.359 --> 00:01:03.760 this topic, considering the fact that 19 00:01:03.760 --> 00:01:06.920 around this topic, we 20 00:01:06.920 --> 00:01:09.280 have a bit of history to contextualize 21 00:01:09.280 --> 00:01:11.799 too, right? Where it came from, the 22 00:01:11.799 --> 00:01:14.600 development of this solution, this 23 00:01:14.600 --> 00:01:16.759 main solution that we have today 24 00:01:16.759 --> 00:01:18.880 at XMACNA, although it's not the 25 00:01:18.880 --> 00:01:23.520 only one. But I'd like to 26 00:01:23.520 --> 00:01:25.840 suggest that we talk in more 27 00:01:25.840 --> 00:01:29.560 detail about this, 28 00:01:29.560 --> 00:01:32.280 because we have a certain context that 29 00:01:32.280 --> 00:01:36.360 is worth sharing with those following us 30 00:01:36.360 --> 00:01:40.040 so they can get to know it and take advantage as well. 31 00:01:40.040 --> 00:01:42.600 solutions, the services we provide today 32 00:01:42.600 --> 00:01:45.719 are ready to offer. So, 33 00:01:45.719 --> 00:01:48.520 once again, thank you for your time and 34 00:01:48.520 --> 00:01:49.719 let's get started. Where would you like to 35 00:01:49.719 --> 00:01:50.840 start? 36 00:01:50.840 --> 00:01:53.119 Wonderful. Welcome, everyone. 37 00:01:53.119 --> 00:01:55.280 Thanks again, Gustavo, for 38 00:01:55.280 --> 00:01:57.360 being here. It's always a pleasure, right, 39 00:01:57.360 --> 00:02:00.520 to have this opportunity to talk to 40 00:02:00.520 --> 00:02:04.799 the XMACNA audience. And well, I think 41 00:02:04.799 --> 00:02:07.360 it's important for us to give context 42 00:02:07.360 --> 00:02:10.920 about XMACNA and digital employees 43 00:02:10.920 --> 00:02:13.599 for the following reason, right, Gustavo? You see, 44 00:02:13.599 --> 00:02:17.840 that lately we've 45 00:02:17.840 --> 00:02:20.959 seen huge growth, right, 46 00:02:20.959 --> 00:02:23.560 when it comes to the topic of 47 00:02:23.560 --> 00:02:26.720 artificial intelligence. And sometimes I get 48 00:02:26.720 --> 00:02:28.560 the impression that people sometimes 49 00:02:28.560 --> 00:02:31.800 think that we created 50 00:02:31.800 --> 00:02:34.160 XMACNA just to ride this wave, when in 51 00:02:34.160 --> 00:02:38.480 fact, XMACNA started long 52 00:02:38.480 --> 00:02:41.599 before it was even called XMACNA and already had 53 00:02:41.599 --> 00:02:44.200 digital employees working there, 54 00:02:44.200 --> 00:02:48.400 for the business even before 55 00:02:48.400 --> 00:02:50.640 artificial intelligence was 56 00:02:50.640 --> 00:02:53.560 the hype it is today, right? 57 00:02:53.560 --> 00:02:56.680 So, I'd really like 58 00:02:56.680 --> 00:02:59.560 to hear from you, telling 59 00:02:59.560 --> 00:03:01.480 our audience about 60 00:03:01.480 --> 00:03:05.200 how all this actually started and, anyway, 61 00:03:05.200 --> 00:03:08.480 So, where did we come from, how were we 62 00:03:08.480 --> 00:03:11.319 created, what do 63 00:03:11.319 --> 00:03:13.599 digital employees 'feed on', and so on, right? 64 00:03:13.599 --> 00:03:15.599 How do they live, right? Where do they live, 65 00:03:15.599 --> 00:03:16.799 How, where do they exist. 66 00:03:16.799 --> 00:03:18.720 Exactly. So, let's go. Today on 67 00:03:18.720 --> 00:03:21.720 Globo Repórter we're going to dive deeper into 68 00:03:21.720 --> 00:03:24.560 these topics here. And, as you said 69 00:03:24.560 --> 00:03:26.480 in other words, long before it was 70 00:03:26.480 --> 00:03:30.280 trendy, we were already here, 71 00:03:30.280 --> 00:03:34.680 working a lot and focusing on 72 00:03:34.680 --> 00:03:37.000 the subject of technology and the application of 73 00:03:37.000 --> 00:03:39.760 artificial intelligence in the platform 74 00:03:39.760 --> 00:03:42.040 Redigir, which is another company that we 75 00:03:42.040 --> 00:03:44.280 have, we say it's kind of a 76 00:03:44.280 --> 00:03:47.080 sister company, and it's an 77 00:03:47.080 --> 00:03:49.280 educational solution that's in another market 78 00:03:49.280 --> 00:03:52.920 niche, but where we've been 79 00:03:52.920 --> 00:03:55.640 working for many years, 80 00:03:55.640 --> 00:03:59.079 Daniel, on developing 81 00:03:59.079 --> 00:04:02.959 solutions that could really scale this 82 00:04:02.959 --> 00:04:08.040 business, bring more quality, 83 00:04:08.040 --> 00:04:09.680 predictability, 84 00:04:09.680 --> 00:04:13.159 scale, increase efficiency in 85 00:04:13.159 --> 00:04:15.840 several areas of the company. So 86 00:04:15.840 --> 00:04:18.359 I can speak from my department, 87 00:04:18.359 --> 00:04:20.479 which is the pedagogical department. 88 00:04:20.479 --> 00:04:24.080 We've gone through major changes 89 00:04:24.080 --> 00:04:25.720 in efficiency that are very important 90 00:04:25.720 --> 00:04:28.000 for operational efficiency, right? We're saying 91 00:04:28.000 --> 00:04:32.479 with solutions that brought improvements 92 00:04:32.479 --> 00:04:35.120 in how our service was perceived by about 93 00:04:35.120 --> 00:04:37.240 28%. 94 00:04:37.240 --> 00:04:39.560 Overnight. So, you know, 95 00:04:39.560 --> 00:04:41.120 overnight it feels like magic, 96 00:04:41.120 --> 00:04:43.560 but actually it takes time to develop a 97 00:04:43.560 --> 00:04:46.440 solution, right? We spent years on 98 00:04:46.440 --> 00:04:48.400 research and development before getting 99 00:04:48.400 --> 00:04:51.840 there, but once it's applied, then the 100 00:04:51.840 --> 00:04:54.160 magic happens, right? We have, well, 101 00:04:54.160 --> 00:04:56.160 very solid feedback regarding this 102 00:04:56.160 --> 00:04:59.600 process. And not just in the educational area, 103 00:04:59.600 --> 00:05:01.800 but in so many other areas of the 104 00:05:01.800 --> 00:05:04.919 Rede Gir platform. We also started 105 00:05:04.919 --> 00:05:07.919 learning to apply and develop, um, 106 00:05:07.919 --> 00:05:10.639 solutions based on artificial 107 00:05:10.639 --> 00:05:14.440 intelligence for the commercial sector, 108 00:05:14.440 --> 00:05:17.360 you know, in sales, customer service, 109 00:05:17.360 --> 00:05:20.720 support, and IT itself, of course. 110 00:05:20.720 --> 00:05:22.800 So, we have quite a long story 111 00:05:22.800 --> 00:05:26.600 to tell and I'll spare 112 00:05:26.600 --> 00:05:28.600 the listeners, hoping that everyone 113 00:05:28.600 --> 00:05:30.639 will just believe me, okay? The result 114 00:05:30.639 --> 00:05:33.360 is this: We created a revolution at 115 00:05:33.360 --> 00:05:35.919 Rede Gir and then at some point we looked around 116 00:05:35.919 --> 00:05:40.560 trying, actually, to figure out 117 00:05:40.560 --> 00:05:43.560 who else could also make this 118 00:05:43.560 --> 00:05:46.840 move in other segments, in other 119 00:05:46.840 --> 00:05:48.919 companies, since we already had 120 00:05:48.919 --> 00:05:51.000 such solid results in our own 121 00:05:51.000 --> 00:05:55.280 it's our own operation. So, at this 122 00:05:55.280 --> 00:05:58.919 moment, we founded XMACNA as a 123 00:05:58.919 --> 00:06:02.840 spinoff from the Redir platform, bringing 124 00:06:02.840 --> 00:06:05.120 it into other niches and other 125 00:06:05.120 --> 00:06:07.960 markets. Many of the solutions we 126 00:06:07.960 --> 00:06:11.520 already tested at Redir before, 127 00:06:11.520 --> 00:06:13.000 at another time and continue to test, 128 00:06:13.000 --> 00:06:14.720 by the way. But 129 00:06:14.720 --> 00:06:17.080 now, here at XMACNA, we're scaling this 130 00:06:17.080 --> 00:06:19.560 solution in a very major way, 131 00:06:19.560 --> 00:06:22.120 and I think that's where the idea comes from that 132 00:06:22.120 --> 00:06:24.599 interests us here, which is about the product, 133 00:06:24.599 --> 00:06:27.800 the most important one we have, 134 00:06:27.800 --> 00:06:31.199 which is the digital employee, and I'd 135 00:06:31.199 --> 00:06:33.800 now like to ask for your input 136 00:06:33.800 --> 00:06:36.639 here, Daniel, to help us with a 137 00:06:36.639 --> 00:06:38.479 characterization that I think is very 138 00:06:38.479 --> 00:06:42.400 important, and now for us to give a 139 00:06:42.400 --> 00:06:45.680 bit more attention, which is: why does the 140 00:06:45.680 --> 00:06:47.759 DE, as we call it, the 141 00:06:47.759 --> 00:06:51.360 digital employee, the DE, we don't 142 00:06:51.360 --> 00:06:54.039 think or it wouldn't be as accurate 143 00:06:54.039 --> 00:06:55.960 to consider it, first of all, a 144 00:06:55.960 --> 00:07:00.360 chatbot, and secondly, an agent of 145 00:07:00.360 --> 00:07:04.080 EA, right? Because that name 'EA agent' or 146 00:07:04.080 --> 00:07:07.240 chatbot, even though they refer to things 147 00:07:07.240 --> 00:07:11.479 that can sometimes be similar or confusing, 148 00:07:11.479 --> 00:07:14.240 they are different. And the digital employee 149 00:07:14.240 --> 00:07:16.800 is also truly different from these 150 00:07:16.800 --> 00:07:18.440 other solutions in a very 151 00:07:18.440 --> 00:07:21.000 Important. So, go a bit deeper 152 00:07:21.000 --> 00:07:22.479 on this topic for us, please, because I 153 00:07:22.479 --> 00:07:24.240 think it's worth us continuing the 154 00:07:24.240 --> 00:07:25.720 discussion from there. 155 00:07:25.720 --> 00:07:28.319 Perfect. Well, I think it's 156 00:07:28.319 --> 00:07:30.319 important, and also, guys, let me 157 00:07:30.319 --> 00:07:33.160 invite you here as well, right? 158 00:07:33.160 --> 00:07:36.120 We have a class where we talk 159 00:07:36.120 --> 00:07:38.599 about the difference between automation and 160 00:07:38.599 --> 00:07:40.840 artificial intelligence in our 161 00:07:40.840 --> 00:07:42.720 'Sales Machine with AI' training. 162 00:07:42.720 --> 00:07:44.400 We'll leave it in the card here in this 163 00:07:44.400 --> 00:07:46.440 video. So, if you haven't seen it 164 00:07:46.440 --> 00:07:48.879 yet, I recommend you check it out. 165 00:07:48.879 --> 00:07:51.599 And I think there you'll be able 166 00:07:51.599 --> 00:07:53.800 to see a practical example of what 167 00:07:53.800 --> 00:07:56.080 I'm going to talk about now, right? But 168 00:07:56.080 --> 00:07:57.639 >> Wow, if you haven't watched it, you're missing out! 169 00:07:57.639 --> 00:08:00.960 Honestly, free content, 170 00:08:00.960 --> 00:08:03.120 >> that's really valuable, right? So, 171 00:08:03.120 --> 00:08:05.240 pedagogically, 172 00:08:05.240 --> 00:08:08.120 of course, I think it's really worth it. So, 173 00:08:08.120 --> 00:08:10.520 I also want to reinforce the invitation you 174 00:08:10.520 --> 00:08:12.479 just made to us, Daniel. 175 00:08:12.479 --> 00:08:15.520 >> Perfect. So, everyone, let's go. 176 00:08:15.520 --> 00:08:18.240 First, a chatbot is that famous 'press 177 00:08:18.240 --> 00:08:21.919 1, press 2,' right? Which came about 178 00:08:21.919 --> 00:08:25.319 replacing the old PABX systems, right? Who 179 00:08:25.319 --> 00:08:28.159 has never dealt with PABX on a call, 180 00:08:28.159 --> 00:08:29.319 right? When you called a company and 181 00:08:29.319 --> 00:08:31.280 That little song would play, 182 00:08:31.280 --> 00:08:33.599 you called, right? And then, press one, 183 00:08:33.599 --> 00:08:35.640 press two and so on. So, 184 00:08:35.640 --> 00:08:37.360 Can you do it again for us, please, 185 00:08:37.360 --> 00:08:39.599 just the sound effect part that I found 186 00:08:39.599 --> 00:08:41.800 to be of incredible quality. 187 00:08:41.800 --> 00:08:42.640 Very well. [laughter] 188 00:08:42.640 --> 00:08:44.560 All right, you can go on now, Daniel. 189 00:08:44.560 --> 00:08:45.120 No problem. 190 00:08:45.120 --> 00:08:46.120 That was it. 191 00:08:46.120 --> 00:08:51.440 And so, in this, when you press 192 00:08:51.440 --> 00:08:54.720 it ends up being transcribed later, right? 193 00:08:54.720 --> 00:08:56.240 Transcribed isn’t the word, but it’s 194 00:08:56.240 --> 00:08:59.000 later translated to the digital 195 00:08:59.000 --> 00:09:01.440 channels, right? Through chatbots. 196 00:09:01.440 --> 00:09:05.000 So, even today you find several 197 00:09:05.000 --> 00:09:07.880 situations where you press there, or call, 198 00:09:07.880 --> 00:09:09.640 to reach a company, right, to get in touch with 199 00:09:09.640 --> 00:09:12.560 a certain company, and it says, look, 200 00:09:12.560 --> 00:09:14.279 for finance, press one; for 201 00:09:14.279 --> 00:09:17.200 sales, press two, and so on. And then 202 00:09:17.200 --> 00:09:18.680 what happens is the conversation isn’t 203 00:09:18.680 --> 00:09:21.279 a smooth conversation, right? Because, 204 00:09:21.279 --> 00:09:23.680 actually, you are not really 205 00:09:23.680 --> 00:09:25.120 interacting with artificial intelligence. 206 00:09:25.120 --> 00:09:27.120 You're dealing with an 207 00:09:27.120 --> 00:09:29.920 automation. So that's the invitation for you 208 00:09:29.920 --> 00:09:33.360 to experience, right? Automation versus 209 00:09:33.360 --> 00:09:36.680 artificial intelligence. So, 210 00:09:36.680 --> 00:09:39.200 here is the definition of what a chatbot is, 211 00:09:39.200 --> 00:09:40.680 which is an automation and not an 212 00:09:40.680 --> 00:09:43.040 artificial intelligence, then we go 213 00:09:43.040 --> 00:09:44.839 to the AI agent. 214 00:09:44.839 --> 00:09:48.480 The AI agent has 215 00:09:48.480 --> 00:09:51.040 a series of capabilities, among 216 00:09:51.040 --> 00:09:52.880 them, talking to people, right? 217 00:09:52.880 --> 00:09:55.560 So, for example, an agent 218 00:09:55.560 --> 00:09:57.200 can have the ability to 219 00:09:57.200 --> 00:10:00.320 chat on WhatsApp and so on, 220 00:10:00.320 --> 00:10:04.480 but it is limited to interacting 221 00:10:04.480 --> 00:10:07.680 within that specific channel, and with a 222 00:10:07.680 --> 00:10:11.120 defined context as well. The AI employee, 223 00:10:11.120 --> 00:10:12.839 or digital employee as we call 224 00:10:12.839 --> 00:10:14.920 it here, the FD, has other capabilities. 225 00:10:14.920 --> 00:10:18.920 The FD can do more than that. 226 00:10:18.920 --> 00:10:21.800 So, besides chatting with 227 00:10:21.800 --> 00:10:24.720 people on WhatsApp, it can also 228 00:10:24.720 --> 00:10:27.760 interact over the phone, 229 00:10:27.760 --> 00:10:30.279 via email, make a 230 00:10:30.279 --> 00:10:32.600 note in your Google Calendar, 231 00:10:32.600 --> 00:10:35.240 or on any calendar you use. 232 00:10:35.240 --> 00:10:38.399 It will classify all the information 233 00:10:38.399 --> 00:10:40.839 collected through this conversation 234 00:10:40.839 --> 00:10:43.959 and show everything on a 235 00:10:43.959 --> 00:10:45.880 platform where you can have 236 00:10:45.880 --> 00:10:48.920 follow-up. And beyond that, it 237 00:10:48.920 --> 00:10:50.720 can also interact with other 238 00:10:50.720 --> 00:10:52.760 systems you have in your 239 00:10:52.760 --> 00:10:55.680 ecosystem through custom integrations. 240 00:10:55.680 --> 00:10:58.480 Right? So, because 241 00:10:58.480 --> 00:11:00.120 Why do we call it an employee? 242 00:11:00.120 --> 00:11:02.160 It's exactly because the analogy that fits best 243 00:11:02.160 --> 00:11:04.880 is this one. If you hire 244 00:11:04.880 --> 00:11:07.320 an employee to do, for example, 245 00:11:07.320 --> 00:11:10.240 an SDR to handle client interactions, 246 00:11:10.240 --> 00:11:12.839 or to be technical support in your 247 00:11:12.839 --> 00:11:16.519 company, that human employee 248 00:11:16.519 --> 00:11:19.160 would do all these tasks that our 249 00:11:19.160 --> 00:11:22.440 digital employee will also do, which is 250 00:11:22.440 --> 00:11:24.760 receiving this information, entering 251 00:11:24.760 --> 00:11:28.240 it into the system, interacting with other 252 00:11:28.240 --> 00:11:31.079 processes that will make this 253 00:11:31.079 --> 00:11:32.839 happen, right? Making sure that the 254 00:11:32.839 --> 00:11:35.399 problem that you want solved 255 00:11:35.399 --> 00:11:38.440 actually gets resolved. So, Gustavo, I even 256 00:11:38.440 --> 00:11:40.200 wanted to add something here, which 257 00:11:40.200 --> 00:11:44.040 is the following: it's possible, right, 258 00:11:44.040 --> 00:11:45.920 actually, it's not just that it's 259 00:11:45.920 --> 00:11:50.079 possible. It's actually very common for us to be 260 00:11:50.079 --> 00:11:52.839 asked here to create 261 00:11:52.839 --> 00:11:55.160 digital employees that interact 262 00:11:55.160 --> 00:11:57.760 with the end customer, with clients 263 00:11:57.760 --> 00:12:01.200 in support, sales, or 264 00:12:01.200 --> 00:12:04.320 technical support, in something 265 00:12:04.320 --> 00:12:08.240 like that. But there's so much 266 00:12:08.240 --> 00:12:10.200 more to it. And I think it's important for us 267 00:12:10.200 --> 00:12:12.079 to explore this as well to open up the 268 00:12:12.079 --> 00:12:14.199 minds of those listening to us 269 00:12:14.199 --> 00:12:17.440 right now, which is that these 270 00:12:17.440 --> 00:12:20.639 digital employees can also 271 00:12:20.639 --> 00:12:24.360 To be support employees for your team, 272 00:12:24.360 --> 00:12:27.120 supporting the team, right? As Gustavo 273 00:12:27.120 --> 00:12:29.120 mentioned here, maybe he hasn’t 274 00:12:29.120 --> 00:12:32.880 explained this point much, but the 275 00:12:32.880 --> 00:12:35.079 start of XMACNA actually happened not 276 00:12:35.079 --> 00:12:37.880 with digital employees who were 277 00:12:37.880 --> 00:12:40.240 interacting with the public, but rather with 278 00:12:40.240 --> 00:12:42.800 digital employees who were being 279 00:12:42.800 --> 00:12:46.519 support and copilots for the team, right? So, 280 00:12:46.519 --> 00:12:48.320 in that sense, what we can 281 00:12:48.320 --> 00:12:50.240 think about, looking at our sales environment, 282 00:12:50.240 --> 00:12:53.079 which is where we have a 283 00:12:53.079 --> 00:12:56.040 stronger presence currently, this 284 00:12:56.040 --> 00:12:57.680 digital employee could be a 285 00:12:57.680 --> 00:13:00.959 worker that generates proposals, 286 00:13:00.959 --> 00:13:03.040 who will 287 00:13:03.040 --> 00:13:05.880 assist with a CRM update, 288 00:13:05.880 --> 00:13:08.880 who helps create an 289 00:13:08.880 --> 00:13:10.440 email. For example, if you received 290 00:13:10.440 --> 00:13:13.040 a reply from a client and you’re not 291 00:13:13.040 --> 00:13:16.240 really sure how to reply to that 292 00:13:16.240 --> 00:13:18.560 message, whether it’s by email or WhatsApp, 293 00:13:18.560 --> 00:13:20.079 you can use this copilot and say: 294 00:13:20.079 --> 00:13:22.800 "Hey, help me with this reply," and it will 295 00:13:22.800 --> 00:13:24.680 already write you a response, 296 00:13:24.680 --> 00:13:27.680 taking into account the company’s 297 00:13:27.680 --> 00:13:30.959 information, your company’s tone of voice, and so on, 298 00:13:30.959 --> 00:13:34.160 right? So there are a lot of 299 00:13:34.160 --> 00:13:35.880 possibilities with digital employees. 300 00:13:35.880 --> 00:13:38.079 And looking at the broader scope, 301 00:13:38.079 --> 00:13:40.440 WhatsApp as well, and we do this with 302 00:13:40.440 --> 00:13:42.720 quite a lot here, we 303 00:13:42.720 --> 00:13:44.600 include these digital employees 304 00:13:44.600 --> 00:13:46.959 in groups as well. So, besides 305 00:13:46.959 --> 00:13:49.480 interacting one-on-one, you have these 306 00:13:49.480 --> 00:13:51.720 possibilities to use it in groups 307 00:13:51.720 --> 00:13:54.800 to open support tickets as well, 308 00:13:54.800 --> 00:13:56.440 all these features that I 309 00:13:56.440 --> 00:13:59.480 mentioned here, all of this could be there 310 00:13:59.480 --> 00:14:01.759 in the group, right? Summing up. So, 311 00:14:01.759 --> 00:14:04.120 for example, summarize here everything we 312 00:14:04.120 --> 00:14:06.680 talked about so we have an agenda for a 313 00:14:06.680 --> 00:14:09.320 next meeting, right? Anyway, minutes, an 314 00:14:09.320 --> 00:14:11.560 infinite memory, right? Like, the 315 00:14:11.560 --> 00:14:13.800 compilation of discussions that 316 00:14:13.800 --> 00:14:16.680 multiply in a way 317 00:14:16.680 --> 00:14:19.880 that is endless in the 300 groups we 318 00:14:19.880 --> 00:14:23.480 have, right? Anyway, this population of 319 00:14:23.480 --> 00:14:28.000 FDS, who should not be confused 320 00:14:28.000 --> 00:14:31.399 with ChatGPT or with AI agents and 321 00:14:31.399 --> 00:14:33.519 or with chatbots, right? Because once 322 00:14:33.519 --> 00:14:35.519 we confuse them, it means we 323 00:14:35.519 --> 00:14:37.199 really haven't understood the potential and the 324 00:14:37.199 --> 00:14:40.279 functionality of each one, right? 325 00:14:40.279 --> 00:14:42.199 Well, Daniel, what I wanted to ask you 326 00:14:42.199 --> 00:14:44.199 here is, you gave a very 327 00:14:44.199 --> 00:14:47.120 interesting explanation of possible paths, 328 00:14:47.120 --> 00:14:50.480 of solutions that are embedded in the 329 00:14:50.480 --> 00:14:54.360 FD solution, but we could still 330 00:14:54.360 --> 00:14:58.440 go further to explore the connection 331 00:14:58.440 --> 00:15:01.480 Smart. A smart call is a... 332 00:15:01.480 --> 00:15:04.639 It's a possible product, right, from FD. It doesn't... 333 00:15:04.639 --> 00:15:08.079 Necessarily come with it, but we... 334 00:15:08.079 --> 00:15:09.519 Also have this solution, which is a... 335 00:15:09.519 --> 00:15:11.759 Closing solution, right? It's a solution... 336 00:15:11.759 --> 00:15:15.680 With even more qualification. If it's true... 337 00:15:15.680 --> 00:15:19.360 That today we don't necessarily... 338 00:15:19.360 --> 00:15:21.399 Love answering phones, right... 339 00:15:21.399 --> 00:15:22.250 Right? 340 00:15:22.250 --> 00:15:22.880 [laughter] 341 00:15:22.880 --> 00:15:24.759 On the other hand, it's true that with... 342 00:15:24.759 --> 00:15:27.040 The consent of the person we're... 343 00:15:27.040 --> 00:15:28.800 Talking to, 344 00:15:28.800 --> 00:15:31.480 Moving from WhatsApp to a phone call, 345 00:15:31.480 --> 00:15:34.480 Our chances of closing, uh, in this... 346 00:15:34.480 --> 00:15:37.319 Checkout are actually much higher, 347 00:15:37.319 --> 00:15:40.560 Right? So, tell us a bit about... 348 00:15:40.560 --> 00:15:43.600 This solution that we already, anyway, have... 349 00:15:43.600 --> 00:15:46.160 Also, uh, experienced very important results... 350 00:15:46.160 --> 00:15:48.279 Important results from this technology... 351 00:15:48.279 --> 00:15:51.639 By the way, here's the XMACNA invitation. 352 00:15:51.639 --> 00:15:54.399 Talk to Hermes, who's there as SDR... 353 00:15:54.399 --> 00:15:56.959 On our website, you will certainly... 354 00:15:56.959 --> 00:15:58.680 Be surprised. 355 00:15:58.680 --> 00:16:01.560 Good. Yeah, I think even before we... 356 00:16:01.560 --> 00:16:04.800 Get into the specific topic of smart calls... 357 00:16:04.800 --> 00:16:07.639 Smart, right, there have been a series... 358 00:16:07.639 --> 00:16:10.720 Of discussions in sales groups, right, 359 00:16:10.720 --> 00:16:14.319 Not only in the XMACNA community, but in... 360 00:16:14.319 --> 00:16:16.920 The sales community in general, 361 00:16:16.920 --> 00:16:21.360 Right, about whether the call is effective or not, 362 00:16:21.360 --> 00:16:23.560 whether WhatsApp or email is effective or not, 363 00:16:23.560 --> 00:16:26.319 anyway, they discuss countless channels, right? And 364 00:16:26.319 --> 00:16:29.079 I really like to say that we, 365 00:16:29.079 --> 00:16:32.160 as a company, we don't have, uh, we 366 00:16:32.160 --> 00:16:34.480 actually can't afford 367 00:16:34.480 --> 00:16:37.440 to choose how the client will contact us 368 00:16:37.440 --> 00:16:40.199 with us, right? So, uh, I am 369 00:16:40.199 --> 00:16:42.600 a supporter that we, as a company, 370 00:16:42.600 --> 00:16:45.279 should be available on all 371 00:16:45.279 --> 00:16:48.240 channels, right, on as many channels 372 00:16:48.240 --> 00:16:51.399 as possible and let the client 373 00:16:51.399 --> 00:16:54.399 choose how they want to contact us, 374 00:16:54.399 --> 00:16:56.399 how they want to consume our 375 00:16:56.399 --> 00:17:00.399 content and so on, right? So, that said, the 376 00:17:00.399 --> 00:17:04.400 phone is indeed a very 377 00:17:04.400 --> 00:17:06.720 important channel to consider as well, 378 00:17:06.720 --> 00:17:11.559 right? And another point is also the matter 379 00:17:11.559 --> 00:17:14.120 of immediacy, right, that more and more 380 00:17:14.120 --> 00:17:16.799 people want to get an answer right there 381 00:17:16.799 --> 00:17:19.039 at the moment they are looking for that 382 00:17:19.039 --> 00:17:21.799 answer. And if your company is not 383 00:17:21.799 --> 00:17:25.000 able to respond through the channel they 384 00:17:25.000 --> 00:17:27.559 want, as I mentioned here, uh, the 385 00:17:27.559 --> 00:17:29.200 probability is that you invest your 386 00:17:29.200 --> 00:17:31.640 traffic to teach your lead to 387 00:17:31.640 --> 00:17:34.720 buy from the competitor, right? And I imagine 388 00:17:34.720 --> 00:17:36.919 that's not the kind of ROI you 389 00:17:36.919 --> 00:17:39.440 expect when you set up a campaign there, 390 00:17:39.440 --> 00:17:42.200 whether it's on Google, Meta Ads, or 391 00:17:42.200 --> 00:17:43.880 Whatever it is, right? 392 00:17:43.880 --> 00:17:46.360 Just imagine, someone pays a lot for the 393 00:17:46.360 --> 00:17:49.840 click, brings the person there, right? Then 394 00:17:49.840 --> 00:17:54.360 guides them through this funnel, it's competitive, which 395 00:17:54.360 --> 00:17:56.400 means attracting people to your own 396 00:17:56.400 --> 00:17:59.240 space, and once they're there, there's no one to 397 00:17:59.240 --> 00:18:01.799 assist them, right? I think that's 398 00:18:01.799 --> 00:18:03.200 where you really need the digital employee 399 00:18:03.200 --> 00:18:05.679 to step in, to serve on Saturdays, 400 00:18:05.679 --> 00:18:08.600 Sundays, mornings, afternoons, and nights, it's 401 00:18:08.600 --> 00:18:12.600 24/7, with a conversational quality 402 00:18:12.600 --> 00:18:16.240 that only those who have experienced this interaction 403 00:18:16.240 --> 00:18:19.159 can really testify to, isn't that right? They can 404 00:18:19.159 --> 00:18:22.120 vouch that it's actually very 405 00:18:22.120 --> 00:18:24.880 impressive, it doesn't resemble at all 406 00:18:24.880 --> 00:18:28.280 the kind of service that 407 00:18:28.280 --> 00:18:30.720 we used to have at the beginning 408 00:18:30.720 --> 00:18:32.679 of this conversation, right, Daniel? 409 00:18:32.679 --> 00:18:36.240 Exactly. So, that being said, 410 00:18:36.240 --> 00:18:38.919 you notice that, 411 00:18:38.919 --> 00:18:40.480 first, the importance of being on 412 00:18:40.480 --> 00:18:44.240 all channels, right? And there's a point 413 00:18:44.240 --> 00:18:47.120 there, Gustavo, well, I think it's not 414 00:18:47.120 --> 00:18:50.880 a bad idea to mention, for those who still haven't 415 00:18:50.880 --> 00:18:52.559 understood, let's make it clear here. 416 00:18:52.559 --> 00:18:54.400 We have the possibility to make the 417 00:18:54.400 --> 00:18:58.360 call, right? And that's through Hermes, 418 00:18:58.360 --> 00:19:01.400 mainly, right? You can interact 419 00:19:01.400 --> 00:19:03.520 with Hermes, ask him to call you and 420 00:19:03.520 --> 00:19:04.960 you'll notice that he has a 421 00:19:04.960 --> 00:19:06.960 memory that it understands, right? It continues 422 00:19:06.960 --> 00:19:09.280 what started on WhatsApp, 423 00:19:09.280 --> 00:19:10.720 it continues on the phone, 424 00:19:10.720 --> 00:19:13.559 and vice versa. So, the link will be here 425 00:19:13.559 --> 00:19:17.720 in the description, but man, beyond that 426 00:19:17.720 --> 00:19:21.000 it's important for us 427 00:19:21.000 --> 00:19:23.720 to be prepared there, right? Because I 428 00:19:23.720 --> 00:19:25.919 hear this a lot from clients, like, Daniel, 429 00:19:25.919 --> 00:19:28.360 but people won't notice that the 430 00:19:28.360 --> 00:19:31.520 artificial intelligence, they'll notice, 431 00:19:31.520 --> 00:19:34.039 okay? Sometimes not, right? On WhatsApp, 432 00:19:34.039 --> 00:19:35.880 sometimes, honestly, they don't notice. I 433 00:19:35.880 --> 00:19:38.080 see it with the digital employees that I 434 00:19:38.080 --> 00:19:40.240 have here for my businesses and sometimes 435 00:19:40.240 --> 00:19:41.760 people don't notice. They send a 436 00:19:41.760 --> 00:19:44.039 They send kisses, they thank you, 437 00:19:44.039 --> 00:19:47.159 they praise the service, right? 438 00:19:47.159 --> 00:19:49.679 >> That happens very often. 439 00:19:49.679 --> 00:19:51.919 >> But I think the point here, the 440 00:19:51.919 --> 00:19:54.799 provocation I leave here is more 441 00:19:54.799 --> 00:19:57.720 important than whether the person is served 442 00:19:57.720 --> 00:20:01.360 by a human or by AI is that they are 443 00:20:01.360 --> 00:20:04.640 served. And then there is a question 444 00:20:04.640 --> 00:20:06.919 here, which is your client, your lead, 445 00:20:06.919 --> 00:20:09.919 from the moment they realize that 446 00:20:09.919 --> 00:20:12.520 by interacting there with the digital 447 00:20:12.520 --> 00:20:14.559 employee, they will have their problem 448 00:20:14.559 --> 00:20:17.480 solved or their question answered 449 00:20:17.480 --> 00:20:21.000 at that moment, they will be able to 450 00:20:21.000 --> 00:20:23.960 talk and interact to get 451 00:20:23.960 --> 00:20:26.480 the answer they want. It's much 452 00:20:26.480 --> 00:20:28.840 better for them to get an answer, even if 453 00:20:28.840 --> 00:20:31.880 it's from artificial intelligence, at the moment and 454 00:20:31.880 --> 00:20:34.280 on the channel they expect, than not 455 00:20:34.280 --> 00:20:36.799 getting an answer, or even worse, getting 456 00:20:36.799 --> 00:20:39.240 that kind of answer: "Look, we're not 457 00:20:39.240 --> 00:20:41.640 available right now, 458 00:20:41.640 --> 00:20:45.080 please wait 24 hours, wait 48 hours and 459 00:20:45.080 --> 00:20:48.400 someone will get in touch with you, 460 00:20:48.400 --> 00:20:50.880 right?" So usually when 461 00:20:50.880 --> 00:20:52.960 I get at least an answer like that, 462 00:20:52.960 --> 00:20:54.559 I say: "Great, it's time for 463 00:20:54.559 --> 00:20:56.640 me to look for the next one." 464 00:20:56.640 --> 00:20:58.760 >> Or maybe it's time for me to sell an FD 465 00:20:58.760 --> 00:21:00.080 to this guy here, right? Tell the 466 00:21:00.080 --> 00:21:00.400 truth. 467 00:21:00.400 --> 00:21:02.039 >> Yes, yes, yes. But I mean from the 468 00:21:02.039 --> 00:21:03.320 customer's point of view, right? 469 00:21:03.320 --> 00:21:04.960 >> Yeah, for sure. 470 00:21:04.960 --> 00:21:07.080 >> The idea is good. And Daniel, you said 471 00:21:07.080 --> 00:21:09.679 like, uh, even if it's artificial 472 00:21:09.679 --> 00:21:11.520 intelligence, I just want to add a quick note 473 00:21:11.520 --> 00:21:14.000 here, uh, to that statement, 474 00:21:14.000 --> 00:21:16.320 because, actually, with the right context, 475 00:21:16.320 --> 00:21:19.279 sometimes, and honestly, from our 476 00:21:19.279 --> 00:21:20.559 experience, we can say 477 00:21:20.559 --> 00:21:23.919 this with confidence, it would be better if 478 00:21:23.919 --> 00:21:25.559 you were served by artificial 479 00:21:25.559 --> 00:21:28.080 intelligence that will be flawless 480 00:21:28.080 --> 00:21:31.120 in the answer and immediate, right? 481 00:21:31.120 --> 00:21:33.120 I think these are qualities that nowadays 482 00:21:33.120 --> 00:21:35.039 are non-negotiable. We need to be 483 00:21:35.039 --> 00:21:38.240 assertive and brief, right? Sales is all about timing, 484 00:21:38.240 --> 00:21:39.880 isn't it? It's about that moment 485 00:21:39.880 --> 00:21:41.600 when it's happening, because after that 486 00:21:41.600 --> 00:21:43.799 person doesn't come back, and it's more expensive to 487 00:21:43.799 --> 00:21:46.200 re-engage them and so on, right? 488 00:21:46.200 --> 00:21:48.440 Well, I'd like to, I want to bring up a 489 00:21:48.440 --> 00:21:50.000 question here just so we can start 490 00:21:50.000 --> 00:21:52.200 wrapping up, Daniel, which is this: 491 00:21:52.200 --> 00:21:56.559 once we have a Digital Employee with or without 492 00:21:56.559 --> 00:21:58.440 smart calling, which is an add-on product 493 00:21:58.440 --> 00:22:01.480 to this solution, tell us 494 00:22:01.480 --> 00:22:04.320 about the XMACNA portal, where all 495 00:22:04.320 --> 00:22:06.240 the information is being processed 496 00:22:06.240 --> 00:22:09.200 by the Autobots, how does the client 497 00:22:09.200 --> 00:22:11.520 access the summary of what matters most 498 00:22:11.520 --> 00:22:14.240 and can make decisions based 499 00:22:14.240 --> 00:22:15.440 on that. 500 00:22:15.440 --> 00:22:18.440 Uh-huh. Perfect. Well, everyone, here in this 501 00:22:18.440 --> 00:22:20.880 context I'll explain to you, 502 00:22:20.880 --> 00:22:23.320 but if you want to see in more 503 00:22:23.320 --> 00:22:25.840 detail, click the link in the description, 504 00:22:25.840 --> 00:22:27.600 where we have a video 505 00:22:27.600 --> 00:22:29.480 presenting the portal so you can 506 00:22:29.480 --> 00:22:32.200 actually see what we're 507 00:22:32.200 --> 00:22:34.760 going to describe here, okay? But inside the 508 00:22:34.760 --> 00:22:38.520 XMACNA portal, every client, right, 509 00:22:38.520 --> 00:22:41.120 who hires a digital employee has 510 00:22:41.120 --> 00:22:44.520 access. We have a CRM, where 511 00:22:44.520 --> 00:22:47.039 You can see there the 512 00:22:47.039 --> 00:22:50.679 movement of leads is done by the 513 00:22:50.679 --> 00:22:53.200 digital employee, right? Or by the 514 00:22:53.200 --> 00:22:55.159 digital employees, if you have 515 00:22:55.159 --> 00:22:58.080 more than one in your structure. Which is 516 00:22:58.080 --> 00:23:00.039 something that happens often, 517 00:23:00.039 --> 00:23:02.600 depending on the size of the company, right? 518 00:23:02.600 --> 00:23:04.840 But in medium to large companies, sometimes 519 00:23:04.840 --> 00:23:07.120 there's even more than one employee. 520 00:23:07.120 --> 00:23:09.919 So you can have all that there and 521 00:23:09.919 --> 00:23:12.400 you will have the schedule of these 522 00:23:12.400 --> 00:23:14.480 employees, understand which were the 523 00:23:14.480 --> 00:23:16.520 appointments made by them, for 524 00:23:16.520 --> 00:23:18.840 which day, for which time. Just like 525 00:23:18.840 --> 00:23:21.440 you have your Google calendar, you 526 00:23:21.440 --> 00:23:22.960 can also see there this 527 00:23:22.960 --> 00:23:25.640 calendar view, you can 528 00:23:25.640 --> 00:23:28.200 see all the appointments with a 529 00:23:28.200 --> 00:23:31.760 summary, right? Why? Well, when as 530 00:23:31.760 --> 00:23:34.880 the manager of a digital employee, you 531 00:23:34.880 --> 00:23:37.520 will manage this employee just like 532 00:23:37.520 --> 00:23:39.480 you would also manage a human employee, 533 00:23:39.480 --> 00:23:42.520 right? So, what do you look at 534 00:23:42.520 --> 00:23:44.400 when you are managing 535 00:23:44.400 --> 00:23:46.880 a human employee? Well, you will 536 00:23:46.880 --> 00:23:49.880 look at the volume of daily appointments. 537 00:23:49.880 --> 00:23:51.760 You will also want to see in which 538 00:23:51.760 --> 00:23:54.720 stages the leads that were 539 00:23:54.720 --> 00:23:57.480 served are. Sometimes you will want to have 540 00:23:57.480 --> 00:24:00.360 access to those conversations to understand 541 00:24:00.360 --> 00:24:01.960 What happened, right? So, for 542 00:24:01.960 --> 00:24:03.840 example, ah, I saw, I saw here that there was a 543 00:24:03.840 --> 00:24:06.720 conversation that the employee marked as 544 00:24:06.720 --> 00:24:08.600 decline. Wow, let me understand why 545 00:24:08.600 --> 00:24:11.480 this decline, right? 546 00:24:11.480 --> 00:24:14.039 Exactly. Or, oh, this one closed. 547 00:24:14.039 --> 00:24:15.880 Let me understand what happened 548 00:24:15.880 --> 00:24:18.440 so we know why it closed and we can 549 00:24:18.440 --> 00:24:20.799 replicate this, right, in other ways 550 00:24:20.799 --> 00:24:23.880 too. So you can also analyze 551 00:24:23.880 --> 00:24:26.679 all these interactions, both in 552 00:24:26.679 --> 00:24:30.799 full, if you want, but 553 00:24:30.799 --> 00:24:33.799 in daily life, with countless conversations, 554 00:24:33.799 --> 00:24:36.000 we usually look for a 555 00:24:36.000 --> 00:24:39.600 short summary, a paragraph, to quickly 556 00:24:39.600 --> 00:24:42.279 scan through and see if there is any 557 00:24:42.279 --> 00:24:45.279 alert, right, that needs to be given. 558 00:24:45.279 --> 00:24:47.919 So, basically, inside this portal, 559 00:24:47.919 --> 00:24:50.240 that we provide, you have access to 560 00:24:50.240 --> 00:24:53.240 all this and also the list, right? So, the 561 00:24:53.240 --> 00:24:57.200 list there with the data that is 562 00:24:57.200 --> 00:24:59.679 customizable. So, for example, if 563 00:24:59.679 --> 00:25:02.720 you work with events, you can 564 00:25:02.720 --> 00:25:06.480 see which event that, uh, 565 00:25:06.480 --> 00:25:09.240 lead was looking for, right? If you work 566 00:25:09.240 --> 00:25:12.520 with clinics, you can see there 567 00:25:12.520 --> 00:25:14.799 who scheduled, who didn't, for 568 00:25:14.799 --> 00:25:16.480 which procedure, for which 569 00:25:16.480 --> 00:25:19.080 specialist inside your clinic, right? 570 00:25:19.080 --> 00:25:21.399 So you can have there 571 00:25:21.399 --> 00:25:23.520 >> The lead's temperature, right? The temperature 572 00:25:23.520 --> 00:25:25.559 of the lead, right? How far it is from 573 00:25:25.559 --> 00:25:27.799 closing. Yes, and for that 574 00:25:27.799 --> 00:25:30.320 it can trigger, for example, a specific action 575 00:25:30.320 --> 00:25:31.919 by a human. You do it, imagine that we 576 00:25:31.919 --> 00:25:34.039 have there, right, an indication of hot leads 577 00:25:34.039 --> 00:25:36.279 that are close to 578 00:25:36.279 --> 00:25:39.000 closing. You mobilize a 579 00:25:39.000 --> 00:25:41.799 human team to work actively 580 00:25:41.799 --> 00:25:44.039 with that lead, right? That is really being 581 00:25:44.039 --> 00:25:46.159 much more strategic with the resource 582 00:25:46.159 --> 00:25:48.240 that is finite, right? 583 00:25:48.240 --> 00:25:49.600 >> Exactly. 584 00:25:49.600 --> 00:25:52.000 >> And you can, in a way, 585 00:25:52.000 --> 00:25:54.720 actually catalog, right, all the 586 00:25:54.720 --> 00:25:56.520 data that is important to you. 587 00:25:56.520 --> 00:25:58.600 So, if you are in real estate and want to 588 00:25:58.600 --> 00:26:00.880 catalog whether your interest is in 589 00:26:00.880 --> 00:26:02.919 houses, apartments, land, you 590 00:26:02.919 --> 00:26:05.520 can do it, whether it's new, for investment, 591 00:26:05.520 --> 00:26:09.440 anyway, regardless of your 592 00:26:09.440 --> 00:26:13.039 niche, right, of business, and there all 593 00:26:13.039 --> 00:26:14.760 businesses always have their 594 00:26:14.760 --> 00:26:16.919 characteristics, right, their 595 00:26:16.919 --> 00:26:19.320 particularities, so the digital employee 596 00:26:19.320 --> 00:26:20.840 will respect those 597 00:26:20.840 --> 00:26:23.399 particularities, collecting the data that 598 00:26:23.399 --> 00:26:27.080 are important, classifying and acting 599 00:26:27.080 --> 00:26:30.520 depending on which information it is, 600 00:26:30.520 --> 00:26:34.480 right? That's it. I 601 00:26:34.480 --> 00:26:36.799 I think that everything you're telling us, 602 00:26:36.799 --> 00:26:41.279 gives the entrepreneur, you know, the owner, 603 00:26:41.279 --> 00:26:44.720 to the manager of this business, much more 604 00:26:44.720 --> 00:26:47.679 information, qualified information 605 00:26:47.679 --> 00:26:49.679 for making more 606 00:26:49.679 --> 00:26:52.559 assertive decisions, and, in short, improvements 607 00:26:52.559 --> 00:26:54.880 in processes, with impacts, 608 00:26:54.880 --> 00:26:57.080 obviously, also on the 609 00:26:57.080 --> 00:26:58.880 company's revenue, which is a 610 00:26:58.880 --> 00:27:01.279 goal that, obviously, the commercial 611 00:27:01.279 --> 00:27:05.200 departments pursue, right? Well, Daniel, 612 00:27:05.200 --> 00:27:08.000 to wrap up, I wanted you to 613 00:27:08.000 --> 00:27:10.320 also give us again a 614 00:27:10.320 --> 00:27:11.840 sense of our work here at 615 00:27:11.840 --> 00:27:15.240 XMACNA, which is particularly the vertical 616 00:27:15.240 --> 00:27:18.240 of XMACNA Partner, for those who 617 00:27:18.240 --> 00:27:22.240 might identify with this 618 00:27:22.240 --> 00:27:25.679 sector, with this industry, whether or not they already have 619 00:27:25.679 --> 00:27:28.880 some experience in this work of 620 00:27:28.880 --> 00:27:31.640 representation and who can have the products 621 00:27:31.640 --> 00:27:34.840 and services from XMACNA. Including the 622 00:27:34.840 --> 00:27:38.520 FD itself, but not only that, also services 623 00:27:38.520 --> 00:27:41.240 and products from their own portfolio, 624 00:27:41.240 --> 00:27:44.000 so they can, in short, be 625 00:27:44.000 --> 00:27:45.679 represented. Tell me a little 626 00:27:45.679 --> 00:27:47.919 about that, how has your 627 00:27:47.919 --> 00:27:50.840 experience been leading this vertical 628 00:27:50.840 --> 00:27:54.240 here with us and, finally, to end with the 629 00:27:54.240 --> 00:27:55.880 invitation for those who follow us 630 00:27:55.880 --> 00:27:58.240 as well. 631 00:27:58.240 --> 00:28:02.600 Perfect. Well, we have been having 632 00:28:02.600 --> 00:28:04.720 great results, right, in the last 633 00:28:04.720 --> 00:28:08.320 months, as we are looking more and more 634 00:28:08.320 --> 00:28:11.320 closely at our partner program, 635 00:28:11.320 --> 00:28:13.080 which is a program 636 00:28:13.080 --> 00:28:15.440 developed for you who are on the other 637 00:28:15.440 --> 00:28:18.320 side and looking, right, at 638 00:28:18.320 --> 00:28:20.880 this artificial intelligence market, 639 00:28:20.880 --> 00:28:23.159 and realize there are a lot of 640 00:28:23.159 --> 00:28:26.159 possibilities and then you think: 'Well, should I 641 00:28:26.159 --> 00:28:28.480 invest my time and money here 642 00:28:28.480 --> 00:28:32.120 to learn how each 643 00:28:32.120 --> 00:28:34.640 screw works and where do I start to 644 00:28:34.640 --> 00:28:37.880 tighten each nut in this 645 00:28:37.880 --> 00:28:42.159 big machine, right? Or should I choose to 646 00:28:42.159 --> 00:28:46.120 actually get faster results, 647 00:28:46.120 --> 00:28:49.720 since here in our 648 00:28:49.720 --> 00:28:52.039 partner program, instead of you 649 00:28:52.039 --> 00:28:55.159 having to study and look for technical 650 00:28:55.159 --> 00:28:58.480 information, bit by bit, you can 651 00:28:58.480 --> 00:29:00.600 simply take the solutions that are already 652 00:29:00.600 --> 00:29:03.320 ready and working right now in 653 00:29:03.320 --> 00:29:06.399 over 800 digital employees as we speak 654 00:29:06.399 --> 00:29:08.640 that we have 655 00:29:08.640 --> 00:29:09.640 available. 656 00:29:09.640 --> 00:29:12.559 and working today in the market, besides 657 00:29:12.559 --> 00:29:14.640 many other solutions we have 658 00:29:14.640 --> 00:29:17.200 as well, and that at some point we can 659 00:29:17.200 --> 00:29:20.039 bring here to this podcast or 660 00:29:20.039 --> 00:29:23.880 to other XMACNA content. But it's 661 00:29:23.880 --> 00:29:27.360 It's important for you to realize that, when 662 00:29:27.360 --> 00:29:29.200 you become a partner, you will have 663 00:29:29.200 --> 00:29:32.720 immediately available all 664 00:29:32.720 --> 00:29:35.880 these solutions in an easy way, without 665 00:29:35.880 --> 00:29:38.519 you actually needing technical knowledge, 666 00:29:38.519 --> 00:29:41.559 but rather having knowledge in 667 00:29:41.559 --> 00:29:43.600 sales, right? Or even if you don't, we 668 00:29:43.600 --> 00:29:45.960 have a series of materials that 669 00:29:45.960 --> 00:29:48.679 support this development, but the fact 670 00:29:48.679 --> 00:29:51.440 is, to enter the artificial intelligence market, 671 00:29:51.440 --> 00:29:55.279 the time to start has already passed, 672 00:29:55.279 --> 00:29:58.559 right? So now we have already 673 00:29:58.559 --> 00:30:00.960 started, we are already moving forward 674 00:30:00.960 --> 00:30:04.559 with a lot of success. So now is the time 675 00:30:04.559 --> 00:30:07.880 to get on this ship that's already 676 00:30:07.880 --> 00:30:11.000 sailing, right? And from there 677 00:30:11.000 --> 00:30:14.159 also be able to achieve good 678 00:30:14.159 --> 00:30:17.200 results, right? So this is the invitation from 679 00:30:17.200 --> 00:30:21.080 XMACNA Partner. And I also leave here another 680 00:30:21.080 --> 00:30:24.640 important point, which is for 681 00:30:24.640 --> 00:30:26.519 those of you who already have a technology 682 00:30:26.519 --> 00:30:28.120 company, because Gustavo, this 683 00:30:28.120 --> 00:30:30.919 happens a lot, you know? For you 684 00:30:30.919 --> 00:30:33.080 who already has a technology company, 685 00:30:33.080 --> 00:30:35.640 who already has a platform that's out there 686 00:30:35.640 --> 00:30:37.519 running today and still doesn't have 687 00:30:37.519 --> 00:30:38.919 artificial intelligence, so, for 688 00:30:38.919 --> 00:30:41.440 example, sometimes you have an ERP, a 689 00:30:41.440 --> 00:30:43.640 CRM, we have some that obviously we 690 00:30:43.640 --> 00:30:46.760 can't mention here. 691 00:30:46.760 --> 00:30:50.440 because they use it in XMACNA's solutions 692 00:30:50.440 --> 00:30:53.399 as a white label, but for you 693 00:30:53.399 --> 00:30:55.639 who also wants to implement 694 00:30:55.639 --> 00:30:57.480 artificial intelligence and doesn't have a 695 00:30:57.480 --> 00:31:00.200 team to develop it, we are here 696 00:31:00.200 --> 00:31:03.159 also with our solutions, 697 00:31:03.159 --> 00:31:05.039 available so you can 698 00:31:05.039 --> 00:31:06.880 implement it in the solution you already 699 00:31:06.880 --> 00:31:09.960 have, offer this right away to your 700 00:31:09.960 --> 00:31:13.320 end client and already be up to date with 701 00:31:13.320 --> 00:31:15.840 the latest in the market, without having 702 00:31:15.840 --> 00:31:18.279 to invest time, without having to invest 703 00:31:18.279 --> 00:31:20.840 money to have a team of 704 00:31:20.840 --> 00:31:22.320 development specialized in 705 00:31:22.320 --> 00:31:24.559 artificial intelligence, which today is one 706 00:31:24.559 --> 00:31:26.519 of the most expensive teams you can 707 00:31:26.519 --> 00:31:29.200 find. And we have this ready here 708 00:31:29.200 --> 00:31:32.360 to also serve you within the 709 00:31:32.360 --> 00:31:34.440 our partnership program as well. 710 00:31:34.440 --> 00:31:37.360 So, here's that invitation as well. 711 00:31:37.360 --> 00:31:42.000 >> Great. At the end, our guarantee that 712 00:31:42.000 --> 00:31:45.399 whoever is with us will have access to 713 00:31:45.399 --> 00:31:48.000 available solutions and to solutions 714 00:31:48.000 --> 00:31:50.399 not yet available as well, that is, [laughter] 715 00:31:50.399 --> 00:31:52.080 >> those that are just emerging in the 716 00:31:52.080 --> 00:31:54.320 world, right, that are not yet 717 00:31:54.320 --> 00:31:56.919 available, but as soon as they are, we 718 00:31:56.919 --> 00:31:58.840 quickly absorb them 719 00:31:58.840 --> 00:32:01.960 here, it's part of our process and, 720 00:32:01.960 --> 00:32:03.840 anyway, we've been very satisfied 721 00:32:03.840 --> 00:32:06.159 in being able to work in this way as well. 722 00:32:06.159 --> 00:32:09.399 Daniel, thank you once again. Uh, 723 00:32:09.399 --> 00:32:11.960 I hope that those who have followed us so far, 724 00:32:11.960 --> 00:32:14.679 uh, please be kind enough to share 725 00:32:14.679 --> 00:32:16.360 this content with anyone else who might 726 00:32:16.360 --> 00:32:19.320 be interested in it. So, that's it. Once 727 00:32:19.320 --> 00:32:21.679 again, a hug to everyone and until the 728 00:32:21.679 --> 00:32:24.679 next time.