Booking infrastructure, on an open-source core.
Event types, availability, routing forms, webhooks and an embeddable booking widget. The assistant runs on top of this core.
Event types
Separate booking types by duration, location, buffer and price.
Availability schedules
Multiple working schedules, timezone handling, date-based exceptions.
Routing forms
Use the form builder to route each request to the right event type and person.
Embeddable widget
Embed the booking flow in your own site; API keys and webhooks are ready.
Out of office and travel
OOO entries and a travel schedule; slots shift while you are in another city.
Blocklist
Keep addresses you do not want out of your booking flow.
Booking audit log
Every change is recorded with who, when and through which channel.
Notifications
Email and WhatsApp notifications; reminder offsets are yours to set.
What’s different
The scheduling core is familiar; the difference sits in the assistant layer and the hosting choice.
| Topic | Classic scheduling tools | KolayMeeting |
|---|---|---|
| Message load | You send a link; the rest is on you. | The assistant writes reschedules and cancellations itself. |
| Channels | Booking page only. | Email, WhatsApp and page chat. |
| Hosting | Vendor cloud only. | Cloud or your own server (MIT core). |
| Paid meetings | An add-on or a higher tier. | A price per slot via Stripe Connect. |
| Data | Stored on the vendor side. | In your own PostgreSQL on self-host. |
Hand your calendar traffic to the assistant.
Ten-minute setup: connect the calendar, add an event type, pick the assistant’s channel.