docs / take-bookings-without-an-account
Take bookings without an account
Ciita is the calendar the lead books himself. One availability feeds both the public page and the times the agent proposes — so they can never contradict each other.
before you start
What this guide covers.
// Ciita is niiko's scheduling module. It is an add-on, not part of every plan.
By the end of this guide you will have a booking page a client can open from a link — no account, no app, no login — backed by your real weekly availability, and an agent that offers those same slots inside a WhatsApp conversation.
Ciita is an add-on: it is not included in every plan. Check that it is enabled for your workspace before you follow the steps below.
step one
Define what can be booked.
// An appointment type is the unit someone books — not a slot on a grid.
Each appointment type carries its own duration and its own minimum notice. The minimum notice is the part people skip and then regret: without it, someone can book you for twenty minutes from now, and the page has no way of knowing you are driving.
- A name the person booking will read, not an internal code
- Duration — how long the slot takes on your calendar
- Minimum notice — how far ahead someone has to book
step two
Set your weekly availability.
// One availability per workspace, in your own timezone.
Availability is a weekly grid in your workspace's timezone: the hours you are open, per day. Everything else derives from it — the slots the public page shows and the times the agent offers are the same source, which is why they cannot disagree.
Availability is a weekly grid. Blocking a single date — a holiday, a trip — is not built yet, so plan around that until it is.
step three
Share the booking page.
// One page per workspace, opened without an account.
The booking page is public by link. The person picks an appointment type, sees the real free slots, and books — without creating an account, installing anything or logging into your workspace. It is not a form that emails you: the appointment lands on the agenda directly.
step four
Let the agent book inside a conversation.
// The agent reads the same availability. It never invents a time.
When the conversation happens over WhatsApp, the agent can propose real free slots from that same availability and book the appointment in the thread. There is nothing to synchronise, because there is nothing separate to keep in sync — the agent reads what the page reads.
Booking is one of the capabilities whose autonomy you can set. If you want a person to confirm before an appointment is created, set that capability to require approval instead of running unattended.
step five
Work from the operator agenda.
// The real state of every appointment, in one screen.
The agenda shows every appointment with its real state — booked, and what happened with it. It is the screen your team works from; the public page is for the person booking, and the two never diverge because both read the same record.
What this guide doesn’t cover
Running in production: the operator's agenda, appointment types, weekly availability, the public booking page and booking from the WhatsApp conversation. What is not built yet:
- Blocking a single date — a holiday or a trip. Availability is a weekly grid today.
- Ciita is an add-on: it is not included in every plan.
Last updated: 2026-09-02.