We wish multiple appointments per time slot, but the system is grouping our appointments, and not allowing individuals to be approved, canceled, or rejected. So if we allow 10 people, we have to cancel all 10 if 1 can't make it. This is unacceptable. These are independent appointments, not families.
Here is how we work during COVID: The doctor will see several people between 9am-10:30am (we do not want to book a specific order or exact time, people need to be available during that window of time). I set the min to 1 and max to 10, allowing booking below minimum. The appointments are coming in as groups, with ALL pending, and ALL have to be confirmed or cancelled at once. Can these be ungrouped to allow them to show as individual, overlapping appointments?
A further issue is the emails are compounding. By allowing 10 appointments during this slot, when the 5th person schedules, all 4 other people's information is included in the email, and when the 10th person signs up, 9 other's contact info is all listed in that email. We can't have this.
I am now seeing when we edit the appointment group, we can confirm and cancel individuals separately, but this is still not ideal.
This is how the plugin works. If you allow multiple people to book an appointment, that appointment will be saved as a group appointment, and when you edit it, you can reject, approve, cancel anyone individually.
Your appointment settings need to be configured like this:
Also, in General settings, you can set the default appointment status is "Approved", not "Pending".
The issue you're referring to with emails is happening only for Events, so I'm not sure if you're using the combination of those two?
Those are the setting I have, however we collect a deposit and only confirm appointments once paid in full, so our default setting needs to be Pending, unless that is causing the issue.
This email issue is for our services, we are not booking events yet. In our email notification to employees, we send the patient contact info along with some custom field info to the doctor and our team. If we allow 5 appointments in a time window, the emails show up as:
And those placeholders are pulling the info from all patients with appointments during that time.
This becomes much more of an issue when we have a longer window of time and allow 15-20 appointments at once. Trying to match up 20 names, phone numbers, and emails that are all on 1 email causes confusion. Why is it compounding the names? How can this be resolved?
I'd like to add that the subject on the notification to the customer AND employee is: PENDING - %service_name% Appointment for %customer_full_name%
Yet on the email to the customer, it correctly shows just the one customer name it is sent to, but the email to the employee shows the full group of names. It is the exact same placeholder, %customer_full_name%, being used in both emails. Works correctly to customer and not to employee. We need this resolved, please.
That's not how it's supposed to work. Each new customer should receive a separate email. Same goes for the employee, they should only receive one email per customer.
Please provide me a temporary WP-admin login for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course we do not provide login data to third party.
You can write credentials here just check Private Reply so nobody can see them except us.
You're absolutely right about this. We've added this per our customers' requests. It was the default behavior for events, but now it's doing the same thing on Appointments with multiple customers in it.
To avoid that, you should use %booked_customer% placeholder instead of
%customer_full_name%
%customer_phone%
%customer_email%
That placeholder (%booked_customer%) consists of all those (email, full name and phone), and it will only send the email with the customer who last booked the appointment
I have a similar problem with this, particularly with how webhooks are grouping - the first appointment takes precedence at all bookings_0 and appointments_0 API values when posting the same information twice is the opposite of what I want to do. This leads to our automation messing up - it attempts to create the same user twice instead of the second user, fails, and then does not email the visitor.
Will switching to bookings_1 or appointments_1 for posting webhooks fix this issue?
Thank you, Aleksandar. Using %booked_customer% solved the issue with our notifications.
To confirm, you are saying that the appointments grouping together should NOT be happening, and you are submitting this issue to be resolved? Is it safe to say you have no idea when this will be resolved? Thank you
As far as I know, they shouldn't be grouped like that, so it will be forwarded to our development team.
I cannot say when it will be resolved, that's correct.
Matthew,
When you are posting on tickets that are not yours or have questions or issues which are not related to the title of the active ticket can you please open a new one, and we will help you there. In that way, issues and questions which are related to different subjects will be in different tickets so other customers or our support agents can find it easily. Our policy is to have one issue or question per ticket because of the reasons that is described already.
We wish multiple appointments per time slot, but the system is grouping our appointments, and not allowing individuals to be approved, canceled, or rejected. So if we allow 10 people, we have to cancel all 10 if 1 can't make it. This is unacceptable. These are independent appointments, not families.
Here is how we work during COVID: The doctor will see several people between 9am-10:30am (we do not want to book a specific order or exact time, people need to be available during that window of time). I set the min to 1 and max to 10, allowing booking below minimum. The appointments are coming in as groups, with ALL pending, and ALL have to be confirmed or cancelled at once. Can these be ungrouped to allow them to show as individual, overlapping appointments?
Thank you
A further issue is the emails are compounding. By allowing 10 appointments during this slot, when the 5th person schedules, all 4 other people's information is included in the email, and when the 10th person signs up, 9 other's contact info is all listed in that email. We can't have this.
I am now seeing when we edit the appointment group, we can confirm and cancel individuals separately, but this is still not ideal.
Hello Barry
Thank you for your purchase.
This is how the plugin works. If you allow multiple people to book an appointment, that appointment will be saved as a group appointment, and when you edit it, you can reject, approve, cancel anyone individually.
Your appointment settings need to be configured like this:
Also, in General settings, you can set the default appointment status is "Approved", not "Pending".
The issue you're referring to with emails is happening only for Events, so I'm not sure if you're using the combination of those two?
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
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
Those are the setting I have, however we collect a deposit and only confirm appointments once paid in full, so our default setting needs to be Pending, unless that is causing the issue.
This email issue is for our services, we are not booking events yet. In our email notification to employees, we send the patient contact info along with some custom field info to the doctor and our team. If we allow 5 appointments in a time window, the emails show up as:
(email body)
patient 1, patient 2, patient 3, patient 4, patient 5
phone # 1, phone # 2, phone # 3, phone # 4, phone # 5
email 1, email 2, email 3, email 4, email 5
But in the notifications, we use:
%customer_full_name%
%customer_phone%
%customer_email%
And those placeholders are pulling the info from all patients with appointments during that time.
This becomes much more of an issue when we have a longer window of time and allow 15-20 appointments at once. Trying to match up 20 names, phone numbers, and emails that are all on 1 email causes confusion. Why is it compounding the names? How can this be resolved?
Thank you
I'd like to add that the subject on the notification to the customer AND employee is: PENDING - %service_name% Appointment for %customer_full_name%
Yet on the email to the customer, it correctly shows just the one customer name it is sent to, but the email to the employee shows the full group of names. It is the exact same placeholder, %customer_full_name%, being used in both emails. Works correctly to customer and not to employee. We need this resolved, please.
Hello Barry
That's not how it's supposed to work. Each new customer should receive a separate email. Same goes for the employee, they should only receive one email per customer.
Please provide me a temporary WP-admin login for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course we do not provide login data to third party.
You can write credentials here just check Private Reply so nobody can see them except us.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
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
Hello again Barry
You're absolutely right about this. We've added this per our customers' requests. It was the default behavior for events, but now it's doing the same thing on Appointments with multiple customers in it.
To avoid that, you should use %booked_customer% placeholder instead of
%customer_full_name%
%customer_phone%
%customer_email%
That placeholder (%booked_customer%) consists of all those (email, full name and phone), and it will only send the email with the customer who last booked the appointment
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
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 have a similar problem with this, particularly with how webhooks are grouping - the first appointment takes precedence at all bookings_0 and appointments_0 API values when posting the same information twice is the opposite of what I want to do. This leads to our automation messing up - it attempts to create the same user twice instead of the second user, fails, and then does not email the visitor.
Will switching to bookings_1 or appointments_1 for posting webhooks fix this issue?
Thank you, Aleksandar.
Using %booked_customer% solved the issue with our notifications.
To confirm, you are saying that the appointments grouping together should NOT be happening, and you are submitting this issue to be resolved? Is it safe to say you have no idea when this will be resolved?
Thank you
Hi again Barry
As far as I know, they shouldn't be grouped like that, so it will be forwarded to our development team.
I cannot say when it will be resolved, that's correct.
Matthew,
When you are posting on tickets that are not yours or have questions or issues which are not related to the title of the active ticket can you please open a new one, and we will help you there. In that way, issues and questions which are related to different subjects will be in different tickets so other customers or our support agents can find it easily. Our policy is to have one issue or question per ticket because of the reasons that is described already.
Thank you for understanding.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
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