A rescheduled demo shows as canceled
How you'll know: Meeting reports undercount, because every moved meeting carries "Canceled" in its title.
Fix: Calendly updates the old event through its CancelEvent flow, and the rescheduled one keeps that wording unless an admin changes the flow. Edit it so a reschedule updates one event instead of reading as a loss.
Events owned by the System Administrator
How you'll know: New leads and meetings belong to the admin user, not the rep who took the call.
Fix: That happens when the rep's Calendly email doesn't match their Salesforce email. Make the two match, then reassign what's already landed.
A new lead for someone who is already a contact
How you'll know: A customer books with a personal email and turns up as a fresh lead beside their contact record.
Fix: Matching only uses the Salesforce ID or the exact email. Send booking links from Salesforce with the record's ID attached, and add duplicate rules that catch the rest.
Your lead router reassigns Calendly leads
How you'll know: A lead booked with one rep, then LeanData or Distribution Engine handed it to someone else.
Fix: Calendly's guidance for both is to exclude records flagged CalendlyCreated, and leads that already have an owner, from your routing rules.
A booked demo, but no opportunity
How you'll know: Sales asks why the pipeline doesn't show this week's demos.
Fix: By default the package logs an event on a lead or contact. Opening an opportunity or moving a stage takes a Salesforce Flow that reads which Calendly event type was booked.