ZenotiHelp

Configure appointment cancellation reasons

ZTZenoti Docs Team Updated September 4, 2026 4 min readHow-to

Reason settings define the predefined options that staff select when cancelling, deleting, turning away, marking no-shows, or refunding appointments. Each reason type has its own section with a dedicated reason management interface. Reasons can be configured at the organization, zone, and center levels, providing flexibility to maintain a consistent global set of reasons while allowing local additions.

Before you begin

  • You need administrator access at the organization, zone, or center level, depending on the scope of reasons you want to manage.
  • Some booking rule settings (such as Record a reason for no-show appointments and Record a reason for refund invoice) must be enabled in Configure appointment booking rules for these reasons to be enforced during workflows.

Permission: Add or Edit under Reasons in the Administrator section β€” required for managing reason entries in each section.

  1. Navigate to Configuration > Appointments.
  2. Scroll past the Personalization section to the five reason rows and open the one you want to manage: Cancellation reasons, Deletion reasons, Turnaway reasons, No-show reasons, or Refund reasons. The rows sit directly on the Appointments page, and each opens its own page (for example, Appointment and Queue management > Turnaway reasons).
  3. Each reason page displays an embedded reason management interface where you can add, edit, and organize reasons.

Section 1: Cancellation reasons

Cancellation reasons are selected when an appointment is cancelled. These reasons help you track why guests or staff cancel appointments, providing data for reporting and analysis.

Setting Type Description
Cancellation reasons Manager (embedded) Create, edit, and manage cancellation reason entries. Each reason can be activated or deactivated and assigned to specific scopes. Available at organization, zone, and center levels.
Use in online booking Checkbox (per reason) When selected, the cancellation reason is made available to guests cancelling appointments through the Webstore (online booking channel). Reasons without this checkbox enabled are visible only to staff.

When staff cancel an appointment, a dialog prompts them to select a reason from the predefined list. If cancellation fees are configured, the reason is recorded alongside the fee transaction. Cancellation reasons appear in appointment audit reports and cancellation analytics.


Section 2: Deletion reasons

Deletion reasons are selected when an appointment is permanently deleted from the system. Appointment deletion is a more severe action than cancellation, and these reasons help maintain an audit trail.

Setting Type Description
Deletion reasons Manager (embedded) Create, edit, and manage deletion reason entries. Deletion reasons are tracked in the audit log for compliance and reporting. Available at organization, zone, and center levels.

When staff delete an appointment they select a reason before confirming the deletion. If Make it mandatory to record a comment when deleting appointments is on in the booking rules, staff must also provide free-text comments alongside the reason. Deletion reasons are logged in the system audit trail.


Section 3: Turn-away reasons

Turn-away reasons are selected when a guest is turned away from receiving a service. Turn-aways represent potential lost revenue and are tracked for business analysis.

Setting Type Description
Turn-away reasons Manager (embedded) Create, edit, and manage turn-away reason entries. Turn-away data feeds into the waitlist and lost revenue analytics. Available at organization, zone, and center levels.

When a guest cannot be served and must be turned away, staff record the turn-away with a reason. Turn-away data integrates with the waitlist feature. When a turn-away is recorded, the guest can optionally be added to the waitlist for the next available slot. Turn-away analytics help you understand demand patterns, staffing gaps, and capacity constraints.


Section 4: No-show reasons

No-show reasons are selected when a guest does not arrive for their scheduled appointment. Tracking no-show reasons helps you identify patterns and adjust your no-show policies.

Setting Type Description
No-show reasons Manager (embedded) Create, edit, and manage no-show reason entries. No-show reasons are linked to fee calculations and guest history analytics. Available at organization, zone, and center levels.

When staff mark an appointment as a no-show, they must select a reason if Record a reason for no-show appointments is on in the booking rules. If no-show fees are configured, the fee is applied automatically when the no-show is recorded and the reason is attached to the fee transaction. No-show reasons appear in guest history so staff can see a guest's no-show patterns when booking future appointments.


Section 5: Refund reasons

Refund reasons are selected when a refund is processed for a service. These reasons provide accountability and are tracked for financial reporting.

Setting Type Description
Refund reasons Manager (embedded) Create, edit, and manage refund reason entries. Refund reasons are linked to financial audit reports. Available at organization, zone, and center levels.

When staff process a service refund, they must select a reason if Record a reason for refund invoice is on in the booking rules. The Allow refunds on services toggle in Configure appointment essentials must be enabled for refund processing to be available. Refund reasons are logged in financial reports and audit trails.


Tips

  • Configure all five reason types before your centers begin operations. Having predefined reasons ensures consistent data collection from day one.
  • Reasons are scoped at organization, zone, and center levels. Start with a standard set at the organization level, then add center-specific reasons only when necessary to keep reporting consistent.
  • Review reason usage reports quarterly. If a reason is rarely selected, consider merging it with a more general option. If one reason is selected disproportionately, consider splitting it into more specific options.
  • Reason enforcement settings in booking rules are separate from reason configuration. You can create reasons without requiring them β€” enforcement toggles control whether staff must select a reason before completing the action.
  • Turn-away reasons are especially valuable for understanding unmet demand. Pair them with the waitlist feature to convert turn-aways into rebooked appointments.
Was this article helpful?
Your feedback helps us improve our documentation.