Biznsbook Booking Management takes appointments, time-range rentals, classes with a seat count, and stays. Staff use the calendar, front desk, and list. Guests use a company public page or a personal /book/s/ link. A new person is a Booker party, not a customer, unless their email or phone already matches someone you have.
Booking Management is the licensed module for appointments, equipment or room rentals, classes, and stays. Restaurant table reservations stay on the Restaurant screens. People are parties: a matching email or phone is linked as-is, and a new person is a Booker.
Setup lives in the module: locations, resources, offerings, hours, and policies. The menu is Calendar, Bookings, Front desk, Waitlist, Reports, and Settings.
Appointment, time range, session, stay, or request. A request is confirmed by staff later and has no slot grid.
A new person is a Booker. An existing email or phone keeps Customer, Supplier, Guest, or whatever type they already have.
Weekly hours and closures decide what is bookable. A hold expires. When a seat frees, the next waitlist person is offered it.
Guests pick an offering and a time on the company page or a personal /book/s/ link. They can move or cancel inside the policy and download a calendar file.
The deposit is stored on the booking. Guests can pay by card into your Stripe Connect account, or mark I have paid when you allow it.
Online offerings can create a Google Meet link on confirm. Staff resources can sync Google or Outlook busy time so personal events hide open slots.
Today’s count, pending approvals, waitlist, utilisation, stay occupancy, revenue booked versus collected, deposits held, and no-show rate.
Location, resources, duration, price, policy, and weekly hours. Without hours, nothing is offered.
Calendar, front desk, or the public page. A walk-in save checks the guest in.
Confirm, reschedule, cancel, or mark a no-show. Record a deposit or send the pay link.
Complete it. Send the balance to POS or create a draft invoice when those modules are licensed.
No. A new person is a Booker party. If the email or phone already exists, that party is linked and keeps its current type, including Customer. Booker is also not a restaurant Guest.
No. Restaurant table reservations stay on the Restaurant screens.
Yes. Connect Stripe in Integration Hub, turn on Accept card deposits online, and send the pay link. Checkout settles to your connected Stripe account. I have paid remains optional for transfers when honour-system pay is on.
Yes. Turn on personal staff pages, set a slug on the resource, and share /book/s/{staffSlug}. Guests only see that person’s offerings and times.
The booking still completes and shows an operational balance. A draft invoice needs Sales. A deposit journal needs Accounting. Licensing Accounting later does not back-post old deposits.
Set up one offering, publish the public page, and take a walk-in without adding those people to the customer list.