Hello Pascal,

I'm afraid that we didn't quite get what the issue is exactly? Can you explain to us in a little more detail, and send us a couple of screenshots? Also Amelia is not designed for room rentals but instead for appointments at a chosen time slot not day. We will try to help as best as we can but we need a little more information.

We wish you all the best. 

Looking forward to your reply. 

Hi, Pascal

Thanks for reaching out to us.

I can see what you mean, but we are truly sorry to disappoint you,

this is not currently possible to achieve with the current Amelia's logic for loading time slots while choosing the recurring "End time".

Our developers have made Amelia's logic for choosing recurring "Ends" time like that, 

 it does not load all the available and unavailable time slots for that "recurring step",

in the same way as it does when you initially choose the appointment time on the "first calendar step".

I can understand that you would like to get a warning in this next image, that the 7th and 8th will not be available when choosing the "End time"

But, unfortunately, it is not currently possible to load that warning there;

 this is why we added this option if you go to Service settings/"Handle unavailable recurring dates" :

Then, Amelia waits for the customer to choose which end date of recurrence they wish - and in the end it shows them that this day is not available,

and it will offer "closest date before" / "closest date after" or both "recommend the closest date before or after",

depending on how you set this up.

-

As we have pointed out on this Documentation about Recurring Appointments,

there are two important notes, the first one :

Unavailable dates set in employee’s working hours will be disabled and customer will be able to choose only repeating for days when the service is provided

Which means that it does not load the days that are completely unavailable in the schedule ( with work hours/ special days/days OFF),

but it can not check if the employee is busy with other bookings on that day, at the moment.

-

The other note : If the same date has available time slots before or after the chosen time slot the plugin will recommend the closest time slot at the same date no matter which option you have chosen here.

So, unfortunately, at this moment we are not able to change that logic.

It is a good idea for a future improvement, though - so please don't hesitate to make a suggestion for our developers and we will do our best to make an improvement for that selection as soon as possible.

Please feel free to search through our feature suggestion page, 

 to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there, and as more people vote, the feature will move higher on the priority list.

You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

-

Let us know if you have any further questions about this. Thank you

Hi, Pascal 

Apology for the delay

You are correct, thank you for pointing this out,

at first i did not recognize this behaviour, but i am able to reproduce it on my local Test site.

1. If i make an employee unavailable for Tuesdays and Wednesdays, 

and if i select the  6th of February,  then if i go for "Repeat after 1 day",

there is no warning , and Amelia automatically chooses the 9th as the next available day ( skips 7th and 8th).

-

2. But If i choose "Repeat after 2 days", in this case it does provide a warning while suggesting the 9th as the next available day and notifies the user that the originally chosen date is busy.

-

I think this is not the intended behaviour, and can't say why the warning only happens with that selection, not the other one.

We will pass this to our QA Team for testing, as soon as they conclude if this is a bug, we will report back to confirm it for you immediately.

Thanks again for pointing this out and for your patience.

Hi, Pascal 

Thank you once again for reporting this behaviour for us.

Our QA Team has confirmed that this is perhaps a potential bug,

so it is added to the list of tasks for our developers to conduct further testing and investigation into this behaviour.

- It seems that it should be the same logic for loading that "notice/warning" message whether we choose "1 day" or "2 or more days" as the recurring interval;

but i will follow this case for you, and i will do my best to push the urgency of it.

-

I can't promise exactly how long it will take to investigate and improve it,

but i can tell you it is added in the task queue for our developers,

they will do their best to work their way through all the tasks they are working on.

-

As mentioned, at this time unfortunately, we don't have an ETA on when this improvement will be available, but please keep a lookout on our Amelia's changeLog.

It will be stated there during updates which fixes and improvements have been implemented at each update.