Updates below will be available as part of our monthly release scheduled for late-June.
New features
Dynamic Content in Email Campaigns
Introduced personalized, condition-driven email campaigns for follow up campaigns that automatically adapt their content to each recipient's choices
One campaign, many variations: Attach conditions to individual content blocks (e.g. "show this block only to contacts where Session = Session 1"). Recipients see only the content relevant to them, with no manual variation management.
Conditions on any list field: Apply dynamic content rules against any list fields (e.g. RSVP, Session, Attendance fields), giving flexibility well beyond event RSVPs so that you can now easily manage follow up campaigns for complex multisession events
Fallback blocks: Include a block with no condition to ensure recipients who don't match any rule still receive relevant content.
Preview by segment: Before scheduling, select any condition in the preview tool to see exactly what a recipient in that segment will receive.
Manual add for offline RSVPs: Contacts who respond outside the form can be manually added to the campaign with their list fields set following the existing add to campaign action, and the correct dynamic content will be applied.
Dynamic marketing lists in Campaigns
You can now select a Dynamic Marketing List as the recipient list when scheduling an email campaign. Previously only static lists were available in the campaign list picker. This is particularly useful for newsletters and any recurring campaigns where the audience needs to stay current — rather than manually maintaining a static list before each send, your dynamic list keeps itself up to date and the campaign sends to whoever matches at the time.
Live audience resolution at send time: When a dynamic list is chosen, campaign recipients are resolved when the campaign is scheduled, based on contacts that match the list's filter criteria at that moment.
List cleaner support: The existing list cleaning flow works with dynamic lists; high-risk email addresses identified during cleaning are automatically excluded from recipients at send time without removing the contact from the list itself.
Preference lists included: Preference-centre managed lists (a subset of dynamic behaviour) use the same experience.
Quality of life improvements
Smarter import flow
Our improved import flow adds more ways to manage and bulk manipulate data in Nexl.
Add / Replace / Remove on multi-select fields: For multi-select fields (both native and custom), users can now choose whether an import adds to existing values, replaces them entirely, or removes specific values. This gives far more control over data cleaning via import.
Smarter validations: The importer now catches address entries where city or state is mapped without a country (flagged as invalid) and identifies duplicate rows in the file before the import runs.
Unarchive on import: Users can choose to unarchive contacts on new interaction, and companies can be unarchived directly via import.
Broader object support: Contacts, Companies, and Key Activities are all supported; all custom fields work with the new flow.
Improved UI: Clearer explanations at each step, with inline validation errors that can be fixed before confirming.
Improved follow-up campaign workflow
Redesigned how follow-up campaigns are created so the setup happens in the campaign, not buried in the form settings.
Set up follow-ups directly from the campaign page: When creating a new campaign, simply choose "Send a follow-up" as the send type. Previously, follow-up campaigns had to be configured from within the form itself, which wasn't an intuitive place to manage campaign logic.
Link your form and set the trigger from the campaign: Once "Send a follow-up" is selected, you link the relevant form and define the trigger condition (e.g. RSVP = Yes) all within the campaign creation flow, keeping everything in one place.
Automatic send on form submission: Once the campaign is scheduled and active, any new form submission that meets the trigger condition fires the campaign automatically, with no manual intervention needed.
Meeting inherited key activity updates
Three targeted improvements on how to log and external meeting as a key activity, addressing how law firm BD teams actually operate: imperfect calendars, last-minute attendance changes, and BD teams who need an edit layer independent of Outlook access.
Editable contacts and staff on meeting-derived key activities: Attendees inherited from a calendar event are no longer frozen after conversion. You can now add or remove contacts and staff to reflect who actually participated (or should be included for BD purposes), without affecting the underlying interaction record or date-based stats. When manually edited, the system flags the record so Outlook sync does not overwrite the change.
Key Activity date defaults to meeting date in Outlook Add-in: When logging a KA directly from an Outlook calendar event, the date now pre-fills with the meeting's actual date rather than today, bringing the Outlook Plugin into line with existing behaviour in the main app.
"Mark as Key Activity" available from the meeting edit window: The key activity conversion action is now accessible directly from the meeting edit window, not only from the meeting list or slide panel. This removes a context-switching step for BD teams who are already working in the edit view.
Contact enrichment controls
Introduced on-demand enrichment so users can immediately trigger a fresh data request for a specific contact or company, rather than waiting for the automated monthly enrichment cycle.
Re-enrich Contact / Re-enrich Company button: Available under the More Actions (
...) menu on contact and company profiles; sends a fresh request to Entity Office using all email addresses on the record, and a forced LinkedIn refresh if a LinkedIn URL is present.Enrichment status badge on contact profiles: Contact profiles now show a "Contact enrichment · Last Checked [date]" badge so users can see at a glance how fresh the current data is before deciding whether to trigger a manual re-enrich.
Bell notification on completion: When enrichment resolves, a notification is sent and clicking it opens the contact's audit trail, where every field changed by the enrichment is logged with a before/after value.
Updated Contacts page: A running log of contacts whose job-related data changed as a result of the automated monthly cycle, filterable by Company Type.