A great place to post your ideas and vote on others so that you can let us know what is important to you.
Please take the time to register, and then share your detailed use case and how the proposed enhancements could provide value to your organisation.
We endeavour to provide an initial response to all ideas in a timely manner.
Hi Steve,
Sure, there are a couple of scenarios where we have done this:
For where we are running 'campaigns' using the EOI function within PageUp rather than a Job. For example, we have an international recruitment campaign running right now where we have one EOI set up in PageUp. We then have jobs that we have added in the RM module for locations around the world where we would like applicants from (US, USA, Philippines, Canada, Ireland, South Africa). For each of these locations we have posted a job via RM, and for the application URL we use the EOI from PageUp - and Indeed.com can then index the job in the respective source country we are targeting. So all applications from all locations we are targeting end up in the one PageUp campaign. We do this method for a couple of reasons (1) Those locations don't exist in PageUp, and locations come from another system in our business and need to be real physical sites. I can manually add locations in RM even if we don't have those physical sites in our business. (2) This method means I can have multiple jobs quickly and easily without creating requisitions in PageUp.
The other time we use this method is to test different job ad copy with Indeed.com. I can manually create a job on RM with different ad copy and still point the application form to the real job in PageUp.
Thanks for taking the time to provide this suggestion Dario.
Are you please able to elaborate on the scenarios where you find yourselves creating jobs directly within the Recruitment Marketing module, rather than via the job card / sourcing screens in the ATS.
Thanks in advance.
--
Steve Oxley
Product Manager