DocsCore ConceptsBooking System

Booking System

Conversion

Visitors book appointments inside the chat, without leaving your website or filling in a separate form.

How booking works

Intent detected
Services shown
Date picked
Slot picked
Details
Confirmed
  1. 1

    A visitor shows interest, or asks to book

  2. 2

    The agent offers booking at the right moment

  3. 3

    Available slots are generated from your availability rules

  4. 4

    The visitor picks a service, a date and a time

  5. 5

    Details are collected and the booking is confirmed instantly

Slot capacity is validated on the server, so two people cannot take the last slot at the same time.

Availability & working hours

  • Working days — enable or disable each day, Monday to Sunday
  • Time range — for example 9:00 AM to 5:00 PM per day
  • Slot duration — how long one meeting lasts, 30 minutes is a good default
  • Buffer time — a 5–15 minute gap between bookings so you are not back-to-back
  • Blocked times — block holidays or a specific afternoon without changing your rules

Services

A service is what the visitor is actually booking. For each one you set:

  • Name — Consultation, Demo Call, Site Visit
  • Description, duration, price and maximum capacity
  • A colour and icon so it is recognisable in the chat and dashboard
  • Which AI Agent may offer it

Booking behaviour

  • Intent-based — the agent notices interest and offers a slot itself
  • User-requested — the visitor asks to book and the modal opens
  • Keyword triggered — phrases like “book a call” open booking directly

After a booking

  • The slot is reserved and appears under Dashboard → Bookings
  • A confirmation is sent to the customer
  • With Google Calendar connected, the event is created in your calendar and your real busy times are respected
  • Reminder channels can notify you by email or on your connected messaging channel

Best practices

  • Define working days properly — the most common mistake is leaving every day off
  • Use 30-minute slots as standard
  • Always add buffer time
  • Keep services few and clearly named
  • Book a test appointment yourself before launch