Tiger Booking

Bookings & customers

Browse/filter/open bookings with service, staff, time and payment status; create bookings manually; every customer gets a CRM profile with booking history.

3 min read Updated August 20, 2026

Every reservation Tiger Booking takes is stored, viewable and manageable, and each person who books builds up a customer profile that is shared across all your modules.

Where: WP Admin → Tiger Booking → Bookings (per module) and Tiger Booking → Customers. Both are in the free wordpress.org plugin; the payment and refund actions described below need the Tiger Booking Pro add-on.

Bookings

Each active module has its own bookings view — for appointments it is Tiger Booking → Bookings; for hotels (Pro add-on) it is Reservations. Open a booking to see the full picture: the service or room, the assigned staff, the date and time, and the customer’s contact details.

  • Browse & filter the list to find bookings by status, date or customer.
  • Open a booking to review or edit its details and see its history.
  • Change status — confirm, cancel, complete, or mark a no-show. The status change sends the matching notification email, and marking a no-show or a late cancellation assesses whatever fee you set in Settings → Payments under your cancellation policy.
  • Create manually — add a booking on a customer’s behalf, useful for phone or walk-in reservations.
  • Refunds (Pro add-on) — taking payment at all requires the add-on, which is where the Stripe, PayPal, Square and Razorpay integrations live. With it installed and refunds enabled in Settings → Payments, a Stripe-paid booking shows a Refund action that calls the gateway. Bookings paid through the other gateways must be refunded from that provider’s own dashboard. In the free plugin there is no payment gateway, so the refunded status is only ever something you set by hand.

Bookings from every module are also attributed to a shared master record, which is what powers the cross-module dashboard totals and the Activity Log.

Customers (CRM)

The Customers page is a shared, lightweight CRM. Every booking is linked to a customer by their contact details, so you build a single profile per person no matter which module they booked through.

  • Contact details — name, email and phone captured at booking time.
  • Booking history — every past and upcoming booking for that customer in one place.
  • Repeat activity — spot your regulars and their lifetime value at a glance.

Because customer records can carry personal data, these views are admin-only; staff signed in through the portal only see their own bookings, not the full customer list.

Walk-in queue & records

The Appointments module has two extra operational views: a Walk-in Queue (a live first-come line for walk-in customers) and Records (per-customer visit notes). They are optional screens — a walk-in queue belongs to a barbershop and patient records to a clinic, so they appear when your chosen business type asks for them, or when the site already has rows in them, rather than cluttering every install. Both live under the Appointments section and, like customers, are admin-only.

Activity Log

For an audit trail across everything, open Tiger Booking → Activity Log. It records booking events from every module so you can see what changed, when.

Troubleshooting

A customer shows up twice.

Customers are matched on their contact details. If someone books once with one email and again with another, they’ll appear as two profiles — reconcile by using a consistent email address.

I can’t see the Customers menu.

Customers is free in every build and needs no license — it is not a Pro screen. The one thing that hides it is the Customer CRM switch under Settings → Features (in the Insights group). It is on by default, so if the menu item is missing, check that it hasn’t been switched off there.

Frequently asked questions

Yes — create a booking manually.

On their Customer profile.

Still stuck?

We’re here to help

Can’t find what you’re looking for, or hit something that looks like a bug? Reach the support team or ask the community.