Beamery Recipes are automated workflows that allow Beamery users to save time, nurture candidate relationships, identify relevant candidates and seamlessly manage candidates through the recruiting funnel. This article is a high-level overview of Recipes, but detailed instructions for creating a recipe can be found here.
Recipes can only be created by users with Admin level permissions. If you have the required permission level, recipes can be accessed by clicking on Automation in the left-hand navigation panel.
What is involved in creating a recipe?
Recipes allow you to develop incredibly efficient automated workflows. They use if > then logic, along with filters, to help ensure that only the right contacts are actioned given the criteria provided.
Recipes are composed of 3 primary components: Triggers, Filters and Actions. These can also be combined within a single recipe to create more complex automation outcomes.
Common Use Cases for Recipes
- Contact management and maintaining data integrity - For example, updating the status of contacts who meet specific trigger criteria; or automating an action for contacts who are moved to a specific status.
- Continuous Sourcing and Talent Pool Management - For example, prioritize candidates with key attributes, such as those who have certain data within their profiles or surfacing contacts due for re-engagement.
- Candidate Communication and Engagement - For example, automating message touches along the candidate journey by sending campaigns to contacts who meet certain trigger and filter criteria.
- Compliance with General Data Protection Regulations - For example, automate the sending consent requests and the anonymization of contacts based on consent activity.
- Vacancy Management - For example, adding or removing contacts from a campaign based on their communication and interaction with recruiters.
- Automating Sign up Forms and Candidate Journeys - For example, pooling and updating the status of contacts who have completed a Beamery form or automating communications for contacts who have registered for an event.
Understanding Recipe Components
These are what determine whether a recipe action will take place. Until the trigger criteria are met by a contact, the recipe will remain unused. A few of the available triggers include when a contact's status has been updated, when they have been added to a vacancy or when they have completed a Convert Flow.
Filters help you ensure your recipe applies only to a very specific set of candidates. The filter options in Recipes are exactly the same as those available in the CRM grid view. This enables many time-based actions as well as allowing you to incorporate your custom fields into your recipe logic.
After applying your triggers and any relevant filters, you can now decide upon an action to be taken for candidates who meet the criteria you have specified. Some of the available actions include adding contacts to a pool, sending them an email campaign, changing their communication status to 'Do not contact' or assigning contact ownership to specific users. You may also select multiple actions if relevant.
Once you have decided on your triggers, filters, and actions, you will see a section where you can review your selections. Once you are happy with these, click on the "Activate" button. You have now created a live recipe.
Additional Recipe Features
You can easily pause a recipe if needed or re-activate a recipe that has been temporarily paused.
You can further manage a recipe by clicking on the 3 dots next to the recipe, where you will see options to duplicate, pause, or delete the recipe.
Recipes can also be categorized using Global Tags and searched by name.
Each recipe will have an indication of the last time it was modified, the owner, the status of the recipe and the number of times it has been used. You also have the ability to export your recipe data for more visibility to audit all Recipes.
Note: Similar to how a contact cannot be added to the same campaign more than once, Recipes will only apply to a particular contact one time, to avoid erroneous process duplication. If you have the 'repeat recipe' option as part of your package, you can create a recipe that will act on contacts more than once.