Changing an appointment — move it rather than lose it
Move an appointment or change its service; availability is rechecked before it goes through.
The problem
A client asking to move is not a lost client — unless moving is complicated. If you have to cancel, recreate, find the record and re-enter the details, the manoeuvre takes time and loses the context of the original appointment.
The real risk of moving things by hand is the silent clash. You note the new date, forget to check what was already there, and create a duplicate you only discover on the day.
A move should be a single operation, and it should refuse slots that are not genuinely free.
How it works in Kagenda
The change happens from the booking detail. The appointment keeps its identity, its client and its history.
- You open the appointmentFrom the calendar, on the slot concerned.
- You change the date, the time or the serviceThe client, their details and the answers to custom fields follow the appointment.
- Availability is recheckedThe new slot goes through the availability engine like a fresh booking: hours, holidays, buffers, resources. An unavailable slot is refused.
- The old slot is returnedIt goes back into booking as soon as the change is confirmed.
Who it helps
Frequently asked questions
Can the client move their appointment themselves?
Not today. From the link received by email they can cancel; to change the time on their own they must cancel and then take a new slot. Moving from the client area is not yet available.
Is the client told about the move?
There is a dedicated email for changes, separate from the original confirmation, so that the message matches what is actually happening.
What becomes of the payment if I change the service?
The payment already taken stays attached to the booking. A price difference is settled outside the move, from your Stripe dashboard.