Overview
A Calendly reschedule can produce both a canceled-invitee notification and a created-invitee notification. If your answering workflow sends scheduling updates into another system, confirm that it recognizes one changed appointment instead of creating unrelated follow-up tasks. This is a planning checklist for your administrator and provider, not a claim that AnSer supports a particular connection.
Distinguish a reschedule from a cancellation
Calendly documents that rescheduling triggers both invitee.created and invitee.canceled webhooks. The canceled payload marks rescheduled as true, and the new payload represents the replacement. Its old and new invitee references belong to the invitee model because the reschedule is per invitee. For a group event, confirm the affected attendee rather than treating the entire event as canceled. Ask the integration owner to show how those references connect the two records.
Do not infer the outcome from the subject of one email or the arrival of one update. Identify the original appointment and verify the replacement in the scheduling system before confirming the final time to the caller.
Define what should change downstream
- Identify which appointment the office should now attend and which prior appointment should no longer be treated as active.
- Check reminders and follow-up tasks tied to the original time; agree on how they are retired or updated.
- Preserve useful intake context while associating it with the replacement appointment.
- Assign an owner to investigate when the scheduling record and the receiving system disagree.
Test a reschedule separately from a new booking
Use an authorized test appointment with fictional details. Change its time, then inspect both the scheduling record and any receiving CRM or task system. A new-booking demonstration alone does not show whether the integration handles an existing appointment changing.
Also test a cancellation with no replacement. The expected business result differs: staff should not search for a new appointment that the caller never requested. Have the administrator demonstrate the distinction using the supported workflow, rather than guessing from the order notifications appear.
Confirm only the outcome you can see
Give the answering team approved wording for a confirmed change and a change still under review. If the replacement cannot be verified, record the request and route it to the responsible person instead of promising that the new time is booked.
Close the test when the current appointment, staff work list, and caller-facing confirmation agree. Record any remaining reminder or integration problem separately so a successful calendar change does not hide unfinished follow-up.
