Beta Program Participant Qualification: Part 2
Who's the best fit for your beta program?
There is a reason people run a beta period for an upcoming feature. A new experimental feature provides a powerful new tool to your arsenal, but it also may not be fully ready yet. While it could have some bugs you haven't found yet, it may be just as likely that you might have missed a powerful use case for it and further work is required. Vetting who has access to it ensures you get the feedback you need to be ready for launch.
This automation runs contacts through a series of If/Else statements, checking their score total generated by Part 1 of this automation series. The contact is then tagged accordingly with how qualified they are for the beta program, with messaging after to either the contacts directly or your team for next steps.
Here's how this automation works:
1. The contact is entered into the automation from an Enter other automation action located in the Beta Program Participant Qualification: Part 1 recipe.
2. The contacts then goes through an If/Else action checking if their qualification score total exceeds a specified threshold.
3. If they meet the condition, they go down the Yes path and are tagged as Beta: Highly Qualified and sent an email welcoming them to the beta program.
4. If they do not meet the condition, they go down the No path to another If/Else condition.
5. This If/Else condition checks to see if the contact's score total is within a specific range.
6. If they meet the condition, they go down the Yes path and are tagged as Beta: Qualifed and a notification action is sent to your team to make a determination on the contact's participation in the beta program.
7. If they do not meet the condition, they go down the No path and are tagged as Beta: Not Qualified.
Note: For this automation, you should set the conditions in the If/Else actions to check for score thresholds based on the amount of points someone could be awarded in Part 1 of this automation series. The first If/Else should be set a high threshold for contacts who are very qualified. The second If/else should be set to a threshold in the middle for contacts who are qualified, but not exceptionally.
Note: For our example, the highest score is 6. The first If/Else checks for the score being at or above 5. The second If/Else checks for two conditions, the first being if the point total is lower or equal to 4 and the second being if the point total is higher or equal to 2.
Note: In our example, we automatically accept highly qualified contacts and send an email message directly. For qualified contacts, we send a notification action to a team to make a determination. Feel free to adjust these messaging options to what makes sense for your process.
Get started today
Try it free. No credit card required. Instant setup.