New Features
Zoom for Bookings New
You can now connect Zoom to your booking module, so a Zoom meeting is created automatically whenever someone books time with you.
Connect your Zoom account per workspace, and from then on every booking creates a Zoom meeting, reschedules update it, and cancellations remove it, with no manual steps. Google Calendar and Zoom now run as separate pipelines, so a booking still lands on your calendar even if one side has an issue, and neither blocks the other.
Example
- Automatically create a Zoom meeting whenever a client books a call.
- Have the Zoom link update itself when a booking is rescheduled.
- Remove the Zoom meeting automatically when a booking is cancelled.
- Connect or disconnect your Zoom account per workspace.
This makes Zoom bookings fully hands-off, from the first invite to the final reminder.
Email Open-Tracking Consent New
Contacts can now opt out of email open-tracking on its own, without having to unsubscribe from your emails entirely.
This supports the French CNIL requirement, in effect since April 2026, that open-tracking pixels used for marketing need their own consent, separate from consent to receive the emails. There is a new workspace setting to require tracking consent, which is off by default, so nothing changes for you unless you turn it on. When it is on, new contacts start with tracking withheld until they opt in. Consent can be collected through a toggle on the preferences page and an optional checkbox at double opt-in confirmation, and a new {{tracking_preferences_url}} merge tag links people straight to it. Open rates now account for recipients whose pixel was withheld, so your numbers stay accurate as opt-outs grow.
Example
- Let privacy-conscious contacts stop open-tracking while still receiving your emails.
- Turn on a workspace-wide tracking-consent requirement to meet CNIL rules.
- Add a tracking preference link to your emails with a single merge tag.
This gives you a compliant way to respect tracking preferences without losing subscribers.
Improvements
Custom Success Pages for Forms Improved
You can now design a custom success page that appears after someone submits your form, instead of only showing a message or a redirect.
Build the page in the landing page builder just like the rest of your landing pages, and it displays inline right after submission. A variable picker lets you drop in submitted details, so the page can greet people by name or reflect what they entered, and those values are filled in at the moment the page is shown. The existing message and redirect options still work exactly as before if that is all you need.
Example
- Show a branded thank-you page after a signup instead of a plain message.
- Greet people by name on the success page using their submitted details.
- Give clear next steps right on the confirmation screen.
- Keep using a simple message or redirect where that is enough.
This makes the moment right after submission feel like part of your brand rather than an afterthought.
Partial Submissions for Multi-Step Forms Improved
Multi-step forms can now save what someone has entered on each step, even if they never reach the end and submit.
This is an opt-in setting that is off by default. When you turn it on, each completed step is saved as a partial submission, so you can see how far people got and what they entered before dropping off. Partial submissions appear in your normal submissions list, marked as partial. Forms without the setting enabled behave exactly as before.
Example
- See where people abandon a long multi-step form.
- Recover details someone entered on step one but never completed.
- Spot which step causes the most drop-off so you can fix it.
- Leave the feature off on forms where you only want completed submissions.
This turns abandoned forms into something you can learn from and follow up on.
Step-Level Email Engagement in Branch and Filter Improved
Automation Branch and Filter conditions can now check engagement with a specific email step inside an automation, not just overall engagement.
Previously you could branch on lifetime engagement, such as whether a contact had ever opened an email. Now you can ask about one particular step, for example whether a contact opened the Welcome Email step or clicked a specific link in it. You can match on opened, not opened, clicked any link, clicked a specific link, opened without clicking, and similar combinations. A picker lists the email steps in the automation by their subject line, so you can choose the right one without opening each node.
Example
- Branch contacts based on whether they opened your Welcome Email specifically.
- Follow up only with people who clicked a particular link in one email.
- Route people who opened an email but did not click into a separate path.
- Pick the exact email step from a list instead of guessing.
This gives you much finer control over automation paths based on how people react to individual emails.
Trigger Automations from Bulk Tag and List Actions Improved
Bulk tag and list actions can now optionally trigger the automations connected to those tags and lists.
When you bulk-add or remove tags or lists across many contacts, you can choose whether that should fire any automations set up on them. It is off by default, so bulk actions stay quiet unless you opt in. When you do turn it on, automations only fire for genuine changes, so re-applying a tag a contact already has will not trigger anything.
Example
- Bulk-add a tag and have its welcome automation run for each contact.
- Move many contacts onto a list and start its nurture sequence.
- Keep a large cleanup silent by leaving the option off.
- Avoid duplicate triggers when re-applying tags contacts already have.
This gives you control over whether large tag and list changes should set your automations in motion.
Contact Language No Longer Defaults to English Improved
New contacts no longer have their language set to English automatically when it is not actually known.
Previously every contact was created with English as their language by default, even when their real language had not been captured. The language field is now left empty until it is genuinely known, which keeps language-based segmentation and any language-specific content accurate instead of assuming everyone is English.
Example
- Keep language-based segments accurate instead of showing every contact as English.
- Send language-specific emails only to contacts whose language you actually know.
- Avoid wrongly assuming a contact’s language before you have captured it.
This keeps your language data honest, which matters as soon as you send in more than one language.
Bug Fixes
Booking Widget Layout on Narrow Embeds Fixed
Fixed an issue where the booking widget’s calendar and time slots broke visually when embedded in a narrow space, such as a WordPress sidebar or a SureDash panel. Slot labels could overlap or become garbled, and two-digit dates could wrap onto two lines. The calendar and time slots now collapse cleanly into a single column based on the space actually available, and the loading state matches the final layout so there is no visual jump once the widget loads.