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

# Manage bookings

> Accept, decline, reschedule and cancel from your Inbox and know what each action does to the calendar and the payment.

Every booking lands in your **Inbox**, split into pending requests, upcoming bookings and past ones. Everything you do to a booking after it arrives happens here.

## The Inbox

Open a booking to see who it's from, the topic they wrote, the duration and price, the location and its meeting link and, for group services, how many seats are taken.

Two things worth knowing:

* **Notes** are private. Add whatever context you want for later; the booker never sees them.
* The approval switch at the top of the Inbox flips your whole account between accepting bookings automatically and reviewing each one. See [Manual approval](/guides/manual-approval).

## Accept or decline

Pending requests wait on you. Nothing is on your calendar until you act.

* **Accept**. For a free service, the booking is confirmed on the spot: calendar event created, meeting link generated, both of you emailed. For a **paid** service, accepting emails the booker a payment link and the booking is confirmed once they've paid.
* **Decline**. The booker is emailed and the slot reopens for someone else. Nothing has been charged at this point, so there's nothing to refund.

<Note>
  A pending request whose slot time has passed is declined automatically, twice
  a day and the requester is told. It keeps dead requests out of your Inbox,
  but it isn't a substitute for answering, since by then the time has been held
  and wasted.
</Note>

## Reschedule

Open the booking and choose **Reschedule** to move it without making the client rebook.

<Steps>
  <Step title="Pick a new time">
    You see your real availability, the same slots a visitor would get.
  </Step>

  <Step title="Confirm">Click **Confirm Reschedule**.</Step>
</Steps>

Behind that button, Tikk re-checks that the new slot is genuinely free. Your calendars, your schedule and your buffers all apply, exactly as they would for a new booking. The one exception is the booking you're moving: it doesn't count as a conflict with itself, so you can shift a meeting by fifteen minutes without its own buffers blocking every nearby slot.

When it goes through, the calendar event moves, any linked CRM meeting is updated and both of you get an email with the new time.

<Warning>
  You can't reschedule a meeting whose time has already passed. Once it's in the
  past, the booking is history. Take the new booking as a fresh one.
</Warning>

## Cancel

**Cancel Booking** calls off a confirmed meeting. You can add a message explaining why, which is included in the email to the other person.

Cancelling removes the calendar event, deletes the meeting from any connected CRM and frees the slot. It can't be undone. A cancelled booking stays cancelled and rebooking means a new booking.

Three bookings can't be cancelled this way:

* **Anything not accepted.** A pending request is declined, not cancelled.
* **Meetings in the past.** There's nothing left to call off.
* **Bookings that have been paid.** Cancelling would leave money to return, so it isn't a one-click action. Email [support@tikk.chat](mailto:support@tikk.chat) to sort out the refund.

## What each action touches

| Action         | Calendar event                  | The other person                                      | The slot         |
| -------------- | ------------------------------- | ----------------------------------------------------- | ---------------- |
| **Accept**     | Created once any payment clears | Confirmation or a payment link if the service is paid | Taken            |
| **Decline**    | None                            | Told; nothing charged                                 | Reopened         |
| **Reschedule** | Moved                           | Told the new time                                     | Old one reopened |
| **Cancel**     | Removed                         | Told, with your message                               | Reopened         |

<Note>
  Group bookings work per attendee: one person cancelling frees their seat and
  leaves the meeting standing for everyone else. See [Group
  bookings](/guides/group-bookings).
</Note>

<Note>
  Reading bookings from your own systems? See [List
  Bookings](/api-reference/bookings/list-bookings). The API is read-only:
  accepting, rescheduling and cancelling happen in the dashboard.
</Note>