Confirmation e-mail or quote sent to customer when agency booking

Hi ​@sdorville,

Are we talking about manually created bookings for a travel agent or about OTA bookings entering the system via a channel manager?

If it’s the latter, I would start by checking if this setting is enabled in the Bookable service settings:

Does this help or can you elaborate on your question?

Best
Svenja

Hi ​@Svenja,

Thank you for your feedback. 

I'm talking about reservations entered manually by our teams on the PMS. The confirmation should be sent to the e-mail address registered for the travel agency if there is one, otherwise to nobody, but especially not to the customer who is going to stay. 

we haven't activated the option you show in the screenshot because our channel manager is D-edge and he already sends confirmation emails.

Best,

Stevens

Hi ​@sdorville,

In that case you’d have to manually decide if you want to send a confirmation email (and to whom) anyway. We can’t hide the functionality to send a confirmation to the guest, just because there’s a travel agency assigned. It’s important not to send a Confirmation but a “Booker confirmation”. That one would go to the booker and not the guest.

Best
Svenja

Hi ​@Svenja,

Yes, I understand that we can’t hide the button. We thought that the configuration automatically prevented it from being sent to customers when it was a travel agency booking, and we know how to send the confirmation to the agency.

Best,

Stevens

Hi ​@sdorville,

Just to clarify, it isn’t sent automatically, correct? So someone decided to send a confirmation to the guest? Then yes, this cannot be prevented. Except for what is shown on the confirmation as ​@j.spiess said.

There might be hotels working with travel agencies, where they want to send their own confirmation template to the guest in addition to whatever they get via the travel agency. So I wouldn’t be sure, what the feature request would be to prevent this..

Best
Svenja

Hi ​@Svenja & ​@j.spiess,

Thanks again or your feedback.

Indeed the confirmation was not sent automatically, the action was done by a collaborator by lack of attention (subject of another of my posts : 

). We've already reviewed the procedures internally to be more vigilant about this kind of thing, and I'll look into ​@j.spiess 's suggestion.

BR

Stevens