Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

24h / 48h delay #163

Closed
zebbez opened this issue Dec 16, 2020 · 4 comments
Closed

24h / 48h delay #163

zebbez opened this issue Dec 16, 2020 · 4 comments

Comments

@zebbez
Copy link

zebbez commented Dec 16, 2020

Hello Sergey,
Thanks for your useful application.
I'd like to add an appointment delay.
Example :
Between now and 24 hours or 48 hours => no possibility to make an appointment.
Thus, if the last appointment is ended at 13Hours, I'm sure to be free during the afternoon.

Regards

@SergeyMosin
Copy link
Owner

Some kind of "cool down" time-out after an appointment if I understand correctly ?

@Nadeige
Copy link

Nadeige commented Jun 21, 2021

Hi Sergey,

I am interested in that functionality too. I would like people to make an appointment at least 24 (or 48) hours in advance. Otherwise people tend to book a slot that is in only 2 hours. To avoid that I have to spend time deleting non-booked slots everyday.

Thank you!

@Jaxom99
Copy link
Contributor

Jaxom99 commented Feb 15, 2022

I think it's what "lead time" is used for, maybe we should explain that in a clearer way? Otherwise this PR #242 would enhance the available settings.

@SergeyMosin
Copy link
Owner

Booked/pending appointment buffers are added in v1.12.2 (Manage Appointment Slots menu)

It is possible to block-off a period of time before and after a booked(and pending) appointment. This could be useful when some preparation/travel time is required before or cleanup/cool-off time needs to be blocked-off after an appointment.

Buffer blocking logic:
appointment-buffers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants