WEBVTT

00:00:00.245 --> 00:00:03.827
So yeah, this is the best, this is the best way to communicate

00:00:03.901 --> 00:00:05.490
With your worker, right?

00:00:05.527 --> 00:00:07.910
With team member and with your client.

00:00:07.946 --> 00:00:08.172
Why?

00:00:08.174 --> 00:00:14.813
Because we believe, first of all, the email is like very, very established,

00:00:14.851 --> 00:00:18.234
program that exists for many, many years.

00:00:19.168 --> 00:00:23.008
all the logic, everyone knows how to use Gmail for in this case or email.

00:00:24.058 --> 00:00:27.964
the logic of the threads, the logic of the search, the logic of filtering,

00:00:28.440 --> 00:00:34.554
and, this is the most secure, place and secure way for you to communicate

00:00:34.582 --> 00:00:38.763
with your team member, with your organization, and with your clients.

00:00:39.482 --> 00:00:44.264
also, it's like extremely important, like, the email, like two steps verification.

00:00:44.600 --> 00:00:47.289
you order something online, Everything goes to the email.

00:00:47.749 --> 00:00:50.913
This is the place to track work to communicate with your client.

00:00:50.933 --> 00:00:55.217
Everyone knows this system and the logic of the system

00:00:56.387 --> 00:00:59.207
and, yeah, this is our belief.

00:01:00.102 --> 00:01:03.402
Of course, if you are a company and also need next to the Gmail, you need a

00:01:03.402 --> 00:01:10.936
project management to store, your clients' task and, strategy and, documentation.

00:01:11.187 --> 00:01:14.304
So it's kind of like, hybrid with Gmail and spreadsheets.

00:01:14.309 --> 00:01:15.101
So you need that.

00:01:16.547 --> 00:01:20.226
But to perform work and to communicate work, internally and

00:01:20.236 --> 00:01:21.793
for your client, this is the place.

00:01:22.983 --> 00:01:27.742
back in the day, we really was advocate for Asana in project management,

00:01:28.267 --> 00:01:32.621
which is, great, but it feels like it's not aligned so much with the

00:01:32.622 --> 00:01:36.250
client's request because the clients do not have access to the project

00:01:36.250 --> 00:01:38.650
management, to the Asana or to Monday.

00:01:39.131 --> 00:01:42.736
Here we have the AI worker listening also to the client request, so

00:01:42.737 --> 00:01:46.600
he can actively, get the request and help us to the internal.

00:01:46.834 --> 00:01:48.670
Okay, I've got this task from the client.

00:01:49.040 --> 00:01:52.840
I did this action, I regenerated the creatives, I did optimization on the

00:01:52.842 --> 00:01:56.018
campaign, and this is for you ready to send and to share for your client.

00:01:56.207 --> 00:01:56.522
Okay.

00:01:57.847 --> 00:02:00.014
So of course it's working because it's a heavy task.

00:02:01.424 --> 00:02:02.757
Let's go to the routine.

00:02:03.764 --> 00:02:06.145
You can see here it's running.

00:02:07.415 --> 00:02:09.826
We can theoretically connect it to everywhere.

00:02:10.415 --> 00:02:12.702
but Slack it's only for internal teams.

00:02:12.805 --> 00:02:17.209
when you work with client, you need to choose platform for communication.

00:02:17.318 --> 00:02:17.975
what it will be?

00:02:19.092 --> 00:02:22.825
in like, AI marketing agency, what it will be?

00:02:23.475 --> 00:02:25.616
Email, you know.

00:02:26.607 --> 00:02:29.916
If I'm a SaaS company with five hundred employee and stuff, so

00:02:29.916 --> 00:02:34.129
yeah, it makes sense to have your AI logged into your Slack channels

00:02:34.387 --> 00:02:36.264
and help you to, manage the stuff.

00:02:37.345 --> 00:02:41.522
and it's, you know, we can do that, but you need to build… In order

00:02:41.522 --> 00:02:45.135
to do it very good, you need to build all the logic around Slack.

00:02:45.135 --> 00:02:47.205
It's not that easy, right?

00:02:47.610 --> 00:02:49.469
We build with, AI infrastructure.

00:02:49.516 --> 00:02:54.769
With Outloop, we build very advanced logic the email, which is two

00:02:54.770 --> 00:03:00.809
providers, Google, Google, Google Gmail and Microsoft, Outlook three,

00:03:00.900 --> 00:03:03.146
six five Also in a secure way.

00:03:03.146 --> 00:03:10.505
So we have a secure, mechanism of, identified when it might be, a spam or,

00:03:11.221 --> 00:03:16.294
like a fraud and to identify if this is the client send the email or it's

00:03:16.297 --> 00:03:20.510
something that we need to worry about and will not perform work for this request.
