WEBVTT

00:00:03.000 --> 00:00:03.639
Hi.

00:00:04.139 --> 00:00:06.169
You can now build rich customer journeys

00:00:06.169 --> 00:00:08.550
with rcs messaging directly inside

00:00:08.550 --> 00:00:09.565
workflows.

00:00:10.065 --> 00:00:12.311
Yes, you heard that right.

00:00:12.311 --> 00:00:15.045
Your RCS messages can now be sent

00:00:15.045 --> 00:00:16.329
through workflows.

00:00:16.829 --> 00:00:18.594
Here's a quick walk-through on how you

00:00:18.594 --> 00:00:21.275
can send them out in an RCS workflow.

00:00:21.775 --> 00:00:24.022
You can create a simple snippet or build

00:00:24.022 --> 00:00:25.589
a workflow based on your specific

00:00:25.589 --> 00:00:26.466
needs.

00:00:26.966 --> 00:00:29.768
If you want to include buttons, CTA ,

00:00:30.109 --> 00:00:32.370
timeouts, or different branches

00:00:32.370 --> 00:00:34.426
depending on what the customer selects,

00:00:34.426 --> 00:00:36.754
you'll need to add the RCS interactive

00:00:36.754 --> 00:00:37.636
message.

00:00:38.136 --> 00:00:40.156
Once you add the interactive message,

00:00:40.156 --> 00:00:42.229
branches will emerge, and each branch

00:00:42.229 --> 00:00:43.912
can define the next step based on the

00:00:43.912 --> 00:00:45.590
customer's response.

00:00:46.090 --> 00:00:48.807
Here, I've created a simple snippet and

00:00:48.807 --> 00:00:50.438
added some interactivity.

00:00:50.938 --> 00:00:53.665
For example, if the customer clicks on

00:00:53.665 --> 00:00:55.831
"view website," they'll be directed to

00:00:55.831 --> 00:00:58.456
the website, and the workflow will end.

00:00:58.956 --> 00:01:01.381
If they click on "show me shoes,"

00:01:01.381 --> 00:01:03.052
another snippet will open so they can

00:01:03.052 --> 00:01:05.073
continue with the shopping journey.

00:01:05.073 --> 00:01:07.478
The same happens for shirts as well.

00:01:07.978 --> 00:01:10.018
There's also a timeout option, which you

00:01:10.018 --> 00:01:12.084
can add in the RCS interactive

00:01:12.084 --> 00:01:13.048
messages.

00:01:13.048 --> 00:01:15.421
You can define the time for the timeout.

00:01:15.421 --> 00:01:17.256
If the customer doesn't reply within

00:01:17.256 --> 00:01:18.923
that time, the timeout branch will

00:01:18.923 --> 00:01:20.977
trigger, and the workflow will continue

00:01:20.977 --> 00:01:23.281
based on the action you've set up.

00:01:23.781 --> 00:01:26.662
That's how you can use RCS messages in

00:01:26.662 --> 00:01:28.570
workflows to create interactive

00:01:28.570 --> 00:01:30.248
customer journeys.

00:01:30.748 --> 00:01:32.572
Here's one example.

00:01:32.572 --> 00:01:34.406
I sent a message and added a note

00:01:34.406 --> 00:01:36.328
because the trigger here was noteasn't

00:01:36.328 --> 00:01:37.024
added.

00:01:37.024 --> 00:01:38.899
The note was added from here.

00:01:39.399 --> 00:01:42.058
Once you add the note, the RCS will send

00:01:42.058 --> 00:01:43.822
a message like this.

00:01:44.322 --> 00:01:47.944
Here, T rcs is sent through the

00:01:47.944 --> 00:01:49.048
workflow.

00:01:49.048 --> 00:01:51.427
The customer replied with "show me

00:01:51.427 --> 00:01:54.085
shoes," and another snippet, which was

00:01:54.085 --> 00:01:56.060
added here, got triggered.

00:01:56.560 --> 00:01:57.227
Thank