What Is Event Type Mapping and Why Does It Matter?
What Is Event Type Mapping and Why Does It Matter?
Event type mapping tells FullSlot which waitlist to notify when a specific type of appointment is cancelled. Without it, FullSlot has no way to know which clients to contact.
Why mapping matters
Calendly has event types (for example: "Botox Consultation", "Laser Hair Removal", "HydraFacial"). FullSlot has appointment types on your waitlist. Mapping connects them: when a Botox appointment cancels, FullSlot looks up which waitlist corresponds to Botox and notifies those clients.
If an event type isn't mapped, cancellations for that service are silently ignored — no notifications are sent.
How to map your event types
1. Go to Integrations → Calendly. You'll see a list of your Calendly event types alongside your FullSlot appointment types.
[Screenshot placeholder: Integrations page showing event type mapping table]
2. For each Calendly event type, select the matching FullSlot appointment type. If you have a "Botox" event type in Calendly, map it to your "Botox" schedule in FullSlot.
3. Save your mappings. Each mapping is saved immediately. You can update them at any time.
What if there's no matching appointment type?
If you don't have an appointment type in FullSlot that matches a Calendly event type, create one first under Settings → Appointment Types. Then come back to map it.
Do I need to map every event type?
No — only the ones you have a waitlist for. If you don't take cancellation waitlist clients for a particular service, you can leave it unmapped. FullSlot will simply ignore cancellations for that event type.
What happens if I add a new event type in Calendly?
FullSlot won't automatically detect it. You'll need to run a manual sync (Integrations → Sync) and then return to the event type mapping page to map the new event type.
Related articles
- How do I connect Calendly?
- Why did a cancellation not trigger a notification?
- How do I add or edit an appointment type?