Ok, so on this one I have a HUGE disadvantage, I'm a newbie to Iterable and to my role at Kahoot! So, I have not yet created many workflows
. I've been here for a month and change.
Now, I'll still share a workflow I'm live testing right now.
Objective: Automating approval/rejection process for our Academy applicants.
Currently, Kahoot teachers on our platform can get certified, which gives them certain premiumness and evelates their content.
The evaluation process is manual because our editorial team needs to review the content they have published, and they had to notify them about their application status.
Summary: Our technical team made sure to create an event for when an application is approved and rejected. These are actually two different events, but I wanted one workflow that could apply to both rejected and approved applicants.
I selected a user prop that is updated when the event happens. This prop is common to both events, so I used it as a trigger, and then I used two filters:
1. One to determine the
kind of user the applicant is, we're currently approving teachers, but this is going to change in the future.
2. To ask the
application status, if approved they would get an email, if rejected they would get a different one.
3. And I also
added lists after the email, so I could have visibility into who was approved, rejected and got the email, so I can compare records with me team when need be.
Results: This workflow is live, but partially. It's not sending emails because I wanted to check first the information we were getting, which will inform my workflow. At Kahoot we have a HUGE contact database and TONS of events and props, so I decided to add this additional layer.
All in all, we're looking to save time to the team members that had to manually communicate with each applicant. Roughly, with 20 to 40 applications per day. This will save the team from 2 to 5 working hours per day.
Workflow: I added a capture of what it looks like at this point in time, but it's a work in progress. We need to add emails for other segments, which we'll do in the future, and I'll connect the email for teachers once we're done seeing the data that's trickling in.
I'm also a newbie and we are in the process of onboarding with Iterable and at the same time we are finishing an integration with Segment. Double the fun! Anyway, this workflow I'm building maybe isn't remarkable but the big win here is that I am currently managing these sends MANUALLY!
Automating this between events from Segment and then workflows in Iterable almost make me want to cry - from happiness.
Workflow Objective: Customer has product X in their cart when they complete their purchase. The product purchased may have digital instruction sheets for installation, videos, related articles or additional related/suggested products they may want to purchase as well.
Workflow Summary:
1. Listen for purchase event from Segment that contains the targeted SKUs so that not every purchase event flows through.
2. Add a slight delay to allow for product to ship. We don't want the email to go out if the customer happens to change their mind. "Listen" for the Shipped event to be passed.
3. Set up queries and send email nodes for each specific email that we are sending. Currently there are only six because this was a very manual process.
4. Add filters to check for the SKU number from the purchase event and to make sure the customer hasn't received this email within the past 180 days.
5. Cycle through each SKU until all conditions have been checked and the customer is done.
Workflow Results:
On our current platform the subsequent conversions from the featured products isn't great, but the open rate is generally 70% and above, unique open rate is 25% and above, CTR is 25% - 30%. As we get them running on Iterable I'm hoping to circle back and adjust the suggested products to boost conversions.
The Workflow: (pending review/confirmation from our most excellent onboarding team)
I am currently using a workflow to test some different value propositions in email for users on file that have not yet converted.
Workflow objective:
- Straightforward A/B test designed to determine what value proposition resonates best with a pre-defined segment (metric of success = cvr to purchase).
Workflow summary:
- Scheduled to a recurring list based on age
- One branch of the workflow designed with a series of email content that emphasizes value 1, a cloned branch with content that emphasizes value 2.
- Delay nodes used to time each send of the workflow
- Filter nodes used to remove users that convert
- Users added to control/test lists for easy performance monitoring
Workflow results:
TBD - A/B test is still live!
The workflow itself:
My very first Iterable workflow was a welcome series sent to new potential home buyers to educate them on the buying process, our properties and cross-selling mortgages.
I launched this the day our IP warmup ended, and as we didn't have our data import automated yet, I manually uploaded the new users every day for a month!
It was a very long manual process - exporting the users from Mailchimp, then running a SQL query to remove irrelevant users (as the data in Mailchimp was wrong), then uploading to a static list in Iterable to trigger the workflow.
That was really tiring, and really makes me appreciate the beauty of automation!
We also launched monthly newsletters for the first time shortly after, with blog articles around the buying and mortgage process, and as they had really great engagement, I added them to the welcome series in between are more sales-driven emails.
Workflow results
We had a shorter 2 email worfklow in Mailchimp, and a longer 7 email workflow when we migrated to Iterable
Results compared to previous Mailchimp workflow:
* 1.5x higher open rate
* 2x higher click / open rate
* 4x more mortgage leads
