> ## Documentation Index
> Fetch the complete documentation index at: https://help.tapp.shop/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage booking status

> Accept requests, record a no-show, or cancel a booking and check the result.

A booking’s status helps the team distinguish requests waiting for a decision from confirmed visits and cancellations. Check the guest and visit time before changing it, especially when several similar reservations appear together.

## Who can do this?

Owners, Managers, and Staff can manage booking status.

## Where

Open **Bookings** in the web app and select a booking from the list or calendar. Its details panel shows the current status and available actions.

## Choose the right action

* **Pending:** choose **Confirm** to accept the request. To decline it, choose **Cancel booking** and confirm the cancellation; the result is **Denied**.
* **Confirmed:** choose **Mark no show** if the guest did not arrive. Choose **Cancel booking** and confirm if the visit should be cancelled; the result is **Archived**.
* **No show:** the web details panel offers cancellation to archive the booking. It does not offer a button to restore confirmation. Contact Tapp support if the status was recorded incorrectly and you need help correcting it.
* **Denied or Archived:** the web details panel has no further status action. Archived bookings remain part of the history and cannot be reopened through this screen.

**Confirm** and **Mark no show** act immediately, without another confirmation dialog. Wait for the change to finish, then check the status again in the list or calendar. If you open a cancellation dialog by mistake, choose **Keep booking**.

## Check tables and guest communication

A pending request’s suggested table is not reserved. More than one pending request may suggest the same table. When you confirm, Tapp keeps the suggestion if free or tries another suitable assignment. If none is available, confirmation can succeed without a table. Reopen the booking and check its assigned tables before planning the seating.

Confirmed bookings reserve their assigned tables for the visit. No-show, denied, and archived bookings do not hold that booking capacity. Check any active seating separately rather than assuming a status change has finished every service task.

Tapp attempts confirmation or rejection messages using the booking’s available email and phone details. A saved status does not confirm delivery. Do not assume that marking a no-show or archiving a confirmed booking sends the guest a cancellation message. Contact the guest when your team needs to explain the change.

## Platform and market notes

In the mobile app, open a pending request to check its party size and full visit details; the compact card omits the party size. The main booking list has no quick confirm/deny buttons. Cards opened from a calendar time slot can show them, so review the request before selecting an action. Guest requests may already be confirmed automatically when the shop allows this and a table is allocated; not every guest booking needs manual acceptance.

## Troubleshooting

If saving a table assignment fails because it is occupied, inspect the conflict and adjust the visit or assignment before trying again. Refresh when the status appears outdated. After an error, check the saved status before repeating the action: it may have changed even if sending a guest message failed. Use no-show for a guest who did not arrive, rather than as a general cancellation label.

## Related articles

* [Resolve overlapping bookings](/en/bookings/resolve-overlapping-bookings)
* [Edit or reschedule a booking](/en/bookings/edit-or-reschedule-booking)
* [Configure booking settings](/en/bookings/configure-booking-settings)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.