Skip to content

Calendar ​

The Calendar page at app.mychatbot.app/calendar is MyChatBot's native booking calendar: your AI sales assistant books, reschedules and cancels events on it during conversations, and your team sees and manages every booking in a day/week grid — staff columns, drag-to-reschedule, client links back to the chat. It can also send booked clients reminders before the visit and a message after it — see Messages to clients.

It is powered by the Calendar integration ("Native booking & scheduling for your AI agent"). This is not the Google Calendar integration — that one syncs an external Google account. See Native Calendar vs Google Calendar below.

At a glance ​

StepWhere in the appResult
Enable bookingIntegrations → pick your assistant → Calendar (under Productivity & Scheduling) → ConnectAssistant can book, reschedule and cancel events
Add Staff Members and ServicesSame Calendar integration card, after connectingRequired — without both, booking doesn't work
Steer the assistantBooking Instructions on the integration cardRouting rules injected into the assistant's instructions
Remind clientsMessages to clients on the integration cardUp to two reminders before the visit and one message after it, in the client's chat
See bookingsCalendar in the sidebar — app.mychatbot.app/calendarDay/week grid of all events
Jump from settingsView Calendar button on the integration cardOpens the Calendar page for that assistant's calendar

Setup incomplete

The integration card warns: "Add at least one staff member and one service for the calendar to work. Without them, your agent won't be able to book events." The Calendar page enforces the same rule — trying to create an event first shows "Please add at least one staff member and one service in Calendar settings before creating events."

Set up the Calendar integration ​

Open Integrations, select the assistant, and find Calendar in the Productivity & Scheduling category. The settings panel is titled "Native booking & scheduling — <agent> can book, reschedule and cancel events".

Core settings ​

SettingDefaultWhat it does
TimezoneUTCThe business clock — the assistant quotes and books all times in this zone (pick from common zones: Europe/Kyiv, Europe/London, America/New_York, Asia/Dubai, …)
Default Duration (min)60Event length when no service duration applies (5–480 min)
Grid step15 min"Controls the Day and Week grid divisions and the step bookings snap to when created or moved." Choose 5, 10, 15, 20, 30 or 60 min
Business Hours Start09:00Start of the bookable window; also the top of the Calendar page grid
Business Hours End18:00End of the bookable window; also the bottom of the Calendar page grid

Click Connect to enable. After connecting, a Save Config button appears whenever you change these settings.

Change the UTC default before going live

Timezone starts as UTC. Until you set it to your business's zone, a customer asking for "tomorrow at 15:00" gets booked at 15:00 UTC — hours off from what they meant. Set it first, then add staff and services.

How times and timezones work ​

  • The Timezone setting is the calendar's clock. The assistant interprets customer requests and quotes available slots in this timezone: "15:00" means 15:00 business time, regardless of where the customer is writing from. Business Hours and each staff member's Schedule are anchored to it too.
  • The Calendar page grid, the New Event form and the event detail panel display times in the calendar's Timezone too — a 09:00 booking in America/New_York reads 09:00 for a teammate in Kyiv. Only when the integration has no valid timezone does the page fall back to your computer's clock.
  • If your customers sit in a different timezone than the business, spell that out in Booking Instructions (e.g. "Customers are in New York; the calendar runs on Europe/Kyiv time — always confirm which timezone the customer means"). The assistant has no automatic per-customer timezone detection.

Staff Members ​

Click + Add Staff and fill:

FieldNotes
NameShown on events, in filters, and as a day-view column header
RoleOptional label (e.g. "Stylist") — also injected into the assistant's instructions
ColorPick from 10 colors; event blocks and column headers use it

Each staff row shows its #number — use these numbers when writing Booking Instructions. Per staff member you can also:

  • Edit — rename or change the role.
  • Schedule — set a per-day working schedule. By default it "Uses business hours (Mon–Fri)"; tick individual days (Mon–Sun) and set a start–end time for each, then Save Schedule.
  • × — delete the staff member.

Services ​

Click + Add Service and fill:

FieldNotes
NameWhat the assistant and the New Event form offer
Duration (min)Auto-fills the event length when this service is selected
PriceOptional ($); shown next to the service and given to the assistant
Group class + Max seatsMarks the service as a group session with a seat limit (the badge reads "Group · N seats"). Group sessions are booked by seat count, not by free slot — several customers hold the same time until the seats run out

Services also get a #number for use in Booking Instructions.

Services of a day or longer are booked by the day

A service whose Duration is 1440 minutes (24 h) or more — a room night, a rental day — is offered as whole days rather than as slots inside business hours: the assistant quotes dates, the form shows Check-in Date / Check-out Date, and staff with no schedule are available all seven days. When every service in the calendar is day-based the whole page switches to that mode; a mixed catalog stays hourly. Stays can run up to 90 calendar days; the assistant's book_event accepts a nights count for exactly-one-day services and refuses longer spans with "Book the stay in consecutive parts or ask an operator."

Booking Instructions ​

Once you have at least one staff member or service, a Booking Instructions section appears:

  • A read-only preview labeled "Auto-injected into agent's instructions:" lists your staff and services with their numbers, names, roles, durations and prices — this is what the assistant knows automatically.
  • A free-text box for your own rules, e.g. "Staff #1 (Anna) handles only Service #2 (Haircut) and #3 (Coloring). Always require phone number. Minimum 24h advance booking."

Click Save Config to apply.

Write rules by number

Reference staff and services by the #numbers shown in the lists ("Staff #1", "Service #2"). That's the unambiguous way to route bookings — names can repeat or change.

Below Booking Instructions, Messages to clients sets up reminders before the visit and a message after it — see Messages to clients.

Remove the integration ​

Remove opens a confirmation ("Remove Calendar Integration"): "This will delete the integration configuration. Your existing events will not be deleted." Events stay in place; only the assistant's booking ability and the configuration are removed. There is no event-delete anywhere — see Event details for what Cancelled does instead.

The Calendar page ​

Open Calendar in the sidebar (app.mychatbot.app/calendar). If no assistant has the Calendar integration connected, the page shows "Calendar integration not connected".

Toolbar ​

ControlWhat it does
TodayJump back to the current day/week
‹ / ›Previous / next day (Day view) or week (Week view)
+ New EventOpen the manual booking form
CancelledToggle pill — show cancelled events (hidden by default)
Agent pickerAppears when the account has calendars for several assistants; each calendar is named after its assistant
Staff filterAll staff or a single staff member — filters events and day-view columns
Day / WeekSwitch views; your choice is remembered for next time

The grid ​

  • Day view shows one column per staff member, each headed by the staff name and color dot. Filtering to one staff member shows only that column.
  • Week view shows the whole week (Monday-start) in a single grid.
  • On mobile the page always uses Day view.
  • The grid spans your Business Hours (default 09:00–18:00) in slots of the Grid step setting (15 minutes by default).
  • If nothing is booked in the visible range, the grid reports "No events found".

Each event block is tinted with the staff member's color and shows a status dot, the client name, the service and the staff member:

StatusDot colorNotes
ConfirmedBlueDefault for every new booking (assistant or manual)
CompletedGreenLocks the event — details become read-only
CancelledGrayHidden unless the Cancelled toggle is on; locks the event
No ShowIndigoCustomer didn't come; event stays editable

Reschedule by drag ​

Drag an event to a new time (or another staff column in Day view), or drag its edge to change the duration. The change saves immediately — "Event updated" on success. A drop that overlaps another booking for the same staff member is refused with the conflict message (see Availability & conflicts). The customer gets no message about the change; only the reminders you've switched on follow the new time (see Customer notifications).

Availability & conflicts ​

Whether a slot is protected from double-booking depends on who is booking:

ActionConflict check
Assistant offers slotsOnly free slots: inside business hours (or the staff member's Schedule), in the future, and not overlapping any existing event for that staff member
Assistant books or reschedulesBlocked — the booking is refused with a conflict message naming the occupying event, and the assistant asks the customer to pick a different time
+ New Event formBlocked — "This time slot conflicts with existing event <ref> (<start> - <end>). Please choose a different time."
Drag / resize, or editing staff / service / status in the panelBlocked the same way whenever the change moves the event's footprint — including restoring a Cancelled event, since its slot may have been resold meanwhile

How conflicts are decided:

  • Conflicts are per staff member: two customers can both hold 15:00 with different staff, but the assistant will never give two customers the same 15:00 with Anna.
  • Cancelled events free their slot immediately. Confirmed, Completed and No Show events keep blocking it.
  • The assistant's conflict check applies to any overlap, not just identical start times — a 60-minute service starting at 14:30 blocks the 15:00 slot too.
  • Two bookings may touch: a 14:00 check-out and a 14:00 check-in are not a conflict, so a room can be resold the moment it is freed.
  • Group classes are never overlap-checked — the seat limit is the gate. An event with no staff member holds no resource and is not checked either.
  • Rules the calendar can't express — minimum advance notice, buffer time between bookings — go in Booking Instructions (e.g. "Minimum 24h advance booking").

Create an event manually ​

Click + New Event, or click/drag an empty slot in the grid (the slot's time — and in Day view, its staff column — is pre-filled). The New Event form:

FieldRequiredBehavior
Dateyes—
Start TimeyesChanging it recalculates End Time from the service duration
End TimeyesAuto-filled; edit freely. An end before the start is treated as crossing midnight (next day)
Staff Memberyes"Select staff..." dropdown
Serviceyes"Select service..." — picking one sets the duration; hint shows "Duration: N min (based on selected service)"
Client NameyesType 2+ characters to search your existing clients
Phoneone of Phone/EmailInternational format, validated ("Invalid phone number")
Emailone of Phone/EmailValidated ("Invalid email"); missing both shows "Phone or Email is required"
NotesnoFree text, visible in the event details

Typing in Client Name or Phone searches your client base; picking a match fills name, phone and email and marks the field Linked — the event is tied to that client's card. A live Duration line updates as you adjust times.

Create Event saves the booking with status Confirmed ("Event created"). Incomplete forms show "Please check the required fields."

Before you save

There is no way to delete an event afterwards: a test or mistaken event can only be hidden by setting its Status to Cancelled — which then locks it for good (see Event details). For a stay, the form takes a start and an end date; "A booking cannot span more than 90 days" and "The end must be after the start" are the two checks.

Event details ​

Click any event to open its side panel (header shows the booking Ref):

  • Status badge and start date/time at the top.
  • Time Info — Start Time, End Time, Duration, Channel (which channel the customer booked through, when the assistant made the booking), Created, and Updated if it changed since.
  • Client → View Client Card and Chat → View Chat links appear when the event is tied to a client/conversation — they jump straight to the client's card and the exact chat where the booking happened.
  • Edit Details — change Status (Confirmed / Completed / Cancelled / No Show), Staff, Service, Client Name, Phone, Email and Notes, then Save Changes ("Event updated").

Times are changed on the grid

Start and end times are read-only in the panel — drag the event on the calendar to reschedule or resize it.

Completed and Cancelled are final — no undo, no delete

Once an event is Completed or Cancelled, the panel switches to read-only — no further edits, including status. The app offers no way to revert a locked status and no way to delete an event (removing the whole integration doesn't delete events either). If you mis-click Completed on the wrong event, it stays that way — double-check the Ref and client before Save Changes. No Show does not lock the event. To get rid of a test or garbage event, set it to Cancelled: it disappears from the grid (unless the Cancelled toggle is on) but remains in the calendar's history.

How assistant bookings appear ​

When a customer books through any connected channel (WhatsApp, Instagram, website widget, voice, …):

  1. The assistant uses the staff, services, business hours and Booking Instructions you configured to offer and confirm a slot.
  2. The event lands on the Calendar page as Confirmed, colored by the assigned staff member.
  3. The detail panel shows the Channel it came from, plus View Client Card and View Chat links back to the conversation.

The assistant can also reschedule and cancel existing bookings when the customer asks — cancelled events disappear from the grid until you switch on the Cancelled toggle.

Customer notifications ​

Changes made from the staff side send the customer nothing at the time. Creating an event with + New Event, dragging it to a new time, or switching its Status to Cancelled in Edit Details sends no chat message, no confirmation and no email. What the calendar does send on its own are the messages to clients you switch on: reminders before the visit and a message after it.

ChangeDoes the customer hear about it?
Assistant books / reschedules / cancels in the conversationYes — as part of the chat itself: the assistant confirms in its reply
Staff creates via + New EventNot at the time. The reminders you've switched on follow if the client is Linked
Staff drags to rescheduleNot at the time. The reminders you've switched on follow the new time
Staff cancels or edits via Edit DetailsNo. A Cancelled or No Show booking gets no more messages
Before the visitYes, when you switch on Reminder 1 or Reminder 2 — see Messages to clients
After the visitYes, when you switch on After the visit
Weeks or months laterYes, when you switch on Invite back, unless the client has booked again

To tell the customer yourself, open the event and follow View Chat to their conversation, then message them there. To win back a client after a cancellation or No Show, set up Follow-ups — the calendar won't do that.

Dragging doesn't tell anyone right away

When you drag a booking to a new time, the app saves the change and sends nothing about it, so the customer still expects the original time. Reminders you've switched on go out for the new time, but nobody tells the client the time has changed. Make messaging the client part of your reschedule routine.

Messages to clients ​

The calendar can message booked clients on its own: up to two reminders before the visit, a message after it, and a later invitation to come back. They work for every booking on this calendar — ones the assistant makes in a chat and ones your team adds with + New Event — and your assistant writes them in the client's chat.

In the app

Open Integrations → your assistant → Calendar. Once the calendar is connected, Messages to clients appears below Booking Instructions. Change the settings, then click Save Config. The card reminds you that each message uses one AI reply.

Set up the messages ​

RowThe time you setAllowedSuggested time
Reminder 1How long before the visit starts15 minutes – 7 days1 day
Reminder 2How long before the visit starts15 minutes – 7 days2 hours
After the visitHow long after the visit ends0 minutes – 30 days3 hours
Invite backHow long after the visit ends0 minutes – 180 days30 days (a haircut), 180 days (a dental check-up)

All four start switched off. For each row:

  • Switch — only the rows you switch on are sent.
  • Time — a number plus minutes, hours or days. Reminder 1 and Reminder 2 can't both be on with the same time ("Reminder 2 must be at a different time from Reminder 1"), and neither can After the visit and Invite back ("Invite back must be at a different time from After the visit").
  • Instructions — optional, shown once the row is on, up to 1000 characters: what this message should say or do, in your own words, e.g. "Remind them to arrive 10 minutes early and bring their passport." Left empty, a reminder reminds the client about the visit and asks them to confirm, or to say if they need another time; the after-visit message thanks them for the visit and asks how it went; Invite back invites them to come again and offers to book their next visit.

Below the rows, If the chat can't be reached, send via picks a second channel for messages that can't go out in the client's chat (see Where messages are sent). It starts at Don't send another way. The list offers only connected channels that can write to a client first: a personal WhatsApp, Telegram or Viber account (E-Chat Viber and E-Chat Telegram included), SMS, Calls (the assistant phones the client), Email, or a Binotel, Ringostat or UniTalk line. WhatsApp Business, Instagram, Messenger and Telegram bots aren't offered: they can't start a conversation.

A value out of range is refused when you save, with the reason — for example "Reminder 1: the time before the visit must be between 15 minutes and 7 days" or "Instructions can be up to 1000 characters".

When messages go out ​

A reminder goes out its set time before the booking starts; the after-visit message and Invite back go out their set time after the booking ends. Expect each within a minute or two of that time.

SituationWhat happens
The booking is Cancelled or No ShowNothing more is sent
The message's time had already passed when the booking was madeThat message is skipped. A client who books 3 hours ahead gets no 1-day reminder; a 2-hour reminder still goes out
The message is more than an hour past its timeIt is skipped, never sent late. Say at 15:00 you move a booking to 10:00 tomorrow: its 1-day reminder was due at 10:00 today, so it doesn't go out
The visit has already startedNo reminder is sent
A staff booking with no linked clientSkipped — see the warning below
Invite back, when the client has booked again since this visitNot sent. Any later booking that isn't Cancelled or No Show counts, whether it's still coming up or already happened, on any calendar in your account

When a booking moves to a new time — dragged on the grid, or moved by the assistant in the chat — its reminders are sent again for the new time, even if one already went out for the old time. For any one booking time, each message goes out only once.

Where messages are sent ​

Each message goes to the first of these that exists:

  1. The chat the booking was made in.
  2. The client's most recently active chat, when the booking is linked to a client.
  3. A new chat on your fallback channel, for a client with no chat at all. This works only when the fallback is Calls, a personal WhatsApp account or SMS and the client card has a phone number, or Email and the card has an email. With a Telegram or Viber account (or any other fallback), or with no fallback, such a booking gets no messages.

If a message can't be delivered in the chat, it is sent on the fallback channel instead, when you've set one.

The 24-hour rule on Instagram and Messenger

Instagram and Messenger only let a business write to someone who has messaged it in the last 24 hours. A client who booked in an Instagram chat a week ago and hasn't written since can't get a reminder there. With a fallback channel such as SMS or a personal WhatsApp account, the reminder goes there instead; without one, it isn't sent. A WhatsApp Business number has the same rule for anything that isn't an approved template.

Staff bookings need a linked client

A booking made with + New Event has no chat behind it, so it gets messages only when it's tied to a client. In Client Name or Phone, type and pick the client from the matches so the field shows Linked. A booking with a typed-in name and phone that isn't linked gets no messages.

What the client gets ​

  • The assistant on that chat writes each message from your Instructions and the booking details — service, staff member, and date and time in the calendar's Timezone — in the language of the conversation.
  • The client's reply lands in the same chat and the assistant answers as usual. It can move or cancel the booking if the client asks.
  • Messages also go out in chats your team has taken over from the assistant. There the client's reply waits for your team, as any message in such a chat does.
  • They go out at their set time even when the assistant's working hours have it off right now. An assistant you've switched off, or an empty message balance, still stops them.
  • Each message leaves a Follow-up scheduled entry in the chat.
  • Each message uses one AI reply from your message balance, like any other assistant reply.

Only this built-in Calendar sends these messages. Google Calendar doesn't, and Altegio sends its own reminders.

Native Calendar vs Google Calendar ​

Calendar (native)Google Calendar
Where events liveInside MyChatBot — viewable at /calendarIn your Google account's calendars
Staff & servicesBuilt in: staff members with schedules and colors, services with duration and priceNone — you steer via assistant instructions
Manage bookings in the appFull grid: drag to reschedule, statuses, manual events, client/chat linksNo in-app view
Statuses & no-show trackingConfirmed / Completed / Cancelled / No ShowNot tracked
Best forService businesses running bookings inside MyChatBot (salons, clinics, studios)Teams that already live in Google Calendar and want invites there

An assistant can have only one of the two. Once one is connected, the other's card on the assistant's Integrations page is greyed out, and hovering it shows "Disconnect Calendar first: they can't both be connected to one agent" (or "Disconnect Google Calendar first: …"). To switch, disconnect the one you have, then connect the other.

If an assistant still had both connected from before, it books, checks and cancels only in the built-in Calendar; its Google Calendar is not used. Disconnect the one you don't want so the setup matches what the assistant does.

From Claude or Codex ​

The Sales Platform MCP sets up the same calendar. calendar_get_settings reads it. calendar_update_settings changes the timezone, defaults, business hours and booking instructions, and calendar_set_staff_hours sets a member's week. The calendar_staff_* and calendar_service_* tools manage staff and services. calendar_booking_create and calendar_booking_update book, move or cancel an appointment. Every change shows a preview first. Like a change made on this page, none of them messages the customer at the time.

No tool switches the Calendar on: do that on the assistant's Calendar card, as in At a glance. integration_setup_link with kind: "Calendar" gives the link to that card. In a test chat the assistant's own bookings are only simulated, so to see a real booking on this page, make one with calendar_booking_create and cancel it afterwards. The Calendar tools reference has the full setup order and what each error means.

Use cases ​

  • Salon / clinic / studio front desk — the assistant books clients into the right specialist's column 24/7; staff check their day at a glance.
  • Service routing — Booking Instructions like "Staff #1 (Anna) handles only Service #2 (Haircut)" keep every booking with the right person.
  • Manual + AI bookings in one place — receptionists add walk-ins and phone bookings via + New Event, linked to existing client cards, next to assistant-made bookings.
  • Fewer no-shows — a reminder the day before and another two hours before, each asking the client to confirm or to ask for another time; then a message after the visit asking how it went. See Messages to clients.
  • No-show follow-up — mark missed events No Show, then jump to the chat via View Chat to re-engage the client.

Test it ​

  1. On a test assistant, open Integrations → Calendar → Connect, then add one staff member (+ Add Staff) and one service (+ Add Service).
  2. In a chat with your assistant on a connected channel, ask to book the service — e.g. "Book me a haircut tomorrow at 15:00." Confirm a slot. The test chat shows which times the assistant offers, but its booking there is only simulated and never reaches the calendar.
  3. Open app.mychatbot.app/calendar — the event should appear as Confirmed in the staff member's column at the agreed time.
  4. Click the event: check Channel, and follow View Chat back to the conversation.
  5. Conflict check: from a second test conversation, ask to book the same staff member at the same time — the assistant should refuse the occupied slot and offer a different time. Then try the same overlap with + New Event and with a drag: both are refused with the conflict message naming the other booking.
  6. Timezone check: with Timezone set to your business zone (not UTC), confirm the "15:00" the assistant agreed to in chat is where the event sits on the grid — the grid renders in the integration's timezone, so a shift means the booking was made before you changed the setting.
  7. Drag the event to a new slot — expect "Event updated". Note that the customer's chat shows nothing about the change. Then ask the assistant (in the same chat) to cancel the booking, switch on the Cancelled toggle, and confirm the event shows with a gray status dot.
  8. Create one booking manually with + New Event, typing an existing client's name — confirm the Linked badge appears and the event lands on the grid.
  9. Reminder check: under Messages to clients, switch on Reminder 2 at 15 minutes and click Save Config. From your chat on a connected channel, book a slot about 30 minutes ahead. About 15 minutes before the start, the reminder should arrive in that chat, with a Follow-up scheduled entry. It uses one AI reply. Cancel the test booking afterwards.

See also ​