You can now insert merge tags directly into Add Task and Add Comment automation steps. Pull in candidate name, job title, job owner, and other field values automatically — so every task description or comment is personalised to the record, with no manual text editing required.

A new automation action allows employment type to be updated on candidate records as part of an automation flow. Teams managing large candidate pools can now apply employment type changes through rules — without manual, record-by-record updates.

Job Owner has been added to the merge tags dropdown, allowing automations to pull the owning recruiter’s name directly into task and comment content. This ensures context-aware communication without hardcoding names or creating separate automation branches per recruiter.

Merge tags in task and comment steps are now filtered by the type of automation you are configuring. Rather than showing every available token, the system surfaces only the tags relevant to the current automation context — reducing noise and making configuration faster and less error-prone.

Tasks created through an automation step are now synced to the calendar automatically. Recruiters no longer need to manually add automation-driven tasks to their schedule — as automations fire, the calendar updates in step.

Automation date criteria now support a “Days After (Range)” option, letting you target records that fall anywhere within a window of days after a given date field. This removes the need to create multiple overlapping rules just to cover a broader time band.

The search functionality for Candidates, Contacts, and other entities now includes an Activity Type filter. You can now narrow results based on the type of activity recorded against a record, making it faster to surface the right people at the right moment in your workflow.

Custom fields for Vincere-integrated clients are now managed dynamically per company in the database, replacing a system of hardcoded logic spread across three repositories. Adding or updating a custom field for any client now requires only an admin panel entry — no code changes, no deployments, no cross-team coordination.

Companies can now define their own document types (e.g. “STCW Certificate”, “Right to Work”, “CFARES Medical”) that appear in the chatbot flow generator’s File Upload block. These map automatically to the corresponding Vincere document type, ensuring uploaded files are classified correctly without any hardcoded entries in the codebase.

Chatbot conversation exports are now delivered as CSV attachments via email rather than as direct HTTP downloads. The new approach handles high-volume exports reliably using pagination (10,000 rows per page), masks file upload values in the export for data hygiene, and allows non-EVO users to specify a recipient email address at the point of export.