A customer texts to move Thursday's appointment to Friday afternoon. You're between jobs and reply, "That should work." Later, someone books the space you had in mind. Thursday's visit is still on the technician's calendar.
Consider a small mobile detailing business serving Orlando and nearby neighborhoods. This is a fictional example. A reschedule affects the customer, the person doing the work and the drive between appointments. The useful question is simple: which time can the customer and technician actually rely on?
Give each change a clear status
First find out whether the customer is asking about another time or telling you the original appointment is impossible. If they're asking, keep the original booking until you agree otherwise. If they cannot attend, mark the visit as needing a new date and stop dispatch for the old slot. Tell the technician directly if the visit is close.
Keep the same visit reference while its time changes. Record the request, who is handling it and when they will reply. Keep an unresolved request on that person's follow-up list until it is confirmed or canceled; a missing calendar event is easy to forget. Use plain labels: "needs new time," "time offered" and "confirmed." These are your operating rules, not a claim that every calendar has those statuses.
Check the whole visit before offering a slot
A gap on the calendar only tells part of the story. Allow for the service, setup and travel from the previous job and on to the next one. Check that the assigned person and equipment are available. If the customer has changed the address or added a second vehicle, reconsider the duration before agreeing.
Offer a specific arrival window, with a date and local time. Explain how long you can hold it. An internal calendar block labeled "HOLD" can reserve the capacity temporarily, but someone must release it when the deadline passes. This is a manual convention, not an automatic expiry feature.
Choose one person to approve schedule changes during each shift. Others can pass along requests. If several people can promise the same opening independently, a shared calendar won't prevent competing commitments.
Close the loop with both the customer and the technician
Once the customer accepts, recheck availability before confirming, especially if the reply arrived after the hold expired. If the offered slot is gone, offer another time instead of treating a late reply as a booking. Once a time is agreed and available, update the existing visit, record the agreement and remove the temporary hold. Avoid leaving two confirmed appointments for the same work.
Send a short confirmation with the service, address and new arrival window. State that it replaces the previous appointment. For example: "Your detailing visit is now Friday, October 23, with arrival between 1 and 2 p.m. Eastern, at the address we confirmed. This replaces Thursday's appointment." Use the customer's actual agreed details.
If you use Google Calendar, an edited event with guests can send email updates. Google's invitation documentation also explains that guests can turn off change emails and that some invitations require a response before appearing on their calendar. Sending an update doesn't establish that the customer read it or accepted the change. Keep their agreement in the job record and use the communication channel they've agreed to use.
Have the assigned technician acknowledge the revised schedule before departure. A customer-facing invitation should contain only details the customer needs. Keep internal notes, access codes and payment information out of it.
Try it with the tools you already have
If your booking system already manages reschedules, holds and staff assignments, review those settings first. A second calendar maintained by hand may create another place for times to drift apart.
For a small operation using a shared calendar, begin with the status labels, one scheduling owner and a short pending-changes list. Use accounts and storage your business approves. This manual process needs no paid add-on or AI service.
A public booking page is a separate decision. Google says a personal Google Account can create one booking page; premium features include email reminders and checking multiple calendars. Check the plan requirements before relying on those features. A booking page still needs rules that fit service duration, geography and travel. Keep human review if those factors vary too much to offer reliable slots.
Try three fictional changes before using the process: a request accepted before the hold expires, a late reply and a customer who can no longer attend the original visit. Ask the scheduling owner and technician to identify the current time, what is pending and who acts next.
For the first week, review pending changes before the day's departures. If requests keep getting stranded between inboxes, consider a small integration that creates a review task. Keep approval with a person until your availability rules are dependable.
The job handoff example shows how agreed changes can reach the team doing the work. If reschedules regularly leave you chasing messages, we can discuss a first change to your current process.