Skip to main content
A Calendly user asked this question 11 months ago and the admin responded that the feature might be added in the future. I am in the same situation and would appreciate the ability to allow a client to book multiple meetings for one set fee. Have there been any updates?

“I am a coach and typically work with clients in 6 session blocks.  

It would be super neat, if a client could pay once and then book session by session until the number of sessions they’ve paid for is spent.

Or if a client can book and pay for multiple sessions at a time.

Is this possible or perhaps a feature coming soon?”

Thank you.

Hi @Lorraine31368!

I appreciate you bring this up! At this time, it is still not an available feature, but we’re continuing to build more support for this and get any feedback over to our team - I’ve sent yours over to our product team in this case!

One way I’ve seen users workaround this is by encouraging invitees to book their next meeting after confirming an event: https://help.calendly.com/hc/articles/226767207-Add-a-link-to-the-confirmation-page#1

Users on our paid plans can also take advantage of our invitee redirect feature. Rather than seeing the Calendly confirmation page after booking, invitees will be automatically forwarded to the website of your choosing which can be the scheduling link for another event. Here's a help article to get you started: https://help.calendly.com/hc/en-us/articles/226767207#h_a20d4878-dce4-44b3-b49f-2829715e4706

So in this case, they can pay for the initial event, then be routed to another event after that first booking. I know it isn’t quite foolproof, but it does work well for some of our users.

​​​​​​​Let me know if you have any questions on this! 


Thanks, David, but this is way too complicated for my clients, who are high school students. They just wouldn’t do it, and that would defeat the purpose of setting it up. I am investigating some other options, an unfortunately (and as much as I like Calendly), I may have to change lanes.


Totally understand @Lorraine31368. I’ve sent this over to our product team, so hopefully we’ll see this as a feature in the future. 🙂