This is for creating a client-facing endpoint that would run the cancel meeting flow when executed.
The public cancel URL with the following structure:
https://subdomain.chilipiper.com/book/cancel/{Event.Id}
Where the {Event.Id} at the end would accept:
- CP Event ID
- SFDC Event ID
You can configure your Meeting Templates and reminders to contain:
{!CP.Meeting.CancelURL}
Both internal team members and external users with this URL will be able to cancel the meeting.
Behavior
When the cancel URL is clicked for a meeting, the expected behavior is the following:
- The prospect/customer will see a screen asking them to confirm the cancelation or reschedule with the date and time of the originally booked meeting.
- Upon confirming the cancelation, the following will happen:
- The User who clicks on the confirm button will see a confirmation message.
- The Meeting and any associated meeting buffers will be deleted from the Calendar.
- The Assignee will receive an email notification that the meeting has been canceled, and the URL will reflect this:
- If using webhooks during the original booking, a webhook will be sent with actionType = ‘prospect_cancel’ and CP Event ID to let your system know the meeting was canceled.
- If you are embedding the URL within a page, Chili Piper adds a new message to the browser `prospect_cancel` that will send once the cancelation is confirmed, allowing you to perform actions such as redirecting away from the page.
- If the prospect attempts to reschedule the event, they will be presented with a message indicating it has instead been canceled: