Skip to main content

RCRM-Volcanic Consultant Assignment - Release Notes FY25 Q4

Integration of Access Volcanic into Access Recruitment CRM, provides a powerful platform to attract top talent, win new clients, and streamline the hiring process with built-in SEO tools, compliant candidate portals, and a user-friendly content editor.

T
Written by Terence Cassidy
Updated over 2 weeks ago

Whatโ€™s new?

A new configuration has been introduced into Access Recruitment CRM which allows the business to decide how consultants are assigned to an applicant that is created into Access Recruitment CRM via Access Volcanic.


Why have we developed this feature?

This feature removes the requirement for manual intervention to assign the correct primary consultant to newly created applicants via Volcanic.


How do I start using it?

Configuration

  • A user with access to Tools ; Integrations ; Volcanic (tab) will now see additional configuration as follows:

    • Below the existing collapsible section Volcanic to RCRM Data Mapping - Contract Jobs is a new collapsible section titled Volcanic to RCRM Data Mapping - Applicants.

    • A label of Consultant appears on the left of the page of the section.

    • To the right of the label is a dropdown, which when clicked shows options of:

      • Consultant who posted the Job

      • Primary Consultant on the Job

    • The default value is blank.

    • A single value can be selected from the dropdown.

Volcanic to RCRM Data Mapping - Applicants


Applicant Matching to Consultant

  • When an applicant applies for jobs posted to Access Volcanic and the application arrives into Access Recruitment CRM, if the applicant record does not already exist in Access Recruitment CRM, twhen it is created:

    • Secondary consultants are added for each applied Job based on the Setting as described below.

  • If the applicant record already exists in Access Recruitment CRM:

    • Secondary consultants are added (if they do not already exist) for each applied Job, based on the Setting as described below.

  • <blank> (setting)

    • Do not assign a consultant to the applicant record (this is the existing flow).

  • Posting the Job (setting)

    • The applicant's secondary consultant = the consultant who posted the job to Volcanic.

  • Primary Consultant on the Job (setting)

    • The applicant's secondary consultant will be the primary consultant on the job (if one is populated, otherwise it will be left as blank).

Did this answer your question?