You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
For some specific use cases I don't mind allowing clients to schedule an appointment without them confirming in the email. I know this is important for them to receive the correct location and etc, but sometimes that's not needed.
Describe the solution you'd like
When creating an appointment, the user can uncheck a box "Ask for email confirmation before scheduling", which is checked by default.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Because I still have some users who believe that they have 'booked' my time and in reality they have simply filled in the form... I have updated the text in my page to this, 'Important: Your booking will not be made until you confirm via the email that you will be sent. In different words: your appointment will not be booked and it will not appear in my calendar and I will have no awareness of it until you click on the *confirm* link in the email. Depending on your email service, it might take a few minutes to arrive.'
noting: #5189
I would most enjoy your proposed enhancement to be in the calendar owners config. Then you could have two public URL's one with and one without spam protection.
Is your feature request related to a problem? Please describe.
For some specific use cases I don't mind allowing clients to schedule an appointment without them confirming in the email. I know this is important for them to receive the correct location and etc, but sometimes that's not needed.
Describe the solution you'd like
When creating an appointment, the user can uncheck a box "Ask for email confirmation before scheduling", which is checked by default.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: