We need the ability to block specific people from being able to book meetings - this is a more specific version of the domain blocker where you can block a specific email from being able to book a meeting.
From there, we’d also like the ability to limit the number of meetings someone can book on a meeting link. Calendly has a functionality for a single-use meeting link.
Hey @MBarton00,
Welcome!
This post may be best suited as a feature request in our our Ideas Forum here. Ideas posted in this forum are seen and reviewed directly by our product team regularly, and this is the best way to raise feature requests and increase the chance it will become a feature in the future!
As for the second part of your request, I’d suggest upvoting and commenting on this existing Idea here:
Hope this helps, and thanks for your understanding in the meantime!
Sam, Community Manager
Hi @MBarton00
I like this idea. While domain blocking can help in some situations, there are cases where the issue is a single individual rather than an entire company or domain.
Being able to block a specific email address from booking again would give users much more control without affecting legitimate contacts from the same organization.
I also think the single-use meeting link suggestion would be valuable. For introductory or one-time consultations, limiting a scheduling link to a single booking could help reduce abuse and prevent repeat bookings without requiring users to create and manage new links.
I haven’t seen these options available natively, so I think they’d be worthwhile additions for teams that rely heavily on HubSpot Meetings.
Hi @MBarton00, This ties directly into the meeting link abuse thread I saw earlier, blocking a specific email is basically the same missing control, just framed from a different angle (bad actors vs. general access management).
The single use link idea is a neat one too, worth noting HubSpot’s “Require email verification before booking” setting can indirectly reduce repeat bookings by invalid/bounced addresses, but it’s not the same as a true single-use or per-person limit. Have you found any workaround for the specific-person blocking in the meantime, or is retiring/recreating the link still the only option you’ve found?