How do I approve or decline online booking requests?
With manual confirmation on, online bookings — all of them, or only big parties and short-notice bookings — arrive as requests you approve or decline, and so do guests' changes.
Online bookings arrive as pending requests when Approve online bookings before they’re confirmed is switched on in Settings → Bookings → How people book, under Approving online bookings. The setting is Available on Plus plan and above. Staff-created and imported bookings always confirm automatically.
Approve every online booking, or only some
With the switch on, every online booking waits for your team — unless you also switch on Approve only some online bookings. Then only the bookings caught by the conditions you set wait:
- Parties of this many or more wait — for example 8, so big tables get a human eye;
- Bookings made less than this many hours ahead wait — counted from when the guest books to the booking's time.
Set either to 0 to turn that condition off. With Approve only some online bookings on and neither condition set, no online booking would wait, and the page says so with a link to approve every online booking instead.
A special date can have its own rule on Settings → Bookings → Special dates (Approving online bookings: Approve every one or Confirm straight away), and it wins on its day. Which wins: "A special date's own approval rule wins on its day; otherwise approving only some bookings works only while approval is on, and a request from a party bigger than your online maximum always waits for approval."
Approving or declining
- Find the request — EVERY booking waiting for your approval, whatever its date, is on the Bookings page's Requests tab: the one waiting longest first, with its day, time, party, name, where it came from, the guest's note and how long it has waited, and Approve and Decline on each row (a request whose day has already passed is marked "Date has passed", with no Approve or Decline — see below). The All venues Home shows one line per venue with requests waiting, and the Bookings item in the menu counts them. A request for today also shows on its day's Active tab with an Approve button on its row and under Needs you on Home (labelled "Awaiting approval"). Requests for later dates aren't listed again under Coming up (on Home and below Needs you on the Bookings list) — it shows one line, "2 requests waiting", and Requests → opens the tab. It doesn't matter why it waits — your own switch, a special date that approves every booking, or a bigger party's request: each one shows in all of these places. When only some bookings wait, a chip beside the status says why: Big party, Short notice or Special date.
- Open the booking. Its action bar shows two buttons: Approve and Decline (the Approve button also sits on the row itself in the list and on Home).
- Click Approve to accept — the guest then receives the booking confirmation email (and SMS, if enabled). With a saved card for the deposit it reads "Approve & take £40" and takes it.
- Click Decline to turn it down — this cancels the request, in one step. For a request with a guest email, a pop-up titled Decline this booking request? opens with Add a personal note (optional, up to 500 characters) — anything you type appears in the declined-booking email — and a ticked Notify the guest by … box when the guest can be reached: leave it ticked and they receive the declined-booking email; untick it to decline silently. Click Decline request and it's done. (A request with no email shows the same question and box as one short confirmation.) A card saved for the deposit is released; a deposit already paid is refunded in full automatically, whatever your refund policy says, and the pop-up says so. With Cancelled by your team texts switched on (Settings → Guest notifications), the guest is also texted the request's own words — "The Bistro couldn't confirm your booking request for Saturday 14 November at 7:00pm. Nothing has been charged." (or that what they paid is being refunded) — never your cancellation wording, because they never had a booking. When they saved a card, the declined email also says nothing was taken and the card is released.
To approve several at once, press Select at the top of the Requests tab, tick them (or Select all) and press Approve: each is approved exactly as its own Approve would — any saved card is charged for that booking — and one message says how many went through and names any that couldn't (open it to see why). A guest's change and a request whose day has passed are still answered one at a time.
When a request goes over one of your limits
A request is judged against your limits as the day is when you look at it — the day may have filled since it came in, and a bigger party's request isn't held to your limits at all unless Stop requests on days that have reached my limits is on (Settings → Bookings → How people book). When it goes over Most guests seated at once, a food or drinks-only limit or one of your pacing rules, it says so in orange on its row on the Requests tab, on Home, under Needs you, on the Bookings list and in its panel, naming the limit and the count — for example "Over your limit — Max evening Start up: 46 of 45 guests".
Pressing Approve on it — anywhere, or giving it a table on the floor plan or timeline — first asks, with the same warning your team gets for its own bookings: "This takes the whole day to 46 covers; the limit is 45." and Approve anyway or Go back. A limit that also stops your team (a pacing rule set to Block staff too, or Most guests seated at once with its Also stop your team switch on) offers no Approve anyway — open the request to change its time or party size, or decline it; a pacing rule set to Block staff too refuses that approval wherever it comes from. With Select, the requests that go over are named first and the rest are approved only when you say yes; one a limit stops your team on is left out.
When a request's date passes unanswered — an old request can't be approved
A request can only be approved until its day is over. From 5am the morning after (your venue's time — the same moment your day turns over everywhere else), it shows "Date has passed" with no Approve or Decline — approving it would confirm a day that's already gone, so ResoFlow won't, wherever you press it. Early that morning it closes on its own as Expired — not answered in time:
- it leaves the Requests tab and every request count (Home, the menu, the bell);
- a deposit they paid goes back in full, and a saved card is released (just as when you decline a request), and no cancellation fee is ever charged;
- the guest gets no cancellation email or text — only when a deposit they paid was refunded do they get one short email: "Your request for Thursday 15 October wasn't answered in time, so it has closed and your £20.00 deposit has been refunded." No deposit, or only a saved card, means no email at all;
- the booking shows Cancelled with an Expired — not answered in time chip, and its History (and the Activity log) says it expired;
- reports count it as an unanswered request, never as a cancellation.
A guest's change that's still waiting when its day passes is never closed on its own — that would cancel their original booking. It stays on the Requests tab: open it and click Decline change to keep their original booking.
When a guest withdraws their own request
A guest can cancel a request you haven't answered yet from their manage-booking page at any time before its time — it isn't a booking yet, so your cancellation deadline doesn't apply to it: they're never asked to call you, no late-cancellation fee is ever charged, and a card they saved is released. Your bell says the booking was cancelled. A guest's waiting change on a booking you've already confirmed is different — that's a real booking, so your normal cancellation deadline and any late-cancellation fee still apply, counted from the booking as it stands (its original date and time) until you approve the change.
Being told about a request
- The bell — each new online request rings as "Booking request — needs approval", with its day, party size, time and name ("Fri 25 Dec · party of 4 at 7:00pm · Ellie Ross"), and pushes to phones with alerts on. It counts in the bell's number until someone approves or declines it — from the Requests tab, the booking itself, Home or anywhere else — and then shows Handled by their name for the whole team. (A request never also rings as "New booking".)
- An email for each request — on Settings → Notifications → Team alerts and sounds, under Email copies to staff, switch on Booking requests to approve (off by default; Available on Plus plan and above, like the other copies). Each request is then emailed to your Venue notification email straight away — "Booking request — needs your approval" with its date, time, party, the guest's note and why it waits, and an Approve or decline button that opens the booking. It always comes at once, even when your other copies come in one email each morning, and while it's on the plain New bookings copy isn't also sent for a request.
- A 9am summary — switch on Booking requests waiting for approval — 9am summary (same section, off by default). At 9am your time, on any day at least one request is still waiting, you get one email listing every one — oldest first, with how long each has waited — and a Review requests button. It goes to your venue notification email, or to the owner if you haven't set one.
A deposit paid online: taken when you approve
A booking that waits for you takes no money when it's made: the guest saves a card (Apple Pay and Google Pay can save it too) and the deposit is taken when you approve — with any paid extras, pre-order paid online or experience price in the same one payment; a gift card the guest added is used first, against what's on it when you approve, and the card pays the rest. Decline it and the card is released. If you hold cards for no-shows and the booking has only paid extras or a pre-order to pay (no deposit), the card stays saved after you approve — it becomes the booking's no-show card, with the no-show fee the guest was shown when they saved it. If the card can't be charged, the booking stays booked with Deposit due and the guest is emailed a link to pay — see What happens when a guest's card is declined?. Details: How do I take booking deposits?
A deposit paid at your venue
When a request's deposit is paid at your venue, the Pay at the venue by days count from the day you approve it — not the day the guest booked. While it waits there's no due date: no reminder goes and it's never marked overdue; the guest reads "due within 7 days of your booking being confirmed" and your team sees "Due 7 days after approval". When you approve it, the due date is set (never later than the booking itself, or a special date's own date for the rest), and from then it's reminded and followed up as usual — see How do payment plans and paying at the venue work?
Requests from bigger groups
With Let bigger parties send a request on (same section; Available on Plus plan and above), a party bigger than your online maximum can send you a request from your booking page instead of being asked to call. It arrives as a pending booking with a Group request chip and no table. It asks the guest for what any booking waiting for your approval asks for — a card for no-shows if you hold one (nothing is charged; declining it, or not answering in time, releases the card) and any deposit or payment your settings ask for. It isn't turned away by your guests limit or pacing rules (you decide), but while it waits it counts towards them, so a group you're about to accept can still be seated. Approve it and arrange the tables, or Decline it.
When a guest changes a booking
A guest's change comes back to you for approval when the booking needed approval when it was made — or when the changed booking would need it now (a party that grows past your size, a move to short notice or onto a special date that approves every booking). Only a change of date, time or party size counts — a new note or allergy doesn't. The booking shows a Change to approve chip, and its action bar shows Approve change and Decline change:
- Approve change accepts it, like any approval.
- Decline change keeps the guest's original booking: "Decline this change? … original booking stands … Nothing is cancelled and no money moves." The date, time, party size and length go back to what they were, with the original table if it's still free — if it has been taken, the booking waits in Unassigned and you're told. Leave Email the guest that their booking is unchanged ticked and they're told their booking is unchanged.
While a change waits, the guest can't change the date, time or party size again (they can still add notes), and their manage-booking page says their original booking stands if you can't make the change. Until you approve it, the original booking is the one that counts for cancelling: the cancellation deadline (and whether any late-cancellation fee applies) is measured from the original date and time, never the time they asked for — a guest who asked to move Saturday 8pm to Wednesday and cancels on Friday evening is inside 24 hours of Saturday, exactly as if they'd asked for nothing; one whose original booking is days away isn't charged, however close the time they asked for. The same goes for money already paid: the refund cut-off for a deposit or payment counts from the original date and time while the change waits (after you approve, the new time is the booking). Their manage-booking page counts its deadlines from the original too. If the guest phones and your team cancels while the change waits, the cancel pop-up offers Cancel & charge £X late-cancellation fee exactly as for a confirmed booking, inside the deadline of the original. A deposit or payment on such a booking follows your refund policy too, counted from the original — it isn't refunded in full the way a declined request is (you can still refund it in full by hand). On a paid-in-full booking, the refund for a smaller party is held with the change: it's paid if you approve the change, and never if you decline it. If an earlier refund on the booking is still going through when you approve, the held refund is added to it — or, when the earlier one is already on its way back or is for something else, it follows straight after — so both are paid.
What the guest sees
When their booking will wait for you, your booking page says so before they commit: the button reads Send booking request (Send request for a bigger group's request, whose last step is Check and send, marked "Request — not a booking yet") and a box titled "This is a booking request" says "{your venue} will check it and email you to confirm." — adding "Any deposit is refunded if they can't." (or "payment" for a booking paid in full) when money is taken. After submitting, the booking page shows "Booking request sent" with "{your venue} will check it and email you to confirm. We've emailed {their email}." (or "{your venue} will check it and let you know." when your booking confirmation emails are switched off, since your approval then sends no email either) — so guests know it isn't locked in until you approve it — and they receive a "request received" email. Add to calendar waits until you approve it: it isn't on that page, in that email or on their manage-booking page while the request waits (your acceptance email carries it). Their manage-booking page says the same until you decide: "This is a booking request — {your venue} will check it and email you to confirm." If you decline it, their manage-booking page and My account call it Request declined; if it closes because nobody answered it in time, Request not answered — never "cancelled", because they never had a booking.
Related: How do I choose how people can book? · When can guests book? · How do I cancel a booking (and what happens to the deposit)? · Which confirmations and reminders do guests get? · Why do online bookings say "pending"?