Email Confirmation is more important than ever – and full disclosure: the Email Confirmation process in Keap (formerly Infusionsoft) has a few quirks.
You may have seen the three Campaign Builder Gotchas I shared, #3 is still one of most popular posts on my blog, but today I want to highlight an issue I’ve seen people stumble on with the Keap Email Confirmation process.
If you have no idea what I’m talking about, take a look at this article for a complete breakdown of the what, how and why behind using an Email Confirmation sequence.
Now, I strongly recommend giving your prospects the chance to confirm their email address, and it’s not terribly hard to do that. Effectively it involves dragging out a pre-bundled campaign process and adding it between two existing steps in your campaign. Then, you just configure it and you’re off to the races.
Unconfirmed folks who reach that part of your campaign will have an opportunity to confirm their email address, and people who have already confirmed will skip right over it as if it’s not even there. All good so far.
The challenge I want to address arises when you give someone the opportunity to confirm and then they don’t click the confirmation link. What happens then?
Well, by default the contact will be stuck in the confirmation sequence. That means they’ll never see the exciting stuff you’ve got planned for them after they click, and that’s not okay.
This causes a big problem if your customers are expecting to receive access to something they just requested, or worse, something they just bought.
Okay, so there are a few ways to solve this issue, and if you give me 6 minutes of your time, I’ll show you exactly what we’re working with:
Just to clarify… this blog post refers specifically to the Max Classic version of Keap (formerly Infusionsoft), but the “gotcha” and advice I’ve outlined also applies to the Pro and Max versions of Keap.
Thanks so much Greg! You’re the best and so is your Monkeypod group. 🙂
Thanks Maritza! Back atcha.
As always, really good stuff. I was already branching them with a 2-3 min delay timer before the content they requested. I always thought that just made the most sense, but then I went to a user group last month and nobody else was doing it so I questioned whether it was best practice or not. Thanks Greg.
My pleasure Chett, thanks for taking the time to read and share. Did you ask others at the meeting about why they weren’t doing it that way?