Double-booking lock
A transaction locks on resource + start; availability is recalculated under the lock and idempotency is enforced.
- Appointment
- Knowledge base
—PRODUCT
Turns an appointment request into a real booking with calendars, resources, approval rules and a waitlist.
Basic and Pro packages, an organisation-wide approval rule and a double-booking lock. There is no automatic reminder; a daily schedule email is available.
—SUMMARY
Turns an appointment request into a real booking with calendars, resources, approval rules and a waitlist.
01HOW IT WORKS
Each step is one screen in the panel; nothing goes live without confirmation.
Enter service duration, staff/room/device/table resources, working hours and holidays; the default slot is 15 minutes.
The approval rule applies to the whole business: automatic or business-approved. Google/Outlook connection is in the Pro package.
An external request becomes CONFIRMED or REQUEST according to the approval rule; a booking entered in the panel is always confirmed.
02WHAT IT DOES
The three capabilities below are today’s scope; the sample dialogue is fictional and contains no real customer data.
A transaction locks on resource + start; availability is recalculated under the lock and idempotency is enforced.
States are Waiting, Called, Assigned and Cancelled; “Assign from waitlist” works only for No-show/Cancelled and an empty slot.
Clinic and beauty are the closest fit; restaurant is an approximate table book; hotel is request-only. Hotel room/night inventory is outside this model.
03THE DIFFERENCE IS IN THE DETAILS
18 items, each tied to a rule, setting or automatic behaviour in today’s product. No unsupported number, ratio or promise appears in this list.
When the appointment add-on is off, the voice route gets 200 plus a redirect, while panel/n8n writes get 403.
1 = Basic (3 calendars), 2 = Pro (10 calendars + Google/Outlook); the package sets the external calendar count.
Defaults: approval AUTOMATIC, 15-minute slot, earliest 120 minutes ahead, 60-day horizon, no daily cap, daily schedule email off.
The approval mode applies to the whole business; there is no per-service approval field.
A booking entered in the panel and “assign from waitlist” are CONFIRMED regardless of the approval mode; external channels under BUSINESS_APPROVED go to the REQUEST queue.
Double-booking protection uses pg_advisory_xact_lock inside a transaction on resource + start; availability is recalculated under the lock and idempotency is enforced.
Immediately before creation the external calendar is read fresh, bypassing cache; if the business has just closed a slot, it is not written.
Google requests only freebusy + events + calendar list; event titles are not visible through freebusy, and written events are tagged with iCalUID to suppress echoes.
The external busy cache is 3 minutes; the panel path uses a 9-second timeout and stale-while-revalidate.
In the Basic package the panel shows “Pro plan required” and the connect buttons are disabled.
The calendar quota shows “{used}/{limit} calendars ({tier})”; when full it says “Calendar allowance full” and shows the extra-calendar option.
The waitlist has Waiting/Called/Assigned/Cancelled states; “Assign from waitlist” works only for No-show/Cancelled and an empty-slot click.
Cancellation is privacy fail-closed: without matching contact there is no cancellation; signed-in staff are exempt, the external event is deleted and the waitlist is notified.
Rescheduling sets the new state to RESCHEDULED, cancels the old external event and verifies the target resource.
The phone is masked in the panel as +90 532 *** ** 33.
The daily schedule email goes out only when the business setting is on, in the 07:00 window, and is not sent twice on the same day.
There is no automatic appointment reminder (24h/2h SMS/WhatsApp/email) in the code; only the daily schedule email exists, and reminders are marked “Coming soon” with no date promised.
An external calendar event title is shown only to ADMIN/OWNER and is not written to the DB; a private event shows no title.
04CONTROL AND SECURITY
These are this surface’s current security behaviours; no general “GDPR compliant” certificate is claimed.
A transaction locks on resource + start; availability is recalculated under the lock and idempotency is enforced.
Without matching contact the cancellation does not happen; signed-in staff are exempt. The external event is deleted and the waitlist is notified.
The phone is shown in the panel as +90 532 *** ** 33.
An external calendar event title is shown only to ADMIN/OWNER and is not written to the DB; a private event shows no title.
05BY SECTOR
The fit below reflects the product model as it stands; what matters is which job works and which does not, not a score.
Closest fit: staff, chair/room, service duration, pre/post buffer, working hours, holidays, waitlist and daily email work today.
He requires doctor + chair (AND) on the same appointment, treatment series and insurance/package fields are absent; chair conflicts are not checked.
Close: staff/stylist, service duration, long sessions, pre/post buffer, waitlist and daily email fit.
Multi-service sessions (colour + cut + blow-dry), deposit/no-show, walk-in queue, staff commission and product formula are absent.
Approximate: table resource, party size, capacity, duration, waitlist, daily email and notifications fit a restaurant flow.
Single-party/table atomicity, turn time, table combining, deposit/prepayment, no-show policy and floor plan are absent; do not say “your table is guaranteed”.
Request-only: dates, nights, adults/children, room type and board note are collected; the request goes to the hotel reservations team.
Room type + night inventory, check-in/out, rate plan, price, deposit/cancellation and OTA channel are absent; “available” or a price guarantee is never promised.
There is no ready reservation-software connector; integration is assessed on request. A connector is discussed only for products whose public API is verified: Masamenu Guest API (unauthenticated), Rezervem Partner API (partner-gated), Ranovu OpenAPI 3.1, Dr.DENTES OpenAPI 3.0.3, HotelRunner REST v2 + realtime push and ElektraWeb Booking API. We do not say “available” for a product whose API is not verified.
06WHICH PLAN
Appointments are a separate add-on: Basic (3 calendars), Pro (10 calendars + Google/Outlook). The extra-calendar fee is on the cards; the add-on is installed after purchase and is not switched on from the panel.
Extra calendar: ₺190 / mo · The add-on is installed after purchase; it is not switched on from the panel.
All amounts are monthly and exclude VAT. See the plans page for the current list and calculator. Plans and calculator →
07FAQ
+RELATED POSTS
Posts from the same topic cluster that complete this page. Appointments posts.
Build an AI appointment flow, understand why people miss appointments, see what reminders can and cannot do today, and measure the result honestly.
A plain guide to what an AI customer agent does, how it answers from a knowledge base and when it hands a conversation to a person.
Both appear in a message box, but they do different work. A guide to the difference between a rule-tree chatbot and an assistant that answers from a knowledge base.
Try free for 14 days without a credit card; we will do the first setup together.