There are various ways of managing the contacts and data within your CRM; this article focuses purely on Profile Tags.
Table of Contents
What are Profile Tags?
It is helpful to think of profile tags as mini Global Tags. Whereas global tags should ideally make sense for the majority of your recruiting organization and offer structure and consistency, profile tags give the flexibility for individual Beamery users or teams to be able to code and tag candidates with skills and attributes relevant to their specific business area - without this resulting in an infinite and overwhelming list of global tagging options.
Who can Manage Profile Tags?
Beamery Admins or Super Admins, as well as Team Members can add profile tags to a contact’s record via the mini or full profile, or in the Extension.
Why are Profile Tags useful?
Searching and Filtering - Profile tags can be entered onto a contact’s full and mini profile and be used within the filter panel to resurface relevant candidates.
- Profile tags can be used as a filter to select recipients within a campaign.
Workflow automation - Profile tags can be used as a filter within a recipe to refine and limit the candidates to whom the recipe is applied.
Reporting - Profile tags can be applied via the filter panel in a pipeline or pivot report, to provide insight into candidates with this particular attribute.
How Can Profile Tags be Applied?
Tips for Using Profile Tags
- Unlike Global Tags, profile tags cannot be used in conjunction with Vacancies or Pools.
- Profile tags cannot be applied in bulk (with the exception of re-importing candidates via CSV with a keyword column). Profile tags also cannot be deleted in bulk.
- Some ATS providers (e.g., Greenhouse) map their tags to Beamery profile tags. This can provide a useful mechanism for transferring key candidate data or lists to Beamery, where they can then be migrated into Talent Pools or assigned particular Global Tags or owners if required.
- Profile tags use a free text input and are therefore less rigid than global tags. When filtering using profile tags the correct term needs to be input to identify relevant candidates. This is fine if users are just using profile tags for their own specialist areas as they will know which profile tags to use, and how they need to input them, however it is possible for inconsistencies to arise. For example a Front End Developer might have profile tags written as "front-end", "front end" or "FE" etc. Therefore if attributes are likely to be relevant for multiple teams or users, it may instead be worth considering capturing this data in a more structured way with a Custom Field or Global Tag. Alternatively, it may be useful to provide guidelines or a list to your team on commonly used profile tags to ensure consistency.