Make your first booking

Find a suitable time, request the appointment and check the returned confirmation.

Start with a configured team

You need a connected assistant, a team you can access, a service linked to a provider, and permission to book. Follow the team setup guide if those pieces are missing.

1. Find a time

Name the team, service, date and timezone. You can request a particular provider or ask for someone who offers the service. Ask the assistant to retrieve availability before asking it to create an appointment.

Start with a read-only request

Example prompt using a synthetic team and date.

For Demo Studio, find available 30-minute Consultation times with Alex on 2 November 2026 in Europe/Vienna. Show the times and timezone. Do not book anything yet.

Check the date, service duration, provider and timezone in the result. Availability is a snapshot; looking up a time does not reserve it. When clocks change, nonexistent local times are not offered, and a repeated local time is offered at its first occurrence only.

2. Request and confirm the booking

Choose one of the returned times. Give the assistant the customer details needed for the booking, then explicitly ask it to create the appointment. Use the returned start time rather than guessing a UTC offset.

Read the tool’s confirmation, including the appointment identifier, service, provider and start/end times. A proposed time or an assistant’s intention to book is not a completed appointment.

If the result is uncertain

Ask the assistant to check whether the appointment exists before starting again. A retry of the same booking request should reuse its original idempotency key, rather than generate a second intended booking.

3. Handle a conflict deliberately

If the time is no longer available, retrieve availability again and choose another slot. Do not assume the earlier list is still current.

When an authorized member names a provider, a time outside that provider’s working hours, in a break, in a blocked period or on a day off returns outside_availability. After confirming the exception with the user, the assistant can retry with allow_outside_availability: true. An overlap with appointments or unavailability instead returns conflict and needs the separate force override. Neither flag grants permission to the other exception. Staff remain limited to their assigned providers; public booking credentials cannot use either override. For routine bookings, keep to the returned available times.

Find an existing appointment

Ask your assistant to retrieve the booking by its returned identifier. Members can also list bookings for a date range; staff see bookings for their assigned providers. Public credentials use the booking’s manage token and cannot list the team’s bookings. Keep that token private.

Reschedule or cancel

Identify the existing appointment and check its current details.
For a move, request fresh availability and choose a new time for the same service.
Explicitly request the change or cancellation, then inspect the returned result.

Public booking credentials are subject to the minimum notice before the current appointment; a late change can return too_late. Authorized members have different override behavior. A cancelled appointment cannot be rescheduled.

If a request fails

No slots: check configuration, timezone, booking limits and existing commitments.
Permission denied: check the team, role and approved scopes.
Booking not found: check the identifier, team and your provider access; public callers need the matching manage token.

See permissions and access controls, or return to the connection troubleshooting checklist.