WEBVTT

00:00:03.000 --> 00:00:04.421
In this video, we will cover email

00:00:04.421 --> 00:00:06.343
verification actions in workflows.

00:00:06.343 --> 00:00:08.091
This is a new action added by the email

00:00:08.091 --> 00:00:08.966
team.

00:00:08.966 --> 00:00:10.634
Let's walk through how to add this

00:00:10.634 --> 00:00:11.144
action.

00:00:11.144 --> 00:00:12.955
We'll click the plus icon and search for

00:00:12.955 --> 00:00:14.516
email verification.

00:00:14.516 --> 00:00:16.410
That's how we add this action to a

00:00:16.410 --> 00:00:17.372
workflow.

00:00:17.872 --> 00:00:19.870
To use the email verification action,

00:00:19.870 --> 00:00:21.460
two conditions must be met.

00:00:21.460 --> 00:00:23.405
First, email verification must be

00:00:23.405 --> 00:00:24.897
enabled on the sub-account.

00:00:24.897 --> 00:00:27.167
Second, the contact must not be excluded

00:00:27.167 --> 00:00:28.507
from verification.

00:00:28.507 --> 00:00:30.266
In the contact settings, there is an

00:00:30.266 --> 00:00:32.212
option to exclude a specific contact's

00:00:32.212 --> 00:00:33.987
email from verification.

00:00:33.987 --> 00:00:35.956
If we want the verification to run on

00:00:35.956 --> 00:00:38.249
that contact, this option must not be

00:00:38.249 --> 00:00:39.340
selected.

00:00:39.840 --> 00:00:41.564
Now let's see how it works.

00:00:41.564 --> 00:00:42.991
Once we add this action, when the

00:00:42.991 --> 00:00:45.146
workflow runs on a contact, the contact

00:00:45.146 --> 00:00:46.563
will be added to the workflow and will

00:00:46.563 --> 00:00:47.886
reach this action.

00:00:47.886 --> 00:00:50.161
The action will take the contact's email

00:00:50.161 --> 00:00:51.508
and verify it.

00:00:51.508 --> 00:00:53.505
If the email is valid, the workflow

00:00:53.505 --> 00:00:55.026
moves on to the next steps.

00:00:55.026 --> 00:00:57.215
If verification fails, or the email is

00:00:57.215 --> 00:00:59.183
invalid, it will not move forward.

00:00:59.183 --> 00:01:00.473
Instead, it will be skipped in the

00:01:02.076 --> 00:01:04.027
There are two more things to keep in

00:01:04.027 --> 00:01:04.521
mind.

00:01:04.521 --> 00:01:06.412
If the email is on the excluded list, it

00:01:06.412 --> 00:01:08.450
will also be skipped.

00:01:08.450 --> 00:01:10.930
If the sub-account has disabled email

00:01:10.930 --> 00:01:12.932
verification, then the verification

00:01:12.932 --> 00:01:14.638
step will be skipped as well.

00:01:15.138 --> 00:01:17.328
We can also use the email verification

00:01:17.328 --> 00:01:19.057
feature with condition settings.

00:01:19.057 --> 00:01:21.094
The values from email verification can

00:01:21.094 --> 00:01:23.602
be used inside condition branches too.

00:01:23.602 --> 00:01:25.709
Let's go to the condition section.

00:01:25.709 --> 00:01:27.317
Here, we have added a condition for

00:01:27.317 --> 00:01:29.349
email verification set to "is

00:01:29.349 --> 00:01:31.903
verified." Let's mark it as true.

00:01:31.903 --> 00:01:34.091
Now let's add one more condition for the

00:01:34.091 --> 00:01:35.015
false case.

00:01:35.015 --> 00:01:36.873
By default, we have the normal state,

00:01:36.873 --> 00:01:38.822
and this is how we create branches.

00:01:39.322 --> 00:01:40.780
So what happens here?

00:01:40.780 --> 00:01:42.724
If the email is valid, it will go to the

00:01:42.724 --> 00:01:44.965
"is email valid?" branch.

00:01:44.965 --> 00:01:47.194
If it is true, we can trigger some kind

00:01:47.194 --> 00:01:48.062
of action .

00:01:48.062 --> 00:01:49.522
If it's false, we can trigger a

00:01:49.522 --> 00:01:51.908
different action for invalid emails.

00:01:51.908 --> 00:01:53.823
For example, if the email is valid, we

00:01:53.823 --> 00:01:54.927
can send emails.

00:01:54.927 --> 00:01:56.981
If it's invalid, we can mark the contact

00:01:56.981 --> 00:01:58.069
as DND.

00:01:58.569 --> 00:01:59.685
Let's test this out.

00:01:59.685 --> 00:02:01.177
We'll add some notes.

00:02:01.177 --> 00:02:03.162
For a valid email, let's add a note that

00:02:03.162 --> 00:02:06.302
says "valid email." And for the invalid

00:02:06.302 --> 00:02:07.962
case, let's add a note that says

00:02:07.962 --> 00:02:11.567
"invalid." We have a couple of contacts

00:02:11.567 --> 00:02:13.786
to test with — one valid and one

00:02:13.786 --> 00:02:15.016
invalid.

00:02:15.016 --> 00:02:17.088
Let's pick a contact and run the

00:02:17.640 --> 00:02:19.585
Now let's go to enrollment history, then

00:02:19.585 --> 00:02:21.472
check the execution history.

00:02:21.472 --> 00:02:23.805
We can see that email verification has

00:02:23.805 --> 00:02:24.687
been executed.

00:02:24.687 --> 00:02:25.924
Let's check the details.

00:02:25.924 --> 00:02:27.867
It was successful, and it went through

00:02:27.867 --> 00:02:29.354
the correct branch.

00:02:29.354 --> 00:02:31.368
Let's confirm it was marked as true

00:02:31.368 --> 00:02:32.953
since this email is valid.

00:02:32.953 --> 00:02:35.078
Let's also check the notes — and yes,

00:02:35.078 --> 00:02:38.359
the note says "valid email." Now let's

00:02:38.359 --> 00:02:40.302
test with an invalid email.

00:02:40.302 --> 00:02:42.259
We have one set up already.

00:02:42.259 --> 00:02:43.843
Let's add it and run the workflow.

00:02:43.843 --> 00:02:46.003
Let's check the execution history.

00:02:46.003 --> 00:02:48.487
Here we can see the execution path.

00:02:48.487 --> 00:02:50.147
It ran through as well.

00:02:50.147 --> 00:02:52.307
Since this email was not valid, it is

00:02:52.307 --> 00:02:53.399
marked as false.

00:02:53.399 --> 00:02:55.819
And as expected, the note shows "invalid

00:02:55.819 --> 00:02:58.705
email." If a contact's email is on the

00:02:58.705 --> 00:03:00.243
excluded list, it will follow a

00:03:00.243 --> 00:03:01.319
different path.

00:03:01.319 --> 00:03:03.388
If there is no matching condition, or if

00:03:03.388 --> 00:03:05.355
email verification is not enabled on

00:03:05.355 --> 00:03:07.433
the sub-account, the condition will be

00:03:07.433 --> 00:03:09.234
skipped and the contact will go through

00:03:09.234 --> 00:03:11.491
the default path, since no condition

00:03:11.491 --> 00:03:13.592
will match as true or false.

00:03:14.092 --> 00:03:16.032
That's how the email verification action

00:03:16.032 --> 00:03:17.575
works in workflows.

00:03:17.575 --> 00:03:19.985
We can use this in many ways — for

00:03:19.985 --> 00:03:21.907
example, only sending emails to valid

00:03:21.907 --> 00:03:24.507
addresses, or setting DND for invalid

00:03:24.507 --> 00:03:25.331
ones.

00:03:25.331 --> 00:03:27.937
This helps protect our domain reputation

00:03:27.937 --> 00:03:29.685
and reduces bounces.

00:03:29.685 --> 00:03:32.274
By only targeting valid emails, we also

00:03:32.274 --> 00:03:34.631
reduce costs, since we won't be sending

00:03:34.631 --> 00:03:36.477
to invalid addresses.

00:03:36.477 --> 00:03:39.060
Focusing on valid emails also helps

00:03:39.060 --> 00:03:41.068
improve open rates and builds a

00:03:41.068 --> 00:03:43.710
stronger domain reputation over time.

00:03:44.210 --> 00:03:46.403
The email verification feature is a

00:03:46.403 --> 00:03:48.040
powerful tool we should use in our

00:03:48.040 --> 00:03:49.039
workflows.

00:03:49.039 --> 00:03:51.257
It helps us reach the right audience and

00:03:51.257 --> 00:03:53.411
make sure we are only sending to valid,

00:03:53.411 --> 00:03:55.506
deliverable email addresses.

00:03:55.506 --> 00:03:56.945
That's how we can use this