Sending Intelligent job alerts with the automated communication engine

One of RoboRecruiter’s core values is keeping candidates engaged through the use of automation. Maintaining regular communication with your database builds a stronger relationship with your candidates and leads to higher engagement rates. This leads to a fresh and accurate database and better placement rates. We have recently launched our Automated Communication Engine to tailor our automated communication and better communicate with your candidate base.

 

The Automated Communication Engine is powered by our Job Alerts system, so let’s quickly discuss Job Alerts. At a high level - our Job Alerts allow a user to set job preferences and will notify the user when we find a job that matches these preferences. We index jobs in real time from your ATS/CRM and users can set preferences such as job types, location + search radius, and alert frequency. Job Alerts are a great step in automatically engaging your user base, but we can further personalize the experience to bring the best possible results. 

 

This is where the Automated Communication Engine (ACE) comes in. With ACE we optimize the Job Alert experience by filtering users into distinct buckets based on their behavior and attributes and contacting these groups accordingly. Below are a few examples of how we can better engage with users via ACE. 

 

X alerts since opening a link - Let’s say a user has received five alerts but has not opened any links. We want to find out why they have not shown interest in the alerts and adjust the Job Alert parameters accordingly. After a user receives five alerts we would trigger an ACE campaign to the user in place of their next scheduled Job Alert campaign. This campaign would inquire whether the user would want to adjust their job alert frequency or pause Job Alerts so we can make sure the user is being notified at an appropriate cadence.

 

X alerts since clicking a job - This is a similar case to the above; here, users may have opened Job Alert campaigns and viewed the jobs displayed but have not clicked on any of the jobs. In this case, we might presume the candidate is generally interested in viewing jobs but has not yet found any that piqued their interest. In this case we would fire an ACE campaign that would ask the user if they would like to narrow their search parameters or search radius so we can dial in the user’s Job Alert results for higher relevancy.

  
Screen Shot 2020-07-13 at 2.25.38 PM.png
Screen Shot 2020-07-13 at 2.24.28 PM.png

 
cce 2 v4.gif

  

X days without receiving an alert - This case is on the other end of the spectrum - say a user signed up for Job Alerts but has not received an alert after some time. Here we could reach out with an ACE campaign to see if the user would like to widen their search. We can even contact the user on the condition that we find jobs outside of their original search radius to ask if the user would be interested in expanding their radius to widen their search and find jobs.

 


cce no alerts.gif

 

As these examples show, the Automated Communication Engine provides a more complete user experience for Job Alerts through a tailored, automated approach. This system benefits end users and job posters by providing better job search results and increasing search engagement. Interested in learning more about ACE? Just ask your Customer Success Manager for more information or contact sales to get started today.