When a guest cancels a meeting booked through a Chili Piper link, there's no mechanism to capture why. The cancellation registers with no context, leaving reps and ops teams unable to distinguish disinterest from a scheduling conflict from a lead that was never serious.
Let admins configure a cancellation reason prompt shown to the guest when they cancel via a Chili Piper link, and let the admin decide whether providing a reason is optional or required. Reason options should be customizable, and the selected reason should be logged against the meeting record and synced to the CRM where applicable.
Cancellation reason data is high-signal for pipeline health, SDR quality, and marketing feedback loops. Without it, teams managing high cancellation volumes have no systematic way to triage or respond, and leads that cancel without a reason fall through the cracks. Some customers have asked specifically for the ability to require a reason, so this shouldn't be left to the guest to skip by default.