Skip to content

Module · switch on per organisation

Somebody outside asks for a time

Enclessa Bookings is the module that lets somebody outside the organisation ask for a time — an initial consultation, a viewing, a call — and somebody inside answer. Appointment types carry their own opening hours, duration and buffers; requests either arrive for approval or confirm themselves; and the visitor gets a link they can use to see or call off their own appointment without ever having an account. It is the one surface on the platform that answers without a session.

Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.

At a glance

Availability
Module, off by default
Requires
Nothing. It stands on its own
Two ways in
A public API your own site embeds, or a booking link we serve
The visitor
Needs no account, ever

How does somebody outside reach it?

Two ways, and the organisation picks. Its own website can embed the public availability and booking API, which is what the module was built for. Or it issues a booking link — one URL naming which appointment types may be booked through it and until when — and the product serves the page itself, so one customer can be sent one link for one kind of appointment.

  • A public availability and booking API any website can embed
  • Or a booking link, served by the product, scoped to named appointment types
  • A link can expire, and names what may be booked through it

What happens to a request once it arrives?

Either it confirms itself or it waits for somebody, per appointment type. When Time is installed the appointment reads the day’s absences before offering a slot, and offers the hour it took once it is done. When Customers is installed the appointment appears on that customer’s record. Notification of a new request or a cancellation reaches the people named on the module’s own screen, and never anybody outside the organisation.

  • Requests that arrive for approval, or confirm themselves
  • Absences are read before a slot is offered, when Time is installed
  • A completed appointment offers the hour it took
  • The appointment lands on the customer’s record, when Customers is installed

What this does not do

  • Bookings is off until an operator enables the module for the organisation.
  • It books time with the organisation, not resources: there are no rooms, no equipment and no seat maps.
  • There is no payment step. Nothing takes a deposit or a card at the point of booking.

Related

Where this shows up

Questions

Bookings: common questions

Can customers book appointments with Enclessa?

Yes, through the optional Bookings module. Appointment types carry their own opening hours, duration and buffers, and somebody outside the organisation books either through a public API embedded in your own website or through a booking link the product serves.

Does a visitor need an Enclessa account to book?

No. Bookings is the one surface on the platform that answers without a session. The visitor gets a link they can use to see or call off their own appointment, and never has an account.

Can somebody be double-booked?

When the Time module is installed the appointment reads the day’s absences before a slot is offered. Buffers and duration are set per appointment type.

Encrypted collaboration, hosted in Europe.

Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.

Open beta. Free plan, no payment card to start.