Skip to main content
J
John Cleary
Community Member
June 9, 2025
Question

Stop people from creating a duplicate booking for a specific group event

  • June 9, 2025
  • 2 replies
  • 256 views

I have set up regular monthly group events for my clients to book onto. The numbers for each event are limited to 5. Increasingly regularly, clients are booking themselves onto the same instance more than once.

For example, this week, 3 people have booked for the event, and 2 of them have booked twice, which means that the session shows as full to other potential clients and leaves me with a 60% full session.

Surely, there must be a way to stop people from booking onto the same session more than once??

This topic has been closed for replies.

2 replies

David
Community Manager
David
Community Manager
June 9, 2025

Hi ​@John Cleary - Thanks for reaching out.

At this time, there is not a way to prevent users from booking in a single event multiple times through the Event Settings. In this case, we recommend users utilize the Single Use-Link to prevent this from happening. You can read more on this here: https://help.calendly.com/hc/en-us/articles/30121266128535-How-to-create-a-single-use-link#h_01JMJ67S2J4095AFP4G5F8V9GS

I know it might not be the best solution, but I’ll forward your feedback to our product team, hopefully we’ll see more on this in the future!

J
John ClearyAuthor
Community Member
June 9, 2025

Thanks ​@David  Unfortunately, single-use links won’t work for my business…I would need to issue them manually for, what I’m planning will be, 300 people each month.

I have two solutions... make sure that people put the appointment in their diary when they book so that they know they’ve booked, which despite my best efforts doesn’t seem to be happening OR the system stops the same person (email address) from booking onto the same instance of an event twice.

I can imagine a few Calendly clients welcome the ability for people to make multiple bookings for the same instance of an event. However, surely it’s not a massive ask to add the ability to stop this from happening? 

Terms & ConditionsAccessibility statement