Connect a calendar
Configure Microsoft 365, Google, or Progenda, and select calendars accessible to the bot.
BeAI separates Microsoft 365, Google and Progenda calendars so that each connection maintains its own rules.
Add a connection
- Enable the skill corresponding to the provider.
- Select Add connection.
- Authorise BeAI with the provider or enter the requested information.
- Select the calendars that the bot can view or modify.
- Add a specific instruction if multiple calendars have different purposes.
For Progenda, connection details, status and synchronisation remain directly visible. The Manual Progenda identifiers panel lets you enter calendar and centre identifiers when synchronisation cannot find your calendar. Otherwise, keep the existing values. Closing the panel does not clear these credentials.
Restrict accessible calendars
The connected account may see more calendars than the bot does. Only add the necessary calendars. Use Add another calendar to complete the selection without recreating the connection.
Renew a connection
BeAI attempts to automatically renew compatible tokens. If the status turns red, use the reconnect button: selected calendars and their instructions are preserved.
Test the end-to-end journey
Ask the bot to:
- check availability;
- suggest a time slot;
- confirm the details;
- create the appointment;
- read back the date and time in the correct time zone.
Then check the event directly in the relevant calendar.
In DEV environments only, each event search performed by the bot deliberately adds 3 seconds of wait time to test the activity sound while the tool runs. This delay does not apply in production, nor to appointment creations, modifications or deletions. It requires no bot configuration.
Reschedule an existing appointment
To move, postpone or reschedule an appointment, the bot follows a journey distinct from a new booking:
- it uses the exact identifier provided by a trusted workflow or searches for the appointment within its original period;
- it precisely identifies the relevant event;
- it checks the new slot;
- it modifies the existing event without creating a duplicate.
An event identifier and a calendar identifier are two distinct values. Events returned by BeAI contain both to avoid any confusion. For Microsoft 365, BeAI also verifies the event's actual parent calendar before making the modification and applies the permissions configured on that calendar.
When an outbound call receives an calendar_event_id in its trusted context, BeAI re-injects this exact value at the time of modification. This protects opaque Microsoft 365 IDs from alteration during the call. The calendar ID is also adjusted when only one calendar authorised for modification matches the connection; in the event of ambiguity, BeAI does not choose a calendar on the bot's behalf.
If multiple events match or if the original appointment cannot be found, the bot asks for clarification instead of creating a duplicate. To make this journey reliable, provide the event ID in the instructions or known context or, failing that, the original date, time, contact name and appointment title.
Customise a booking journey
In the instructions for the bot and the selected calendar, specify pricing, time zone, mandatory information and the summary to be confirmed before writing. A quote is not a booking: the bot must wait for the calendar tool to succeed before announcing a confirmation. Disable connections from previous scenarios to avoid conflicting instructions. The same instructions can be accessed via the bot API, in extra_infos and calendar_connections[].selected_calendars[].prompt. Bot edit rights and calendar permissions remain required.
For a multi-seat resource, describe the concurrent capacity and request a check of the entire period, followed by a re-verification before writing. Multiple successive events do not necessarily mean multiple seats occupied at the same time. A capacity specified in a prompt does not provide a lock against concurrent bookings. The generic "busy" result indicates the presence of a blocking event; it does not calculate multi-seat capacity. If access to the calendar fails, no availability or booking must be announced as confirmed.
Calendar actions and responses
Every calendar lookup, event search, creation, modification or deletion is visible in the conversation actions, along with its date and result. A failure remains displayed as a failure; it does not confirm any booking. The Calendar filter, exports and the conversations API use the same history and access permissions. Internal tools such as time or hangup do not create calendar actions.
During a call, BeAI transmits short references specific to that call and a single copy of each relevant event to the AI. BeAI resolves the Microsoft 365, Google, or Progenda identifiers before executing the operation. Times, non-blocking events, and information required for availability are preserved; no artificial limit on the number of events is applied by this reduction. An unknown reference or one associated with the wrong calendar is rejected. Logs and the API retain provider identifiers for tracking.
This reduction decreases the context sent to the model. It does not constitute a cost guarantee per call: billed tokens may include context carried over across multiple responses and tool steps.
Local times and time zone
For "today", "tomorrow" or "the day after tomorrow", the time tool provides the exact date and day of the week calculated in the bot's time zone. The bot must include the day corresponding to the booked date in its summary; if it does not have a verified day, it only announces the date and times.
Dictated times are interpreted in the bot's time zone, with automatic daylight saving time adjustments. For Europe/Brussels, 9:00 corresponds to 09:00:00+02:00 in summer and 09:00:00+01:00 in winter. The Z suffix indicates UTC: it must not be added to a local time. BeAI passes the local time and its time zone separately to Outlook. Dates without an offset use the configured time zone, not the server's.
If a tool provides an offset incompatible with this time zone, the request is rejected before any read or write operation with the provider. The bot receives an instruction to verify and reformat the times, then try again. It must not confirm a rejected booking. A time explicitly provided in UTC must first be converted to local time.