We love to hear your feedback. Your suggestions and ideas are important to us. Our feedback forum is a great place to post your ideas and vote on others. Please share your detailed use case and how the proposed enhancements can increase value to your business. We do read all of your posts, but may not be able to respond to all comments.
More information on the status of submitted ideas can be found here
Add Preferred name as a merge field for the Applicant Email Change Notificaion email that was recently added as a configurable template. We use the preferred name merge on all communications to our applicants.
|
What is the business process you are trying to achieve?
I don’t understand why we can use Preferred Name as a merge field. You have that merge for Applicant reset password, but not this new one. We also use preferred name in all our communication templates. Any reason why they wouldn’t have done it for this one? It makes us inconsistent in our emails to our applicants. |
If the platform could provide the ability to use a preferred name if provided and if not then drop back to First name provided.
Thank you for your feedback. This communication template was recently added to the system and contains a limited number of merge fields. This is because for some templates, it doesn't always make sense to support a wide range of fields relating to a job or application (as as example) based on the context of the template.
Having said that, we want to ensure consistency where possible and will be adding Preferred Name as well as Last Name to this template. This will allow our users to address their applicants in a consistent manner across their communications. Information on this change as well as release dates will be added to the upgrades page on our Knowledge Portal shortly