1!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{};e.SENTRY_RELEASE={id:"1.0.0"};var n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="09863da9-8877-4ba5-b36e-2b67d872e68e",e._sentryDebugIdIdentifier="sentry-dbid-09863da9-8877-4ba5-b36e-2b67d872e68e")}catch(t){}}();const e="__RESOFLOW_HELP_BODY__",n="Open the booking and click **Cancel** on its action bar. What happens next depends on whether the customer paid a deposit. Cancelling needs the booking-cancel permission; refunding a deposit also needs the refund permission.\n\n## Cancelling a booking with no deposit\n\n1. Click **Cancel**. For a booking with a customer email, a pop-up titled **Cancel this booking?** appears with **Add a personal note (optional, max 500 chars)** â anything you type appears in the cancellation email to the customer.\n2. A confirmation dialog follows. When the customer can actually be reached, it shows a ticked **Notify the customer by email** / **Notify the customer by text message** / **Notify the customer by email and text message** box â the wording matches exactly which messages will send for this booking. Leave it ticked to notify the customer, or untick it to cancel silently.\n3. Click **Confirm** to cancel, or **Go Back** to back out.\n\nIf the customer can't be notified automatically â no email address or mobile number on file, or your cancellation notifications are switched off in Settings â the dialog says so plainly instead of promising a notification, and no notify box is shown. The booking moves to the **Cancelled** tab either way.\n\n## Cancelling a booking with a paid deposit\n\nA **Cancel Booking** dialog appears with three choices:\n\n- **Cancel & Issue Refund** â cancels and returns the deposit to the customer's card. You'll be asked to confirm your password (or approve with a manager's PIN where offered).\n- **Cancel & Retain Deposit** â cancels and keeps the deposit. No password prompt, since no money moves.\n- **Go Back** â changes nothing.\n\nIf the customer is already outside your refund policy (for example, past the refund cut-off, or under a no-refund policy), the refund button reads **Refund deposit anyway** â an explicit override.\n\nThis dialog carries the same ticked **Notify the customer by â¦** box as the plain cancel â untick it to cancel without messaging the customer. The deposit choice and the notify choice are independent: keeping or refunding the deposit works exactly the same either way.\n\nA **paid-in-full booking** gets the same choice with honest wording â the dialog says the booking \"was paid in full\", and the buttons read **Refund payment anyway** / **Cancel & Retain Payment**.\n\nIf the booking or its payments change while cancellation is being confirmed, ResoFlow stops that request and asks you to review the latest details before confirming again. This protects your refund or retain choice from a payment arriving at the same moment. Guests cancelling online also review the amount still held after any earlier refunds; if that amount changes, they must confirm the updated warning.\n\n## Original terms and payment reviews\n\nChanging todayâs refund settings does not rewrite the terms already agreed for a confirmed booking. ResoFlow uses the structured original agreement when it can verify it. It keeps any valid booking holdâs agreed terms too.\n\nA booking made before ResoFlow began recording the agreed terms (8 September 2026) carries no record to verify, so it is handled exactly as it always was: its refund, its cancellation deadline and any fee follow the venue's current settings, and it never needs a review. For a booking whose recorded terms cannot be verified, a guest can still cancel immediately. The request time is recorded and only the uncertain money goes to **Booking payment reviews**. A booking with no outstanding money and no possible saved-card fee does not need a financial review. ResoFlow does not guess a fee, a refund or a forfeiture from old policy prose or from a record it cannot verify.\n\nStaff with booking-refund permission can open the review from the bookingâs details or **Payments â Booking payment reviews**. Check the original policy record if available, or document an agreement with the guest. Use the existing **Refundâ¦** control to return any agreed amount, then refresh the amounts. Record the reason and agreement reference before confirming exactly how much remains retained. Closing the review records the settlement; it does not move money or replace the original policy. Any uncertain fee is waived. A payment operation still processing must be reconciled before the review can close.\n\nIf another person changes the booking or payment, your notes stay in the review and you must refresh and check the new amounts before saving again.\n\nSwitching off fee collection prevents the corresponding fee under the existing operational rules. Turning off the fee alone does not remove an established ordinary online-cancellation deadline. Losing the planâs booking-rule feature keeps the existing rule that removes that online deadline. Neither change increases an agreed fee or substitutes todayâs refund policy for the original one.\n\n## Restoring a cancelled booking\n\nOpen the cancelled booking and click **Restore**. It returns to confirmed if its tables are still available. If the original place is now occupied, ResoFlow offers suitable tables or times within the next two hours of that service, keeping the party size and duration. Your selection is checked again before restoring; if nothing suitable is offered, keep the booking unchanged and edit its date, time or tables first. If the deposit (or full payment) was refunded when it was cancelled, the pop-up warns that it won't be re-charged and points you at **Request payment** on the booking â send the customer a [payment link](faq-payment-links) if you need to collect it again.\n\n## Cancel vs delete\n\nWalk-ins and waitlist entr
1ies (including self-service waitlist joins) show **Delete** instead of **Cancel** â they never received a booking confirmation, so deleting removes the entry without sending the customer anything. Cancelling keeps the record in the **Cancelled** tab and can notify the customer.\n\nDeclining a **pending** online request works the same way as cancelling â see the pending-bookings guide.\n\nRelated: [When do customers get their deposit back?](deposit-refunds) · [How do payment links work?](faq-payment-links) · [How do I approve or decline online booking requests?](pending-bookings) · [How do I mark a no-show (and charge the fee)?](mark-a-no-show) · [How do approvals with a manager's PIN work?](approve-with-manager-pin)";export{e as __helpBodySentinel,n as default}; 2//# sourceMappingURL=cancel-a-booking-DdyW6iaS.js.map
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.