What's new

You can now delete options from Dropdown, Multi-select, Radio, and Checkbox fields for Custom Objects and Companies, bringing the same capability already available for Contact and Opportunity fields.

If an option is already used, existing records keep the value while the option is removed from future selection.

• Delete unused options permanently
• Remove used options from future selection without losing existing record data
• See how many records use an option before deleting it
• Existing filters, Smart Lists, and workflows continue to work

You can clean up outdated or incorrect field options without breaking historical data or existing automation.

1. Go to Settings → Custom Fields
2. Open a Custom Object or Company field
3. Delete the required option
4. Review the affected-record count, if applicable
5. Confirm deletion

• Used options remain visible on existing records
• Deleted options cannot be selected for new records, filters, or workflow conditions
• Contact and Opportunity fields already support deleting options

Due to an upstream carrier migration, SMS is no longer supported on Mexico local phone numbers. To make this clear, we've added a status indicator directly in the Phone Numbers table.

"SMS not supported" status pill on Mexico local numbers ":

• Under Manage Numbers >> Phone Numbers, any Mexico local number now shows an "SMS unavailable" pill alongside its existing status pills, so admins can see at a glance which numbers lost SMS capability.
• This applies to both existing and newly purchased Mexico local numbers.
• Improved multi-pill layout : When a number carries more than two status pills, they now wrap within the column instead of breaking the table layout.

• Go to Settings >> Phone Numbers >> Manage Numbers >> Phone Numbers tab.

• If you have a Mexico local number, you'll see the "SMS not supported" pill with a tooltip for more context.
• Voice (and WhatsApp, where applicable) continues to work as normal.
• The buying journey for phone numbers remain unchanged and the numbers which are affected because of this carrier side dependency will show up with capability other than SMS . Please ensure that you make your number purchases accordingly

No setup is required ,the pill appears automatically for affected numbers.

Please feel free to reach out to our support teams in case of any queries.

When a service appointment's calendar event was rescheduled or cancelled directly from a connected third party calendar (e.g., Google or Outlook calendar) — the change previously updated the calendar event only, leaving the service appointment record out of sync. For single-service appointments, this is now fixed: changes made directly on a third-party calendar sync back correctly everywhere. Multi-service appointments would still remain out of sync if directly updated on third party calendars.

✅ Full two-way sync for single-service appointments

When a service appointment has just one service/event, a reschedule or cancellation made directly in third party calendars (e.g., Google or Outlook) now updates the calendar event and the service appointment together — so your third-party calendar and in-app calendar always agree.

✅ Correct appointment data everywhere you look

For single-service appointments, the calendar view, the appointment list view, and the appointment's view-details all now correctly reflect reschedules or cancellations made directly on a connected third-party calendar.

• No setup needed — these improvements are live automatically.
• Single-service appointments: Reschedule or cancel directly from third party calendars (e.g., Google or Outlook) — the change syncs back automatically, and shows correctly in the calendar, appointment list, and view-details.
• Multi-service appointments: These are not yet synced with third-party calendar changes — continue managing schedule changes for multi-service appointments directly in-app to avoid your appointment and calendar event going out of sync.

• Closes a double-booking risk that occurred when a third-party cancellation or reschedule for a single-service appointment wasn't reflected in the in-app appointment.
• Keeps the calendar view, appointment list, and appointment details in agreement for single-service appointments, no matter where the change is made.
• Reduces support reachouts stemming from mismatched appointment times or statuses between the services calendar and connected calendars.

What's New

For SaaS V2 accounts, when the clients update their default payment card, we now automatically update the card used for the active SaaS subscriptions too.

Why It Matters

Your subscription renewals will use the latest card automatically, reducing the chance of a missed or failed payment because an old card was still on file.

Notes

This applies to SaaS V2 accounts with an active subscription plan. Wallet recharges continue to use your default card as before.

What's New

When you enable SaaS for a sub-account and choose to attach a snapshot, we now check whether the snapshot would overwrite anything you've already customized in that sub-account. If it would, you'll see a warning before any changes are made, and you can choose to either keep your existing assets or overwrite them with the snapshot's version. If there's no conflict, the snapshot applies just like before.

Why It Matters

Previously, attaching a snapshot could silently overwrite funnels, websites, or other assets you'd already updated in a sub-account — with no warning and no way to undo it. Now you're always in control: you'll see exactly when a conflict exists and get to decide what happens to your work.

Notes

• This applies to both SaaS V1 and V2 accounts.
• For bulk SaaS enablement, attaching a snapshot isn't available as an option yet, so we automatically protect your existing assets by default in that flow — no prompt, no risk of overwrite.

Coming Soon

• The same conflict warning and choice you get in individual SaaS enablement, brought to bulk SaaS enablement once snapshot attachment is added there.

What's New

If your plan is priced in Hungarian Forint (HUF), the price shown in your client portal Billing view now matches exactly what your agency configured. Previously, this view could show an amount 100 times higher than your actual plan price (for example, a 9,700 HUF plan appeared as 970,000 HUF).

Why It Matters

You'll now see the correct, accurate price for your HUF plan every time you check your billing details — no more confusing or alarming numbers that don't match what you're actually being charged.

Notes

• This fix applies to plans configured in Hungarian Forint (HUF).
• No action is needed on your part — the correct price now displays automatically.

The User login workflow trigger now fires for logins from the new Client Portal experience — not just legacy membership logins. We've also added a dedicated Client Portal category in the workflow trigger picker, so all Client Portal triggers live in one place.

🔑 New Client Portal logins now fire the "User login" trigger Successful logins from the new Client Portal experience now emit the same workflow trigger event as legacy membership logins. Any workflow already using the User login trigger will start running on these logins automatically — no reconfiguration required.

🗂️ New "Client Portal" category in the trigger picker A dedicated Client Portal category now groups all Client Portal triggers together:

User login — moved from Courses

Client portal file uploaded — moved from Membership

💬 Clearer helper text The User login trigger now spells out that it covers both legacy membership logins and logins from the new Client Portal experience — removing the confusion caused by its old placement under Courses.

Automate on Client Portal member login

• Open the Workflow Builder.
• Click Add trigger and search for User login.
• Select it under the new Client Portal category (previously found under Courses).
• Save your workflow — it will now fire on both legacy membership logins and logins from the new Client Portal experience.

Already using this trigger? No action needed. Existing workflows continue to run as-is and will automatically pick up login events from the new Client Portal experience.

Agencies on the new Client Portal experience previously had no way to automate off a member login, because the trigger only covered legacy memberships. Trigger placement was inconsistent too — login sat under Courses while file upload sat under Membership — making it unclear what each trigger actually covered. This update closes the gap and puts both triggers where you'd expect to find them.