ZenotiHelp

Release notes - August 3, 2026

ZTZenoti Docs Team Updated September 29, 2026 151 min readGuide

On this page

This document describes the new features and enhancements delivered in this release. Updates are organized by module for ease of access and to cover the changes relevant to a specific role or workflow.

Each update appears as a separate entry. An entry may include the affected roles, a description of the change, a business scenario, the steps to configure or use the feature, and links to detailed documentation. The elements included depend on the nature and scope of each update.

AI Dispute Manager

Activation prompt dismiss behavior clarified and 'Don't show again' control added

Audience/Roles: Business Owner, Administrator, Center Manager

Overview: The activation prompt's dismiss behavior has been updated: closing the prompt without making a selection now causes it to reappear the following day (previously it reappeared on an unspecified later visit). A clearly labeled 'Don't show again' control permanently suppresses the prompt for the entire organization, leaving only the activation banner on the dashboard. The troubleshooting guidance now explicitly references 'Don't show again' so users can identify why the prompt no longer appears.

Business Scenario: A center manager closes the activation prompt without acting on it and expects to revisit the decision tomorrow. The prompt returns the next day as expected. When she is certain she wants to defer activation indefinitely, she selects 'Don't show again' to suppress the prompt organization-wide and uses the persistent activation banner whenever she is ready to proceed.

Default behavior and validations: Closing the prompt without selecting an action causes it to reappear the following day. Selecting 'Don't show again' permanently suppresses the prompt for the organization; the activation banner remains available on the dashboard as an alternative entry point to activation.

Notes: The permanent suppression applies at the organization level, not per user. If neither the prompt nor the activation banner appears and the active-state banner is shown, AI Dispute Manager is already active.

Learn more: Activate AI Dispute Manager

AI Dispute Manager billing usage measurement

Audience/Roles: Business Owner, Administrator

Overview: AI Dispute Manager (AIDM) now tracks and measures billing usage by identifying which disputes received genuine AI involvement in evidence preparation or submission. Only disputes that meet specific AI-assisted criteria—such as evidence submitted by the AI auto-submission job, disputes handled in Instant AI mode, or AI with Manual mode disputes submitted within the configured takeover window—are counted toward your invoice. Disputes involving buy-now-pay-later payment methods (Klarna, Affirm, Afterpay), disputes with no submitted evidence, and auto-defended disputes without AI involvement are always excluded. The AI-Assisted tab on the Disputes Management dashboard reflects the same qualification logic used for billing, giving you a direct way to verify and reconcile your invoice.

Business Scenario: An organization administrator receives a monthly AIDM invoice and wants to confirm the billed dispute count before approving payment. They navigate to Payments > Disputes Management, select the AI-Assisted tab, apply the billing period date range, and compare the dashboard count against the invoice line item—resolving any discrepancy by checking for BNPL disputes or boundary-date timezone differences.

How to Use:

  1. Ensure AI Dispute Manager is activated for at least one center via the Zenoti Marketplace.
  2. Confirm you have the Dispute Payments permission.
  3. Navigate to Payments > Disputes Management.
  4. Use the center filter to select a specific center or choose the organization-level view.
  5. Select the AI-Assisted tab to view only disputes where AI generated or submitted evidence.
  6. Apply advanced filters and set the date range to match your billing period start and end dates.
  7. Note the dispute count shown—this is your AI-assisted billing usage count for the selected center and period.
  8. For organization-level totals, switch to the organization-level view and apply the same date filter.
  9. Export the dispute list from the AI-Assisted tab for offline reconciliation against your invoice.

Default behavior and validations: Billing period boundaries are interpreted using the center's local timezone, not UTC. For organization-level calculations, the timezone anchor is the organization's oldest active center. Inactive centers are excluded from organization-level counts. A dispute qualifies as AI-assisted only when evidence has been submitted, the dispute was not auto-defended without AI involvement, and the payment method is not BNPL. At least one of the following must also apply: evidence was submitted by the AI auto-submission job, the dispute was handled in Instant AI mode, or the dispute was handled in AI with Manual mode with evidence submitted on or after the configured takeover threshold date (T-4, T-5, or T-6).

Notes: AI Dispute Manager must be activated through the Zenoti Marketplace before billing usage tracking applies. Organizations with centers in multiple timezones should review the AI-Assisted tab at the individual center level to accurately attribute boundary-date disputes. The AI with Manual takeover threshold configured per center directly affects which disputes qualify; verify the threshold setting if fewer disputes than expected appear as AI-assisted. For pricing and commercial terms, contact your account manager.

Learn more: AI Dispute Manager Billing Usage Measurement

AI Photo Manager

Billing usage metering for Photo Manager and AI treatment visualizations

Audience/Roles: Business Owner, Administrator

Overview: Photo Manager now tracks two categories of billable activity: photos captured through the Photo Manager camera interface and AI-generated treatment visualizations. Usage is calculated over a defined date range, can be scoped to the entire organization or to a single center, and automatically excludes voided records. Overage indicators are also recorded on individual guest files to flag activity that occurred when the relevant feature was not enabled, helping billing teams identify potential overage charges.

Business Scenario: An organization administrator wants to understand Photo Manager consumption before the billing period closes. They ask their Zenoti account representative for an organization-level usage summary and a center-level breakdown to see which locations are generating the most AI visualizations, then confirm that any photos captured in error were properly voided so they are excluded from the billable count.

Default behavior and validations: Usage counts are read-only and cannot be manually adjusted. Only photos captured through the Photo Manager camera interface are counted; photos uploaded directly to a guest gallery are excluded. Voided photos and visualizations are excluded from all counts. Overage indicators are set at the time of capture or generation and are not updated retroactively if the feature is later enabled or disabled. Organization-level scoping is used by Zenoti for billing; center-level breakdowns are available on request from your account representative.

Notes: Photo Manager must be enabled for your organization before any usage is recorded. Contact your Zenoti account representative to activate Photo Manager or to request a center-level usage breakdown. To avoid overage indicators on new records, ensure Photo Manager and the AI Photo Manager feature are enabled before your team begins capturing photos or generating visualizations.

Learn more: Billing Usage Metering

Audience/Roles: Administrator, Center Manager, Front Desk Operator, Service Provider

Overview: The guest gallery now supports advanced filtering, allowing staff to narrow a guest's full photo history by center, provider, service category, treatment concern, upload source, and file type. Filters combine using AND logic so multiple criteria can be applied simultaneously to surface exactly the files needed. This reduces time spent manually scanning large galleries when reviewing treatment progress, preparing for consultations, or auditing photo records.

Business Scenario: A clinical staff member preparing for a follow-up consultation wants to review only before-and-after images taken by a specific provider at the downtown center for facial services. By combining the Center, Provider, Service category, and File type filters, they immediately see the relevant photos without scrolling through the guest's entire history.

How to Use:

  1. Open the guest profile for the guest whose photos you want to review.
  2. Select the Gallery tab to open the guest gallery.
  3. Locate the filter controls at the top of the photo list.
  4. Select values for one or more filters: Center, Provider, Service category, Treatment concern, Upload source, or File type.
  5. Review the gallery, which updates automatically to show only files matching all active filters.
  6. To remove an individual filter, clear its selected value; to remove all filters at once, select the clear all filters option.

Default behavior and validations: All filters are optional and inactive by default; when no filter is selected, the gallery displays all photos for the guest across all centers. Filters combine with AND logic. The Provider filter returns only files linked to an appointment — photos uploaded directly to the guest profile without an appointment association are excluded. The Treatment concern filter requires that services are mapped to treatment concerns in the organization configuration; photos with no associated service are always excluded from treatment concern filter results. File type categories are: Images (png, jpg, jpeg, tiff, gif, webp, heic), PDFs (pdf), and Videos (mp4, mov, avi, wmv, mkv, webm). Filters persist within the current session.

Notes: Photo Manager must be enabled for the organization before the guest gallery is accessible. Users require the Gallery View permission (Configuration > Security roles > Appointment book section > Gallery View). The guest must have at least one photo on file for filters to return results. Treatment concern filtering requires treatment concern mappings to be configured at the organization level.

Learn more: Guest Gallery Advanced Filtering

Updated permission label and worked example for AI treatment progress analysis

Audience/Roles: Service Provider, Administrator

Overview: The required permission label has been corrected from 'Guest View' to 'Guests View' to match the actual permission name in Zenoti. A worked example has also been added to the analysis step, showing a concrete scenario—selecting a service, setting a date range, and reviewing the returned photo and session counts—so providers can better understand what to expect from the AI output.

Default behavior and validations: The 'Guests View' permission (Photo Management) remains required alongside Camera Access or Gallery View. The Photo Manager feature must be enabled for the organization, and the guest must have treatment photos from multiple sessions before analysis can be run.

Notes: The permission name change is a documentation correction only; no functional access control has changed. The worked example is illustrative and actual results will vary based on the guest's photo history and selected filters.

Learn more: Analyze treatment progress with AI

Audience/Roles: Business Owner, Center Manager, Administrator, Service Provider

Overview: The Global Gallery filter panel now includes three additional filters: Service Categories, Providers, and Centers. Service Categories lets users broaden a search across all services within a treatment category, Providers narrows results to photos associated with specific providers, and Centers limits results to photos from specific locations. These additions give multi-center organizations more precise control when browsing large photo collections.

Business Scenario: A center manager at a multi-location medspa wants to review all before-and-after photos for body contouring services across two locations. They apply the Service Categories filter set to 'Body' and the Centers filter set to their two locations, instantly narrowing the gallery without needing to know every individual service name.

How to Use:

  1. Navigate to Medical hub > Global gallery.
  2. Open the filter panel.
  3. Select Service Categories to filter photos whose associated service belongs to a specific category.
  4. Select Providers to filter photos associated with specific providers.
  5. Select Centers to filter photos from specific centers.
  6. Apply one or more filters in combination; the gallery updates as each filter is applied.

Default behavior and validations: All filters are optional and unset by default. Multiple filters can be applied simultaneously. Existing filters (File Tags, Services, Guidelines, Date Range, Photo Sequences, Image Guideline Types) remain unchanged.

Notes: The Photo Manager feature must be enabled for your organization, and your role must have View permission on the Global Gallery to access these filters.

Learn more: Manage global gallery

Bulk edit file tags renamed to 'Bulk edit file tags'

Audience/Roles: Business Owner, Center Manager, Front Desk Operator, Administrator

Overview: The 'Bulk tag photos' section has been renamed to 'Bulk edit file tags' in the guest gallery. This change aligns the section heading and navigation anchor with consistent terminology used across the Photo Management module, making it easier to locate the bulk-editing workflow in documentation and in-product navigation.

Default behavior and validations: Required permissions remain unchanged: Camera Access or Gallery View (Photo Management) AND Guest Add, Edit, or Delete permission.

Notes: This is a terminology and navigation label change only. The underlying bulk tag editing functionality and required permissions are unaffected.

Learn more: Manage guest gallery

AI Scribe

AI Scribe billing model: licensed vs. per-minute usage

Audience/Roles: Business Owner, Administrator

Overview: AI Scribe recordings are now billed under one of two tracks based on whether the recording provider held an active AI Scribe license at the exact moment the recording was created. Licensed-provider recordings are covered under the provider's license fee with no additional charges, while recordings from unlicensed providers are billed by total minutes consumed per billing period. The billing track is permanently stamped at recording creation and cannot be altered by later license changes, so verifying provider license status before a session directly controls which track applies.

Business Scenario: A multi-center organization notices an unexpectedly high AI Scribe charge. By reviewing center-level usage data, the finance administrator identifies one location where several high-volume providers were unlicensed during a busy week. Activating licenses for those providers before future sessions moves their recordings to per-license billing, reducing per-minute charges going forward.

How to Use:

  1. Confirm AI Scribe is enabled for your organization; contact your administrator if it is not active.
  2. Navigate to Configuration > AI Scribe and open AI Scribe - user access.
  3. Search for a provider using the Search employees field and review the Status column (Active = licensed, Inactive = unlicensed).
  4. Activate or deactivate a provider's license as needed before any recording session begins.
  5. Review AI Scribe usage reports to view per-minute totals at organization level (all centers combined) or center level (single center) for cost allocation.

Default behavior and validations: The billing track is determined at the moment a recording is created and is permanent. Per-minute usage includes only recordings that are not voided and have reached a completed processing state. Rounding to whole minutes is applied once to the aggregate second total for the entire billing period, not per individual recording. Partial minutes are always rounded up.

Notes: AI Scribe must be enabled at the organization level before license assignments take effect. The AI Scribe user management permission is required to view and manage provider license assignments. Current license status shown in Configuration reflects today's status; historical status at the time of a specific recording must be verified through AI Scribe usage reports.

Learn more: AI Scribe Billing Model — Licensed vs. Per-Minute Usage

AI Scribe insight categories for clinical documentation

Audience/Roles: Service Provider, Administrator

Overview: AI Scribe now organizes generated clinical documentation into two independent insight categories: SOAP+ notes and Recording Summary. Each category maintains its own content, version history, and audit trail, so changes to one category never affect the other. When multiple recordings exist for the same service appointment, AI Scribe automatically merges content into a single consolidated insight per category, with newer recordings taking precedence. This gives providers a clear, auditable record of clinical documentation at every stage of a multi-session appointment.

Business Scenario: A provider records two sessions for a facial service appointment. After processing, the SOAP+ notes category displays a consolidated charting summary merging both recordings. The provider edits the SOAP+ notes to add a clinical observation, creating version V1.1 in that category's version history. The Recording Summary remains at V1.0 and is completely unaffected, preserving a clean, independent audit trail for each documentation type.

How to Use:

  1. Ensure AI Scribe is enabled for your organization and that your user account has AI Scribe access (Configuration > AI Scribe).
  2. Confirm your security role has 'AI Scribe user management' and 'AI charting notes - view access' permissions.
  3. Open the appointment in Zenoti Mobile App (ZMA) or Zenoti Web.
  4. Navigate to the AI Insights section of the appointment.
  5. Select the Insights tab to view SOAP+ notes, or the Recordings tab to view the Recording Summary.
  6. To review edit history for a category, tap the three-dot menu and select Version History.
  7. When multiple recordings exist, look for the consolidated indicator in the insights view to confirm you are viewing the merged result.

Default behavior and validations: Consolidation is automatic when multiple recordings exist for the same service; no manual trigger is required. Version sub-entries (V1.1, V1.2, etc.) are created only when insight content is manually edited and saved — viewing without saving does not create a new version. Earlier versions can be viewed and compared but cannot be restored. If no consolidated insight exists yet, the view reflects a baseline state rather than an error. Recording is supported on ZMA only (Android or iOS devices with 4 GB RAM or more); Zenoti Web provides view-only and edit access to insights. Individual recordings are capped at 95 minutes, with a 3-hour cumulative cap across all recordings for the same service.

Notes: AI Scribe must be enabled at the organization level before insight categories are accessible. Banner color indicates category-level processing status: green = processed, yellow = processing in progress, red = generation failed. A failure in one category does not affect the other category. If insights are missing or a red banner appears, try regenerating from the AI Insights section; contact your administrator if the issue persists.

Learn more: AI Scribe Insight Categories

AI Scribe license revocation via subscription cancellation (void-all)

Audience/Roles: Administrator

Overview: When an organization cancels its AI Scribe subscription, a void-all operation automatically revokes every active AI Scribe license across the organization in a single atomic step. All license associations are marked voided and set to inactive, any pending termination records are resolved, and voided records are excluded from future license-cap counts. After the operation completes, no employees retain AI Scribe access — recording, insight generation, and form auto-fill become unavailable immediately.

Business Scenario: An organization with 12 active AI Scribe licenses submits a cancellation request through their Zenoti account representative. Once the cancellation is processed, the AI Scribe - user access screen shows Employees enabled: 0 and all 12 employees display Inactive status. If the subscription is later reinstated, the clean license count ensures new assignments are not blocked by previously voided records.

How to Use:

  1. Before cancellation, navigate to Configuration > AI Scribe and select AI Scribe - user access to review the Employees enabled count and identify all active license holders.
  2. Notify all AI Scribe-enabled providers of the upcoming cancellation at least several business days in advance.
  3. Export any required charting notes, transcripts, or session recordings and confirm data retention terms with your Zenoti account representative.
  4. Contact your Zenoti account representative or submit a cancellation request through your organization's account management channel to initiate the void-all operation.
  5. After the cancellation is processed, return to Configuration > AI Scribe > AI Scribe - user access and confirm Employees enabled shows 0 and all previously active employees show Inactive status.
  6. If any employees still show Active after a full page reload, contact Zenoti support — do not manually disable remaining employees as a workaround.

Default behavior and validations: Void-all revocation is triggered automatically by the backend subscription-cancellation process; there is no in-product button to initiate it. The operation is irreversible from within the product. Individual employee disablement on the AI Scribe - user access screen is a separate action and does not process pending termination records or guarantee the same atomic result. The AI Scribe user management permission is required to view and verify license assignments.

Notes: Providers who are mid-session when revocation occurs lose access immediately and any in-progress recording is interrupted. AI Scribe recording runs on the Zenoti Mobile App (ZMA); if a provider still sees access after cancellation, they should fully close and reopen ZMA. If access persists, contact Zenoti support, as the void-all operation may not have propagated to the device session.

Learn more: AI Scribe License Revocation — Void-All (Cancellation) Path

Partial recovery flag on AI Scribe recordings

Audience/Roles: Service Provider, Administrator

Overview: When AI Scribe captures a session and the audio stream is interrupted — due to a network drop, device interruption, or unexpected app state change — the system now marks the recording as partially recovered and still attempts to generate insights from the audio data that was successfully captured. The recording status is set to Insights Generated and displays a green banner, the same as a fully captured recording, while the partial recovery condition is tracked internally. Because insights may reflect only a portion of the session, providers should review the AI Charting Summary carefully and add any missing information manually before finalizing.

Business Scenario: A provider records a 40-minute facial consultation. At the 28-minute mark the device loses its network connection and the recording ends. AI Scribe marks the recording as partially recovered, generates insights from the first 28 minutes, and displays a green banner. When the provider opens the AI Charting Summary, the initial assessment and treatment discussion are populated, but post-treatment recommendations from the final 12 minutes are absent. The provider adds those recommendations manually before saving.

How to Use:

  1. Open the Zenoti Mobile App (ZMA) on your Android or iOS device.
  2. Navigate to the appointment for which the recording was made.
  3. Tap AI Insights to open the insights panel, then select the Recordings tab.
  4. Locate the recording and confirm the banner color — a green banner indicates insights were generated.
  5. Tap the recording to open the AI Charting Summary.
  6. Review each SOAP+ section carefully and compare against your own recollection of the session.
  7. Manually edit any sections that are incomplete or missing content from the interrupted portion of the session.
  8. Save the charting summary when it accurately reflects the full session.

Default behavior and validations: Partial recovery is a system-level indicator and does not appear as a separate labeled badge in the UI. A partially recovered recording that reaches the Insights Generated state displays a green banner, identical to a fully captured recording. Recording is available on ZMA (Android or iOS, 4 GB RAM minimum) only; Zenoti Web provides view-only access. Users must have AI Scribe access enabled and view access for AI charting notes granted by an administrator via Configuration > AI Scribe. When multiple recordings exist for the same service, insights are merged into a single consolidated charting summary and newer content takes precedence.

Notes: A green banner does not guarantee that the full session was captured. If you know a recording was interrupted, always review the insights against your own session notes before finalizing. A red banner indicates a complete insight generation failure, which is distinct from partial recovery and produces no charting summary. To reduce the likelihood of partial recovery, ensure a stable network connection before recording and avoid closing or backgrounding ZMA during an active session.

Learn more: AI Scribe Partial Recovery Flag on Recordings

AI Scribe Usage Summary Dashboard

Audience/Roles: Administrator, Center Manager

Overview: The AI Scribe Usage Summary Dashboard provides a consolidated view of AI Scribe activity across an organization or individual center. Administrators and center managers can track total recording sessions, appointments with recordings, and AI-filled form counts for any selected month, and review per-service time-saved calculations and per-provider breakdowns. A trend view shows month-over-month changes in recording volume and form-fill adoption, helping managers identify where AI Scribe is delivering value and where provider training may be needed.

Business Scenario: A center manager notices that organization-wide AI-filled form counts are growing but one center is lagging. She applies the center filter, reviews the per-provider breakdown, and sees that several providers at that location are recording sessions but not completing the Fill form using AI step. She uses the time-saved data from the per-service rollup to illustrate the productivity gap in the next team meeting and schedules a refresher training session.

How to Use:

  1. Navigate to Configuration > AI Scribe.
  2. Select the AI Scribe - user access section.
  3. Locate the usage summary panel at the top of the page.
  4. Select the Month and Year you want to report on.
  5. Optionally select a center from the center filter dropdown to scope results to a single location.
  6. Review the headline metrics: Total recordings, Appointments with recordings, and AI-filled forms.
  7. Scroll to the Time saved by service section to see AI-assisted versus non-AI baseline form-fill times per service.
  8. Scroll to the Provider breakdown section to view per-provider recording and form-fill counts (requires AI Scribe user management security access).
  9. Scroll to the Trend section and adjust the Trend months setting to view month-over-month usage changes.

Default behavior and validations: The dashboard defaults to the current month and organization-wide scope. The Employees granted access pill always reflects the organization-wide count of employees with AI Scribe access enabled and does not change when a center filter or search filter is applied. A form is counted as AI-filled only when the Fill form using AI action was used and the AI contributed at least one field value. The date filter supports a single month at a time; multi-month comparisons require the trend view. The per-provider breakdown requires access to the AI Scribe user management security object.

Notes: AI Scribe must be enabled for the organization before any usage data appears in the dashboard. Usage data is captured only for providers with an active AI Scribe license. The time-saved rollup requires both AI-assisted and non-AI baseline form-fill data for the same service; rows may be empty for newly introduced services or services with low appointment volume.

Learn more: AI Scribe Usage Summary Dashboard

Analytics — Amazon S3

Resident tax identity columns in Bi_FactInvoiceItem

Audience/Roles: Administrator

Overview: The Bi_FactInvoiceItem fact table now includes three new columns — ResidenceCountryName, ResidentRegistrationId, and ResidentTinNumber — that carry guest tax identity information at the invoice line-item level. These columns are populated during both full and incremental data refresh cycles, reflecting the guest profile data recorded at the time each invoice line item was created. BI analysts can use them to produce country-level tax summaries, filter by tax identification number, and meet local compliance reporting requirements without additional joins to guest dimension tables.

Business Scenario: A tax compliance analyst needs a monthly report of all invoice line items for guests with a registered TIN in Brazil. They filter Bi_FactInvoiceItem where ResidenceCountryName = 'Brazil' and ResidentTinNumber IS NOT NULL, then join to Bi_DimUser on the guest surrogate key (WID) to include guest name and contact details, producing a dataset ready for submission to the local tax authority.

How to Use:

  1. Navigate to the SchemaFull folder in your S3 bucket at the path //SchemaFull/ and open the schema definition file for Bi_FactInvoiceItem.
  2. Confirm that ResidenceCountryName, ResidentRegistrationId, and ResidentTinNumber appear in the column list; if absent, apply the schema upgrade script from the SchemaUpgrade folder before proceeding.
  3. In your S3 bucket, navigate to the appropriate GroupID folder (GroupID 1 for the initial full load; the latest incremental GroupID for ongoing analysis) and confirm no _processing folder exists before consuming files.
  4. Load the Bi_FactInvoiceItem CSV file into your BI tool or query engine, mapping the three new columns by their positional order as defined in the SchemaFull definition.
  5. Use ResidenceCountryName to filter or group by country of residence, ResidentRegistrationId for registration-based joins or filters, and ResidentTinNumber in tax compliance reports or invoice exports.

Default behavior and validations: All three columns are VARCHAR. They may contain NULL when the corresponding tax identity field was not recorded on the guest profile at the time the invoice line item was created. Values reflect guest profile data at invoice processing time; retroactive profile updates in Zenoti do not modify historical records already delivered to S3. Leading zeros and special characters in registration identifiers and TIN values are preserved exactly as entered.

Notes: Requires an active Analytics — Amazon S3 (S3 Data Share) subscription. Buckets provisioned before this schema change must have the schema upgrade script from the SchemaUpgrade folder applied before querying these columns; querying CSV files generated after the schema change against a pre-change table definition will cause column misalignment errors. If the SchemaUpgrade folder does not contain a relevant script, contact your Zenoti implementation team. The same three columns are available with identical names and data types if your BI tool connects directly to the Redshift layer.

Learn more: Bi_FactInvoiceItem — Resident Tax Identity Columns

Appointment Book

Show employee photo in Appointment Book setting seeded for new organizations

Audience/Roles: Administrator, Business Owner, Center Manager

Overview: When a new organization is created in Zenoti, the Show Employee Photo in Appointment Book setting is now automatically seeded in a disabled state, giving administrators a clear, explicit default to review and configure. Administrators can enable the setting to display provider profile photos in the Appointment Book provider section. The setting operates at the organization level, so enabling it applies to all centers simultaneously. Employee profile photos must be uploaded before enabling the setting; providers without a photo on file will display a placeholder image.

Business Scenario: A newly onboarded organization wants providers' headshots visible in the Appointment Book so front-desk staff can quickly identify who is scheduled. The administrator navigates to Appointment and Queue management, locates the Show Employee Photo in Appointment Book toggle, enables it after confirming all provider photos are uploaded, and saves. All centers immediately begin displaying provider photos in the Appointment Book.

How to Use:

  1. Select the Configurations icon in the left navigation bar.
  2. In the search field, type 'Show employee photo' and press Enter, or navigate directly to Appointment and Queue management > Appointments > Interface.
  3. Locate the Show Employee Photo in Appointment Book setting.
  4. Toggle the setting to the enabled state.
  5. Select Save.
  6. Open the Appointment Book and review the provider section to confirm employee photos are now visible.

Default behavior and validations: Disabled by default for all newly created organizations. The setting applies at the organization level and affects all centers unless a center-level override is in place. Changes take effect immediately upon saving. Providers without an uploaded profile photo will display a placeholder image regardless of the setting state.

Notes: This default seeding applies only to new organizations created after this release; existing organizations are not affected. You must have the Admin role or a security role with Appointment Book settings access to view and modify this setting. Notify center managers before enabling, as the Appointment Book appearance changes for all centers simultaneously. If photos do not appear immediately after saving, users should refresh their browser.

Learn more: Show employee photo in Appointment Book setting seeded for new organizations

Last-segment processing time propagation for slot availability

Audience/Roles: Administrator, Center Manager, Front Desk Operator

Overview: When a segmented appointment includes one or more processing time segments, Zenoti now identifies the final processing segment — the one with the latest end time — and propagates its processing time value to the parent appointment row used in slot availability calculations. This extends the availability window through the end of the processing period, preventing double-booking of providers, rooms, or equipment during that time. The propagation affects only the in-memory availability table used during booking; it does not alter the stored appointment record.

Business Scenario: A guest books a hair-color service that splits into a service segment and a 45-minute color-development processing segment. Because the processing time is now propagated to the parent row, the system correctly blocks the provider and room through the end of the development window, so the front desk cannot accidentally book another guest into that slot before the color treatment is complete.

How to Use:

  1. Navigate to Configurations and search for Services, then open the relevant service record and confirm a non-zero processing time is entered; click Save if you make changes.
  2. In Configurations, search for Booking rules and configurations and open Service rules.
  3. Enable 'Mark room as unavailable for other bookings during the processing time of an ongoing appointment' if the room must remain blocked during processing.
  4. Enable 'Mark equipment as unavailable for other bookings during the processing time of an ongoing appointment' if equipment must remain blocked during processing.
  5. Review 'Enable service providers to be booked for a guest during processing time segments of other guests' and disable it if providers should remain blocked through the processing window.
  6. Click Save to apply the booking rule changes.
  7. Open the Appointment Book and attempt to book a new appointment for the same provider during the processing window of an existing segmented appointment to confirm the slot is blocked or available as expected.

Default behavior and validations: Processing time propagation occurs automatically for segmented appointments that have at least one processing segment row with a non-zero adjusted processing time. If the last segment has an empty or zero processing time value, no propagation occurs and the parent row retains its original processing time. The 'Mark equipment as unavailable for other bookings during the processing time of an ongoing appointment' setting is enabled by default; room and provider blocking settings must be enabled manually. Changes to booking rules apply to new bookings only; existing appointments are not retroactively affected.

Notes: Segmented appointments must be configured for the relevant services before this behavior applies. Processing time must be set at the service level before appointments are created; changes to service processing time do not update existing appointment segments. When multiple processing segments share the same end time, the segment with the highest segment identifier is used as the tiebreaker. Availability rule behavior can differ across booking channels (Booking Wizard, Queue, Kiosk), so test from the same channel used in production. Requires the Configurations access permission.

Learn more: Last-segment processing time propagation for slot availability

Future appointment price sync

Audience/Roles: Center Manager, Administrator

Overview: When a service price, employee rate, or job rate is updated and saved, Zenoti automatically queues a background job that applies the new price to all eligible future appointments whose invoices have not yet been closed. Before saving, users can preview the exact count and details of affected invoice items — including provider, service, center, and appointment times — so they can assess the scope of the change before it takes effect. Each repriced item is recorded in the invoice audit log under the action 'Future appointment price sync', providing a clear compliance and troubleshooting trail. The sync scope can be limited by appointment type (all, recurring only, or non-recurring only) and an optional date-range window configured at the center level.

Business Scenario: A center manager raises the price of a popular facial service by $10. Before saving, she uses the preview to see that 47 future appointment invoice items across two centers will be repriced. She confirms the scope is correct, saves the change, and later verifies the update in the invoice audit log — without manually editing a single appointment.

How to Use:

  1. Navigate to the service, employee rate, or job rate you want to update.
  2. Before saving, open the preview option to review the count of affected future invoice items and the list of appointments (provider, service, center, start and end times).
  3. If the scope is not as expected, ask your administrator to adjust the date-range window or the FutureAppointmentPriceSyncAppointmentType center-level setting before proceeding.
  4. Save the price change; Zenoti automatically queues the sync for background processing.
  5. Allow time for the background job to complete, then open an affected future appointment and confirm the invoice item reflects the updated price.
  6. Navigate to the invoice audit log for any affected appointment and look for entries with the action 'Future appointment price sync' to verify the update was applied.

Default behavior and validations: The sync triggers automatically when a price change is saved; no separate activation step is required. Only future appointments with open (not closed) invoices are eligible. The appointment types included in the sync are controlled by the FutureAppointmentPriceSyncAppointmentType center-level setting (all, recurring only, or non-recurring only). An optional date-range window can restrict which appointments are repriced. When the Enable employee price scaling organization setting is active, employee-scaling or job-scaling factors are applied during the sync, so the final repriced amount may differ from the base service price. Failed items are marked and retried automatically by the background job.

Notes: The date-range window and appointment-type filter must be configured before the price change is saved; they cannot be applied retroactively to a sync already queued. Administrator-level access is required to modify service prices, employee rates, or job rates. If the repriced amount differs from the expected base price, verify whether Enable employee price scaling is active for the organization.

Learn more: Future Appointment Price Sync

Waitlist and turnaway management article restored and expanded

Audience/Roles: Front Desk Operator, Center Manager, Administrator

Overview: The waitlist and turnaway management article was previously retired and replaced by a redirect stub. In this release it has been restored as a full, active workflow reference covering both manual (V1) and first-in-line (V2) waitlist modes. The article now includes step-by-step instructions for creating, viewing, filtering, editing, and deleting waitlist and turnaway entries, as well as guidance on recurring entries, required permissions, and prerequisite settings.

Default behavior and validations: The Turn-Away or Waitlist icon appears in the appointment book right navigation panel only when the Show Create and Manage Turnaways Button setting is enabled at the organization level or overridden to On at the center level. The Add and Edit permissions on the Appointments security object are required to create or update entries. The waitlist panel opens in the Today view by default.

Notes: Centers must be configured for either manual (V1) or first-in-line (V2) waitlist mode before staff can use these workflows; contact an administrator to confirm which mode is active. The icon label displayed in the navigation panel differs by mode: Turn-Away in V1, Waitlist in V2.

Learn more: Manage the waitlist and turnaways

All-services booking frequency validation

Audience/Roles: Front Desk Operator, Center Manager, Administrator

Overview: Zenoti now enforces a minimum number of days between any two service bookings for a guest across all services organization-wide, not only for the specific service being booked. When a proposed appointment falls within the restricted interval, the booking wizard surfaces a conflict showing the guest name, the conflicting appointment date, and the required minimum interval before the booking can be confirmed. Front desk staff can resolve the conflict by selecting a different date or, if their role permits, overriding the restriction. When editing an existing appointment, the system automatically excludes that appointment group from the check to prevent false conflicts.

Business Scenario: A front desk operator begins booking a facial for a guest who already has a massage scheduled three days out. Even though the services differ, the all-services minimum interval of seven days has not been met. The system surfaces the conflict with the conflicting appointment date and the required interval, allowing the operator to reschedule the facial to a compliant date rather than inadvertently booking too soon.

How to Use:

  1. Ensure at least one active service in your organization has a positive all-services minimum interval configured (contact your administrator if changes are needed).
  2. Open the appointment book and select the desired time slot for the guest.
  3. In the booking wizard or New Booking Experience, search for and select the guest, then select the service.
  4. If a frequency conflict appears, review the guest name, conflicting appointment date, and minimum interval displayed.
  5. Select a different date that falls outside the minimum interval window, or override the conflict if your role permits, then confirm the booking.

Default behavior and validations: The all-services frequency check runs automatically during booking when at least one active service in the organization has a positive minimum interval value configured. If no service meets this condition, the check is skipped entirely and the booking proceeds without a conflict prompt. When editing an existing appointment, the system excludes only the appointment group currently being edited from the frequency check; all other appointments for the same guest remain subject to the rule.

Notes: The frequency check evaluates both past appointments within the lookback window and future appointments already on the books, so a scheduled future appointment can trigger a conflict even if the guest has not visited recently. Override access is role-dependent; front desk operators without override permissions should contact their manager. Service-level minimum interval configuration requires administrator access.

Learn more: All-Services Booking Frequency Validation

Configurations

Bulk security role permission update

Audience/Roles: Administrator

Overview: Administrators can now apply a single ADD or REMOVE permission change to multiple security roles across the organization in one atomic operation, rather than editing each role individually. The operation either succeeds for all valid roles or none, preventing partial updates. After the operation completes, any role IDs that were skipped — because they are voided or belong to a different organization — are returned in a result set for review. This reduces the time and risk involved in maintaining consistent permissions across large sets of roles.

Business Scenario: An organization adds a new 'Add Loyalty Points' permission that should be granted to all active front-desk and manager roles simultaneously. Instead of opening each role and toggling the permission one by one, the administrator submits a single bulk ADD operation targeting all relevant role IDs. The system updates every valid role instantly and returns a list of any voided or unrecognized role IDs for follow-up.

How to Use:

  1. Click the Configurations icon in the main navigation.
  2. In the search field, type 'Security roles' and select it from the results.
  3. Review the active security roles and note the IDs of the roles you want to update.
  4. Determine whether you are adding or removing a permission and identify the specific security object and permission pair.
  5. Submit the bulk update by specifying the list of security role IDs, the security object and permission pair, and the operation type (Add or Remove).
  6. After the operation completes, review the returned result set for any invalid role IDs that were not processed.
  7. For each invalid ID, verify whether the role is voided or belongs to a different organization, then restore, replace, or correct the ID and resubmit if needed.

Default behavior and validations: The operation is atomic — all valid roles are updated or none are. Roles that are voided or do not belong to the current organization are excluded from processing and returned as invalid; the operation still completes for all valid roles. ADD does not duplicate an existing permission; REMOVE does not error if the permission is already absent. Changes take effect immediately upon completion. The Security Roles permission is required to access and modify security role settings.

Notes: This procedure operates at the organization level only. If you manage multiple organizations, confirm you are in the correct organization context before submitting. To both add one permission and remove another across the same roles, run two separate operations. Export current security role settings before running bulk updates so you have a reference if you need to reverse changes.

Learn more: Bulk Security Role Permission Update

Appointment reminder deduplication guard

Audience/Roles: Administrator, Front Desk Operator, Center Manager

Overview: Zenoti now automatically prevents duplicate appointment reminders from being queued when a pending reminder of the same type — First Appointment Reminder or Second Appointment Reminder — already exists for an appointment. Before queuing a new reminder, the system checks whether an unsent reminder of the same type is already in the queue; if one is found, the duplicate is skipped and a success result is returned. This protects guests from receiving the same reminder multiple times due to rapid scheduling events, bulk reschedules, or batch re-queue attempts, without requiring any configuration changes.

Business Scenario: A center runs a bulk reschedule for 50 appointments after a provider calls out sick. Without deduplication, each rescheduled appointment could trigger a second reminder queue entry on top of one already pending, causing guests to receive the same reminder twice. With the deduplication guard in place, the system detects the existing pending reminder for each appointment and skips inserting a duplicate, so every guest receives exactly one reminder.

How to Use:

  1. Select the Configurations icon in the main navigation.
  2. Search for 'Appointment notifications' or navigate to Appointments > Notifications and alerts.
  3. Under Guest notifications, confirm that Send first reminder for appointment is enabled for the relevant centers.
  4. Enable Send second reminder for appointment if your organization uses a second reminder.
  5. Review and set the timing option for each reminder (previous day, morning of appointment, or minutes before).
  6. Confirm the delivery channel (Email, Text, or Email and text) under How should the reminder be sent?
  7. Select Save to preserve any changes.

Default behavior and validations: Deduplication is always active and cannot be toggled off. It applies only to First Appointment Reminder and Second Appointment Reminder types. A reminder is considered a duplicate only while it is still pending (not yet sent); once a reminder has been delivered, a new reminder of the same type can be queued normally. Deduplication checks across all channels — email, text, and push notification — regardless of which channel is configured. Reschedule notifications are a separate type and are not affected by reminder deduplication.

Notes: Appointment notifications must be enabled at the organization level under Configurations > Appointments > Notifications and alerts for reminders to be queued at all. Deduplication does not recall or suppress reminders that have already been delivered; cancellations should be processed promptly to clear pending reminders before they send. If a guest did not receive a reminder, verify the guest's contact details, opt-in status, and whether the appointment was booked inside the reminder timing window rather than attributing the absence to deduplication.

Learn more: Appointment reminder deduplication guard

Honor therapist-specific interval behavior by booking source

Audience/Roles: Administrator

Overview: When the Honor therapist specific intervals setting is enabled at the organization level, Zenoti now applies provider-preferred booking slot intervals differently depending on the booking channel. For the online booking channel, the system reads the Honor therapist specific intervals for all services value directly from your organization's app settings, which may be on or off. For all other channels — including Booking Wizard, Queue, and Kiosk — the interval is always treated as enabled when the parent setting is on. This distinction gives administrators precise control over how provider-preferred slots are enforced across different booking surfaces.

Business Scenario: A spa uses both online booking and the Booking Wizard. The organization wants provider-preferred intervals enforced for staff-assisted bookings but needs flexibility for online bookings. With this behavior, the Booking Wizard always applies provider-preferred intervals, while the online booking channel follows whatever value is configured in app settings — allowing the spa to manage the two channels independently.

How to Use:

  1. Select the Configurations icon in the main navigation.
  2. Search for 'Honor therapist specific intervals' and select the matching result.
  3. Confirm the Honor therapist specific intervals toggle is enabled at the organization level.
  4. Contact your Zenoti support representative to verify the Honor therapist specific intervals for all services value in your organization's app settings.
  5. If the app settings value needs to change, request the update through your standard support process.
  6. After any change, make test bookings through the online booking channel and at least one other channel (such as Booking Wizard) to confirm interval behavior is applied as expected.

Default behavior and validations: When Honor therapist specific intervals is enabled: the online booking channel reads the Honor therapist specific intervals for all services value from app settings (no automatic default to enabled); all other booking channels (Booking Wizard, Queue, Kiosk, and others) always treat the interval as enabled. If the app settings value for the online channel has not been explicitly configured, the stored value — which may be off — will be used.

Notes: Enabling the Honor therapist specific intervals toggle alone is not sufficient to apply provider-preferred intervals to online bookings; the Honor therapist specific intervals for all services value in app settings must also be on. Viewing or updating the app settings value may require assistance from Zenoti support. If online booking behavior is inconsistent across centers, check whether center-level app settings overrides are in effect.

Learn more: Honor therapist-specific interval behavior by booking source

Localization support for Clinical Rule Sets and Treatment Charts

Audience/Roles: Administrator

Overview: Administrators can now add translated names and descriptions for Clinical Rule Sets and Treatment Charts in any language configured for their organization. When a translation is available, guests and providers see clinical item names and descriptions in their preferred language instead of the default language. Language display follows a four-level precedence chain: guest preference, center language, organization language, then English. Only the name and description fields are translated; clinical rule logic, chart structure, and service mappings are unaffected.

Business Scenario: A multilingual medspa operates centers in English- and Spanish-speaking markets. After adding Spanish translations for each Clinical Rule Set and Treatment Chart, providers and guests at Spanish-language centers see clinical items labeled in Spanish, reducing confusion during intake and treatment documentation without requiring separate rule sets or charts to be created.

How to Use:

  1. Confirm the target language is active: select the Configurations icon, go to Business details > Manage Languages, and verify the language is enabled.
  2. To translate a Clinical Rule Set: select the Configurations icon, search for 'Clinical Rules', and select Clinical Rules from the results.
  3. Locate the Clinical Rule Set to translate and select Translate next to its name.
  4. In the translation dialog, enter the translated Name and Description for each target language, then select Save.
  5. Repeat for each additional Clinical Rule Set.
  6. To translate a Treatment Chart: select the Configurations icon, search for 'Treatment Charts', and select Treatment Charts from the results.
  7. Locate the Treatment Chart to translate and select Translate next to its name.
  8. Enter the translated Name and Description for each target language, then select Save.
  9. Repeat for each additional Treatment Chart.
  10. Verify translations by setting a test center's language to the translated language and reviewing the clinical workflow.

Default behavior and validations: The Translate button appears only when at least one non-default language is active for the organization. Translations apply to existing Clinical Rule Sets and Treatment Charts only; they do not create new items. If a description translation is left blank, the description falls back to the default language. Each language maintains its own independent translation entry.

Notes: Languages must be configured in Zenoti before translations can be added. Translations for inactive languages will not display to users. The original default-language name and description remain the fallback for any language without a configured translation.

Learn more: Localization support for Clinical Rule Sets and Treatment Charts

Product master creation V2 setting auto-enabled for new organizations

Audience/Roles: Administrator

Overview: When a new organization is created in Zenoti, the product creation V2 setting is automatically seeded as enabled in the Inventory section of organization settings. This means all new products are created using the updated V2 product creation page from day one, with no manual configuration required. Existing organizations are not affected and must contact their Zenoti representative to have the V2 experience enabled.

Business Scenario: A new franchise location is onboarded as a separate Zenoti organization. The administrator can immediately begin building the product catalog using the V2 product creation page without first navigating to Configurations to enable any settings.

How to Use:

  1. Click the Configurations icon in the main navigation.
  2. Type 'Inventory' in the search field to filter settings.
  3. Select Inventory from the results.
  4. Locate the product creation setting in the Inventory section and confirm it is enabled.

Default behavior and validations: The product creation V2 setting is seeded to enabled by default for all newly created organizations. It is applied at the organization level and applies across all centers. Existing organizations do not receive this seed behavior and must request enablement through their Zenoti representative.

Notes: This seed behavior applies only to organizations created after this change was introduced. If the V2 product creation page does not appear after organization setup, allow a few moments for organization-level settings to propagate across centers; if the issue persists, contact Zenoti support.

Learn more: Product master creation V2 setting seeded for new organizations

Bulk import/export support for the Show Therapist Picture in Appointment Book setting

Audience/Roles: Administrator

Overview: Administrators can now include the Show Therapist Picture in the provider section of the Appointment Book setting when performing bulk organization setting imports and exports. The setting maps to the key EmployeePhotoInAppointmentBook in the AppointmentBook section of the import/export file and accepts Yes or No as valid values. This allows multi-center or multi-organization administrators to configure provider photo visibility at scale without manually updating each organization through the UI.

Business Scenario: An administrator managing several franchise organizations needs to enable provider photos in the Appointment Book across all of them at once. Instead of navigating to each organization's settings individually, they export the current settings, set EmployeePhotoInAppointmentBook to Yes in the import file, and upload it — applying the change to all organizations in a single operation.

How to Use:

  1. Select the Configurations icon in Zenoti.
  2. Navigate to Configurations > Import/export.
  3. Export organization settings and open the exported file.
  4. Locate the AppointmentBook section and find the row for EmployeePhotoInAppointmentBook.
  5. Set the value to Yes (display provider photo) or No (hide provider photo).
  6. Save the import file.
  7. Return to Configurations > Import/export and upload the updated file.
  8. Confirm the import and review the import results log to verify the row was applied successfully.

Default behavior and validations: The setting operates at the organization scope and applies across all centers unless a center-level override exists. Only Yes or No are valid values; any other value (including yes, YES, 1, or 0) will cause the import row to fail validation. The mapping key EmployeePhotoInAppointmentBook is case-sensitive.

Notes: Requires the Import/Export permission. Export and save a backup of current organization settings before running a bulk import that includes this setting so you can restore the previous value if needed. After a successful import, affected staff may need to refresh their browser or log out and back in for the change to appear.

Learn more: Show Therapist Picture in Appointment Book — Import/Export Mapping

Smart Targets setting enabled by default for new organizations

Audience/Roles: Administrator

Overview: When a new organization is created in Zenoti, the Smart Targets setting is now automatically seeded to enabled at the organization scope. This means Smart Targets is active from the moment the organization is set up, with no manual activation required. Administrators can verify the setting in Configurations and disable it if their business does not require Smart Targets functionality.

Business Scenario: An administrator onboarding a newly created Zenoti organization no longer needs to locate and manually enable Smart Targets as part of the setup checklist — the feature is ready to use immediately upon organization creation.

How to Use:

  1. Click the Configurations icon in the main navigation.
  2. In the search field, type 'Targets' and select Targets from the results.
  3. Review the Smart Targets toggle to confirm it is set to Enable.
  4. If Smart Targets is not needed, set the toggle to Disable and click Save.

Default behavior and validations: Smart Targets is seeded as enabled by default for all newly created organizations. This seeding occurs once at organization creation and does not affect existing organizations. Disabling the setting removes Smart Targets functionality for all centers under the organization.

Notes: This behavior applies only to newly instantiated organizations; existing organizations are not affected. The Configurations edit permission is required to view or modify this setting. If the Smart Targets toggle is not visible, confirm that your role has the Configurations view permission or contact your Zenoti representative.

Learn more: Smart Targets setting seeded for new organizations

Employees

Employee module overview documentation updated

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: The Employee module overview article has been updated to reflect the current scope of workforce management capabilities in Zenoti. The article now documents the full employee lifecycle—from profile creation and job designation through scheduling, attendance, commission, payroll, leave, and performance monitoring—along with prerequisites required before configuring the module for a center. This gives administrators a single reference point for understanding how the module is structured and how its components relate to one another.

Business Scenario: An administrator setting up the Employee module for a new center can consult the updated overview to confirm licensing requirements, verify that job designations and security profiles are in place, and identify which setup articles to follow before creating employee records.

Notes: The Employee Management license (Core Platform) must be active to use the base employee features. Add-on licenses—PTO, Payroll/HC Payroll, and ePrescription—are required for their respective capabilities. Multi-center and deputation features depend on having more than one center configured in the organization.

Learn more: Employee overview

Future appointment price sync on employee service assignment

Audience/Roles: Administrator, Center Manager

Overview: When an administrator or center manager saves an employee service assignment with a new or changed scaling factor, Zenoti now automatically evaluates and updates the prices of future appointments at the employee's home center and any active deputation centers. This eliminates the need to manually reconcile appointment pricing after scaling factor changes. The sync is controlled by two settings — one at the organization level and one at each center — giving businesses precise control over where the evaluation runs.

Business Scenario: A center manager increases the percentage override scaling factor for a senior therapist's deep-tissue massage service. On saving, Zenoti automatically recalculates the price on all future appointments booked for that therapist at the home center and at the two deputation centers where she is currently active, ensuring guests are charged the correct amount without any manual intervention.

How to Use:

  1. Confirm the 'Show Future Appointment Price Sync' setting is enabled at the organization level.
  2. Confirm the 'Enable Future Appointment Price Sync' setting is enabled for each center where price sync should apply, including any deputation centers.
  3. Navigate to Employee > Employees > Employees and open the employee profile.
  4. Select the Services tab.
  5. To add a new service, click Add Service and select the service by Category, Sub Category, or Service name; to update an existing service, locate it in the list.
  6. Set the scaling factor type to Percentage override or Absolute amount and enter a non-zero value.
  7. Click Save — Zenoti automatically evaluates and updates future appointment prices for the affected service across the employee's home center and active deputation centers.

Default behavior and validations: Price sync is off by default and requires both the organization-level 'Show Future Appointment Price Sync' setting and the center-level 'Enable Future Appointment Price Sync' setting to be active. Sync is triggered only when a scaling factor changes on an existing service association, or when a new service association is saved with a non-zero scaling factor; saving without modifying the scaling factor does not trigger sync. A new association saved with a zero scaling factor does not trigger sync. Price scaling applies to services and add-ons only; packages are excluded. The center-level setting is not inherited from the organization and must be enabled independently for each center, including deputation centers.

Notes: Deputation center scope is evaluated at the time of the future appointment, not at the time the service assignment is saved; centers where the employee is deputized after the save are also in scope if their center-level setting is enabled. The Manage Employees permission is required to update service assignments and trigger price sync.

Learn more: Future Appointment Price Sync on Employee Service Assignment

Employee blockout management on the Employee Schedule page

Audience/Roles: Center Manager, Administrator

Overview: Employee blockout management on the Employee Schedule page now covers additional blockout scenarios. Center managers and administrators can create, edit, and delete blockout entries for any employee directly from that page.

Learn more: Employee blockout management on the Employee Schedule page

Payroll Earnings Summary and Drilldown

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: Payroll administrators can now review a consolidated earnings summary for all employees in a pay period — covering hours, base pay, commission, overtime, tips, deductions, and PTO — and then drill into per-employee detail to see exactly how each figure was calculated. The drilldown exposes the hourly rate source, overtime granularity (daily, weekly, or pay-period), overtime premium math, and the result of the higher-of comparison between straight-time hourly pay and commission. This gives payroll teams a clear audit trail for every compensation decision without leaving Zenoti.

Business Scenario: A center manager is reconciling payroll for a two-week period and notices that one employee's total pay is lower than expected. She opens the drilldown for that employee, sees that the Winner column shows 'commissions' for week one and 'hourly' for week two, and can immediately verify the OT multiplier and straight-time pay figures used in each week's higher-of comparison — resolving the discrepancy without a manual spreadsheet.

How to Use:

  1. Confirm that at least one pay period is configured: navigate to Configuration > Employee > Payroll and Commissions > Pay Period.
  2. Confirm that payroll has been generated for the period you want to review.
  3. Navigate to Employee > Payroll.
  4. Select the center from the center selector.
  5. Set the Start Date and End Date to match the target pay period.
  6. Optionally select a specific employee from the employee filter to narrow results.
  7. Review the summary grid columns: Employee, Total Hours, Pay, Commission, Overtime, Tips, Deductions, and PTO.
  8. Select an employee row to open the drilldown panel.
  9. In the drilldown, review columns including Hourly Rate, OT Hours, OT Multiplier, OT Premium, Straight-Time Pay, Rate Type, Granularity, Considered Pay, and Winner.
  10. Use the Rate Type column to confirm whether the hourly rate came from a work-task assignment ('ahr') or the employee profile ('profile').
  11. Use the Granularity and Winner columns to verify how the higher-of comparison was resolved for each evaluation period.

Default behavior and validations: The summary always reflects the most recent payroll batch for the selected pay period; earlier batches are not displayed. Results are paginated server-side; configure Page and Page Size to navigate large employee lists. The higher-of comparison between hourly pay and commission is only performed when the center's payroll controls are configured for that comparison mode — if not configured, the Winner column may not be applicable. The Employee Payroll permission is required to access both views; the View Grooming Points permission is additionally required to see grooming points columns.

Notes: Pay periods must be configured and payroll must be generated before any data appears. The payroll lock setting in Configuration > Employee > Payroll and Commissions > Payroll Controls determines how far back recalculations and edits are permitted; locked periods block attendance changes, tip reassignments, and commission recalculations. For employees without prior payroll history in Zenoti, the look-back period setting (1, 2, or 3 pay periods) is used to determine whether commission pay is likely to exceed non-commission pay.

Learn more: Payroll Earnings Summary and Drilldown

Remove a level assignment from an employee

Audience/Roles: Administrator, Center Manager

Overview: Administrators and center managers can now clear an employee's level assignment without replacing it with another level. Setting the Level field to no selection voids the employee's active level record, removing them from tier-based booking flows until a new level is assigned. Previously, there was no documented way to unassign a level without substituting a different one.

Business Scenario: A senior stylist goes on extended leave and the center manager wants to remove her from the 'Senior' booking tier so guests cannot book her by level during her absence. The manager opens her profile, clears the Level field, and saves — she no longer appears in tier-based booking until the level is reassigned on her return.

How to Use:

  1. Navigate to Employee > Employees > Employees.
  2. Search for and open the employee's profile.
  3. Select the Employee Role tab.
  4. In the job association section, locate the Level field.
  5. Clear the current level selection so no level is assigned.
  6. Select Save.

Default behavior and validations: After the Level field is cleared and saved, the employee has no active level record and will not appear in tier-based booking flows. A new level must be explicitly assigned to restore tier-based visibility.

Notes: The Employee Levels feature toggle must be enabled at the organization level before the Level field is available in employee profiles.

Learn more: Employee levels

Wallet balance transfer request for a deceased employee

Audience/Roles: Administrator, Center Manager

Overview: Authorized business representatives can now request that a deceased employee's Zenoti wallet balance be disbursed to a named beneficiary. The process is initiated by contacting Zenoti Support, which coordinates with its banking partner to verify documentation and authorize disbursement. Funds are released exclusively by cashier's check mailed to the beneficiary's address — no electronic transfer option is available. This feature is available only for employees at centers whose country is set to the United States.

Business Scenario: An HR administrator learns that an employee who held a Zenoti wallet has passed away. The administrator emails Zenoti Support with the employee's name and the beneficiary's mailing address, submits the death certificate, and waits for the banking partner to confirm any additional estate documentation requirements before a cashier's check is issued and mailed to the beneficiary.

How to Use:

  1. Email support@zenoti.com to report the deceased employee and request a wallet balance transfer, identifying yourself as the authorized business representative.
  2. Provide the employee's full name, the beneficiary's complete mailing address, and an official copy of the death certificate.
  3. Wait for Zenoti Support to acknowledge the request (same business day) and open a case with the banking partner.
  4. Supply any additional estate documentation (such as a small estate affidavit, letters testamentary, or a court order) if requested by the banking partner after case review.
  5. Await notification from Zenoti Support that the cashier's check has been issued; confirm receipt with the beneficiary within the 2–5 business day delivery window.

Default behavior and validations: Disbursement is made only by cashier's check; there is no electronic transfer option. The wallet balance is disclosed only after the banking partner has verified authorization. Estate documentation requirements vary by state and are confirmed by the banking partner after case review — they do not need to be determined before contacting Support. Feature is limited to employees at centers whose country is set to the United States.

Notes: Zenoti communicates exclusively with the authorized business representative throughout the process; family members should be directed to the organization's HR team or legal counsel. Expected timeline: same-day Support acknowledgement, 2–5 business days for banking partner review, 1–2 business days for check issuance after final approval, and 2–5 business days for delivery after issuance. Timelines may vary based on documentation completeness and state requirements.

Learn more: Request a wallet balance transfer for a deceased employee

ezConnect

Saved response org-level promotion

Audience/Roles: Administrator

Overview: Organization administrators can now promote center-level saved responses in ezConnect to the organization level, making them instantly available to agents at every center without requiring each center to recreate the same content locally. Multiple responses can be promoted in a single operation, and Zenoti automatically records the promoting user and the UTC timestamp for audit purposes. Organization-level responses appear alongside each center's own center-level responses in the saved responses list.

Business Scenario: A spa chain wants all front-desk agents across 20 locations to use the same appointment-confirmation and cancellation-policy responses. Instead of manually creating those responses at each center, the organization administrator promotes the finalized versions once, and they become available to every center immediately.

How to Use:

  1. Open ezConnect and navigate to the saved responses management area.
  2. Review the list of center-level saved responses and identify the responses to promote.
  3. Select one or more saved responses you want to make available organization-wide.
  4. Choose the option to promote the selected responses to organization level.
  5. Review the content of each selected response, then confirm the promotion when prompted.
  6. Verify that the promoted responses appear in the organization-level saved responses list and are visible to agents at other centers.

Default behavior and validations: At least one center-level saved response must exist before promotion is possible. Promoted responses are immediately visible to all centers upon confirmation; there is no staged or scheduled rollout. Both organization-level and center-level responses appear together in the saved responses list for any center. If a response with the same name exists at both levels, agents will see duplicate entries.

Notes: Requires the Edit Guest, Edit Guest Email, and Edit Guest Mobile permissions on the administrator's security role (Organization → Security → Security Roles → [your role] → Guests). If the promotion option is not visible, confirm that these permissions are assigned. If promoted responses do not appear at other centers after a successful operation, contact your Zenoti administrator to confirm that the organization-level saved responses feature is active for your organization. Before promoting, verify that any macros used in a response (such as guest name or appointment details) will resolve correctly for guests across all centers, not only the originating center.

Saved responses documentation updated with table-format macro reference and worked example

Audience/Roles: Administrator, Front Desk Operator

Overview: The Saved Responses and Macros help article has been restructured to present all available macros in categorized reference tables (Center/Location, Guest, Appointment) instead of inline lists, making it faster to locate the correct macro syntax. A worked example showing a complete appointment-reminder template has been added to illustrate how macros resolve at send time. The Title field behavior is now explicitly documented: leading and trailing whitespace is removed automatically when a saved response is saved.

Business Scenario: An ezConnect administrator setting up a new appointment-reminder template can now consult the macro reference tables to confirm the exact bracket syntax for each dynamic field — such as [ServiceName] or [StartTime] — without trial and error, and use the worked example as a starting point for their own template.

Default behavior and validations: Leading and trailing whitespace entered in the Title field is stripped automatically on save. Macros use bracket syntax ([MacroName]) and are resolved against live guest, appointment, and center data at the time the message is sent.

Notes: The Connect Access Enable permission and Create/Edit Responses permission are required to create or edit saved responses. Saved responses can be scoped to a single center or to the entire organization depending on the user's permissions.

Learn more: Saved responses and macros

Fitness

Undo no-show for class registrations

Audience/Roles: Front Desk Operator, Center Manager, Administrator

Overview: Front desk staff and managers can now reverse a no-show mark on a student's class registration directly from the session roster. Selecting Undo No-Show restores the registration status to Registered, reinstates voided invoice line items, and restores the class price on the associated invoice — all in a single atomic operation. This corrects accidental no-show marks before the invoice is closed, without requiring manual invoice edits or administrator intervention.

Business Scenario: A student arrives late to a Yoga Beginner session that ended at 7:00 PM and was incorrectly marked as a no-show at check-out. At 7:08 PM, the front desk opens the session roster, locates the student's No-Show row, and selects Undo No-Show. The system restores the registration to Registered, un-voids the invoice line item, and reinstates the class price — all before the invoice is closed or any fee is collected.

How to Use:

  1. Click the Fitness icon in the main navigation and select Classes.
  2. Locate the class, open the Schedule tab, and click the session to open its roster.
  3. Find the student whose registration shows a status of No-Show.
  4. In the action menu for that student's row, select Undo No-Show.
  5. Confirm the action when prompted.
  6. Refresh the roster to verify the student's status now shows Registered and invoice items are reinstated.

Default behavior and validations: The Undo No-Show action is available only when all of the following conditions are met: the registration status is No-Show; the action is performed within 15 minutes of the session end time; the associated invoice is open; and the invoice has no recorded payments. If any condition is not met, the action is blocked or does not appear. The operation is atomic — if any step fails, all changes are rolled back and no updates are saved. Invoice item price is restored only when the current sale price differs from the class price; tax handling respects the organization's tax inclusion setting.

Notes: Users must have permission to manage class registrations, including the ability to mark and undo no-show status, configured under Security Roles > Classes. The 15-minute window starts at the session end time, not at the time the no-show was marked. If the invoice is already closed or a payment has been recorded, the action is blocked; coordinate with the billing team for an alternative correction path.

Learn more: Undo No-Show for Class Registrations

Weekly calendar view for class scheduling

Audience/Roles: Front Desk Operator, Center Manager, Administrator

Overview: The weekly calendar view provides a visual, seven-day grid of all scheduled class sessions, giving front-desk staff and managers a clear picture of the week's schedule at a glance. Users can navigate between weeks using arrow buttons, a date-field widget, or a 'This Week' shortcut, and can filter visible sessions by instructor, class, room, or utilization tier—with multi-select support and live count badges on each active filter. A stats bar at the top of the calendar summarizes total classes, total students, overall utilization, top class by attendance, and top instructor by sessions, updating automatically as filters change. New sessions can be created directly from the calendar using the Schedule Class button, which opens a slide-in panel on the right side of the screen.

Business Scenario: A center manager wants to confirm that a specific instructor has no scheduling conflicts before adding a new session on Thursday afternoon. They open the weekly calendar view, apply the Instructor filter to show only that instructor's sessions, visually scan Thursday's column for open time slots, and then click Schedule Class to create the new session—all without leaving the calendar.

How to Use:

  1. At the center level, click the Fitness icon in the left navigation.
  2. Select Classes, then select Calendar View.
  3. Use the Previous Week, Next Week, or This Week buttons—or the date-field widget—to navigate to the desired week.
  4. Click a filter button (Instructor, Class, Room, or Utilization) and select one or more options to narrow the sessions displayed; a count badge appears on each active filter.
  5. Review the stats bar at the top of the page for a summary of the filtered week's activity.
  6. To create a session, click Schedule Class, complete the required fields in the slide-in panel, and click Save.

Default behavior and validations: The calendar opens on the current week by default. Column width defaults to fill-width mode (columns expand to fill the viewport); using the + or − zoom buttons sets a fixed width and disables fill-width mode until the page is reloaded. The vertical time scale defaults to 95 px per hour (range: 20–195 px, step 10 px); column width fixed range is 60–320 px in 20 px steps. Compact view is off by default; when enabled, only one session tile can be expanded at a time. The stats bar reflects only the sessions visible under the current filter state. The Schedule Class button and schedule management actions (create, edit, cancel, delete) require the Schedule permission under Classes in the user's security role.

Notes: The fitness module must be enabled for the center before the calendar view is accessible. At least one class, and configured rooms and instructors, must exist at the center before sessions can be scheduled. Users who do not have the Schedule permission under Classes will not see the Schedule Class button and cannot perform schedule management actions. The Room filter includes an Unassigned option to surface sessions that have not yet been assigned a room.

Learn more: Weekly Calendar View for Class Scheduling

Audience/Roles: Center Manager, Front Desk Operator, Administrator

Overview: The in-article tip links pointing to membership freeze/unfreeze guidance and membership class benefits configuration have been updated to reflect the current documentation structure. The links now resolve to the correct pages, ensuring staff can navigate directly to the relevant membership topics without encountering broken or outdated references.

Learn more: Manage class sessions and schedules

Copy Schedule popup for class schedules

Audience/Roles: Administrator, Center Manager

Overview: The Copy Schedule popup lets you duplicate an existing class schedule to a new date range without rebuilding it from scratch. You open it from the schedule edit slider, specify a start and end date, and confirm to create the copied schedule. The start date defaults to the day after the source schedule ends, and the end date defaults to the same value as the start date, making back-to-back recurrences straightforward. The copied schedule inherits all sessions, instructor assignments, and room assignments from the source.

Business Scenario: A yoga class runs a weekly schedule that ends on Friday, June 6. Rather than recreating the schedule manually, the center manager opens the edit slider for that schedule, clicks Copy Schedule, adjusts the end date to June 13, and confirms. The full week's schedule is created instantly with all instructor and room assignments carried over.

How to Use:

  1. At the center level, click the Fitness icon and select Classes.
  2. Locate and open the class whose schedule you want to copy.
  3. Select the Schedule tab to view the List of Schedules.
  4. Find the schedule you want to copy and click its edit (pencil) icon to open the schedule edit slider.
  5. In the schedule edit slider, click the Copy Schedule button (the Copy icon) to open the Copy Schedule popup.
  6. Review or update the Start Date (defaults to the day after the source schedule's end date).
  7. Set the End Date to the last date you want the copied schedule to cover (must be on or after the Start Date).
  8. Click Copy Schedule to confirm and create the copied schedule.

Default behavior and validations: Start Date defaults to the day after the source schedule's end date. End Date defaults to the same value as the Start Date, producing a single-day copy unless changed. End Date must be on or after Start Date; setting End Date earlier than Start Date triggers an inline validation error and blocks confirmation. The copied schedule inherits the source schedule's session, instructor, and room configuration. After copying, the system displays a conflict indicator on any session where an instructor or room is already assigned to an overlapping time slot.

Notes: The user role must have the Classes > Schedule permission enabled under Security Roles to access the Copy Schedule button. If the button is not visible in the schedule edit slider, contact your administrator to verify permissions. After copying, review the newly created sessions in the List of Schedules to identify and resolve any instructor or room conflicts.

Learn more: Copy Schedule Popup

Schedule Create/Edit Slider Panel for class sessions

Audience/Roles: Administrator, Center Manager

Overview: A new right-side slider panel in the weekly calendar view lets fitness administrators and center managers create or edit class sessions without leaving the calendar. The panel supports single-session and recurring session configuration from one interface, including instructor assignment with pay rates, room selection, capacity, virtual links, and catalog visibility. Recurring schedules can repeat daily, weekly, or monthly, ending on a specific date or after up to 30 occurrences.

Business Scenario: A center manager needs to schedule a yoga class every Monday and Wednesday for eight weeks. Instead of creating 16 individual sessions manually, they open the slider panel, configure the class details once, set the recurrence to Weekly on Mon and Wed, and set Ends after 16 occurrences — generating the full series in a single save.

How to Use:

  1. At the center level, click the Fitness icon in the left navigation.
  2. Select Classes, open the target class, and select the Schedule tab.
  3. In the weekly calendar view, click + Schedule to open the panel in create mode, or click an existing session block to open it in edit mode.
  4. Select the Class, Date, Start time, and End time.
  5. Assign one or more Instructors and select a pay rate for each.
  6. Optionally select a Room and set the Capacity.
  7. Toggle Free Session or Show in Catalog as needed, and enter an HTML Description if required.
  8. If virtual classes are enabled, enter the instructor and student Virtual Link values.
  9. To create a recurring series, set the Repeat field to Daily, Weekly, or Monthly; configure the Every interval and, for Weekly, select the applicable day circles; then set Ends on with an end date or Ends after with a number of occurrences (maximum 30).
  10. Click Save (create mode) or Update Changes (edit mode) to finalize the session.

Default behavior and validations: The Repeat field defaults to Does not repeat, creating a single session. The Ends after Occurrences field does not default to 1 when cleared — it submits as empty and triggers a validation error if left blank. Show in Catalog and Free Session toggles are off by default. Virtual link fields are visible only when the Enable Virtual Class organization setting is active. The Copy Schedule icon appears only in edit mode.

Notes: The Fitness module must be enabled at the center level before schedules can be created. The class definition must exist before it can be scheduled. Schedule creation, editing, cancellation, and deletion require schedule management permissions under Classes > Schedule in Security Roles. Rooms must be configured at the center level before they can be assigned. Instructor pay rates must be set up before they are available for selection during scheduling.

Learn more: Schedule Create/Edit Slider Panel

Session L3M (Last-Three-Months) utilization metric for recurring classes

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: Zenoti now automatically computes a rolling 90-day utilization percentage for recurring class sessions, showing how full those sessions have been on average over the past three months. The metric is calculated as total attended registrations divided by total capacity across all qualifying historical occurrences in the window. Fitness managers and administrators can use this data to identify consistently under-attended sessions, adjust capacity settings, and make informed scheduling decisions without manual tracking.

Business Scenario: A fitness manager reviewing the weekly schedule notices that the Tuesday 7 AM cycling class shows an L3M utilization of 22%. Recognizing this as consistently low attendance relative to capacity, the manager decides to reduce the session's capacity or merge it with the Wednesday morning class rather than continuing to hold unused spots.

Default behavior and validations: The metric is read-only and computed automatically — no configuration is required to activate it. It applies only to recurring class sessions; single-session classes do not generate L3M data. The 90-day window ends at the start of the current week (not today's date), so sessions from the current week are excluded from the historical sample. Daily and weekly recurrence types are bucketed by day of week; monthly recurrence types pool all historical occurrences regardless of day. A blank value indicates no qualifying historical data in the window, not zero attendance. Cancelled sessions are excluded from the sample entirely. Only registrations with a status of Signed In or Closed (and not marked as no-show or cancelled) are counted as attended. All date calculations use UTC.

Notes: At least one session occurrence must have run to completion within the 90-day window for a utilization value to appear. If all occurrences within the window were cancelled, or if the session was created fewer than 90 days ago without sufficient history, the metric returns no value. For monthly sessions, fewer than one prior occurrence in the window also results in a blank value. Seasonal demand patterns (such as a January attendance spike) will be reflected in L3M values computed during that period and should be considered when interpreting results.

Learn more: Weekly Calendar View for Class Scheduling

Forms

Form ID lookup helpers for guest HTML data and tag appointment forms

Audience/Roles: Administrator, Center Manager, Front Desk Operator

Overview: Zenoti now provides two lookup helpers that retrieve the form ID of the most recent non-voided form record for a given context: one for guest HTML forms (scoped to a guest and organization) and one for tag forms (scoped to an appointment, tag, and user combination). These helpers allow administrators and integration configurators to quickly identify the correct form record to open, review, or act on without manually searching through multiple records. Each helper returns a single form ID — the most recent non-voided record — which can then be used directly in the form review workflow.

Business Scenario: A front desk manager needs to locate the correct form record before a provider review session. Guest Maria Chen has submitted multiple guest HTML forms over the past year. The manager requests a guest HTML form ID lookup for Maria's guest record and receives the form ID for her most recent non-voided submission, which is then opened directly in the form review interface to assign a reviewer. For tag forms, the manager performs a separate lookup using the appointment ID, tag name, and provider to retrieve the correct post-treatment tag form record.

How to Use:

  1. Confirm that the guest has at least one submitted or in-progress guest HTML form record, or that the appointment has an associated tag with a tag form record.
  2. For a guest HTML form lookup: identify the guest's record in Zenoti and note the guest ID and organization.
  3. For a tag appointment form lookup: identify the appointment ID, the tag associated with the appointment, and the user (provider) linked to the form record.
  4. Contact your Zenoti administrator or use the supported form management interface to request the appropriate form ID lookup.
  5. Use the returned form ID to navigate to, review, or act on the specific form record in the form review interface.

Default behavior and validations: Each lookup returns only one form ID — the most recent non-voided record for the given context. Voided form records are excluded from all lookup results. Tag form lookups are scoped to a specific appointment, tag, and user combination; if an appointment has multiple tags, a separate lookup is required for each tag. The number of tag form slots available per appointment is controlled by an organization-level setting.

Notes: Requires the Custom Fields and Guest Custom Data permissions. The guest record must exist in the organization before a guest HTML form lookup is attempted. The appointment must be associated with a tag before a tag form lookup is attempted. To review form records older than the most recent non-voided record, use the form review interface or the forms report.

Learn more: Form ID Lookup Helpers for Guest HTML Data and Tag Appointments

V2-to-V3 form conversion and adoption

Audience/Roles: Administrator

Overview: Administrators can now convert legacy (V2) HTML forms to the current form builder (V3) format and adopt the converted versions as active forms. A background conversion pipeline processes legacy forms in batches of up to 25, tracks each attempt as Completed or Failed (with up to three automatic retries), and stores results in a conversion cache for review. When an administrator adopts a converted form, all active form–service and tag form associations are migrated from the legacy form to the new form builder version in a single transaction, so no associations need to be manually reassigned.

Business Scenario: A spa has 30 legacy intake forms tied to dozens of services. Instead of rebuilding each form from scratch in the form builder, the administrator monitors the conversion cache, reviews the component count and field layout of each completed conversion, and adopts the forms one by one. After adoption, every service that previously referenced the legacy form automatically points to the new form builder version.

How to Use:

  1. Confirm the form builder is enabled for your organization and that you have the Custom Fields permission.
  2. Navigate to Admin > Settings > Forms.
  3. Review the converted forms list and note which forms show a Completed status.
  4. Open each completed form to verify field order, labels, component count, and conditional logic against the original legacy form.
  5. Select a completed form and choose the option to adopt it.
  6. Read the confirmation prompt, which summarizes the association migration and the voiding of the legacy conversion record, then confirm.
  7. After adoption, navigate to the relevant service records to verify the new form builder version appears in the associated forms list.
  8. For any forms showing a Failed status after three attempts, contact Zenoti support to reset the retry count.

Default behavior and validations: The conversion pipeline runs automatically in the background; no manual trigger is required. Batches contain up to 25 forms. Forms are retried automatically up to three times on failure; after three failed attempts they are excluded from automatic processing. Only active associations are migrated — previously voided associations are not carried over. Adoption executes as a single transaction and rolls back entirely if any part of the migration fails, leaving the legacy form and its associations unchanged. Eligible form types are: Service, Guest, Membership, Tag, and related HTML-based types. Forms already built in the form builder are not eligible for conversion.

Notes: The form builder must be enabled for your organization before conversion or adoption is available. Verify that legacy forms are not currently being filled in active appointments before adopting, as this can cause adoption to fail. Adoption cannot be automatically reversed once completed. Complex legacy layouts with custom HTML blocks or non-standard field types may not convert fully; review the component count and open the converted form in the form builder to add any missing fields before adopting. Performing adoptions during low-traffic periods reduces the risk of conflicts with forms actively in use.

Learn more: V2-to-V3 form conversion and adoption

HyperConnect

Employee-level Voice DND and ring volume controls in HyperConnect

Audience/Roles: Front Desk Operator, Service Provider, Employee, Administrator

Overview: HyperConnect now lets each employee independently configure two personal voice notification preferences: Voice Do Not Disturb (DND) and ringer volume. When Voice DND is enabled, the employee stops receiving inbound calls without logging out, and calls are automatically routed to other available agents. The ringer volume slider adjusts how loud incoming calls ring within the HyperConnect soft phone interface, independently of the device's system volume. Both settings are stored per employee and take effect immediately after saving.

Business Scenario: A front desk operator needs focused time to complete end-of-day reports without missing their shift. They enable Voice DND so inbound calls route to a colleague, confirm the DND banner appears in HyperConnect, and lower the ringer volume for the rest of the day — all without logging out or affecting anyone else's settings.

How to Use:

  1. Open HyperConnect by selecting Chat in the Zenoti navigation.
  2. Click the Settings icon in the app header.
  3. Select the User tab and locate the Notifications section.
  4. To enable Voice DND, toggle Do not disturb on; confirm the banner 'Your status is set to Do Not Disturb' appears at the top of the interface.
  5. To adjust ringer volume, drag the Ringer volume slider to the preferred level (default is 100).
  6. Click Save; both settings take effect immediately with no page refresh required.

Default behavior and validations: Voice DND is off by default; employees receive all inbound calls unless they enable the toggle. Ringer volume defaults to 100. Settings are per-employee and persist across sessions. The ringer volume slider controls the HyperConnect soft phone only — it does not affect device system volume or a physical phone device's ring volume. The Connect Access Enable permission is required to access these settings.

Notes: The organization must have HyperConnect provisioned with voice calls enabled. Each employee configures their own preferences independently; these are not center-level settings. If the DND banner does not appear after saving, clear the browser cache and reload HyperConnect, or ask an administrator to verify the Connect Access Enable permission is assigned to the employee's security role.

Learn more: Employee Notification Settings — Voice DND and Ring Volume

Audience/Roles: Business Owner, Center Manager, Administrator, Front Desk Operator

Overview: Three new center-level configuration options are now available in HyperConnect Settings. Centers can opt out of organization-wide conversation visibility using the Disable Cross-Center Communication toggle, send guest intake or service form links directly within a conversation using the Send Form Link feature, and send secure payment links to guests using the Send Credit Card Link feature. Each link feature requires a customizable message template that is stored per center and delivered alongside the link.

Business Scenario: A front desk operator is chatting with a guest who booked a new-client appointment. Without leaving the conversation, the operator sends a pre-appointment intake form link and, when the guest is ready to add a card on file, follows up with a secure credit card link — all using message templates configured by the center manager in advance.

How to Use:

  1. Ensure your security role includes the Connect Access Enable permission (Organization > Security > Security Roles > [your role] > Zenoti HyperConnect > Connect Access Enable).
  2. Navigate to Chat in the main navigation to open HyperConnect.
  3. Click the Settings icon in the HyperConnect interface.
  4. Select the Configuration tab.
  5. To opt out of organization-wide conversation sharing: locate the Cross-Center Communication section and toggle Disable cross-center communication on, then click Save.
  6. To enable form link sending: locate the Send Form Link section, toggle Send Form Link on, enter the required message text in the Form link message text field, then click Save.
  7. To enable credit card link sending: locate the Send Credit Card Link section, toggle Send Credit Card Link on, enter the required message text in the Credit card link message text field, then click Save.

Default behavior and validations: Cross-center communication sharing is disabled by default at the center level. The Send Form Link and Send Credit Card Link features are off by default. Both link features require a non-empty message template text field; saving with an empty field will prevent the setting from being applied. The center-level cross-center disable flag only takes effect when the organization-level communications sharing setting is active.

Notes: HyperConnect must be enabled for your organization before these settings are accessible. The organization-level events sharing setting and the center-level communications sharing setting have opposite defaults — confirm your organization's configuration with your administrator before changing the cross-center communication toggle. If cross-center communication sharing is disabled for a center, staff at other centers will no longer see that center's conversations.

Learn more: HyperConnect Settings — Cross-Center Communication, Form Link, and Credit Card Link

Call volume heatmap with heatmap type filter

Audience/Roles: Center Manager, Administrator

Overview: The HyperConnect Analytics dashboard now includes a heatmap type filter that lets you switch between Call Duration and Call Volume display modes. Call Volume mode visualizes the number of calls per hour across a full 24-hour window (00:00–23:00) for each day of the week, with color intensity indicating relative call count. This gives managers a clear view of peak call traffic periods to compare against staffing schedules and identify coverage gaps.

Business Scenario: A center manager notices that front desk calls go unanswered on Monday mornings. By switching the heatmap to Call Volume mode and filtering the Analytics dashboard to the past month, they can confirm that Monday 9 AM–11 AM consistently shows the darkest cells, confirming high call volume, and use that data to justify adding a second front desk operator during those hours.

How to Use:

  1. Open HyperConnect from Chat in the Zenoti navigation.
  2. Click Analytics in the HyperConnect navigation.
  3. Scroll down to the heatmap section on the Analytics dashboard.
  4. Click the dropdown selector in the heatmap section.
  5. Select Call Volume to switch the visualization to call count per hour.
  6. Review the heatmap — rows represent days of the week, columns represent hours (00:00–23:00), and darker cells indicate higher call volume.
  7. Scroll vertically to view hours outside the default 9 AM starting view.
  8. To return to duration data, click the dropdown and select Call Duration.

Default behavior and validations: The heatmap defaults to Call Duration mode and opens scrolled to 9 AM. Both modes support vertical scrolling across the full 24-hour range. The Connect Access Enable permission is required to access the HyperConnect Analytics dashboard and the heatmap type filter.

Notes: HyperConnect voice must be enabled and provisioned for your organization before heatmap data is available. If your center recently activated HyperConnect voice, the heatmap may appear empty until sufficient call data has been collected.

Learn more: Call Volume Heatmap with Heatmap Type Filter

Unknown guest search extended to include HyperConnect timeline events

Audience/Roles: Administrator, Front Desk Operator, Center Manager

Overview: When an inbound call or message arrives from an unrecognized phone number, HyperConnect now searches not only guest profile records but also timeline event records where no guest profile was previously linked. This allows front desk staff to surface prior interaction history for unknown callers who contacted the center before completing a profile registration. Staff can then link the conversation to an existing guest or create a new profile with full context of past interactions.

Business Scenario: A caller contacts the center from a number not tied to any guest profile. Previously, the interaction would appear with no history. Now, HyperConnect surfaces a prior call from the same number that was logged as an unknown event months ago, giving the front desk operator context to recognize the caller as a returning contact and create or link a guest profile accordingly.

How to Use:

  1. Open HyperConnect from Chat in the Zenoti navigation.
  2. When an inbound call or message arrives from an unrecognized number, locate the interaction in the conversation panel.
  3. Click Link guest to open the guest search.
  4. Review results — HyperConnect automatically searches both guest profile records and unlinked timeline event records.
  5. If a match is found in timeline events, review the prior event details and click Link now to associate the conversation with the identified guest, or click Link to right one if multiple matches appear.
  6. If no match is found, click Create a guest profile to register the caller as a new guest.

Default behavior and validations: The extended timeline event search activates only when the center is operating in HyperConnect mode (not legacy ezConnect mode) and the holder context is a center, not the organization level. Linking a conversation to a guest profile does not retroactively update prior timeline events that surfaced in the search. The Connect Access Enable permission is required to access HyperConnect features.

Notes: HyperConnect must be enabled for your organization by an administrator. This feature does not apply at the organization level — only center-level holders benefit from the extended search. In hub-spoke call center configurations, the timeline event search applies to the center context in which the interaction is received. Cross-center event visibility depends on your organization's events sharing settings.

Learn more: Unknown Guest Search — HyperConnect Timeline Events Inclusion

Inventory

On-page navigation added to Manage purchase orders article

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: The Manage purchase orders help article now includes an on-page table of contents linking directly to each major section, such as editing, closing, copying, returning, and back-dating orders. This allows users to jump to the relevant procedure without scrolling through the full article.

Notes: This is a documentation update only; no changes were made to product functionality or permissions.

Learn more: Manage purchase orders

Kiosk

Automatic deduplication of wait-time threshold notifications

Audience/Roles: Administrator

Overview: Zenoti now prevents duplicate wait-time threshold notifications from being sent to guests by checking whether a matching pending notification already exists before adding a new one to the queue. The check applies to First Threshold and Second Threshold notification types and evaluates the appointment group or invoice reference, the notification type, void status, and whether at least one delivery channel is still pending. If all four conditions match an existing record, the new notification is skipped; otherwise it is enqueued normally. This protects guests from receiving the same threshold alert more than once for the same appointment or group booking.

Business Scenario: A guest is waiting for a service and the system attempts to enqueue a Second Threshold notification. Because a pending Second Threshold notification for the same appointment group already exists and has not yet been sent, the duplicate is suppressed and the guest receives only one alert.

Default behavior and validations: Deduplication is automatic and always active for First Threshold and Second Threshold notifications. It cannot be disabled per center and requires no configuration. All other notification types — confirmations, reminders, cancellations, and others — are not subject to this guard. The guest kiosk must be enabled at both the organization and center level, and the 'Enable wait time notifications for guests' center setting must be turned on.

Notes: Reviewing or modifying kiosk and notification settings requires the Edit permission on the Organizations security object (Admin > Settings > Organization). If duplicate notifications are observed for any type other than First Threshold or Second Threshold, that behavior is unrelated to this mechanism and should be investigated under Admin > Settings > Center.

Learn more: Appointment Notification Deduplication — Wait Time Threshold Reminders

Marketing

Campaign content risk scoring — persistence and retrieval

Audience/Roles: Administrator, Business Owner, Center Manager

Overview: Zenoti now stores content risk evaluation results for each language variant of a campaign's message template when the campaign is submitted through the Save and publish gate. Authorized users can open a blocked campaign's details to see a plain-language explanation of why the content was flagged, along with the specific keywords that triggered the block. This gives marketing administrators a clear, actionable reason for a blocked campaign without needing to contact support. Users can correct the flagged content and resubmit directly from the same workflow.

Business Scenario: A campaign manager submits an SMS campaign promoting a seasonal offer. The campaign is blocked at the content review gate. The manager opens the campaign details, reads the blocking reason — 'Content contains terms associated with unsubstantiated claims' — and sees 'guaranteed' listed as a flagged keyword. After replacing the term and selecting Save and publish, the revised content passes the gate and the campaign is scheduled.

How to Use:

  1. Navigate to Marketing > Manage Email/Text Message Campaigns.
  2. Locate the campaign showing a blocked status and select it to open campaign details.
  3. Review the blocking reason and flagged keywords displayed in the content section.
  4. If the campaign has multiple language variants, use Select Content Language to switch between variants and review each variant's blocking reason and flagged keywords independently.
  5. Edit the campaign content to remove or replace the flagged terms.
  6. Select Save and publish to resubmit the campaign through the content review gate.
  7. If the revised content passes, the campaign proceeds to scheduling or sending; if blocked again, a new blocking reason is recorded and displayed.

Default behavior and validations: Risk data is generated only after a campaign has been submitted through Save and publish at least once. The blocking reason displayed in the campaign summary reflects the first language variant with a blocked status; switch to individual variants using Select Content Language to see variant-specific explanations. The content risk explanation is the only risk field surfaced in the UI — numeric scores and internal status codes are not displayed. A campaign can be blocked based on overall content risk even if no individual keywords are listed in the flagged keywords field.

Notes: Requires the Campaigns permission under the Marketing security role to view campaign details and content risk information. Campaigns created before the content review gate was active for the organization will not have stored risk data until resubmitted through Save and publish. The content review gate evaluates the full message body on each submission, so additional terms beyond those previously flagged may be identified after resubmission.

Learn more: Campaign content risk scoring — persistence and retrieval

On-page navigation added to gift card promotions article

Audience/Roles: Business Owner, Administrator

Overview: The gift card promotions documentation page now includes an 'On this page' navigation section at the top, listing anchor links to each major section of the article. This makes it faster to locate specific topics such as bonus promotions, quantity-based configurations, discount promotions, and promotion behavior without scrolling through the full page.

Learn more: Create gift card promotions

Memberships

Membership Redemption Center Templates

Audience/Roles: Administrator, Business Owner, Center Manager

Overview: Organization administrators can now create and manage reusable Membership Redemption Center Templates that define which centers are eligible to redeem membership benefits. Each template groups one or more centers under a named, coded configuration that can be applied consistently across the organization. This eliminates the need to configure redemption rules center by center, reducing setup effort and the risk of inconsistent rules. Templates can be activated or deactivated at any time, and a read-only center count in the edit view shows how many locations will be affected before any change is saved.

Business Scenario: A spa chain with 20 locations wants to restrict a premium membership tier so benefits can only be redeemed at flagship centers. An administrator creates a 'Flagship Centers' template, associates the relevant locations with it, and applies the template to the membership tier — instead of updating each center's redemption settings individually.

How to Use:

  1. Ensure membership settings for your organization are already configured (see Configure membership settings).
  2. Click the Configurations icon in the main navigation.
  3. Type 'Membership' in the search box or navigate to Memberships, then locate the Membership Redemption Center Templates section.
  4. Click Add to create a new template.
  5. Enter a Name, a unique Code, an optional Description, and set Active to Yes or No.
  6. Click Save.
  7. After saving, associate centers with the template from the membership configuration screens.
  8. To update an existing template, click its name in the list, review the displayed center count to assess impact, edit the required fields, and click Save.

Default behavior and validations: New templates are active by default. The Code field must be unique within the organization. The Description field is optional. The Centers field is read-only and displays the count of centers currently associated with the template; it is not editable from this screen. Active status displays as localized Yes or No values based on the organization's localization settings.

Notes: You must have permission to access the Configurations area; contact your organization owner or administrator if the area is not visible. Membership settings must be configured before creating redemption center templates. Changes to a template affect all centers currently associated with it — review the center count in the edit view before saving.

Learn more: Membership Redemption Center Templates

Membership advance booking days for amenity services

Audience/Roles: Administrator, Center Manager, Business Owner, Guest

Overview: Zenoti now evaluates membership-based advance-booking-day rules when guests book amenity services, allowing members with qualifying memberships to reserve amenity slots further ahead than non-members. For each guest, the system selects the highest qualifying advance-booking-days value across all their active memberships, then applies the most restrictive of those per-guest values across the entire group. This gives individual guests the maximum window their memberships allow while ensuring the group booking respects the most constrained guest's limit. The feature requires the Enable advance booking days for services / amenities setting to be active for your organization.

Business Scenario: A couple books a sauna session. Guest A holds a Platinum membership with a 30-day advance booking rule for the sauna; Guest B holds a Silver membership with a 14-day rule. Zenoti sets the effective booking window to 14 days — the most restrictive value across both guests — so the slot opens to them 14 days before the session date.

How to Use:

  1. Confirm that the Enable advance booking days for services / amenities setting is active for your organization; contact your Zenoti representative if the setting is not visible.
  2. Navigate to the Memberships configuration area and open the membership whose advance booking rules you want to set.
  3. Define advance booking day rules at the parent service level for each amenity service, specifying a value greater than zero.
  4. Ensure each guest's membership record is in an Active, Pending Upgrade, or Pending Downgrade status so the rules are evaluated at booking time.
  5. Save your changes; the rules take effect on the next amenity slot availability check.

Default behavior and validations: Rules are evaluated only for bookings flagged as amenity bookings. Service variants are resolved to their parent service ID, so rules must be defined at the parent level to apply to variants. Qualifying membership statuses are Active, Pending Upgrade (before the upgrade executes), and Pending Downgrade (before the downgrade executes). Terminated family add-on member records are excluded from evaluation even if the primary membership is active. Rules with a value of zero or that are voided are excluded.

Notes: The Enable advance booking days for services / amenities organization-level setting must be active before membership advance booking rules are applied. If this setting is not visible in your configuration, contact your Zenoti representative. Advance booking rules defined only at the variant level — not at the parent service level — will not be picked up by the evaluation logic.

Learn more: Membership advance booking days for amenity services

Membership Operations Report

Audience/Roles: Administrator, Center Manager

Overview: The Membership Operations Report provides a time-series view of membership count changes over a selected date range. Administrators and center managers can track new sales, cancellations, freezes, upgrades, downgrades, and other status transitions grouped by day or month. The report includes Active Start and Active End counts alongside configurable movement labels that show the net change per transition type, making it possible to identify trends and investigate shifts in membership population. An active-count drilldown lets users click any active-count figure to view the individual members in that bucket at that point in time.

Business Scenario: A center manager notices a drop in active members during March. She opens the Membership Operations Report, sets the date range to cover March, and groups by Day. The movement columns reveal a spike in cancellations during the second week with no corresponding increase in new sales, giving her a specific window to investigate retention efforts.

How to Use:

  1. Navigate to Finance > Collections > Membership Operations Report.
  2. Select a Start date and End date for the reporting period (End date is capped at yesterday UTC).
  3. Optionally filter by Centers and Category, and choose Day or Month in the Group by field.
  4. Select Refresh to load results.
  5. Review Active Start, Active End, and movement columns to interpret net membership changes.
  6. Click any active-count figure to open the member-level drilldown for that snapshot date.
  7. Select Export to Excel to download the report data.
  8. To customize which status combinations count as active, navigate to Configuration > Memberships > Membership Operations Report, configure the Active bucket checkboxes, and click Save.
  9. To configure movement label names and impact values, scroll to Movement configuration on the same page, update the relevant rows, and click Save.

Default behavior and validations: If no Group by value is selected, the report defaults to Day. If no organization configuration has been saved, the report uses system-defined defaults for both the active bucket and movement label mappings. The End date is automatically capped at yesterday (UTC); today and future dates are not permitted. The Start date must not exceed the End date. Report data is pre-computed nightly; data for the previous day becomes available the morning after. Coverage begins from 2024-01-01; data before this date is not available. When both the From and To status combinations of a transition fall within the active bucket, the system automatically sets that transition's impact to 0 and this cannot be overridden manually.

Notes: This report requires the Membership Operations Report feature to be enabled for your organization; contact your Zenoti administrator if the report does not appear or returns no data. Movement column labels are configured at the organization level and may differ across organizations. Changes to the active bucket or movement label mappings affect how Active Start, Active End, and all movement counts are computed for all future report runs; review the impact on historical comparisons before saving changes. Historical backfill of data starting from 2024-01-01 may still be in progress; contact your Zenoti administrator if data gaps persist.

Learn more: Membership Operations Report

Fractional multiplier validation for service equality templates

Audience/Roles: Administrator, Center Manager, Business Owner

Overview: Zenoti now automatically checks whether any Active or Frozen memberships are linked to a service equality template whose equivalence factor rounds to 0.33 or 0.67 before a configuration change is saved. If affected memberships are found, a warning appears so administrators can review the scope of impact before confirming the change. This prevents unintended shifts in credit calculations for members who are currently able to redeem services. Memberships in Cancelled, Expired, Closed, or other non-redeemable states are excluded from the check.

Business Scenario: A center manager updates the equivalence factor on a service equality template used by a popular monthly membership. Before the change is applied, Zenoti detects that 42 Active memberships are linked to that template and displays a warning. The manager pauses, reviews the affected memberships, briefs the front-desk team, and notifies members before confirming the update — avoiding surprise discrepancies at the next redemption.

How to Use:

  1. Navigate to Configuration > Memberships > Membership actions.
  2. Open the service equality template or membership setting you want to change.
  3. Make your intended configuration change.
  4. Review the on-screen warning if Zenoti detects Active or Frozen memberships using a template with a 0.33 or 0.67 equivalence factor.
  5. Use membership reports filtered by Active or Frozen status to identify the scope of affected memberships.
  6. Confirm the change to apply the update, or select Cancel to exit without saving.

Default behavior and validations: The check runs automatically as part of pre-save validation; it cannot be triggered or skipped manually. It evaluates only Active (status 1) and Frozen (status 3) memberships. A warning is shown only when the check returns a positive result. If no Active or Frozen memberships are linked to a fractional-multiplier template, no warning appears and the change saves normally.

Notes: The check can be triggered by any configuration change that affects redemption behavior for memberships using service equality templates, not only direct edits to the template itself. Before making changes to fractional-multiplier templates, consider notifying affected members, as they may notice a difference in credits applied at their next redemption. Use the Membership Benefits Detail report to cross-reference memberships with specific service equality templates when investigating the scope of a warning.

Learn more: Service Equality Template — Fractional Multiplier Validation

Proration sub-setting now requires refund sub-setting to be enabled

Audience/Roles: Business Owner, Center Manager, Administrator, Front Desk Operator

Overview: The proration sub-setting (Enable membership fee to be prorated for freeze actions) now has no effect unless the refund sub-setting (Enable membership fee to be refunded for freeze actions) is also turned on. Previously, the dependency between these two sub-settings was not explicitly enforced or documented. Enabling proration alone will not produce any financial adjustment at unfreeze; both sub-settings must be active together for pro-rated calculations to apply.

Business Scenario: A center manager enables proration for freeze actions but leaves the refund sub-setting off, expecting pro-rated credits to appear on guest invoices at unfreeze. With this change, no adjustment is generated until the refund sub-setting is also turned on, preventing silent misconfiguration and unexpected zero-adjustment invoices.

Default behavior and validations: Both sub-settings default to off. The proration sub-setting is blocked from producing any financial adjustment when the refund sub-setting is off. The parent toggle (Enable proration and refund for freeze actions) must be on before either sub-setting is visible. Calculations apply only when the skip-billing-cycles freeze option is selected.

Notes: If your organization previously enabled only the proration sub-setting without the refund sub-setting, no pro-rated adjustments were being applied. To activate proration behavior, turn on both sub-settings under Configuration > Memberships > Membership actions > Freeze rules. This behavior applies to both individual and family (add-on) memberships, and is consistent on the Zenoti Mobile App (ZMA).

Learn more: Proration and refund for membership freeze and unfreeze actions

In-place membership upgrade/downgrade fee queue

Audience/Roles: Front Desk Operator, Administrator

Overview: When a guest schedules an in-place membership upgrade or downgrade, Zenoti now creates a fee queue entry that links the scheduled change to a fee invoice and tracks it through payment. The membership transition to the target tier occurs automatically once the associated fee invoice is paid — no manual intervention is needed to trigger the switch. If the fee invoice is voided before payment, the transition does not proceed and the guest remains on their current membership. Staff can view queue status, collect payment, or cancel a pending change directly from the guest's membership detail view.

Business Scenario: A guest schedules an upgrade from a Basic membership to a Premium membership effective the 15th of the month. On that date, the front desk sees a Pending status in the Recurrence Details section, collects the $25.00 upgrade fee, and closes the invoice. Zenoti automatically activates the Premium membership and updates the fee queue status to Paid — no additional steps required.

How to Use:

  1. Open the guest's profile from the Appointment Book or by searching for the guest.
  2. Select the Memberships tab and open the membership with a scheduled upgrade or downgrade.
  3. In the Recurrence Details section, review the fee queue status (Pending or Paid), the associated invoice number, and the effective date.
  4. To collect payment: navigate to the fee invoice from the Recurrence Details section or the Payments tab, select Pay, choose a payment method, and confirm. Zenoti closes the invoice and processes the membership transition automatically.
  5. To cancel a pending change before payment: select Cancel Upgrade or Cancel Downgrade in the Recurrence Details section, then confirm in the dialog. Zenoti voids the fee invoice and removes the queue entry.

Default behavior and validations: The fee queue applies only to in-place upgrades and downgrades — scheduled changes that take effect without cancelling the current membership. It does not apply to immediate upgrades or downgrades processed at the time of the action. Cancellation of a pending change is available only while the fee invoice status is Pending; once paid and processed, the change cannot be reversed through this flow. Each scheduled change generates its own queue entry with its own invoice.

Notes: Required permissions: Upgrade Membership (Organization → Security → Security Roles → [role] → Memberships → Upgrade) and Downgrade Membership (Organization → Security → Security Roles → [role] → Memberships → Downgrade). If the fee queue entry shows a non-zero retry count and an error message, the system encountered an error during transition processing — note the error and contact your Zenoti administrator rather than re-paying the invoice. A voided invoice blocks the transition; a new upgrade or downgrade must be initiated to generate a fresh fee invoice and queue entry.

Learn more: In-place membership upgrade/downgrade fee queue

In-place membership upgrade and downgrade fee queue

Audience/Roles: Front Desk Operator, Center Manager, Administrator

Overview: When a guest upgrades or downgrades a membership in place and the action carries a fee greater than zero, Zenoti now inserts a pending row into a fee queue rather than applying the change immediately. The front-desk operator pays the associated fee invoice at Point of Sale, and a background job then replays the upgrade or downgrade to completion. This two-step process ensures the membership change is only applied after payment is confirmed, preventing billing gaps. If the fee is zero, the change still completes instantly without entering the queue.

Business Scenario: A guest on a Standard recurring membership requests an upgrade to a Premium recurring membership that carries a $50.00 fee plus $4.50 tax. The system inserts a Pending queue row and holds the membership change. The front-desk operator opens the fee invoice, collects $54.50 from the guest's card on file, and closes the invoice. Within a few minutes, the background job updates the queue row to Completed and the guest's Memberships tab shows the Premium membership as Active.

How to Use:

  1. Open the guest's profile from the Appointment Book or guest search and navigate to the Memberships tab.
  2. Initiate an in-place upgrade or downgrade; confirm the fee amount with the guest before proceeding.
  3. Navigate to the open fee invoice linked to the pending queue row.
  4. Select a payment method and select Pay to collect the fee, then close the invoice.
  5. Return to the guest's Memberships tab after a few minutes to confirm the target membership is now shown as Active.
  6. If the guest changes their mind before payment, select Cancel Upgrade or Cancel Downgrade on the Memberships tab and confirm; the queue row is voided and the fee invoice is canceled.

Default behavior and validations: The fee queue is triggered only when the upgrade or downgrade fee is greater than zero; a zero-fee change completes immediately. The queue row starts in Pending state, moves to Processing when the invoice is paid, and reaches Completed when the background job finishes. Failed rows are retried automatically. Voided rows are permanently excluded from processing and cannot be updated. The Cancel Upgrade and Cancel Downgrade options are available only while the queue row is in Pending state and the fee invoice has not been paid.

Notes: Requires the Upgrade permission (Memberships > Upgrade) to initiate an upgrade, and the Downgrade permission (Memberships > Downgrade) to initiate a downgrade. Do not void the fee invoice without also canceling the pending queue row, as this leaves the membership in an inconsistent state. Do not create a second fee invoice manually if one already exists for a pending row. If a queue row is in a Failed state, do not re-initiate the upgrade or downgrade until the failed row is resolved, to avoid duplicate pending rows.

Learn more: In-place upgrade and downgrade fee queue — insert and update operations

Membership advanced booking rules for classes and amenities

Audience/Roles: Administrator

Overview: Administrators can now define per-membership rules that limit how many days in advance a member may book a specific class or amenity. Rules are configured at the membership level and can cover multiple memberships and items in a single rule when the same day limit applies. This allows organizations to reserve earlier booking windows for higher-tier members and manage demand for popular sessions.

Business Scenario: A fitness studio offers Gold and Platinum memberships. The administrator creates two rules targeting the 'Morning Yoga' class: Platinum members can book up to 14 days ahead, while Gold members are limited to 7 days. This gives Platinum members a priority booking window without requiring any manual intervention.

How to Use:

  1. Navigate to Master data > Manage Memberships.
  2. Select the membership you want to configure; it opens in edit mode.
  3. Locate the advanced booking rules section and select Add new.
  4. Select one or more memberships and one or more classes or amenities to restrict.
  5. Set the Item type to Classes or Amenities to match the items selected.
  6. Enter a positive integer for Advance booking days.
  7. Select Save to apply the rule.
  8. To delete a rule, return to the advanced booking rules section, select the delete action for the rule, and confirm the deletion.

Default behavior and validations: A rule applies uniformly to all memberships and items included in it. The Advance booking days field must be a positive integer; blank or zero values prevent saving. Deleting a rule takes effect immediately, restoring the standard booking window for all affected members. Item type must match the selected items exactly — a rule set to Classes does not restrict Amenities bookings.

Notes: Requires the Delete Membership permission to delete advanced booking rules, and the Delete Category permission to delete membership category-level rules. Advanced booking rules control booking timing only; class capacity settings must be configured separately to manage the number of bookings. Review existing rules after any membership rename, deactivation, or restructuring to ensure policies remain accurate.

Learn more: Membership Advanced Booking Rules

Membership phase history

Audience/Roles: Center Manager, Administrator

Overview: Zenoti now maintains a chronological phase history for every membership, recording a snapshot of membership terms, billing amounts, credit balances, and add-on member details each time a tier transition occurs — including upgrades, downgrades, and cancellations of pending transitions. Each phase is numbered in the order it was created and displayed in ascending order on the membership details page, giving managers a complete audit trail from the original sale to the current state. Staff with the appropriate permissions can also cancel a pending upgrade or downgrade directly from this view, which marks the scheduled phase as Cancelled without affecting the guest's current benefits or billing.

Business Scenario: A guest disputes a change in their monthly collection amount. The center manager opens the guest's membership details, reviews the phase history, and identifies exactly when the tier transition occurred and what the billing amounts were before and after — resolving the dispute without guesswork.

How to Use:

  1. Navigate to the guest's profile page.
  2. Select the Memberships tab.
  3. Locate the membership you want to review and select its name to open the membership details.
  4. Review the phase history listed in ascending order by phase number.
  5. To cancel a pending upgrade, select Cancel Upgrade; to cancel a pending downgrade, select Cancel Downgrade.
  6. Confirm the cancellation in the Cancel Upgrade / Downgrade dialog.

Default behavior and validations: Phase history is generated automatically when a membership is sold (Phase 1, state: Current) and updated on every tier transition. No manual setup is required. Phase records are read-only and cannot be edited or deleted. Only one phase can carry the Current state at a time. Cancelled phases remain visible in the history permanently. Cancelling a pending transition cannot be undone; a new upgrade or downgrade must be scheduled if needed.

Notes: Cancelling a pending upgrade requires the Upgrade Membership permission (Organization → Security → Security Roles → [role] → Memberships → Upgrade). Cancelling a pending downgrade requires the Downgrade Membership permission (Organization → Security → Security Roles → [role] → Memberships → Downgrade). Memberships upgraded via full cancellation and re-sale rather than in-place upgrade appear as separate membership records, each with their own phase history starting at Phase 1.

Learn more: Membership phase history

MyZen

MyZen appointment management updates

Audience/Roles: Service Provider, Front Desk Operator

Overview: The Appointments tab has been renamed to Schedule. The date picker no longer advertises navigation beyond three years in the past or future. The Upcoming & Past Appointments section in appointment details now explicitly scopes results to the current center. Staff Calendar has been clarified as view-only for inline editing, but tapping any appointment or blockout slot now navigates to its detail screen where actions can be taken.

Business Scenario: A service provider reviewing another therapist's bookings in Staff Calendar can tap a blockout slot to open its detail screen and take action, rather than assuming the calendar itself is fully non-interactive.

Notes: Staff Calendar visibility remains controlled by organization-level settings. The rename from Appointments to Schedule applies to the bottom navigation tab in MyZen only.

Learn more: Manage appointments in MyZen

MyZen app navigation and sign-in flow updates

Audience/Roles: Service Provider, Employee

Overview: The MyZen app sign-in flow now specifies that the one-time verification code is sent to the employee's registered phone number or email address, and that linking an employer requires validating the organization's account name. Session handling has been updated so that returning to the app after inactivity triggers automatic session validation, redirecting to sign-in if the session has expired. The Home screen now greets employees by first name and surfaces a tips summary, appointment count, and current clock-in status at a glance. The Performance tab has been removed from the bottom navigation bar, and a Navigation section has been added to the overview documentation.

Business Scenario: A service provider reopens MyZen after a long break between clients. The app detects the expired session and prompts re-authentication, keeping the account secure without requiring a full reinstall or manual sign-out.

Default behavior and validations: The PIN or biometric lock runs on every app launch after initial setup. Session expiry redirects the user to the sign-in screen automatically. The bottom navigation bar now contains four tabs: Home, Appointments, My Money, and Menu.

Learn more: MyZen overview

Dispute button renamed to 'Request Dispute' in wallet transaction flow

Audience/Roles: Employee

Overview: The button used to initiate a wallet transaction dispute has been renamed from 'Raise Dispute' to 'Request Dispute'. This label change aligns the in-app terminology with the dispute workflow language used elsewhere in MyZen.

Default behavior and validations: The renamed button appears on the transaction detail screen when an employee taps a transaction in their wallet history. All other dispute form fields and steps remain unchanged.

Learn more: File a dispute

Expanded card management and wallet home screen in MyZen

Audience/Roles: Employee

Overview: The wallet home screen now surfaces Available Balance, recent transactions, card status, and quick-action buttons directly on the My Money tab, replacing the previous two-step navigation. Card management options—including Freeze/Unfreeze, Change PIN, Request New Card, Cancel Card, and Account Details with Apple Pay/Google Pay support—are now consolidated under a single Card Settings menu. Card activation now routes through Card Settings rather than a direct home-screen button, and includes an explicit OTP-then-PIN flow with status feedback. These changes give employees faster access to card controls and clearer guidance at each step.

Business Scenario: An employee notices an unfamiliar charge and wants to freeze their card immediately. They open MyZen, tap My Money, tap Card Settings, and select Freeze Card in a few taps—without navigating through multiple screens—then file a dispute from the same wallet home screen.

How to Use:

  1. Open MyZen and tap My Money in the bottom navigation.
  2. Review Available Balance, recent transactions, and card status on the wallet home screen.
  3. Tap Card Settings to access Activate Card, Freeze Card, Unfreeze Card, Change Card Pin, Request New Card, Cancel Card, or Account Details.
  4. Follow the on-screen prompts for the selected action (OTP and PIN entry for activation or PIN change; confirmation dialog for freeze, unfreeze, or cancellation).
  5. To add your card to a mobile wallet, tap Card Settings, select Account Details, then choose Apple Pay or Google Pay.

Default behavior and validations: Card management options are available only to employees at US-based centers with KYC verification-approved accounts. Freezing a card declines all transactions until unfrozen. Cancelling a card is permanent and cannot be reversed; use Freeze Card for temporary situations. A fee may apply when requesting a physical replacement card.

Notes: If an OTP is not received during card activation or PIN change, verify that the registered mobile number in the MyZen profile is correct. The use-cases UC-3.11 through UC-3.14 previously associated with this article have been removed from the article metadata in this release.

Learn more: Wallet and financial services

Notifications

Workflow and AI notification types for automated communications

Audience/Roles: Administrator

Overview: Zenoti introduces four notification types to support workflow-triggered and AI Scribe communications. Two types handle workflow events: Workflows Transactional (ID 351) for guest-facing messages and Workflows Internal (ID 352) for employee-facing messages, each with a distinct macro set appropriate to its audience. Two additional types — AI Concern Mapping Completed and AI Service Type Mapping Completed — fire by email when AI Scribe finishes background processing tasks and do not consume communication credits. Selecting the correct type ensures recipients receive only the macros relevant to them and that guest marketing compliance macros appear where required.

Business Scenario: A spa administrator sets up an automated post-visit follow-up workflow. They select Workflows Transactional for the guest email so the template can include [MailUnsubscribeLink] for marketing compliance, and separately configure a Workflows Internal notification to alert front-desk staff of the same event — without exposing guest opt-out macros in the staff message.

How to Use:

  1. Verify that Activate email and Activate SMS master toggles are enabled: navigate to Admin > Notifications > Email settings.
  2. Navigate to Admin > Notifications > Manage Templates.
  3. Create or edit a notification template and select the appropriate type: Workflows Transactional (ID 351) for guest recipients or Workflows Internal (ID 352) for employee recipients.
  4. Insert supported macros for the selected type; include [MailUnsubscribeLink] and [SMSMarketingOptOutLink] in any guest-facing marketing communication.
  5. For AI Scribe completion alerts, locate the AI Concern Mapping Completed or AI Service Type Mapping Completed notification type and configure the email template.
  6. Save the template.

Default behavior and validations: Workflows Transactional (ID 351) supports guest contact macros plus marketing compliance macros ([MailUnsubscribeLink], [SMSMarketingOptOutLink], [DownloadLink], [ClaimAccountLink], [AutoApplyDiscountWebstoreURL]). Workflows Internal (ID 352) supports staff contact macros only; guest marketing macros are unavailable on this type. AI Scribe notification types are email-only and cannot be configured for SMS, WhatsApp, or push; they do not appear in the Credit Usage Dashboard.

Notes: Edit permission on the Organization security object is required to configure notification templates. Using Workflows Transactional for internal recipients exposes guest marketing opt-out macros not appropriate for staff. Using Workflows Internal for guest recipients omits macros required for guest-facing content.

Learn more: Workflow and AI notification types

Packages

Custom package tax recalculation on invoices

Audience/Roles: Front Desk Operator, Administrator

Overview: When a custom package is added to an open invoice, Zenoti now automatically applies the tax rules configured for the center where the sale occurs. This ensures that center-specific tax rates are correctly reflected on the invoice, which is especially important for multi-center organizations where tax rates differ by location. Tax recalculation applies only to non-voided custom package line items; voided line items are excluded.

Business Scenario: A guest purchases a 'Relaxation Bundle' custom package at a downtown center that has a 10% service tax rate configured. After the package is added to the invoice, the custom package line item automatically displays the correct 10% tax amount without any manual adjustment by front desk staff.

How to Use:

  1. Navigate to Admin > Configurations > Tax groups and confirm that a tax group is assigned to the center where the invoice was created.
  2. Open the guest's profile and navigate to the relevant invoice.
  3. Confirm the invoice is not voided and contains at least one custom package line item.
  4. Confirm the invoice is associated with the correct center, as tax is applied based on the center recorded on the invoice.
  5. Review the custom package line item to verify that the expected tax amount is displayed.
  6. If tax is missing or incorrect, return to Admin > Configurations > Tax groups and verify the tax rates and components assigned to the center.

Default behavior and validations: Tax recalculation is triggered automatically when a custom package is added to an invoice. No tax is applied if the center has no tax group configured. Tax for custom package line items is calculated independently from services and products on the same invoice. Voided invoices and voided line items are excluded from recalculation.

Notes: The Packages security role permission is required to manage package-related invoice actions. Tax group changes apply to new invoices going forward; corrections to existing invoices require administrator review. In multi-center organizations, tax is applied based on the center recorded on the invoice, not the center the logged-in user is currently accessing.

Learn more: Custom package tax recalculation

Package agreement form data retrieval at point of sale

Audience/Roles: Administrator, Front Desk Operator, Business Owner

Overview: When a guest purchases a package that has an HTML agreement form assigned, Zenoti now stores the submitted form data against the invoice item created for that sale and makes it retrievable for rendering. The system matches the form ID, invoice item ID, and a confirmed submission status to return the signed HTML content, guest-specific form data, and a submission confirmation flag. This enables the signed agreement to be included in dispute evidence for payment chargebacks and renders consistently with membership agreement forms.

Business Scenario: A guest purchases a 'Wellness 10-Pack' series package and signs the HTML agreement form at checkout. When a payment dispute is later raised on that invoice, staff can retrieve the signed form by matching the package's form ID to the invoice item ID, and include the rendered agreement as evidence in the chargeback response.

How to Use:

  1. Assign an HTML agreement form to the package during package setup before selling it to guests.
  2. At the point of sale, ensure the guest completes and submits the agreement form.
  3. Navigate to the guest profile and select the Packages tab to confirm the form status shows as submitted.
  4. Open the invoice associated with the package sale and note the invoice item ID.
  5. When dispute evidence or a rendered form is needed, the system automatically uses the form ID and invoice item ID to locate and return the submitted form data.

Default behavior and validations: Retrieval returns only the most recent confirmed submission matching the form ID and invoice item ID. Forms that were opened but not submitted return no data. Each package supports only one HTML agreement form; attempting to assign a second form of the same type produces an error. Form data is retrieved as it existed at the time of submission — updates to the form template after submission do not affect the stored record.

Notes: Agreement forms can only be retrieved for sales where the form was submitted at the time of purchase; adding a form to a package after it has already been sold will not produce retrievable data for earlier sales. The Packages security role permission is required to view package details and associated form data in the guest profile. Package HTML agreement forms (form type 7) follow the same retrieval and rendering pattern as membership agreement forms (form type 6).

Learn more: Package agreement form data retrieval

Payments

On-page navigation added to PayCom billing article

Audience/Roles: Business Owner, Administrator

Overview: The PayCom billing documentation page now includes an on-page table of contents with anchor links to all major sections, including the billing portal, invoice history, charge breakdowns, invoice statuses, the PayCom Monthly Summary report, and troubleshooting guidance. This makes it faster to locate specific billing information without scrolling through the full article.

Default behavior and validations: The table of contents is present on the article page by default and requires no configuration. Access to the billing portal itself remains restricted to organization owners and designated billing contacts.

Learn more: Understanding and managing PayCom billing in Zenoti Payments

IC Plus rates backup and restore for surcharge

Audience/Roles: Business Owner, Administrator

Overview: When surcharge is enabled on an IC+ (Interchange-Plus) rate plan, Zenoti automatically backs up the complete set of current IC+ fee rates before applying any changes. If surcharge is later disabled, Zenoti restores those backed-up rates to both the live IC+ fee table and the mirrored processor rate table in a single atomic transaction, ensuring no partial updates occur. Only one active backup exists at a time per subscriber and processor pair, so the original pre-surcharge rates are preserved even if surcharge is toggled multiple times. This protects payment fee configurations from accidental loss and gives administrators a reliable way to revert rate changes tied to surcharge enablement.

Business Scenario: A payment administrator enables surcharge for a center on an IC+ plan. Zenoti backs up the existing IC+ rates automatically. Several months later, the business decides to disable surcharge. When the administrator initiates the disable flow, Zenoti displays the backed-up rates for review before confirmation. Upon confirmation, both rate tables are restored simultaneously. If anything goes wrong during the restore, the entire operation rolls back and no rates are changed, leaving the administrator free to retry or contact support.

How to Use:

  1. Navigate to Configurations > Payments > Payment processor onboarding > Pass card fee.
  2. Enable or disable surcharge for the relevant center or processor configuration.
  3. When disabling, review the IC+ rate values displayed — these are the rates that were in effect before surcharge was enabled.
  4. Confirm the action to trigger the restore; both the live IC+ fee table and the mirrored processor rate table are updated simultaneously.
  5. After disabling, navigate to Configurations > Payments > Payment processor onboarding and open the rate configuration for the relevant processor to verify the restored rates match your pre-surcharge records.
  6. If rates do not match expectations, contact Zenoti support before making any manual edits.

Default behavior and validations: Backup creation and restore are fully automatic; administrators cannot manually trigger either operation. A new backup is created only when no active backup already exists for the subscriber and processor pair — duplicate backups are skipped. After a successful restore, the backup record is voided (soft-deleted) and will not be used again; re-enabling surcharge creates a fresh backup at that point. The surcharge add-on rate is stored separately and is not included in the IC+ rate backup, so it can be updated independently without affecting the backup or restore cycle. Surcharge applies to credit card transactions only and cannot be enabled for centers in Connecticut, Maine, or Massachusetts. Surcharge and tips convenience fee are mutually exclusive per center. Supported processors are Adyen and Stripe.

Notes: The organization must be configured with an IC+ rate plan through Adyen or Stripe. Payment administrator permissions are required to modify processor rate configurations. Colorado and Oklahoma cap surcharges at 2%. If a restore operation fails, the atomic transaction rolls back automatically and no rate data is changed; the administrator should retry the disable-surcharge action and contact Zenoti support with the failure timestamp if the issue persists. Maintaining an independent record of pre-surcharge IC+ rates is recommended as a verification reference after a restore.

Learn more: IC Plus Rates Backup and Restore for Surcharge

Payout fund transfer — enhanced failure tracking

Audience/Roles: Administrator

Overview: When a fund transfer attempt fails, Zenoti now automatically records the transfer amount, the available balance at the time of the attempt, a failure code, and the failure stage on the attempt record. This gives administrators and support staff the specific diagnostic details needed to identify the cause of a payout failure — such as insufficient funds, processor rejection, or a network error — without additional investigation. Failure code and failure stage fields are populated only on failed attempts; they remain empty for successful transfers.

Business Scenario: A payout fails overnight and the finance team needs to determine whether the cause was an insufficient account balance or a processor-side rejection. Instead of contacting support with no context, the administrator opens the attempt record, reviews the failure code and failure stage, compares the available balance against the transfer amount, and either resolves the issue directly or escalates to Zenoti support with all required details in hand.

How to Use:

  1. Navigate to the payout or fund transfer section of the payment dashboard.
  2. Locate the fund transfer record you want to investigate.
  3. Open the attempt history for that fund transfer to view individual attempt records.
  4. On the failed attempt record, review the Failure code, Failure stage, Available balance, Transfer amount, and Associated fund transfer references.
  5. If the available balance was lower than the transfer amount, verify the funding account balance before retrying.
  6. If the balance was sufficient, use the failure code and failure stage to determine the error category, and escalate to Zenoti support with all four values if the issue persists.

Default behavior and validations: Failure code and failure stage fields are populated automatically only when a transfer attempt fails; both fields are empty on successful attempt records. Records are created at the time of each attempt and are not retroactively updated for prior attempts.

Notes: You must have administrative permission to view fund transfer attempt records; contact your Zenoti administrator to confirm access. Do not manually re-trigger a fund transfer before understanding the failure cause, as repeated failed attempts may affect your payout schedule or funding account status.

Learn more: Payout fund transfer — enhanced failure tracking

Surcharge on IC+ (Secondary Markup) billing model

Audience/Roles: Business Owner, Administrator

Overview: Zenoti now supports a secondary markup billing model (Model 3) for organizations onboarded to Interchange-Plus (IC+) payment processing. Under this model, an additional secondary markup fee is calculated on the total transaction amount — including tips and taxes — on top of standard IC+ rates, and appears as a distinct line item in transaction details. The model is activated at the processor level during onboarding and is reflected automatically in Zenoti; no in-app configuration is required. Finance staff can verify whether the model is active and review per-transaction fee breakdowns directly in the payment dashboard.

Business Scenario: A multi-location spa has negotiated an IC+ billing agreement that includes a secondary markup fee. After onboarding, the finance manager opens the payment dashboard, locates a recent membership collection, and confirms the secondary markup fee appears as a separate charge alongside standard IC+ fees — making fee reconciliation straightforward without needing to contact the processor.

How to Use:

  1. Navigate to the payment dashboard.
  2. Use transaction search to locate the transaction you want to review.
  3. Open the transaction detail view.
  4. Review the fee breakdown — the secondary markup fee appears as a distinct charge alongside the standard IC+ fees.
  5. If no secondary markup fee is visible and you expect one, contact your Zenoti account representative to verify the billing model configured during onboarding.

Default behavior and validations: The secondary markup model is enabled or disabled at the processor level during onboarding — it cannot be activated or deactivated from within Zenoti settings. The fee is calculated on the total transaction amount including tips and taxes, not the base service amount alone. Transactions processed before the model was activated will not show a secondary markup fee. The model applies to all qualifying payments, including recurring membership collections, at the rate active on the collection date.

Notes: Organization must be onboarded to Zenoti Payments with an IC+ billing model. Secondary markup activation is agreed upon during processor onboarding; contact your Zenoti account representative to confirm which billing model applies to your organization. When reconciling fees across periods where the billing model changed, filter transactions by date range to isolate and compare fee structures accurately.

Learn more: Surcharge on IC+ (Secondary Markup) Billing Model

Canada tips payout — current release boundaries and unsupported capabilities

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: The Canada release of the tips payout platform supports electronic disbursement of tips to employees via EFT or Interac, but a defined set of capabilities are out of scope for this release. Administrators cannot set or override an employee's payout method, same-day EFT settlement is not available, failed tip amounts do not move to an employer-held balance, Social Insurance Numbers are not collected, multi-currency processing is not supported, bank accounts are linked by manual entry rather than a vault or Plaid-style connection, and enrolled employee payout accounts cannot be deleted from the payout provider. Understanding these boundaries before configuring tips payout for a Canada organization helps set accurate expectations and avoids configuration errors.

Business Scenario: A center manager in Toronto is preparing to roll out tips payout for their team. Before configuring enrollment, they review the current release boundaries and learn that employees must select their own payout method in myZen, that EFT payouts will not settle on the same day tips are earned, and that a departing employee's account should be frozen rather than deleted. This allows the manager to communicate accurate timelines and procedures to staff before go-live.

Default behavior and validations: All Canada tips payout amounts are processed in Canadian dollars only. EFT bank account details (Account number, Institution number, Transit number, Bank name, Account type) are entered manually by the employee and validated at entry. Interac payouts require no bank account details and are directed to the employee's confirmed phone number or email. Failed tip transfers accumulate and are retried on subsequent payout cycles; they do not move to an employer balance. Once an employee is enrolled, their payout account persists and cannot be deleted; freezing the employee as a participant stops future disbursements without removing the account record. A freeze applied after a payout batch has been created does not affect tips already identified for disbursement in that batch.

Notes: This release applies only to organizations operating in Canada. Employees who have not completed enrollment and selected a payout method will not receive tip disbursements until enrollment is complete. To stop tip disbursements for a departing employee, freeze the employee as a participant rather than attempting account deletion.

Learn more: Canada tips payout — overview of what is not yet available

Canada tips payout via Interac e-Transfer and EFT direct deposit

Audience/Roles: Business Owner, Center Manager, Administrator, Employee

Overview: Canada tips payout is a new electronic disbursement service that automatically transfers tips earned at the point of sale to employees' personal Canadian bank accounts. Employees choose their own payout method — Interac e-Transfer for same-day delivery or EFT direct deposit within one to two business days — during MyZen onboarding. The business funds all payouts from a single verified Canadian bank account, debited by EFT regardless of the employee's chosen method. Payout scheduling and accumulation settings are configured independently per center, giving administrators control over when batches run and how frequently debits occur.

Business Scenario: A spa with three Canadian locations wants to pay out tips daily to employees who prefer Interac e-Transfer while allowing employees with EFT direct deposit to receive funds within two business days. The administrator enables tips payout for each center separately, sets a daily payout time, and optionally turns on accumulation mode to reduce debit frequency. Employees complete their own bank or contact-detail setup in MyZen, and tips flow automatically without front-desk involvement.

How to Use:

  1. Complete business bank account onboarding at the organization level by providing account holder name, email, branch transit number, institution number, account number, and account type.
  2. Wait for micro-deposit verification to confirm the business bank account before payouts can begin.
  3. Navigate to each center's tips payout settings and enable tips payout, set the payout start date, and configure the daily payout time.
  4. Optionally enable accumulation mode and set an accumulation start date to batch tips across multiple days into a single payout run.
  5. Direct employees to complete their payout method selection (Interac e-Transfer or EFT direct deposit) during MyZen onboarding.

Default behavior and validations: Tips payout is off by default for each center and must be enabled individually. One payout batch runs per center per day at the configured payout time. Accumulation mode is optional; when disabled, tips are disbursed daily as earned. If payouts are paused, tips continue to accumulate and are released when payouts resume. All amounts are in Canadian dollars. Transaction fees are borne by the business and are not displayed in the product.

Notes: Available only for organizations operating in Canada. The business bank account must pass micro-deposit verification before any payouts begin. Only one business bank account funds all centers in the organization. Tips allocation across employees on an invoice is handled separately through Employee Payroll and is not part of this feature. Fee details are not shown in the product; contact Zenoti for applicable fee information.

Learn more: Canada tips payout overview

Automated tips payout email notifications for Canadian businesses

Audience/Roles: Administrator, Business Owner, Center Manager

Overview: Zenoti now sends four automated email notifications to business administrators at key stages of the Canada tips payout lifecycle: when a micro-deposit is initiated for bank account verification (B1), when an EFT debit is reversed by the bank (B2), when one or more employee payouts in a batch fail (B3), and when payouts resume for a center that was previously paused (B4). Each notification identifies the affected center, relevant batch details, and the in-app path needed to take corrective action. This gives administrators timely visibility into payout issues without requiring them to monitor the Tips Payout Dashboard continuously.

Business Scenario: A center manager receives a B3 notification indicating that three employee payouts in a batch failed because the employees' wallets were inactive. The notification includes the center name, batch date, number of failures, and total failed amount. The manager navigates to Reports > Tips Reconciliation > Payout View, filters by the batch date, resolves each wallet issue, and retries the payouts — all without needing to discover the failures through manual reconciliation.

How to Use:

  1. Confirm that the email address recorded on the business funding account is current by navigating to Configuration > Payments > Tips Payout > Bank account.
  2. When you receive a B1 notification, wait up to 2 business days for the micro-deposit labeled 'Zenoti Verify' to appear in your bank statement, then navigate to Configuration > Payments > Tips Payout > Bank account and enter the exact deposit amount to complete verification.
  3. When you receive a B2 notification, navigate to Reports > Tips Reconciliation > Payout View, locate the affected batch using the center name and batch date from the notification, resolve any funding account issues if needed, and retry the debit.
  4. When you receive a B3 notification, navigate to Reports > Tips Reconciliation > Payout View, filter by the center and batch date, review the status code for each failed payout, resolve the underlying cause for each employee, and retry the failed payouts.
  5. When you receive a B4 notification, review the next scheduled payout run time and update the center's Payout time setting if it does not match your expectations.

Default behavior and validations: Notifications are sent automatically to the email address entered in the Email address field during business funding account setup. All four notification types (B1–B4) are active by default for organizations based in Canada that have completed tips payout onboarding. Failed employee payouts (B3) and reversed debits (B2) do not retry automatically; manual retry is required. B4 is informational and requires no action. No notification includes transaction fee details.

Notes: The organization must be based in Canada and have completed tips payout onboarding for at least one center before notifications are triggered. The administrator must have permission to access the Tips Payout Dashboard and Tips Reports to act on notifications; contact a Zenoti administrator to confirm role access. Tips continue to accumulate for a center while payouts are paused and are disbursed when payouts resume. Retrying a failed payout without first resolving the underlying cause will result in the same failure.

Learn more: Canada tips payout notifications for businesses

Per-center tips payout configuration for Canadian centers

Audience/Roles: Administrator

Overview: Administrators can now configure tips payout behavior independently for each Canadian center after completing organization-level onboarding. Per-center settings control whether tips payout is active, the earliest date tips are eligible for disbursement, whether tips are held in accumulation mode before release, and the time of day the automated daily payout run executes. This gives multi-center organizations the flexibility to align payout schedules and accumulation behavior with each center's payroll cycle and operating hours.

Business Scenario: A Canadian organization with two locations wants Downtown to accumulate tips for two weeks before disbursing them, with a payout run at 21:00 after closing, while Westside uses standard daily payouts at 20:00. The administrator configures each center separately under Configuration > Payments > Tips Payout, setting distinct start dates, accumulation options, and payout times without affecting the other location.

How to Use:

  1. Confirm that organization-level tips payout onboarding is complete and the center is linked to the tips payout setup.
  2. Go to Configuration > Payments > Tips Payout and open the Centers tab.
  3. Locate the center you want to configure and select it to open its settings.
  4. Set Enable tips payout to Yes.
  5. Select a Payout start date using the date picker — tips earned on or after this date are eligible for payout.
  6. To hold tips before disbursement, set Accumulate tips to Yes and then select an Accumulation start date.
  7. Enter the desired daily payout run time in the Payout time field using HH:MM format (default is 20:00).
  8. Select Save, then repeat this procedure for each additional center.

Default behavior and validations: Enable tips payout defaults to No; all other per-center settings are unavailable until it is set to Yes. Accumulate tips defaults to No. Payout time defaults to 20:00. Payout start date and Accumulation start date (when accumulation is enabled) are required fields — saving without them produces a validation error. There is exactly one automated payout run per day per center. Tips earned before the payout start date are not included in payout batches. Disabling tips payout for a center does not forfeit tips already identified for disbursement.

Notes: Organization-level tips payout onboarding must be completed before per-center settings can be configured. The Configure Payment Settings permission is required. Settings must be saved per center individually; there is no bulk configuration option. Changing the payout time takes effect on the next scheduled run. The payout start date cannot be backdated to before onboarding; contact Zenoti Support if earlier tips must be included. Accumulation mode can be reversed at any time; tips already held are included in the next payout run after the change is saved.

Learn more: Configure per-center payout settings in Canada

Tips payout setup for Canadian businesses

Audience/Roles: Administrator

Overview: Canadian organizations can now configure electronic tip payouts to employees directly through Zenoti using a guided four-step onboarding wizard. The wizard covers accepting terms and conditions, linking a verified Canadian business bank account via micro-deposit, selecting which centers draw from that account, and configuring per-center payout settings such as payout time and accumulation options. Once set up, Zenoti automatically debits the business bank account daily to fund employee tip payouts, while employees independently choose their payout method (EFT or Interac) through the myZen app.

Business Scenario: A multi-location spa group operating in Canada wants to stop manually distributing tips and instead pay employees electronically after each shift. The organization administrator opens the Tips Payout wizard, links the company chequing account, assigns three active centers to it, and sets a nightly payout run at 21:00 for each center — all without configuring individual employee payout preferences.

How to Use:

  1. Ensure your organization is registered in Canada and has at least one active center.
  2. Confirm you have the Configure Payment Settings permission (Configuration > Security > Security roles).
  3. Navigate to Configuration > Payments > Tips Payout to open the onboarding wizard.
  4. Step 1: Read the Canada-specific terms and conditions, select the acceptance checkbox, then select Save & Continue.
  5. Step 2: Enter account holder name, email address, bank name, branch transit number (5 digits), bank institution number (3 digits), account number (7–12 digits), and account type; accept the Pre-Authorised Debit agreement, then select Save & Continue.
  6. Confirm the micro-deposit amount from the verification email sent to the address entered in Step 2 to complete bank account verification.
  7. Step 3: Select each center to link to the verified bank account, then select Save & Continue.
  8. Step 4: For each linked center, set Enable tips payout to Yes, choose a Payout start date, configure Accumulate tips and Accumulation start date if needed, set Payout time (default 20:00), then select Save & Continue to complete the wizard.

Default behavior and validations: Enable tips payout defaults to No for each center. Payout time defaults to 20:00. Accumulate tips defaults to No. All bank account fields in Step 2 are required. The Save & Continue button on Step 1 is disabled until the terms checkbox is selected; on Step 2 it is disabled until all bank fields are complete and the PAD agreement checkbox is selected. Advancement to Step 3 is blocked until micro-deposit verification is confirmed. Only active centers appear in the Step 3 selection list. One automated payout run executes per center per day at the configured payout time.

Notes: The business bank account is the funding account Zenoti debits to cover all employee tip payouts for linked centers; employees set their own payout method (EFT or Interac) in the myZen app and cannot be configured here. Setting Payout start date to a past date may cause unexpected behavior on the first payout run; a future date is recommended. If multiple centers share one bank account, staggering their Payout time values reduces the risk of simultaneous debits. Micro-deposit verification notifications may take several minutes; check spam if not received promptly.

Learn more: Tips payout setup for your business in Canada

Automated tips payouts for Canadian centers via EFT and Interac

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: Zenoti now processes tips payouts for Canadian centers automatically on a daily schedule. The business bank account is debited by EFT for the total batch amount, and each enrolled employee is credited by their chosen method — EFT to a linked bank account or Interac to a registered phone number or email. This eliminates manual disbursement steps and ensures employees receive accumulated tips on a predictable cadence.

Business Scenario: A spa with three enrolled employees runs its payout at 10:00 PM. Zenoti calculates each employee's owed tips, debits the total from the business EFT account, and credits two employees by EFT and one by Interac — all without manual intervention. Each employee receives a payout notification automatically.

How to Use:

  1. Confirm your organization is onboarded for Canada tips payouts and that at least one center has passed its configured Payout start date.
  2. Ensure each participating employee is enrolled with a payout method (EFT or Interac) before the scheduled payout run.
  3. Grant payroll administrators and center managers the View permission under Configuration > Security > Security roles to access the Tips Payout Dashboard and related reports.
  4. Monitor payout outcomes in Reports > Tips Payout Details; hover over a Failed badge to read the failure reason, then select the inline Retry control if needed.
  5. For a reversed business debit, navigate to Reports > Tips Reconciliation, open the Payout View, and select the retry option.

Default behavior and validations: One payout run executes per day per center at the center's configured Payout time. Real-time or on-demand payouts are not available. The business is always debited by EFT regardless of the employee's chosen payout method. Interac payouts expire if the employee does not accept within 30 days. Failed payouts remain in Failed status until retried; they are not automatically moved to an employer-owed balance. If payouts are stopped for a center, tips continue to accumulate and are disbursed in full on the next run after payouts resume.

Notes: Organization must be onboarded for Canada tips payouts before this workflow is active. Each employee must be enrolled with a payout method prior to the scheduled run or they will not receive a payout in that cycle. A business debit reversal does not claw back tips already delivered to employees; the debit must be retried separately. Allow the standard EFT settlement window to elapse after any retry before rechecking status.

Learn more: How Canada tips payouts are processed

Updated permission description for viewing tips payout data

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: The permission requirement for viewing tips payout history, pending payouts, and summary graphs has been clarified. The description now refers to view access to tips payout reports rather than a specific security object name, and the permissions reference article has been updated to include recommended role assignments alongside the full permissions matrix.

Notes: No functional change to permissions or access control has been made; this update affects documentation language only. Refer to the Enable permissions for tips payout article for the complete permissions matrix and role guidance.

Learn more: Tips Payout overview

Tips payout configuration enhancements for sync delay, cutoff, and accumulation mode

Audience/Roles: Administrator

Overview: The tips payout configuration screen now includes a Use Calendar Days setting that controls whether the sync delay is counted in calendar days or business days. The Sync delay and Cutoff time fields now display -1 to indicate that no value is configured, making it clearer when a setting is absent rather than zero. The Payout start date field is now explicitly locked once a payout cycle has begun for that date, and the navigation path to center settings has been simplified by removing the intermediate Manage setup step.

Business Scenario: An administrator configuring a center with weekend-only closures can now select calendar days for the sync delay to ensure tips from Friday invoices are not held longer than intended, and can immediately see that no cutoff time is set (shown as -1) rather than assuming a zero-hour cutoff applies.

How to Use:

  1. Go to Configuration > Payments > Tips Payout.
  2. Select the center you want to configure.
  3. Set Sync delay and Cutoff time as needed; a value of -1 indicates no delay or cutoff is configured.
  4. Enable Use Calendar Days if the sync delay should be counted in calendar days rather than business days.
  5. Set or confirm the Payout start date, noting it cannot be changed once a payout cycle has started for that date.
  6. Click Save.

Default behavior and validations: Sync delay and Cutoff time display -1 when no value has been configured. The Payout start date can only be updated before a payout cycle has begun or when the computed sync datetime is still in the future. Use Calendar Days defaults to off. Configuration is per center; each center can have different values.

Notes: The Manage setup intermediate navigation step has been removed; centers are now selected directly from the Tips Payout page. Tips that accumulated while a center was inactive are disbursed in subsequent payout runs after reactivation. The Manage permission under Tips Payout Configuration is required to make any changes.

Learn more: Configure tips payout settings

Tax responsibilities guidance for Same Day Tips Payout

Audience/Roles: Business Owner, Administrator

Overview: Zenoti now provides structured guidance on the tax obligations that arise when using Same Day Tips Payout. Because Zenoti does not withhold taxes at the time of payout, employers must complete two actions each year: reconcile tip amounts from Form 1099-K gross receipts to avoid overstating business income, and report disbursed tip amounts through payroll each pay period to drive correct employee withholding, employer FICA remittance, and accurate Form W-2 reporting. Businesses using Zenoti Integrated Payroll (ZIP) have Responsibility 2 handled automatically, while Form 1099-K reconciliation remains a manual obligation for all businesses regardless of payroll platform.

Business Scenario: A spa owner using Same Day Tips Payout receives a Form 1099-K at year-end that includes all tips collected through the payment processor. Without adjustment, those tip amounts would inflate reported business revenue. The owner pulls the disbursed tip totals from Zenoti tips payout reports, subtracts them from gross card receipts, and retains the reports as supporting documentation — avoiding overpayment of business income tax while ensuring each employee's tips are correctly reflected on their W-2.

How to Use:

  1. Ensure your organization has completed Same Day Tips Payout onboarding before year-end.
  2. At year-end, navigate to your Zenoti tips payout reports and obtain the total tip amounts disbursed to employees during the year.
  3. Subtract the disbursed tip totals from your payment processor's Form 1099-K gross receipts when calculating net business income; retain the reports as supporting documentation.
  4. Each pay period, enter each employee's earned tip amounts in your payroll system under the Cash Tips earnings code — or confirm that Zenoti Integrated Payroll is handling this automatically.
  5. Consult your accountant or tax advisor to verify compliance with federal, state, and local tip reporting requirements, including any updated Form W-2 fields introduced by the IRS from 2026 onward.

Default behavior and validations: Zenoti does not withhold any taxes at the time of tip payout; the full tip amount is deposited to the employee's myZen Wallet or linked bank account. Employees have no separate tax action to take — all obligations rest with the employer. Zenoti Integrated Payroll (ZIP) automatically maps tips to the Cash Tips earnings code and handles employee withholding, employer FICA remittance, and W-2 reporting, but does not perform Form 1099-K reconciliation. The One Big Beautiful Bill Act (OBBBA) provides a federal income tax deduction of up to $25,000 for qualifying employees for tax years 2025–2028, claimed on the employee's personal return; FICA obligations for both employees and employers are unchanged.

Notes: Applies to US-based businesses using Same Day Tips Payout through Zenoti Payments (Adyen or Stripe). Viewing tips payout reports requires the Configure Payment Settings permission. Large food or beverage establishments with more than 10 tipped employees on a typical business day may also be subject to Form 8027 filing requirements. State income tax treatment of tip income varies; consult a qualified tax advisor. This guidance does not constitute tax, legal, or financial advice.

Learn more: Understand tax responsibilities for Same Day Tips Payout

Prescriptions

Automated ePrescription expiry and expired reminder notifications

Audience/Roles: Administrator, Business Owner, Center Manager

Overview: Zenoti now runs two daily scheduled jobs per center that automatically send email notifications to prescribers and guests when a prescribed medicine is approaching its expiry date or has expired. The advance-expiry reminder fires a configurable number of days before expiry, while the expired-medicine reminder fires on the day the medicine expires. Both jobs evaluate only the latest, non-voided, non-re-prescribed, and non-refill-denied ePrescription records, ensuring notifications are relevant and accurate.

Business Scenario: A medical spa prescribes a topical treatment with a 90-day supply. Thirty days before the medicine expires, the prescriber receives an email prompt to review the guest's prescription, and the guest receives a heads-up to schedule a follow-up. On the expiry date itself, both parties receive a second notification confirming the medicine has expired, reducing the risk of guests continuing to use an expired product.

How to Use:

  1. Confirm that the Enable Prescription toggle is turned on at the organization level; contact your Zenoti representative if it is not visible.
  2. Navigate to Configurations > ePrescribe settings > Manage centers and users (requires the Manage centers and users permission under ePrescriptions).
  3. Verify that the ePrescription expiry window setting is defined in your organization settings with a valid numeric value representing the number of days before expiry for advance reminders.
  4. Confirm that the ePrescription dashboard is enabled for each center that should receive notifications; centers without it enabled are skipped automatically.
  5. Once configured, both daily jobs run automatically — no manual trigger is required.

Default behavior and validations: The expired-medicine reminder runs daily for all qualifying centers regardless of the ePrescription expiry window setting. The advance-expiry reminder requires a valid numeric value in the ePrescription expiry window organization setting; if the setting is absent or non-numeric, the advance-expiry job does not run. Both jobs skip voided, re-prescribed, refill-denied, and non-latest-version ePrescription records. Centers without the ePrescription dashboard enabled are skipped entirely. Notifications are sent by email only.

Notes: The Enable Prescription toggle must be active at the organization level before any expiry notification jobs execute. Centers must have the ePrescription dashboard enabled; contact your Zenoti representative to confirm which centers qualify. If the ePrescription expiry window setting is missing or contains a non-numeric value, the advance-expiry reminder will not run until the setting is corrected.

Learn more: ePrescription Expiry and Expired Reminder Notifications

Queue

Clarifications to queue notifications, wait time, and position settings

Audience/Roles: Front Desk Operator, Center Manager, Administrator

Overview: Three reference-level clarifications have been made to the Front Desk Queue settings documentation. The 'Client ready for queue' notification now specifies that staff trigger it by selecting 'Ready for client' from the ellipsis menu on a waiting guest's queue card, and its description reflects that it notifies the guest their provider is ready. The 'Minimum wait time label' has been renamed 'Minimum guest wait time' and clarified as a functional eligibility threshold in minutes rather than a static display label. The path to the 'Show guest numbers in Queue view' permission has been updated to the full navigation path: Configuration > Security Roles > Permissions > Queue accordion.

Notes: A new note has been added clarifying that for notification types 9 (First Reminder) and 160 (Second Reminder), the queue automatically skips sending a duplicate if a pending notification of the same type already exists for the same appointment, preventing guests from receiving the same reminder more than once.

Learn more: Notifications and wait time reference

Reports

Custom KPI Reports setting seeded as disabled for new organizations

Audience/Roles: Administrator

Overview: When Zenoti provisions a new organization, the Custom KPI Reports setting is now automatically seeded as disabled at the organization level. This ensures a consistent, predictable starting state for all new organizations. Once an MMS Admin enables the setting, administrators can configure up to two additional percentage-based KPI columns with custom labels and service mappings, and the Custom KPI service types section becomes available for use in KPI calculations.

Business Scenario: A newly onboarded organization wants to track custom service-category performance in KPI reports. Because the setting ships disabled, the organization's Zenoti representative enables Custom KPI Reports for them, after which the center's administrator defines the column labels and service mappings before the columns appear in reports.

How to Use:

  1. Contact your Zenoti representative to request that Custom KPI Reports be enabled for your organization.
  2. Once enabled, select the Configurations icon in the main navigation.
  3. In the search field, type 'KPI reports setup' and select it from the results.
  4. Use the Custom KPI columns configuration setting to define labels and service relationships for columns 3 and 4.
  5. Use the Custom KPI service types section to configure custom labels and services for each custom type used in KPI calculations.
  6. Save your configuration.

Default behavior and validations: The Custom KPI Reports setting is disabled by default for all newly provisioned organizations. It is an organization-level setting and cannot be overridden at the center scope. Enabling the setting does not automatically configure any KPI columns; administrators must define custom columns and service mappings separately after activation. The setting is managed exclusively by an MMS Admin.

Notes: If the Custom KPI Reports setting is not visible on your organization's Configurations page, contact your Zenoti representative. Enabling the setting requires MMS Admin access and cannot be performed by organization-level administrators independently.

Learn more: Custom KPI Reports setting seeded for new organizations

Package reports navigation order updated

Overview: The Package reports article has been repositioned in the reports navigation, moving from sort position 1 to position 27. This reflects a reorganization of the reports section to better group related content.

Learn more: Package reports

Package Sales Financial report moved out of Legacy reports group

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: The Package Sales Financial report has been removed from the Legacy reports group and is no longer collapsed under that category. Its sort order has also been updated, placing it higher in the reports list for quicker access.

Default behavior and validations: The report now appears ungrouped in the reports navigation at an earlier sort position (999), rather than within the collapsed Legacy reports group.

Learn more: Package Sales Financial report

Direct Payments report

Overview: The Direct Payments report is now available under the Zenoti Payments reporting section. This report gives business owners and managers visibility into direct payment transactions processed through Zenoti Payments. The report lives in the Payments category, and the Reports section automatically redirects users to that location.

Notes: The article in the Reports > Zenoti Payments section is a redirect stub; the full report content is maintained under the Payments > Reports category. Users navigating to the Reports path will be automatically redirected to the Payments path.

Learn more: Direct Payments report

PayCom billing report article relocated to Payments category

Audience/Roles: Administrator, Business Owner

Overview: The 'Understanding and managing PayCom billing in Zenoti Payments' article has been moved from the Reports section to the Payments category. The previous Reports URL now automatically redirects to its new location in the Payments section. No report functionality has changed; only the documentation location has been updated.

Notes: The original Reports-section URL remains in the sidebar for discoverability but is retired as a standalone page. All links and bookmarks pointing to the old URL will be redirected automatically to the Payments category article.

Learn more: Understanding and managing PayCom billing in Zenoti Payments

Markup Fee and Secondary Markup Fee columns in the Digital Payments Report

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: The Digital Payments Report now includes two new columns — Markup Fee and Secondary Markup Fee — that expose the individual fee components applied to each digital payment transaction. These columns are available to all organizations without additional configuration and can be added to the report view through the column chooser. With this visibility, finance and operations teams can audit fee breakdowns, reconcile payment costs, and identify fee patterns by center, date range, or transaction type.

Business Scenario: A center manager reviewing monthly payment costs opens the Digital Payments Report, adds the Markup Fee and Secondary Markup Fee columns via the column chooser, and filters by center and date range to compare fee components across transaction types — enabling accurate cost reconciliation without manually cross-referencing external statements.

How to Use:

  1. Navigate to Reports and open the Digital Payments report.
  2. Open the column chooser from the column header area or the report toolbar settings icon.
  3. Locate Markup Fee in the available columns list and select it to add it to the report view.
  4. Locate Secondary Markup Fee in the available columns list and select it to add it to the report view.
  5. Apply your column selection to update the report grid.
  6. Use the date range, center, and transaction type filters to narrow results.
  7. Review Markup Fee and Secondary Markup Fee values alongside other transaction columns to analyze fee breakdowns.
  8. Export the report as needed for external analysis or sharing.

Default behavior and validations: Both columns are available to all organizations with no additional configuration required. Depending on your organization's default column visibility settings, the columns may be hidden by default and must be added manually via the column chooser. If a transaction does not carry a value in one or both columns, the corresponding fee component was not applicable to that transaction.

Notes: Access to the Digital Payments Report requires access to the Reports section in Zenoti. For organization and center payment settings, refer to the Configurations category.

Learn more: Digital Payments Report — Markup Fee and Secondary Markup Fee Columns

Membership Tries Report payment type filter deduplication

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: The Payment Type filter in the Membership Tries Report previously displayed a redundant All entry alongside the dropdown's built-in Select All control, creating two competing mechanisms for selecting all payment types. The standalone All entry has been removed, leaving the built-in Select All control as the single way to include all payment types at once. This eliminates filter ambiguity when analyzing recurring membership payment collection attempts. Report data and columns are unaffected by this change.

Business Scenario: A center manager reviewing dunning cycle results opens the Membership Tries Report and applies the Payment Type filter. Instead of seeing both an All entry and a Select All control, they now see only individual payment type options and a single Select All control, making it clear how to broaden or narrow the filter without confusion about which selection mechanism to use.

How to Use:

  1. Navigate to the reports area and open the Membership Tries Report.
  2. Locate the Payment Type filter in the filter panel.
  3. Open the Payment Type dropdown to view the payment type options — Card, Check, Cash, Others, and Custom.
  4. Select one or more individual payment types, or use the built-in Select All control at the top of the dropdown to include all payment types.
  5. Apply your filter selections to run the report.

Default behavior and validations: When all payment types are selected via Select All, the report returns data across all payment types — equivalent to running the report with no payment type filter applied. The removed All entry produced the same result; existing workflows relying on that entry should switch to using Select All.

Notes: This change affects filter presentation only; no report columns are added, removed, or renamed. Requires active recurring membership payment collection to be configured for the Payment Type dropdown to populate.

Learn more: Membership Tries Report

On-page navigation added to Packages reports article

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: A table of contents with anchor links has been added to the Packages reports documentation page. Users can now jump directly to the Package Liability v1, Package Status, or Package Refunds report sections without scrolling through the full article.

Default behavior and validations: The navigation block appears at the top of the page and links to all major sections and subsections within the article.

Learn more: Reports

Package Liability Report — Credit Card Liability Breakdown

Audience/Roles: Business Owner, Administrator

Overview: The Package Liability Report now includes a Credit Card Liability Breakdown that isolates package liability figures to transactions paid by credit card. A parallel set of columns — Opening Balance, Sales, Redemptions, Refunds, Suspense, Expired, and Closing Balance — appears alongside the standard liability totals, restricted to credit card–funded invoice items. This breakdown supports credit card balance reconciliation and financial audits by making it clear how much of your organization's outstanding package obligations are attributable to credit card payments. Both the by-sale and by-revenue/payment liability calculation methods are supported.

Business Scenario: A finance manager running a period-end audit needs to confirm how much of the organization's package liability is backed by credit card payments versus other payment types. By reviewing the credit card liability columns alongside the standard columns in a single report run, she can quickly determine the credit card–funded closing balance and reconcile it against the organization's credit card settlement records.

How to Use:

  1. Navigate to Admin > Reports > Packages.
  2. Select Package Liability report (v1) from the report list.
  3. Set the Date range, Center, Package type, and Liability type filters as needed.
  4. Select Run to generate the report.
  5. Review the credit card liability columns alongside the standard liability columns to compare credit card–funded figures against overall package liability totals.
  6. Contact your Zenoti administrator if you need the credit card liability breakdown included in a scheduled or daily liability snapshot report, as the credit card liability mode is not a user-selectable toggle in the standard report UI.

Default behavior and validations: The credit card liability breakdown is computed only when the credit card liability mode is active for the report run; it is not a user-selectable toggle in the standard report UI and is intended for internal callers such as the daily liability snapshot. When this mode is active, pagination and total-row-count result sets are skipped and full detail rows are returned directly. Both by-sale and by-revenue/payment liability types are supported. Required permissions: Edit on the Packages security object; Edit on the Custom Package security object if custom packages are in use; Edit on the Package Categories security object if filtering by package category.

Notes: Confirm with your finance team which liability calculation method (by-sale or by-revenue/payment) your organization uses before interpreting results. To have the credit card liability breakdown surfaced in a scheduled report, contact your Zenoti administrator.

Learn more: Package Liability Report — Credit Card Liability Breakdown

Package reports navigation and permission labels updated

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: Package reports are now accessed from Admin > Reports instead of the Reports Dashboard, and the report interface now uses an advanced grid view instead of the interactive data grid. Permission group and permission names have been updated to remove underscores, now displayed as Marketing Reports V2, Financial Reports V2, Packages Report, Packages Payments Report, Packages Liability Report, and Package Benefits Detail Report. A new Package Benefits Detail Report permission has also been added to the documented permission list.

Business Scenario: A Center Manager who previously bookmarked the Reports Dashboard to reach the Package Liability report can now navigate directly via Admin > Reports, and can verify their access using the updated permission names shown in the permission panel.

How to Use:

  1. Navigate to Admin > Reports.
  2. Use the search field or browse the report list to locate the package report you need.
  3. Click the report name to open it in the advanced grid view.
  4. Configure filters in the filter panel (date range, date type, centers, package categories) and apply them.
  5. Export results using the flat-file export option in the report toolbar.

Default behavior and validations: All four package reports — Packages, Package Payments, Package Liability, and Package Benefits Detail — follow the same access pattern. Each report requires its own permission under either Marketing Reports V2 or Financial Reports V2.

Notes: If you have existing bookmarks or direct links pointing to the Reports Dashboard for package reports, update them to use Admin > Reports. Permission names no longer use underscores; verify role assignments reflect the updated naming.

Learn more: Package reports

On-page navigation added to Loyalty Reports article

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: A table of contents with anchor links has been added to the top of the Loyalty Reports documentation page. Users can now jump directly to any report section—such as Guest Feedback Summary, Guest Retention Summary, Turnaways, or Employee Tasks—without scrolling through the entire article.

Default behavior and validations: The table of contents appears at the top of the page and links to all major sections and subsections covered in the article.

Learn more: Reports

Gift Card Liability report: CC liability breakdown and bonus gift card refund correction

Audience/Roles: Business Owner, Administrator

Overview: The Gift Card Liability report now supports two specialized computation modes for internal liability reconciliation. The CC liability breakdown isolates gift card liability attributable to credit card purchases, returning a per-center breakdown of Opening Balance, Sales, Redemptions, Refunds, Suspense, Expired, and Closing Balance figures filtered to credit card–purchased gift cards only. The bonus gift card refund correction adjusts value-based liability figures when a bonus card's parent sale invoice has been refunded, preventing inflated liability totals and ensuring each bonus card is adjusted exactly once regardless of when the refund was recorded.

Business Scenario: A finance administrator running the daily liability snapshot needs to isolate how much outstanding gift card liability is attributable to credit card purchases. By using the CC liability breakdown mode, they receive a per-center view of only credit card–attributed transactions. Separately, when a promotional bonus gift card was issued alongside a sale that was later refunded, the bonus gift card refund correction automatically reduces the Opening Balance or Refunds column—depending on when the refund occurred—so the liability report reflects the true outstanding balance without manual adjustments.

How to Use:

  1. Navigate to Configuration > Gift cards > Gift card settings.
  2. Select the Reports section from the main navigation.
  3. Locate and open the Gift Card Liability report.
  4. Set your reporting period using the Start Date and End Date filters.
  5. Select the centers to include in the report.
  6. Set the Liability Type filter to Value-based to enable the bonus gift card refund correction; leave it as appropriate for CC liability breakdown use.
  7. Apply any remaining filters, then select Run to generate the report.
  8. Review CC liability breakdown columns (Opening Balance, Sales, Redemptions, Refunds, Suspense, Expired, Closing Balance) for credit card–attributed figures, and verify bonus gift card refund corrections in the Opening Balance, Refunds, and Closing Balance columns as applicable.

Default behavior and validations: The CC liability breakdown mode is intended for internal automated callers (such as the daily liability snapshot); when active, the report does not return record counts, totals result sets, or apply row-limit filtering. The bonus gift card refund correction applies only when Liability Type is set to value-based; quantity-based liability reports are not affected. Payment type attribution differs by record type: redemption rows inherit the payment type of the original sale, while sale and refund rows use their own payment type. A double-count guard ensures a bonus card whose parent sale was refunded before the period start date is not also counted in the within-period Refunds column.

Notes: Access to the Gift Card Liability report requires permissions to the gift card reports section. The bonus gift card refund correction is triggered by a refund record on the parent sale invoice, not on the bonus card itself. When comparing Opening Balance figures across consecutive report periods, verify that the prior period's Closing Balance matches the current period's Opening Balance, as retroactively applied bonus gift card refund corrections may cause discrepancies.

Learn more: Gift Card Liability Report — CC Liability Breakdown and Bonus Gift Card Refund Correction

Waitlist V2 reporting for waitlist activity and conversion tracking

Audience/Roles: Business Owner, Center Manager, Front Desk Operator, Administrator

Overview: The Waitlist V2 report provides a structured view of waitlist activity across one or more centers, showing each waitlist group with guest details, service information, appointment status, booking type, and financial data. Staff can track how open slots were filled, identify no-shows and turnaways, and measure how much waitlist conversion was handled automatically by the first-in-line engine versus manually by staff. The report also surfaces appointment value and applicable no-show fees, giving operations teams visibility into the revenue impact of waitlist activity. Pagination and count-only mode allow high-volume centers to retrieve record counts before paging through large result sets.

Business Scenario: A zone manager wants to review last month's waitlist performance across three locations. She runs the Waitlist V2 report filtered to those centers and the relevant date range, checks the record count first to gauge volume, then pages through results. She can see which appointments were auto-booked by the first-in-line engine, which required manual intervention, and which guests were turned away or did not show — along with the no-show fees that applied.

How to Use:

  1. Confirm that waitlist management is enabled for your organization with the version set to First in line.
  2. Navigate to the Reports area within the Appointment Book module.
  3. Select the Waitlist V2 report.
  4. Specify one or more centers, your date range, and pagination settings.
  5. Optionally enable count-only mode to retrieve the total record count before loading full detail rows.
  6. Run the report and review waitlist group rows, including appointment status, booking type, appointment value, and no-show fee columns.
  7. Expand add-on and provider detail result sets for each waitlist group as needed.

Default behavior and validations: The report returns paginated detail rows by default; count-only mode must be explicitly requested. Appointment booking type is blank when the booking method cannot be determined. Valid appointment status values are NoShow, Confirmed, Turnaway, and Waitlist. When the number of matching records exceeds the configured row count cap, the report returns an over-limit status instead of detail rows, and the date range or center filter must be narrowed before re-running.

Notes: Requires waitlist management to be enabled with the version set to First in line. Users must have access to the Reports area of the Appointment Book module and to the specific centers whose data they want to review.

Learn more: Waitlist V2 reporting overview

Canada tips payout reports for enrollment and transaction monitoring

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: Two new reports are now available for Canadian centers using tips payout: the Tips Payout Adoption Report and the Tips Payout Details report. The Adoption Report tracks each employee's enrollment progress through statuses such as Not Started, Bank Account Pending, and Enrolled, and displays an adoption rate across centers. The Tips Payout Details report shows every payout transaction with numeric status codes, payment method, and payout amounts in CAD, and allows administrators to retry failed payouts directly from the report.

Business Scenario: A payroll administrator at a multi-center Canadian organization notices a low adoption rate in the Adoption Report and uses the Onboarding Status filter to identify employees still at the Bank Account Pending stage. They follow up with those employees, then use the Tips Payout Details report to confirm that a previously failed EFT transfer has been resolved and retry it without leaving the page.

How to Use:

  1. Go to Configuration > Payments > Tips Payout.
  2. Open the Reports tab.
  3. Select Adoption Report to view employee enrollment status, summary chips, and the adoption rate; use filters for Employee Name, Center, Onboarding Status, Employee Job, or Date Range, then select Apply.
  4. To opt out an employee, locate their row in the Adoption Report, select Opt-Out in the Action column, and confirm the prompt.
  5. Select Tips Payout Details to view payout transactions; use filters for Employee Name, View Type, Payout Type, Center, Payment Method, Payout Status, or Date Range, then select Apply.
  6. To investigate a failed payout, hover over the Payout Status column to read the failure reason, resolve the underlying issue, then select Retry on the failed row.

Default behavior and validations: The Adoption Report reflects enrollment status in real time. The Tips Payout Details report shows records for the selected date range, available immediately after each payout run completes. Interac payouts expire if unclaimed within 30 days. EFT payouts take 1–2 business days. The reports do not include Physical Card, Virtual Card, Account Upgrade Status, KYC Status, Wallet Status, Wallet Balance, or SSN columns. Hovering over an Enrolled status reveals the last four digits of the bank account (EFT) or the employee's phone number (Interac). The MyZen Tips Adoption Report permission is required for the Adoption Report; the Access Zenoti wallet bank account details permission is required to view bank account details.

Notes: Tips payout must be enabled for at least one Canadian center before these reports are accessible. Tips earned but not yet paid out will not be disbursed after an employee is opted out. Retrying a failed payout without resolving the root cause will result in another failure.

Learn more: Canada tips payout reports

Tips Payout

Canada Interac tips payout: permission label, status 8 behavior, and enrollment flow updates

Audience/Roles: Business Owner, Center Manager, Administrator

Overview: Several updates have been made to the Canada same-day tips payout workflow. The permission required to access tips payout configuration and retry workflows is now labeled 'Configure Payment Settings' (previously 'TipsPayoutConfiguration'). Status 8 (Center Payouts Stopped / Business Paused) now clarifies that tips accumulate during a pause and are disbursed when payouts resume. The Interac enrollment flow now requires confirming both the employee's phone number and email address, and the non-Canada report filter behavior has been updated to automatically apply status 1 when the filtered result set would otherwise be empty.

Business Scenario: A center manager at a Canada-based center notices payouts are paused (status 8) and reassures employees that their tips are not lost — accumulated tips will be disbursed automatically once payouts resume. When enrolling a new employee via Interac, the manager now confirms both the pre-filled phone number and email address on the Payment Method screen before saving.

Default behavior and validations: For Interac enrollment, the Payment Method screen pre-fills the employee's phone number (marked as Primary) and email address; no bank coordinates are required. For non-Canada organizations, if the status filter would return an empty result set after being restricted to status 1, status 1 is applied automatically.

Notes: The 'Configure Payment Settings' permission replaces the former 'TipsPayoutConfiguration' permission label for tips payout configuration and retry access. If either the phone number or Interac email address needs to be updated, the employee must update their wallet details before the next payout run. For status 8 issues, contact your Zenoti administrator to determine when center payouts will be reactivated.

Learn more: Same day Tips payout in Canada

Zenoti Driven Growth

Zenoti Integrated Payroll

Instructor Pay earning type for payroll mapping

Audience/Roles: Administrator

Overview: Zenoti Integrated Payroll (ZIP) now supports a dedicated Instructor Pay earning type that payroll administrators can map to instructor compensation during business onboarding. Once mapped, ZIP recognizes instructor pay as a distinct category and passes it to the payroll earnings staging process alongside other earning types such as Service Commission, Hourly Pay, and Salary. This ensures instructor compensation appears as a separate line item in payroll runs and payroll register reports, making it straightforward to reconcile instructor costs independently from other compensation categories.

Business Scenario: A fitness studio employs several yoga instructors whose compensation is tracked in Zenoti. During onboarding, the payroll administrator maps the instructor compensation category to the Instructor Pay earning type. When payroll is run for the period, each instructor's earnings appear as a distinct Instructor Pay line in the payroll summary, separate from service commissions and hourly pay, simplifying cost reconciliation.

How to Use:

  1. Navigate to Employees > Zenoti Integrated Payroll.
  2. In the right-side menu, select Settings.
  3. Locate the earning type mapping section within your payroll configuration settings.
  4. Find the instructor compensation row and set the earning type to Instructor Pay.
  5. Map any additional earning types required for your organization (Service Commission, Product Commission, Hourly Pay, Salary, Additional Pay, Total Hourly Pay).
  6. Save your changes.
  7. To verify, select Payrolls from the right-side menu, open or initiate a draft payroll run that includes instructors, and confirm that instructor compensation appears under the Instructor Pay earning type in the earnings breakdown.

Default behavior and validations: Earning type mappings must be configured manually during business onboarding; they are not pre-populated. Mapping changes apply only to future payroll runs — the run in progress at the time of a change retains the mapping that was active at initiation. Once a payroll run is initiated, compensation data is frozen; amounts added after initiation will not appear in that run.

Notes: ZIP must be fully enabled for your tenant by Zenoti's implementation team before the Instructor Pay earning type appears in the mapping list. The Configure Payroll Payouts permission is required to access earning type mapping settings. Instructors must be set up as employees in Zenoti with compensation tracked through Zenoti's instructor pay functionality before mapping will produce results in payroll runs.

Learn more: Instructor Pay Earning Type

Payroll Earnings Summary Breakdown

Audience/Roles: Administrator

Overview: A new center-level setting in Zenoti Integrated Payroll (ZIP) lets payroll administrators decompose hourly earnings into granular sub-components during the payroll summary import. When enabled, a single aggregate hourly earnings row is replaced by two distinct line items — straight-time pay and overtime premium — each carrying hours worked and the applicable rate as metadata. At the same time, service commission and product commission rows are updated with their final calculated values, replacing amounts carried forward earlier in the payroll run. This gives payroll reviewers line-item visibility to verify calculations without changing how earnings are computed.

Business Scenario: A payroll administrator at a multi-location business needs to audit overtime costs for the Downtown center before approving payroll. With earnings summary breakdown enabled for Downtown, the next payroll summary import produces separate straight-time pay and overtime premium line items, making it straightforward to confirm that overtime was applied correctly. The Uptown and Midtown centers continue using aggregate rows and are unaffected.

How to Use:

  1. Navigate to Admin > Settings > Payments for the center you want to configure.
  2. Locate the earnings summary breakdown option.
  3. Enable the setting for that center.
  4. Select Save.
  5. Repeat these steps separately for each additional center that requires granular earnings breakdown.

Default behavior and validations: The setting is disabled by default. When disabled, the payroll summary import uses existing aggregate earning-type rows with no sub-component breakdown and no commission row replacement. The setting is scoped per center; enabling it for one center has no effect on any other center in the organization. The overtime premium sub-component appears only when overtime hours are present for an employee in the pay period.

Notes: ZIP must be enabled for your tenant by Zenoti's implementation team before this setting is available. The Configure Payroll Payouts permission is required to access and modify payroll configuration settings. Review any in-progress payroll runs before enabling or disabling this setting, as changing it mid-run may produce inconsistent earnings rows within the same payroll period. The setting affects how earnings data is structured during the payroll summary import only — it does not change how earnings are calculated.

Learn more: Payroll Earnings Summary Breakdown

Was this article helpful?
Your feedback helps us improve our documentation.