From empty calendar to bookable business

OneBooking covers two booking models: resource booking (turfs, courts, grounds) and staff/service booking (clinics, salons, academies). Onboarding adapts to whichever you pick.

1. 1

   Sign up and choose your business type — Turf, Appointments (clinic), Salon, or Academy. This sets the terminology, default calendar view, and starter checklist for the rest of setup.

2. 2

   Complete the onboarding wizard: name your business and set your city/timezone, add your first turf/resource (or your first branch, services, and staff for a clinic/salon/academy), set opening hours, set pricing, then publish.

3. 3

   Back in the dashboard, add more locations any time — Settings → Turfs/Resources for resource-based businesses, or Settings → Branches, Services, and Staff for staff-based ones.

4. 4

   Brand it: crop your logo in Square or Rectangle mode from Settings, and OneBooking applies your category's accent color automatically across the booking page and dashboard.

5. 5

   Copy your live booking link from "View booking page" in the dashboard header, or go to Settings → Integrations to embed it as a WordPress custom-HTML block, a plain iframe, or a direct link — for the whole business or a single resource/branch.

6. 6

   Place a test booking end-to-end (as a customer would) before you share the link on your website, Google Business Profile, Instagram bio, or WhatsApp.

Calendar shows a live slot grid for resource businesses, or a staff agenda for staff/service businesses — either way, it's the same data your customers book against.

1. 1

   Open Calendar in the sidebar. Resource businesses see a slot grid per turf/resource; staff/service businesses see an agenda per staff member.

2. 2

   Click an open slot to record a walk-in or phone booking directly — no separate "new booking" flow to hunt for.

3. 3

   Open Bookings (or Appointments) for the full list; open any entry to reschedule, edit customer details, change payment status, or cancel.

4. 4

   Double-booking is blocked at the database level, not just in the UI, so two customers can never be confirmed into the same slot even under concurrent traffic.

5. 5

   Use the header's Refresh button, or just keep the tab open — new online bookings and cancellations update live via a polling fallback so you always see the current state without a hard reload.

6. 6

   Turn on Waitlist for a resource so customers can join a waitlist once a slot fills, and cross-midnight slots (e.g. 11 PM–1 AM) work the same as any other slot for late-night businesses.

For clinics, salons, and academies, availability comes from staff schedules mapped to services and branches. For turf-style venues, it comes from each resource's own hours and pricing.

1. 1

   Go to Settings → Branches to add each physical location — name, address, city, and a photo.

2. 2

   Go to Settings → Services to define what's bookable (service name, duration, price), then map each service to the staff who can perform it.

3. 3

   Go to Settings → Staff to add staff members, assign them to branches and services, and set their weekly working hours, breaks, and time off.

4. 4

   For resource-based businesses (turfs, courts), use Settings → Resources instead: add each ground/court, set its open hours, and configure base, peak, and off-peak pricing.

5. 5

   Restrict what a teammate can see: Settings → Team lets you limit a staff account to specific dashboard pages (e.g. Bookings + Calendar only) — see Team access & permissions below.

6. 6

   Hide modules your business doesn't use (like Membership) from the sidebar in Settings, so the dashboard only shows what's relevant to you.

Online payments run through Razorpay — UPI, cards, and netbanking — with every payment verified server-side before a booking is marked paid. OneBooking never touches or stores card numbers.

1. 1

   Connect Razorpay from your environment/integration settings (RAZORPAY_KEY_ID / RAZORPAY_KEY_SECRET); once configured, online payment becomes available on the booking page.

2. 2

   Turn on online payments per resource or service, and choose full payment or a smaller advance/deposit to cut no-shows without requiring the full amount upfront.

3. 3

   Customers pay through a secure Razorpay checkout at booking time; OneBooking verifies each payment with a signed webhook before flipping the booking to Paid — a browser-only "success" screen is never trusted on its own.

4. 4

   For walk-ins, phone bookings, or cash, record a manual/offline payment directly on the booking instead of routing it through Razorpay.

5. 5

   Track everything under Finance: Payments, Expenses, Reports, Cash Handover, and Daily Book — including GST details on the Payments CSV export for company customers.

6. 6

   Higher plans (Team, Business, Enterprise) unlock higher volume and features, but checkout for them isn't live yet — clicking Upgrade shows a "Coming soon" message. Email support in the meantime (see the FAQ).

Confirmations and reminders go out automatically once configured — email is built in, and WhatsApp/SMS are usage-billed add-ons you switch on when you need them.

1. 1

   Email confirmations send automatically after a booking, once Settings → Integrations → Email is configured (an org-level on/off toggle controls this).

2. 2

   Turn on WhatsApp confirmations and reminders from Settings → Integrations → Add-ons — a usage-billed extra, charged per message sent.

3. 3

   Turn on SMS reminders the same way, as a fallback for customers who don't use WhatsApp.

4. 4

   Reminders fire ahead of the appointment or slot automatically once enabled — there's nothing to send manually.

5. 5

   Set a reply-to address and BCC so replies to confirmation emails land in the right inbox for your team.

6. 6

   Every confirmation includes the booking number, your business name and logo, the resource/service, the date and time, and the amount due or paid.

Owners and admins always see every dashboard page. Staff accounts can be scoped down to exactly what their role needs.

1. 1

   Go to Settings → Team to invite a teammate by email and assign them a role: Owner, Admin, or Staff.

2. 2

   For a Staff role, choose exactly which dashboard pages they can open — for example, a front-desk account might get only Bookings and Calendar.

3. 3

   Optionally restrict a page to create-only, blocking edit or delete — so that same front-desk account can add walk-ins but can't modify or remove existing bookings.

4. 4

   Access is enforced with row-level security in the database, not just hidden in the UI, so a restricted account can't reach blocked data even by calling the API directly.

5. 5

   Transfer ownership to another teammate from Settings → Team if you're handing the business off.