Setup: 1 service, 2 employees, min capacity 1, max capacity 2.
Booking fails to create seperate appointments when 1 user books an appointment as a single customer, then another unrelated customerbooks for the same service and same timeslot gets grouped with the previous appointment/customer. This behavior is extremely undesirable and should on exist if the 1st customer chooses to bring other people with him/her.
If for example you have 2 employees assigned to the same service, then the 2nd customer should be assigned to a new appointment and to the 2nd employee.
That makes logical sense because the 2 customers are in no way related to each other.
There are two scenarios where it's possible to book the same timeslot. First is when you have the setup as you described, two employees, one service, min 1 and max capacity 2. In this case, if two customers book the same timeslot for the same day, Amelia will assign the appointment according to the settings. The second employee will be assigned, if the first one is already booked.
It will look like this
But, if you have the option "Allow booking below minimum capacity" enabled in Appointment settings, with the same setup, the customer can book the same timeslot multiple times until the maximum capacity is reached. In the appointment section, you will see that the appointment is assigned to same employee, even though there are two employees assigned.
Please check if the option "Allow booking below minimum capacity" is enabled, since by default, it should be displayed as per the screenshot above.
If customer A books 1 of 2 attendees for a service that allows more than 1 person, in time slot #1, then customer B books 1 attendee in time slot #1, then both customers' will be assigned to the same appointment.
This appears to be a bug.
I will try to recreate the scenario I describe over the weekend, with the settings on the backend included for the service.
Again, I was able to book 2 different customers/email address in the same appointment, which should not be possible.
Have you had a chance to recreate the scenario? Perhaps providing a video showcasing the issue? Strange, we haven't had this issue reported previously.
Setup: 1 service, 2 employees, min capacity 1, max capacity 2.
Booking fails to create seperate appointments when 1 user books an appointment as a single customer, then another unrelated customer books for the same service and same timeslot gets grouped with the previous appointment/customer. This behavior is extremely undesirable and should on exist if the 1st customer chooses to bring other people with him/her.
If for example you have 2 employees assigned to the same service, then the 2nd customer should be assigned to a new appointment and to the 2nd employee.
That makes logical sense because the 2 customers are in no way related to each other.
Hello Richard,
There are two scenarios where it's possible to book the same timeslot. First is when you have the setup as you described, two employees, one service, min 1 and max capacity 2. In this case, if two customers book the same timeslot for the same day, Amelia will assign the appointment according to the settings. The second employee will be assigned, if the first one is already booked.
It will look like this
But, if you have the option "Allow booking below minimum capacity" enabled in Appointment settings, with the same setup, the customer can book the same timeslot multiple times until the maximum capacity is reached. In the appointment section, you will see that the appointment is assigned to same employee, even though there are two employees assigned.
Please check if the option "Allow booking below minimum capacity" is enabled, since by default, it should be displayed as per the screenshot above.
Kind Regards,
Stefan Petrov
stefan.petrov@tmsproducts.io
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
I think you misunderstood.
If customer A books 1 of 2 attendees for a service that allows more than 1 person, in time slot #1, then customer B books 1 attendee in time slot #1, then both customers' will be assigned to the same appointment.
This appears to be a bug.
I will try to recreate the scenario I describe over the weekend, with the settings on the backend included for the service.
Again, I was able to book 2 different customers/email address in the same appointment, which should not be possible.
Hello Richard,
I see now, thanks for the additional explanation.
Have you had a chance to recreate the scenario? Perhaps providing a video showcasing the issue? Strange, we haven't had this issue reported previously.
Kind Regards,
Stefan Petrov
stefan.petrov@tmsproducts.io
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables