Docs/What BookFlow Is

What BookFlow Is

BookFlow is a booking operating system for businesses that sell time-based services. In plain words, it lets a business get booked, get paid, manage staff, show trustworthy public pages, and bring customers back.

Simple Definition

BookFlow is not just a calendar. A calendar only shows time. BookFlow connects the time slot to a customer, service, staff member, room/resource, price, payment, invoice, receipt, review, and rebooking opportunity.

Customer wants service->BookFlow finds a valid slot->Booking is created->Payment is tracked->Vendor operates the appointment->Customer returns

Who Uses It

Platform owner

Runs the SaaS product, plans, tenant signup, directory, central customer portal, and global settings.

Vendor owner

Runs one tenant workspace, such as Nimbus Wellness Studio. They manage staff, services, prices, bookings, website pages, programs, and reports.

Customer

Books online, pays, receives confirmations, views receipts, reviews completed appointments, and rebooks from the customer portal.

Platform vs Tenant

BookFlow is multi-tenant. That means many businesses can use the same app, but each business has its own workspace and its own data.

Layer	Example URL	Owns
Platform	/plans, /directory, /customer	SaaS plan selection, tenant signup, global customer portal, directory discovery.
Tenant	/t/nimbus, /t/nimbus/admin	Public storefront, services, bookings, calendar, staff, resources, website pages, payments, reports.

Core Data Chain

Most BookFlow features sit on this chain. If a user changes one part of the chain, later parts react.

Business->Location->Service->Staff->Resource->Slot->Booking->Invoice->Payment->Receipt->Review->Retention

Example: Deep Tissue Massage

Nimbus creates a Deep Tissue Massage service. That service is linked to the Downtown Studio, bookable therapists, and a therapy room. When a customer opens the booking page, BookFlow checks all those links before showing a time. If the customer pays a deposit, the invoice and payment records update. After completion, the customer portal can ask for a review or suggest rebooking.

Why The System Feels Connected

User action	Connected result
Vendor changes service price	Storefront price, new booking invoice, payment page, revenue reports, and package economics use the new price.
Staff member is marked unavailable	Availability slots stop showing times for that staff member.
Customer pays balance	Booking balance, receipt history, customer portal, and reports update.
Customer leaves review	Marketplace and storefront trust surfaces can show stronger proof.
Vendor edits FAQ	The public FAQ page and footer links reflect the new answer.

Screens You Will See

BookFlow plans page — Plans define what a business can buy before creating a workspace.

Nimbus booking page — The tenant booking page turns service setup into real customer appointments.