Multiple Service Bookings - Separate Confirmation Emails for one appointment.. WHY?

Hi, I use my Wii site for client bookings… I have noticed that each multi-service booking send a separate confirmation email for each service! Example: A client books a haircut and a hair treatment for the same visit… the automated confirmation system sends 2 (TWO) emails - one email per service - even though it is one appointment. Is there a way to change this? It is very confusing to a client because the emails also state 2 separate appointment times due to the duration of each service. Please Help! :
[Clearly ask your question.]

Product:
[WIX bookings]

1 Like

I know this is an old post but I came here to find an answer to this same issue.

My client is set up for multi-service bookings so that part of the functionality is working properly. But let’s play through this scenario:

  • Customer books two services, a haircut and a color
  • The haircut takes one hour, the color takes one hour
  • The customer books a time of 12pm but with the multi-service booking the system automatically allocates two hours for the service so the calendar is booked from 12pm-2pm
  • The system now (unfortunately) sends TWO confirmation emails to the customer. One for the service from 12pm-1pm and another for the service from 1pm-2pm

The issue with this is that is causes customer confusion and in some cases they come in based on the booking time for the 2nd half of services causing a scheduling conflict.

So how should I set up the services so that only ONE confirmation email is sent that shows a time from 12pm-2pm?

Thank you in advance!

Hi, I’m Ireen from the Wix Bookings team :slight_smile: I completely understand the need but unfortunately this is currently not supported and an email is sent out for each booking. We’ll look into the best way to provide this sort of flexibility with emails – we know it is extremely important.

Thank you for the response!

It’s not the answer I wanted to hear but glad I can now figure out a way to work around it and it’s not something we’re doing wrong or not understanding functionality.

Thanks again!