ZenotiHelp

Deposit collection

ZTZenoti Docs Team Updated November 3, 2026 3 min readGuide

SmartBot can collect deposits from guests during the appointment booking flow when services require prepayment. Deposit processing is handled entirely through Zenoti's existing payment system β€” SmartBot coordinates the collection but does not maintain a separate payment gateway.

Audience: Administrators configuring deposit requirements and staff understanding how deposits work in SmartBot.

Why use deposit collection

Deposit collection is purpose-built as a no-show / last-minute-cancellation prevention mechanism. The business value is threefold:

  • Secures client commitment β€” guests who pay an upfront deposit are more likely to keep their appointment.
  • Minimizes revenue loss β€” when no-shows do happen, the deposit recovers some of the lost revenue.
  • Improves cash-flow predictability β€” deposits move part of the revenue from the appointment date to the booking date.

Before you begin

  • Deposit rules must be configured in Zenoti for the services that require prepayment.
  • Deposit collection must be enabled in the business configuration for the center.

Deposit types

You configure two deposit models on the underlying Zenoti service:

  • Flat-rate β€” A fixed monetary amount, regardless of the service price (for example, a $25 deposit on every massage booking).
  • Percentage-based β€” A percentage of the service price (for example, 20% of the service total).

SmartBot reflects whichever model is configured on the service β€” the deposit amount the guest sees is computed based on that model and the chosen service.

How deposit collection works

SmartBot checks for deposit and card-on-file requirements together as part of the appointment booking flow, after the guest has selected their services and time slot. This check runs only after the appointment slot has been successfully reserved.

The check evaluates deposit and card-on-file requirements in the following order:

  1. If a deposit is due β€” SmartBot presents the deposit amount to the guest and requests confirmation. Upon confirmation, the deposit is charged through Zenoti's payment processing system β€” the same payment gateway that powers center-side appointments and Webstore checkouts. After the deposit is collected, SmartBot confirms the appointment. If the guest has a saved card on file in their Zenoti profile, SmartBot can use that card; otherwise, the guest receives a secure card link to complete the payment.
  2. If no deposit is due and the center has card-on-file enabled β€” SmartBot checks whether the guest has a saved payment card. If no card is saved, SmartBot generates a card link so the guest can save one before the appointment is confirmed.
  3. If neither a deposit nor a card on file is required β€” SmartBot proceeds directly to booking confirmation without requesting any payment.

Note: SmartBot does not maintain a separate payment gateway. Card data flows through the same payment-gateway integration used for center-side appointments and Webstore checkouts.

If the deposit cannot be collected (for example, the configured payment options are unavailable for the guest), the booking flow continues per the center's deposit-failure policy and the deposit may need to be settled at the center.

Tips

  • Configure deposit amounts on individual services in Zenoti before enabling SmartBot booking for those services. Guests will see the deposit amount that is set on the service at the time of booking.
  • Use percentage-based deposits when service prices vary by provider or duration, so the deposit always reflects a consistent proportion of the total.
  • Use flat-rate deposits for high-demand services where you want a predictable, fixed commitment from the guest regardless of service variant or add-ons.

Troubleshooting

Problem Resolution
Guest is not prompted for a deposit even though one is configured on the service. Confirm that deposit collection is enabled in the business configuration for the center. Also verify that the deposit rule is correctly saved on the service in Zenoti β€” SmartBot reads the deposit requirement at booking time from the service configuration.
Guest receives a card link but already has a card saved. Check the guest's Zenoti profile to confirm the saved card is valid and not expired. An expired or removed card is treated the same as no card on file.
Deposit is not being collected before appointment confirmation. The deposit and card-on-file check runs only after the appointment slot is successfully reserved. If reservation is failing earlier in the flow, the deposit step will not be reached. Review earlier booking-flow configuration for the affected services.
Was this article helpful?
Your feedback helps us improve our documentation.