—PRODUCT

Appointment assistant

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.

Ready Plan: add-on

—SUMMARY

What is it for?

Turns an appointment request into a real booking with calendars, resources, approval rules and a waitlist.

01HOW IT WORKS

Three steps to a working result.

Each step is one screen in the panel; nothing goes live without confirmation.

  1. 1 Define service and resource

    Enter service duration, staff/room/device/table resources, working hours and holidays; the default slot is 15 minutes.

  2. 2 Choose approval and calendar

    The approval rule applies to the whole business: automatic or business-approved. Google/Outlook connection is in the Pro package.

  3. 3 Turn the request into a booking

    An external request becomes CONFIRMED or REQUEST according to the approval rule; a booking entered in the panel is always confirmed.

Scope

02WHAT IT DOES

Real work in one flow.

The three capabilities below are today’s scope; the sample dialogue is fictional and contains no real customer data.

01

Double-booking lock

A transaction locks on resource + start; availability is recalculated under the lock and idempotency is enforced.

  • Appointment
  • Knowledge base
02

Waitlist

States are Waiting, Called, Assigned and Cancelled; “Assign from waitlist” works only for No-show/Cancelled and an empty slot.

  • Waitlist
  • Ownership
  • Cancel
03

Honest fit by sector

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.

  • Sector
  • Stock
  • Model
SAMPLE FLOW · FICTIONAL Appointment assistant
CUSTOMER Can I book a dental check-up for tomorrow?
AGENT Tomorrow at 14:00 and 16:30 look available; which would you prefer?
CUSTOMER 14:00, please.
AGENT Your appointment is confirmed for 14:00 and added to the calendar. If the approval rule were business-approved, it would first go to the REQUEST queue.
NO REAL CUSTOMER DATA SAMPLE
Tiers

03THE DIFFERENCE IS IN THE DETAILS

Small details that change the decision.

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.

01

Add-on gate

When the appointment add-on is off, the voice route gets 200 plus a redirect, while panel/n8n writes get 403.

  • Add-on
  • Voice
  • Appointment
02

Basic and Pro packages

1 = Basic (3 calendars), 2 = Pro (10 calendars + Google/Outlook); the package sets the external calendar count.

  • Calendar
  • Automation
03

Default settings

Defaults: approval AUTOMATIC, 15-minute slot, earliest 120 minutes ahead, 60-day horizon, no daily cap, daily schedule email off.

  • Settings
  • Approval
  • Email
04

Approval applies to the whole business

The approval mode applies to the whole business; there is no per-service approval field.

  • Approval
  • Field
05

Panel vs external channel

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.

  • Channel
  • Panel
  • Approval
06

Double-booking lock

Double-booking protection uses pg_advisory_xact_lock inside a transaction on resource + start; availability is recalculated under the lock and idempotency is enforced.

  • Appointment
  • Knowledge base
07

Fresh external calendar read

Immediately before creation the external calendar is read fresh, bypassing cache; if the business has just closed a slot, it is not written.

  • Calendar
  • Closing
  • Cache
08

Google freebusy

Google requests only freebusy + events + calendar list; event titles are not visible through freebusy, and written events are tagged with iCalUID to suppress echoes.

  • Calendar
  • List
  • Tag
09

Three-minute cache

The external busy cache is 3 minutes; the panel path uses a 9-second timeout and stale-while-revalidate.

  • Duration
  • Cache
  • Panel
10

Pro gate in the panel

In the Basic package the panel shows “Pro plan required” and the connect buttons are disabled.

  • Panel
  • Plan
11

Calendar quota

The calendar quota shows “{used}/{limit} calendars ({tier})”; when full it says “Calendar allowance full” and shows the extra-calendar option.

  • Calendar
  • Quota
  • Limit
12

Waitlist

The waitlist has Waiting/Called/Assigned/Cancelled states; “Assign from waitlist” works only for No-show/Cancelled and an empty-slot click.

  • Waitlist
  • Ownership
  • Cancel
13

Privacy-safe cancellation

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.

  • Privacy
  • Cancel
  • Waitlist
14

Rescheduling

Rescheduling sets the new state to RESCHEDULED, cancels the old external event and verifies the target resource.

  • Knowledge base
  • Cancel
  • State
15

Phone is masked

The phone is masked in the panel as +90 532 *** ** 33.

  • Privacy
  • Hidden
  • Phone
16

07:00 daily email

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.

  • Email
  • Settings
  • Window
17

No automatic reminder

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.

  • Appointment
  • WhatsApp
  • Email
18

Calendar privacy

An external calendar event title is shown only to ADMIN/OWNER and is not written to the DB; a private event shows no title.

  • Calendar
  • Privacy

04CONTROL AND SECURITY

Human approval, masking, records.

These are this surface’s current security behaviours; no general “GDPR compliant” certificate is claimed.

Double booking is prevented

A transaction locks on resource + start; availability is recalculated under the lock and idempotency is enforced.

Privacy-safe cancellation

Without matching contact the cancellation does not happen; signed-in staff are exempt. The external event is deleted and the waitlist is notified.

Phone is masked

The phone is shown in the panel as +90 532 *** ** 33.

Calendar titles are limited

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

Four sectors, honest limits.

The fit below reflects the product model as it stands; what matters is which job works and which does not, not a score.

Clinic / dental

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.

Beauty / salon

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.

Restaurant / table

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”.

Hotel / accommodation

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.

Software integration: on request

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

Plan and add-ons.

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.

Basic ₺990 / mo excl. VAT 3 calendars
Pro ₺1,990 / mo excl. VAT 10 calendars · Google/Outlook

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

Four questions, four clear answers.

Can it book a hotel room?
No. For hotels it only collects a request: dates, nights, adults/children, room type and board note. Room type + night inventory, rate plan and price are absent; “available” or a price guarantee is not given.
Does it guarantee a restaurant table?
It works as an approximate table book. Single-party/table atomicity, turn time, table combining and deposit are absent; “request received, the business will confirm” is more accurate.
Which package includes Google and Outlook?
Google Calendar and Microsoft Outlook connections are in the Pro package; in Basic the panel shows “Pro plan required” and the connect buttons are disabled.
Is there an automatic reminder?
No. There is no automatic 24-hour/2-hour SMS, WhatsApp or email reminder in the code; only a 07:00 daily schedule email when the business setting is on. Automatic reminders are marked “Coming soon” with no date promised.

+RELATED POSTS

Posts on this topic

Posts from the same topic cluster that complete this page. Appointments posts.

Let’s set this up on your account.

Try free for 14 days without a credit card; we will do the first setup together.

Call Start 14-day trial