enaudo
Coordinate appointments using real availability
Scheduling can be automated by checking calendars, required resources and booking rules together. The workflow offers available times and confirms a booking only after checking again. Rescheduling and cancellation remain traceable in the same case.
When this workflow helps
This example helps service businesses that need several calendars, people or rooms to line up for an appointment. A gap in one calendar is not enough if travel, preparation or capacity is missing. The workflow therefore needs named availability sources and explicit rules for duration, buffers and eligible people.
The workflow, step by step
Hello, we are planning a company event for 12 people. Is 14 May still available?
Reply draft Please review Sent
Could we move our appointment back by one hour?
Reply draft Please review Sent
We are now coming with 20 instead of 15 people. Does that still work?
Reply draft Please review Sent
Contacts
May
14 May
No appointments on this day.
Try it: pick a day in the calendar and jump from the appointment to the matching conversation. Nothing is sent or saved.
Examples built for this website with invented data: no client systems, no references, no AI running. The scope is defined per project.
-
Capture the request
Record purpose, duration, attendees, preferred time and time zone in one case.
-
Check availability
Compare permitted calendars and capacity with working hours, buffers and resource needs.
-
Offer valid options
Present available time windows with an explicit time zone. A suggestion is not a confirmed booking.
-
Confirm the booking
ApprovalThe owner approves the selected time. Recheck availability and any capacity reservation before writing the event.
-
Record the appointment
Create one calendar event linked to the case, check invitation status and record confirmation.
-
Reconcile changes
Process rescheduling or cancellation against the same event reference and track notifications to affected people.
Data, systems and people involved
- Required calendars and resources with checked read and write permissions. Free/busy information may be sufficient; private event details are not copied unnecessarily.
- Rules for appointment type, duration, working hours, buffers, capacity and any travel time.
- Unique attendee and event references plus an agreed approach to time zones.
- For deadlines, a confirmed source, the applicable date, advance notice and the person responsible for deciding what happens next.
- A scheduling owner and backup who decide special requests, priorities and conflicts.
What runs automatically and who decides
Availability queries, suggestions, reminders and reconciliation of approved changes can run automatically. In this example a person decides the booking and exceptions to capacity rules. A separately agreed set of rules may permit narrowly defined standard bookings. Conflict checks, eligible resources and error handling must be established first. For contract or certificate deadlines, the confirmed source creates an advance follow-up task. Missing responses are escalated to the agreed backup. This does not automatically trigger cancellation or renewal.
Exceptions, errors and stopping points
- Two people select the same slot: Recheck at confirmation and allow only one booking where the target system supports safe reservation. Otherwise refer the conflict for manual resolution.
- Calendar access is missing or the data is stale: Do not claim that capacity is available. Route the request to the scheduling owner.
- An event moves, is cancelled or an invitation fails: Update the existing event and verify the new state. Do not create a second booking to compensate for an uncertain first attempt.
- A deadline or its source is unclear: The responsible person establishes the date. A reminder does not confirm that the required business action was completed.
A useful first scope and acceptance check
Begin with one appointment type and a small set of calendars, or a clearly defined deadline list. Check a regular booking, simultaneous slot selection, time zones, rescheduling and cancellation. For deadlines, also test a missing response. Acceptance requires matching event and case states, visible conflicts and no binding confirmation when required permissions are missing.
Related workflows and implementation
Frequently asked questions
Is a free calendar slot enough?
Only if all required people and resources have been considered. Duration, buffers, working hours and capacity can rule out a slot that initially looks free.
How are different time zones handled?
The case stores an unambiguous point in time and the necessary time-zone information. Suggestions and confirmations show the appropriate local time. Clock changes belong in the acceptance checks.
Can our existing booking system stay?
Yes, if it can provide the required availability and changes through a checked route. The permissions and features of your actual configuration are verified first.
Can contract deadlines be tracked too?
A deadline can be tracked as a separate case with a source, date and owner. That is a follow-up task rather than an appointment booking. Binding follow-up actions are reviewed and approved separately.
If a process is eating time in your team, describe it. We will say honestly whether automation is worth it.