Reschedule the specific occurrence only after confirming its original date and the customer's intended scope. Show the proposed move alongside the appointments that will remain unchanged, apply an occurrence-specific change, then read the calendar back. If the request could mean several dates, stop the change and ask for clarification.
For a South African service business, this can be a practical receptionist workflow: move a customer's regular consultation once without shifting every subsequent booking. The checklist below provides a proposed process for staff or a custom automation; it is not a built-in product feature.
Separate the appointment from its recurring pattern
A recurring booking has two things to identify: the repeating arrangement and the individual appointment the customer wants to change. An appointment that has already been moved needs particular care because its current date may differ from its place in the original pattern.
Microsoft Graph distinguishes these when retrieving calendar information. Its calendar documentation says an events list contains single appointments and series masters, while a calendar view over a time range returns occurrences, exceptions and single appointments. A series-level listing alone therefore does not give you the same view of the actual scheduled dates. Source: Microsoft Graph calendar resource
In your proposed workflow, record the owning calendar, series reference, occurrence reference, original scheduled date and current date. Keep the customer's booking reference too. Staff should be able to match these records without relying on a title such as “Monthly consultation”.
Before deployment, check current account, plan and region eligibility, calendar permissions, and the provider's documented occurrence-update behaviour. The supplied calendar overview establishes how appointments can be retrieved; it does not establish every detail of changing recurrence.
Ask a scope question that names the dates
“Move my regular appointment” leaves the most consequential detail unresolved. Offer three plain choices: this appointment only, this appointment and future appointments, or the whole series. Treat them as separate requests with different previews and approvals.
For a single move, confirmation should name the original date, proposed date, start and finish times, and timezone. For example: “Move only your appointment on 14 October 2026, from 09:00–10:00 to 15 October, 11:00–12:00, Johannesburg time. Your other appointments stay as booked.” All dates and times in this example are hypothetical.
Do not interpret “yes” without knowing which proposal it answers. Attach the response to the exact preview. If the customer changes the time afterwards, prepare a new preview and obtain fresh confirmation.
For future appointments, establish a start date and whether previously moved appointments should keep their exceptions. For a whole-series request, clarify whether past appointments are intended to change. Neither should inherit approval from a one-appointment request.
Preview the affected dates before saving
The preview should answer two questions immediately: what moves, and what stays put? For one occurrence, display the old and new appointment plus the next scheduled occurrence. Include any nearby exception that could otherwise make the result confusing.
For multiple dates, show the affected date list, the recurrence end date where present, and any existing exceptions. If the series has no end date, say so and explain the proposed future rule. A sample of upcoming dates must be labelled as a sample; it cannot imply that those are the only dates affected.
Check the destination slot for the appointment's actual duration and required staff or room. Microsoft Graph documents free/busy retrieval for users and resources, but your application must decide which availability checks this particular booking needs. Source: Microsoft Graph availability methods
If the slot is unavailable, offer alternatives without changing the existing appointment. Preserve the original booking until the customer approves a feasible replacement.
Reusable checklist for moving one occurrence
Use this checklist as the staff handoff and approval record. These are proposed operating rules, including the requirement to verify neighbouring dates.
- Match the customer and booking reference to the owning calendar.
- Identify the series and exact occurrence; record its original and current date.
- Confirm scope explicitly: one occurrence, future appointments or whole series.
- For this checklist, proceed only when scope is one occurrence.
- Record the proposed start, finish, timezone, staff and location.
- Check the destination slot and required resources; keep the original booking while unresolved.
- Preview the old and new appointment, next occurrence and relevant existing exceptions.
- Obtain customer confirmation for that exact preview and staff authorisation where required.
- Recheck the booking immediately before saving; rebuild the preview if anything changed.
- Apply only the verified occurrence-specific operation; never substitute a series update.
- Read back the moved appointment and compare the series pattern and neighbouring dates with the before-change record.
- Record the result and notification status; confirm success only after verification.
- If the result is uncertain, pause retries and ask staff to inspect the calendar.
Worked cases: ordinary, missing, ambiguous and duplicate
All booking references, dates and times in these cases are hypothetical.
Ordinary request: Booking B-204 repeats on the 14th of each month at 09:00. The customer asks to move only 14 October 2026 to 15 October at 11:00. Staff match the occurrence, check the replacement slot and obtain confirmation. Expected handling: save that occurrence only, verify its new time, and check that 14 November remains at 09:00 and the recurrence pattern is unchanged.
Missing occurrence: The customer refers to 14 October, but no matching appointment appears. Staff check the correct calendar, customer reference and surrounding dates for an earlier move. Expected handling: explain that the appointment has not yet been located and request the original confirmation. Do not create a replacement that might become a duplicate, or change the closest-looking appointment.
Ambiguous request: “Can we do Thursdays instead?” follows a conversation about one October booking. Expected handling: ask whether this means the October appointment only or future appointments too. If it means future appointments, identify the first affected date and prepare a separate series-change preview. Leave existing bookings untouched while awaiting the answer.
Duplicate candidates: Two calendars contain the same customer name and appointment time. One may be the booking record and another a staff copy, but that relationship is unverified. Expected handling: staff establish which record controls the booking and how the other is maintained. Update through the agreed booking process; never move both merely because their titles match.
Keep interpretation separate from the calendar change
AI may help extract a requested date and proposed scope from a message. Require missing details to remain marked as missing. The booking lookup and approved change should use verified records rather than a model's guess.
Structured Outputs can constrain an AI response to a supplied schema. That formatting capability does not establish that the selected appointment or inferred intention is correct. Use explicit fields for unresolved scope and missing dates. Source: OpenAI Structured Outputs
OpenAI's function-calling guide describes the model requesting a tool call and the application executing it. In this proposed design, the application checks the approved occurrence and scope before allowing the calendar operation. Source: OpenAI function calling
Where suitable, n8n documents human review that pauses a selected AI tool until a person approves or denies its inputs. Approval should show the appointment details and scope clearly. Source: n8n human review
For implementation planning, compare AI agents and automation, then use the custom AI agents workflow guide. The custom AI agent definition provides shared terminology for the brief.
FAQ: recurring appointment changes
What if the appointment was already moved once?
Match its original occurrence identity and current scheduled time. Include both in the preview so the customer recognises the booking. Staff should verify that the second move updates the same appointment rather than creating another replacement.
What if the save times out after approval?
Treat the result as uncertain. Read the calendar before retrying and check whether the approved move already happened. Staff should resolve any mismatch before another attempt. A timeout alone proves neither success nor failure.
What should we check if the whole series moved accidentally?
Pause further changes and compare the calendar with the before-change record. Identify affected dates, existing exceptions and any updates already sent. Staff should approve a correction plan before restoration; avoid a blanket reverse move that could overwrite legitimate changes.
If your business needs recurring bookings handled with explicit scope checks, workflow automation can form part of the implementation brief. Explore AI automation, or get in touch with a sample booking pattern and the rules your staff currently follow.