Understand your work OS
Calendar & Booking: agree on a time. Arrive prepared.
Online booking is one capability of your company’s environment. Share available times and useful questions in one link, let the customer confirm, and keep the answers with the appointment.
Requesting an appointment and confirming a time are different.
A customer can express an appointment request in the agreed journey. Availability, booking rules and confirmation follow the configuration documented here. Calendar documentation does not mean that every journey is included in the customer base scope.
Everyday work
An appointment in the calendar. But who has the details?
Finding a time takes several messages. Then someone still needs the address, the reason for the visit and the access instructions. Booking brings those answers into the invitation instead of leaving them scattered across conversations.
One invitation, shaped around this visit.
Address · Access · Reason for the visit
01Prepare the invitationOffer times that work.
“Prepare a 45-minute visit on Tuesday afternoon. Offer three times.”
Tuesday: 2 pm, 3 pm or 4 pm. Only the availability offered for this request is shared.
The invitation can be enriched before the customer books.
02Collect the answersAsk what the visit needs.
The customer selects 3 pm and provides the useful details in the same place.
Address: 12 Station Road. Access: ask for Camille at reception. Reason: diagnose a recurring fault.
Selecting a time is not the final booking confirmation.
03Confirm and prepareA time, a customer, a reason to be there.
After successful confirmation, the appointment is created in AlefOS.
Tuesday, 3–3:45 pm. Camille, 12 Station Road. Reception access. Diagnostic visit.
This invitation can no longer be booked. External calendar synchronization has its own status.
Fictional example, not a product screenshot. Sources and access require configuration; illustrated answers use the information shown.
The booking is only the beginning.
Before the visit, retrieve the available customer context and what needs preparing. Afterwards, use the recorded outcome to prepare the next step. A scheduled appointment and the content of a meeting remain distinct.
Keep the decisions after the meetingOn this page
- A link suited to the appointment
- Track what still needs an answer
- Prepare and continue the work
- Calendar events and meeting content are separate
- Creation, changes and confirmation
- Shape the invitation, then enrich the same link
- What confirmation changes
- Booking tools and availability
- A customer asks. Your team confirms.
- Tools and prerequisites
A link suited to the appointment
The employee prepares availability, booking questions and useful instructions. The customer chooses an offered time and answers in the same place.
The booking link serves a specific appointment. It does not expose the employee’s entire private calendar or make all company availability public.
Track what still needs an answer
Where the relevant tracking is available, the interface distinguishes sent links, pending answers, completed bookings and appointment sources. A sent link is not a confirmed appointment.
Customer answers, the subject, contact matching and preparation context must remain associated with the appointment instead of disappearing behind a date and time.
Prepare and continue the work
Before a visit, the file can show its purpose, access conditions, required document and linked missions. After the appointment, decisions and next actions can enrich context in supported workflows.
An appointment keeps a visible owner. Assignment or reassignment in a member’s calendar depends on company permissions; it must not impersonate a colleague.
Calendar events and meeting content are separate
The calendar provides the scheduled time, participants and available event information. A meeting source can provide notes, a summary or a transcript when these have been generated and authorized.
Adding a Google Meet or Zoom link to an event does not prove that the meeting is recorded, transcribed or analysed.
Creation, changes and confirmation
Draft tools let users review a creation or change before confirmation. Direct internal operations are also available for explicit, authorized requests. The list exposed to an assistant depends on the deployed server’s policy.
A preview, a saved event and external synchronization are different states. A local change does not prove every provider accepted the update. Time zones, permissions and provider results still matter.
Shape the invitation, then enrich the same link
Define the duration, time zone and windows to offer. Booking can collect short or long text, an email address, phone number, address, number or a choice from a list. Required questions help the customer provide what the appointment needs.
The invitation concerns one appointment, not a permanent public view of a private calendar. In a team workflow, the setup can preassign a resource or let the visitor choose a member from the permitted resources. The modes available follow the environment’s configuration.
What confirmation changes
An active invitation offers the available choices. Successful booking creates an AlefOS event and consumes the link: it cannot be booked again. An expired or revoked invitation is unavailable. The confirmed appointment page remains available until twenty minutes after the appointment ends in this booking flow.
A reliable Contact match can attach the booking to the relationship. An internal event is not proof of successful Google or Outlook synchronization. Check the scheduling result and provider status separately; if a time is no longer available, the visitor must select an available option.
Booking tools and availability
The Booking contract includes calendar.booking_link.create to create an invitation, calendar.booking_link.get to inspect it and calendar.booking_link.update to enrich or change an eligible invitation. Creating an invitation following an explicit request is different from a customer confirming their booking.
These tools belong to the Booking implementation. Their availability in your assistant must be checked during setup; they are not part of every deployed MCP catalogue. The public link and customer confirmation have their own access rules.
A customer asks. Your team confirms.
“Can you arrange a boiler service?” A customer can request an appointment through your business plugin in ChatGPT. The agreed journey collects the address, equipment and useful details before sending the request to your team.
A received request is not a confirmed visit. Availability, validation and confirmation follow your booking rules. The customer can also use the booking page you share; these are two entry points into the configured process.
Operational reference
Modules, tools and access conditions
This reference describes MCP operations and their effects. The list exposed to your assistant depends on the deployed server, enabled modules and permissions. Reading, preparing and executing are distinct operations.
Calendar and booking context
An invitation, a booking link and a confirmed event are not the same state. Draft tools support review; authorized internal calendar operations can also run directly, according to the deployed tool policy.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
calendar. | List appointments, optionally filtered by date range. |
calendar. | Read an event’s available owner, contact, mission and provider context. |
calendar. | Prepare an event creation preview with an action_id. |
calendar. | Prepare an update or move preview for an existing event. |
calendar. | Assign or reassign an event with the required company role and audit trail. |
Missions and responsibility
Read the source and execution state before acting. Confirming executes a pending mission; rejecting and archiving have different effects. Assignment follows company roles.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
missions. | List the current user’s missions, optionally grouped by contact. |
missions. | Read a mission’s source, related objects and execution state. |
missions. | Confirm and execute a pending mission. |
missions. | Reject a pending mission without executing it. |
missions. | Archive a mission without executing or deleting its action. |
missions. | Assign from the company queue or reassign with the required role; changes are audited. |
The scenarios on this page illustrate workflows, not real customer data or guaranteed outcomes. Connections and capabilities must be enabled and verified for your environment. Official business systems retain their responsibilities.
Continue exploring
A capability of your company’s environment. Your team can use this capability from a compatible assistant through its configured MCP access. The deployment defines the enabled tools and permissions. Understand your AI connection ↗