Appointment cancellation and rescheduling in chat

Cancellation, rescheduling, waiting list: why changing an appointment takes more effort than booking, how identity is checked and what the law says on fees.

In plain language

Changing an appointment is harder than booking one. The chat has to find the appointment and match it to the right person. A name in the chat is no proof of who someone is. It only changes a request from the chat within the same conversation. It names deadlines but is not meant to judge them. Whether a late cancellation costs money is decided by a person. Moving an appointment is often better than cancelling: first hold the new slot, then release the old one. The business confirms every change outside the chat.

August 20, 2026 13 min read By XICBOT

Key points

A change is not a smaller case than a booking but a larger one: the assistant has to find an existing record, tie it to a person and update several systems.
Identity comes before any change. A name typed into a chat window is not proof; the assistant changes an appointment request taken in the chat only within that same conversation.
The assistant states deadlines but is not meant to judge them. Whether a late cancellation triggers a fee is decided by a person against the company's own rules.
Rescheduling beats cancelling almost every time. Reserve the new slot first, release the old one afterwards.
A waiting list run by the business itself turns a cancellation into a filled slot, provided order, time window and reply deadline are defined in advance.
Every change needs a confirmation outside the chat, and the business gives it; with the assistant the reminder for the old appointment lapses by itself.

Why a change is more work than the booking

A booking starts from nothing. There is no record yet, no assignment, no confirmation already sent, no slot that belongs to someone. The assistant takes preferences, checks availability and creates something new. A change, by contrast, starts from something that already exists and has left several traces: an entry in the calendar, a confirmation in an inbox, perhaps a prepared file, a reserved machine, a member of staff scheduled for it. The assistant first has to find that record, then tie it safely to the person currently writing, and then update every trace. That is why appointment handling in chat regularly fails at exactly the point where it really begins.

Aspect	New booking	Cancellation or reschedule
Precondition	None	An existing record has to be located
Identity	Collected while creating	Must be proven before the change
Write operations	One entry	Release, refill, stop the reminder
Deadlines	Rarely relevant	Decide leniency and any fee
Knock-on effects	Confirmation to one person	Waiting list, staffing, billing
Failure mode	Appointment missing	Two appointments, none, or the wrong person

A cancellation is two operations

It ends an appointment and at the same moment creates a free slot that could belong to someone else. Automating only the first half leaves half the value on the table.

Check identity before anything is changed

The most dangerous shortcut in an appointment assistant is making "What is your name?" the only hurdle. Anyone who gives a common name will otherwise be shown other people's appointments, and anyone who gives someone else's name can cancel them. Personal data is involved here, and the General Data Protection Regulation does not prescribe a particular procedure, but it does demand an appropriate one.

processed in a manner that ensures appropriate security of the personal data, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage, using appropriate technical or organisational measures

Article 5(1)(f) of Regulation (EU) 2016/679

In practice that means the assistant does not know the record because someone typed a name, but because the person brings proof. For an appointment request taken in the chat, that proof is the conversation itself: only an appointment requested in the same conversation can be moved or cancelled, and no other. In the same browser that conversation can be picked up again for a while. If a calendar is connected through a set-up calendar integration (Custom package), the conversation's identifier goes to its interface with every call, and the business decides there what proof it requires for a change. If someone arrives in the chat without that conversation, what remains is the route via the business and, in case of doubt, a handover to a person. We have described how that handover runs cleanly separately.

A change reaches only the appointment requested in the same conversation, and no other.
Without proof the assistant names no list of appointments, no date and no name, not even confirming one.
Where a person checks after a handover, their follow-up question is a second factor, not a repetition: a detail that was in the confirmation, not the name.
Special cases such as an appointment for a child or a stand-in belong in the rules, not in the model's improvisation.
Every reply goes to the stored channel, never to an address newly given in the chat.

Deadlines: technology may calculate, a person judges

Cancellation deadlines live in the terms and conditions or in the appointment confirmation. For them to apply at all they must have been incorporated when the contract was concluded; Section 305(2) of the German Civil Code requires an express reference and a reasonable opportunity to take note of the text. A notice the assistant supplies for the first time during the cancellation conversation does not make up for that. For automation this produces a clear division of labour: the assistant states the stored deadline; whether it has been met and what follows is judged by a person against the time the cancellation came in. Two details govern whether the result is correct: the time zone and the reference point. Twenty-four hours before the appointment is something different from noon on the previous day, and a cancellation at 23:50 local time already falls on the next day in another time zone.

Time of cancellation	What the assistant does	What stays with a person
Well before the deadline	Cancel and release the slot	Nothing
Just before the deadline	Cancel; the time received is in the conversation history	Checking whether the deadline was met
After the deadline	State the agreed rule, release the slot	Whether a claim is raised
No-show	Nothing; it does not learn of it	Note, assessment and any request for payment
Illness or emergency	Record it, do not assess it, pass it on	The leniency decision
Cancelled by the business	If the person writes again, take a new request	Inform the customer; compensation where promised

The reason for this split is not caution but attribution. What an assistant says on behalf of a company binds that company; the OLG Hamm ruling on liability drew that line clearly. A sentence such as "then nothing will be charged to you" is therefore not a courtesy but a commitment the company will be held to later.

The missed-appointment fee: what the law says

Whether a business may charge for a missed appointment is not a question of chat technology but of the contract. For contracts for services the starting point is default of acceptance: someone who does not accept the agreed service although it was available may still owe the fee.

If the person entitled to services is in default of acceptance, the party obliged to render them may demand the agreed remuneration for the services not rendered as a result of the default, without being obliged to render them subsequently. (translated)

Section 615 sentence 1 of the German Civil Code

The second sentence of the same provision matters more for appointment handling. It requires the business to set off what it saves through the absence or earns elsewhere. That is exactly what happens when the freed slot is refilled from a waiting list: the loss is then wholly or partly offset. An automated refill is therefore not only a revenue topic but a fact that changes the size of any claim.

the other party to the contract is not expressly permitted to show that no loss or damage has occurred at all, or that it is substantially lower than the lump sum (translated)

Section 309 no. 5(b) of the German Civil Code

A lump sum in the terms is therefore only effective if the customer is expressly free to prove otherwise. For the assistant this has a very concrete consequence: it may mention the lump sum, but never present it as a settled claim, and never omit the note that a lower loss can be shown. The cleanest line is for the assistant to describe the rule and leave the decision on whether to apply it in the individual case to the business.

Rescheduling almost always beats cancelling

Many cancellations are not cancellations at all. Someone writing "I cannot make Thursday" often still wants to come, just later. An assistant that cancels straight away and signs off loses an appointment that was still there. The better order is to treat the message as a reschedule and only cancel when the person explicitly asks for it. That is not a sales trick but a reconstruction of what was meant.

Record the reason and show two or three fitting alternatives without being asked.
Base the alternatives on the original preference: same time of day, same person, same duration.
Only carry out a cancellation if no alternative fits or the person explicitly asks for one.
When rescheduling, do not ask for a reason where none is needed.
Cap the number of reschedules per record and hand over to a person after that.

Technically a reschedule is two write operations, and their order is not arbitrary. If the old appointment is released first and the new booking then fails, the person is left with no appointment, often without noticing. The correct order is: reserve the new slot first, have it confirmed, and only then release the old one. If the connection drops in between, one appointment too many exists for a short while, and that is the more harmless failure. How an assistant triggers such steps at all is covered under tool control and in detail in the article on function calling.

New slot first, old slot afterwards

The order of the two write operations decides which failure you get when something goes wrong: one appointment too many, or none at all.

The waiting list: turning a cancellation into a booking

A cancellation two days before the appointment is a free slot that someone else usually needs. When someone cancels in the chat, the assistant releases the time directly and the next request can take it. A business that also wants people waiting to move up organises that itself, by hand or in its own system, and it only works if the rules are fixed in advance. A waiting list without a defined order creates resentment, and a notification without a reply deadline blocks the slot just as the cancellation did.

Order

Whoever is first on the list is asked first. Any deviation, for urgent cases say, belongs in a written rule beforehand, not in a case-by-case decision.
Time window

Not every person waiting fits every freed slot. Someone who can only come in the afternoon is not contacted about a morning slot.
Reply deadline

Every enquiry carries a deadline after which it lapses and the next person on the list is asked. Without a deadline the slot does not move on.
Opting out

Leaving the waiting list has to be possible in the same channel in which the entry was made, and take effect without asking anyone.

A waiting list is a collection of personal data that ends with its purpose. Article 5(1)(c) of Regulation (EU) 2016/679 requires processing to stay limited to what is necessary. In practice that means an expiry date per entry, no notes that are not needed for scheduling, and deletion that runs without anyone chasing it. Which periods make sense here is covered under retention periods for chat logs. The assistant does not keep a waiting list itself; whether one achieves anything shows in how often a freed slot was filled again.

Confirmation on a second channel, not in the chat window

A chat window is ephemeral. Once the browser is closed the history is often gone for the customer, and for the business it sits in a system nobody opens when there is a dispute. A change confirmed only in the chat is therefore poorly documented for both sides. The second channel is not an extra; it is the actual record. The assistant confirms no appointment in the chat. That channel is the business's: it sees every appointment request with its current status under Cases, and once it confirms one, the person receives a confirmation email, provided they gave an email address. In addition, it can trigger its own message through a webhook when an appointment comes in and when it is confirmed.

The confirmation names the old and the new state, not only the new one.
It names the time the change was received, in the business's own time zone.
It names the deadline that applied and whether it was met.
It goes to the stored channel, not to an address newly given in the chat.
It says how a further change works: in the same chat conversation or directly with the business.
For a cancellation it expressly stops the reminder for the old appointment.

The last point is forgotten most often. Reminders frequently live in a different system from the calendar, and a cancellation that never reaches it produces a message the evening before about an appointment that no longer exists. To the recipient it looks as though the cancellation never arrived, and the next call ends up with a person after all. Incidentally, the fact that the sender is a machine has to remain recognisable; Article 50(1) of Regulation (EU) 2024/1689 requires that disclosure. What this means in detail is covered in the article on transparency obligations.

What can run automatically and what cannot

Not every change belongs in automation. The dividing line does not run along the difficulty of the case but along the question of whether a decision has to be made that binds the company. Moving and cancelling are executions of a rule defined beforehand. Leniency, claims and exceptions are decisions.

Automatic: after asking, move or cancel an appointment requested in the same conversation and release the slot; the business confirms the moved appointment again.
Automatic: state the stored deadline without assessing its consequences.
With a person: every demand for payment and every waiver of one.
With a person: cases where someone asks for access to a record without proof.
With a person: health-related or personal reasons, which the assistant records but is not meant to assess.
With a person: appointments that involve third parties, such as an escort or an external provider.

How far this split carries can only be measured, not asserted. In our own measurement series 43 out of 48 questions stayed without a handover to a person; that was measured on a single assistant working on our own knowledge base, not on customer projects, and a figure from live operation is not available yet. The method is documented under measurement series. For an appointment assistant this mainly means that the remaining cases are not a malfunction but the part the handover was built for.

Honest limits and a list to work through

An appointment assistant takes work off your hands; it does not replace organisation. Where cancellation rules are unclear, automation makes that lack of clarity visible faster, but no smaller. Where several calendars run side by side, it only moves the problem elsewhere. And where a business has so far judged every cancellation individually, it has to commit to what the rule should be before going live. That is the real effort in such a project, and it is not incurred in the technology. How the booking assistant takes appointment requests in chat and passes them into your process is shown on the product page; which businesses it suits is set out by the industry solutions.

The cancellation deadline exists in writing, was incorporated at conclusion of the contract and is stored in the assistant.
Changes happen only in the conversation where the appointment was requested, otherwise through a person, and without that the assistant discloses no appointment data.
Rescheduling reserves the new slot before releasing the old one.
Cancelling demonstrably stops the reminder, even when that lives in another system.
Waiting list, order, time window and reply deadline are written down, not agreed verbally.
For claims, leniency and no-shows there is a named person and a route to them.

Frequent questions

May an assistant cancel an appointment without checking identity?

Technically yes, sensibly no. Without a check, anyone who knows a name can delete other people's appointments, and the assistant already discloses personal data by confirming that an appointment exists. With our assistant the proof is the conversation itself: an appointment request taken in the chat can only be cancelled in the same conversation, and everything else is handled by the business.

What is the difference between a cancellation and a withdrawal?

A cancellation follows from the contract and its deadlines. A withdrawal is a statutory right in distance contracts and, for certain date-bound services, does not exist at all under Section 312g(2) no. 9 of the German Civil Code. The assistant should not merge the two cases and should hand over in case of doubt.

May the assistant announce a missed-appointment fee in the chat?

It may describe the agreed rule but must not raise a claim. Under Section 309 no. 5(b) of the German Civil Code a lump sum in standard terms is only effective if the customer is expressly free to show that the loss was lower. Whether anything is charged in the individual case is decided by a person.

Why should the new slot be reserved before the old one is released?

Because a reschedule consists of two write operations that can fail separately. If the old slot is released first and the new booking fails, the person is left with nothing. The other way round, at worst one appointment too many exists briefly, and that is noticed at the next check.

How long may waiting-list entries be stored?

As long as the purpose lasts and not a day longer. Article 5(1)(c) of Regulation (EU) 2016/679 requires processing to be limited to what is necessary. In practice that means an expiry date per entry and deletion that runs by itself, rather than a clean-up somebody has to remember.

Is a confirmation inside the chat window enough?

No. Once the window is closed the history is usually gone for the customer and hard to find for the business. The confirmation belongs on the stored channel and names the old state, the new state, the time it was received and the deadline that applied. The assistant confirms no appointment in the chat; once the business confirms it, the customer receives a confirmation email, provided they gave an email address.

Ask it yourself, Assistant of this website

Automated assistant

Settings