Sixty-four things it does. Search for yours.

Five steps, and the ones your data cannot answer never render. Block, shortcode or page.

A UNIQUE index decides it inside the database. The second booking is impossible, not unlikely.

Seats claimed by conditional INSERT, so a class cannot oversell under load.

Each provider their own weekly hours, per-service durations and buffers either side.

Minimum notice, how far ahead people may book, holidays and weekly closures.

Next free slot in one tap, plus filters by day and by time of day.

They see their own timezone; you see yours. Nobody does the arithmetic.

Book for a parent, a partner or a patient who telephoned instead.

Both sides can move or cancel, through a magic link that needs no password.

Drag into an open slot, add a walk-in, and a Today view for the front desk.

Checked in, completed or no-show, recorded — the history the risk score reads.

One offer at a time, never a scramble, and it says plainly the slot is not held.

Where the booking came from, so you learn which channel is worth paying for.

Separate hours, prices and services per person, plus “any available”.

Rooms, branches or sites, each with its own hours and its own diary.

Ten sessions, weekly, same time, booked once and then tracked to the end.

Ticketed events with early-bird pricing, named attendees and a register.

Take money on day one: pick the gateway, and the free plan still takes it.

GST split, GSTIN on the invoice, and a sequential numbering an auditor accepts.

Per-item rates, inclusive or exclusive, decided per service rather than per site.

Full or partial, from the admin, reconciled against what the gateway actually did.

Pay at the desk. The admin marks it paid and the booking behaves identically.

Run several at once and let the customer choose the one they trust.

Sell appointments through your existing WooCommerce checkout and its tax setup.

₹500 now, the balance at the desk — or a percentage, or nothing at all.

Codes, rules, first-visit offers, and discounts that apply themselves.

Ten sessions at a price, or a monthly membership that just keeps working.

Bought by somebody else, redeemed by the person who turns up.

Points, rewards, and referral attribution that says which customer sent which.

Split per provider, so paying the people who did the work is arithmetic, not a spreadsheet.

Your own SMTP, HTML templates you control, and reminders timed before you touch a setting.

A real calendar invite attached, so it lands in whatever diary they actually use.

Everybody told when something moves, including the practitioner it moved to.

Through your own Twilio account, on the channel your customers already read.

They reply and it acts: confirm, cancel, move, claim a slot, or stop.

A text channel and one-time codes for the customers who do not use WhatsApp.

They got three steps in and left. One message brings them back to the same slot.

Follow-up after the visit, a nudge to rebook, and a win-back for the ones who drifted.

Confirm-or-release, the waitlist filling the gap, and deposits that adapt to history.

Injury, history, goals, consent — asked at booking, on the screen before they walk in.

Notes against the visit itself, not a document somebody has to go and find.

Full history, notes, merge duplicates, and block the ones you need to block.

No password. A link that identifies them, and an optional WordPress account if they want one.

Who has sessions left on a package and has quietly stopped coming back.

Pain, movement and sleep collected by message and charted across the course.

Speak the note; the copilot writes it and you approve it before it saves.

Filter it however you need and take the whole thing out as CSV.

What came in and how many, without opening a spreadsheet.

Any date range, sliced by service, by provider or by where the booking came from.

Who is unconfirmed, what is owed, which provider is unusually free — before the first patient.

What changed since last month, written as sentences rather than a chart to interpret.

Each branch on its own line, so you can see which one is carrying the others.

A search box on the wizard, not a chat bubble. It fills the form and cannot invent a price.

Ask in a sentence. It plans, checks with you, then does it — every write audited and undoable.

Both directions. Their own commitments block your slots, which is half the double-booking guarantee.

Reads all four of their own tables. Dry-run first, and it refuses by name rather than importing nothing.

LocalBusiness, Service and Event markup, so search engines understand the page.

Right-to-left stylesheet and a fully translated interface, not a machine-translated string file.

Bookings and revenue land in the analytics you already run.

A room per booking, created when it is needed and not before.

Your services, extras, packages and email templates, each in every language you sell in.

Fire your own automations on any booking event, or wire it into the tools you use.

Reception sees the diary, a practitioner sees their own day, and nobody sees the money by accident.

Issue a key and let your other systems create and read bookings directly.