Appointments
Appointments is the booking native app: availability, capacity, requests, and a public booking page. Install it under Team settings → Apps, then open Appointments in the sidebar.
Overview
- Configure booking policy (hours, capacity, buffers, notice windows, features)
- Manage appointment requests (approve / decline) and upcoming meetings
- Offer a public book page for customers
- Share services with Shop when both are installed
- Agents check availability and book over MCP
- A booking-details field named or labeled like phone/mobile/Telefon is saved onto the CRM contact (matched by email or existing phone; never overwrites a phone already on file)
In the app
Home
- New appointment — team members can book a slot for one or more CRM contacts, choosing staff, service, and an available time; staff bookings skip customer notice/approval rules and are confirmed immediately
- Upcoming meetings — join video when configured, cancel, open contact, open meeting summary when linked
- Request queue — approve or decline pending requests (food & drink teams may assign a table on approve)
Settings / policy
- Open Appointments → Settings
- Set timezone, weekly hours, capacity, buffers, min notice, max days ahead, slot interval
- Optional features: video/conference, service selection, payment at booking, require approval (plan-gated)
- Booking agent — which agent owns booking automations
- Notification email for the team
- Master online booking switch (disables the public page without uninstalling)
- Appearance — choose the public booking page theme and preview it before saving
Capacity can be limited per booking or per person. Booking themes change the public page’s surfaces, typography, spacing, and accent treatment without changing the flow; existing teams stay on the default theme until changed.
blockedDates / holidays may exist on the policy payload for agents/API; there is no dedicated holidays UI in the product today. Appointment policy can also align with team place hours when place is set (update_team_place / place settings) — prefer documenting place on Teams and syncing via policy MCP when automating.
Public surfaces & sharing
Booking page
From Appointments, use Booking page (opens the storefront book URL). Online booking must be enabled in Settings.
| URL | Purpose |
|---|---|
https://store.joai.ai/{locale}/{team}/book | Full booking page (store chrome) |
https://store.joai.ai/{locale}/{team}/book/{serviceSlug} | Pre-select a service |
https://store.joai.ai/{locale}/{team}/book/embed | Embed — same flow, no store header/footer/cart |
Example:
https://store.joai.ai/en/my-shop/book
https://store.joai.ai/en/my-shop/book/haircut
https://store.joai.ai/en/my-shop/book/embedEmbed on your website
Use the embed URL in an iframe so customers book without leaving your site:
<iframe
src="https://store.joai.ai/en/YOUR-TEAM/book/embed"
title="Book an appointment"
style="width:100%;min-height:720px;border:0;"
loading="lazy"
allow="payment *"
></iframe>Notes:
- Replace
en/YOUR-TEAMwith your locale and team slug - The embed path hides store navigation, cart, and footer (
/book/embed) - Give the iframe enough height for calendar + form steps
- Keep online booking on; if disabled, the public/embed pages stop accepting bookings
- For a fully branded multi-page booking app (not just an iframe), use Sites
Other ways to share
| Method | Notes |
|---|---|
| Direct link | Share /book or /book/{service} |
| Smart Links | Short tracked URL to the book page |
| Sites | Appointment brand site on sites.joai.ai |
| Website Widget | Agent chat embed (Website Widget) — not the calendar booking UI |
See Public surfaces.
For agents (MCP)
Requires Appointments (service tools also work when Shop is installed).
| Tool | Purpose |
|---|---|
get_appointment_policy / update_appointment_policy | Policy |
check_appointment_availability | Free slots |
book_appointment | Book a confirmed slot |
reschedule_appointment / cancel_appointment | Change or cancel |
create_appointment_request / update_appointment_request / list_appointment_requests | Request queue |
list_services / create_service / update_service / delete_service | Bookable services; create/update accept priceDisplay (exact / from) |
Typical agent flow:
- Resolve attendees via CRM (
joai-contact-find-or-create/ list) and passcontactIds— prefer that over free-textattendeeName - Check availability with a tight window when a time is already agreed (
windowStart= that time,windowEnd= start + duration). Only use a broad day/range when the user is still flexible - Confirm a slot with the user
- Book with the same
contactIds - If booking cannot complete, create an appointment request
Live schemas: tools/list. See MCP and SKILL.md.
Tips
- Set policy before sharing or embedding the book URL
- Use services with clear durations when you also bill via Shop
- Keep notification email on for team awareness
- Prefer
/book/embedfor iframes; use Sites when you need a full branded web app - When chatting about a specific time (“Wed 7.10 at 11”), do not expand the availability window to midnight→next day
- Book with the exact
startAtfrom availability (includes a numeric offset). Do not invent a trailingZfor a local wall-clock time - Add a string field named or labeled like phone/mobile/Telefon to a service’s booking details when you want the customer’s number on the contact after they book