Contents
Emails - Plugixa Chauffeur
The plugin sends three kinds of email: a confirmation to the customer when a booking is made, a notification to you at the same moment, and an update to the customer whenever the booking status changes.
Settings
Go to Plugixa Chauffeur -> Settings -> Notifications, “Emails sent when a booking is made or changes.”
Booking emails is one switch for all of them: “Send a confirmation to the customer and a notification to you for every booking.” It is on by default. Switched off, the plugin sends no email at all, including status updates.
| Field | Default when empty |
|---|---|
| From name | The site name. |
| From email | The site admin email. |
| Admin notification recipients | The site admin email. |
Admin notification recipients takes several addresses separated by commas. Anything that is not a valid email address is ignored.
Press Save settings after a change.
The emails
When a booking is made
Two messages are sent as soon as a customer confirms a booking in the wizard.
| To | Subject | Heading |
|---|---|---|
| The customer | Your booking PXC-20261002-0421 is received | Booking received |
| Each admin recipient | New booking PXC-20261002-0421 | New booking |
The customer’s message opens with “Thank you for your booking. Here are your trip details:” and the admin’s with “A new booking has been placed:”.
For a Stripe booking these are sent when the booking is saved, before the customer has paid.
When the status changes
Each time the Booking status of a booking changes, the customer is sent one message. Its subject is the heading followed by the booking reference.
| New status | Heading |
|---|---|
| Processing | Your booking is confirmed |
| Completed | Your trip is complete |
| Cancelled | Your booking has been cancelled |
| Pending, On hold, Refunded, Failed | Booking update |
This covers changes you make on the booking detail screen and the automatic move from Pending to Processing when Stripe confirms a payment.
Status emails go to the customer only. Admin recipients are not notified of status changes.
What does not send an email
- Changing only the Payment status.
- Editing the customer details, the notes or the fare.
- Saving a booking without changing its status.
- Assigning a driver PRO.
- Deleting a booking.
- A booking created through the REST API by an administrator.
What an email contains
Every message uses the same layout: your site name in a header band, the heading, and a table of the booking.
| Row | Contents |
|---|---|
| Reference | The booking number. |
| Status | The booking status at the moment of sending. |
| Service | The service type. |
| Pickup | The pickup address. |
| Drop-off | The drop-off address. |
| Date & time | The pickup date and time. |
| Passengers | The number of passengers. |
| Vehicle | The vehicle name. |
| Payment | The payment method, when it is still enabled in Settings. |
| Total | The currency code and the fare, for example USD 34.00. |
When the payment method has instructions, they are shown in a box under the table. This is where a customer finds your bank details for a transfer. See Payments.
The footer shows the site name and address. The emails do not contain the customer’s phone number or notes, and they do not contain a link to cancel or change the booking.
Delivery
Emails are sent through WordPress’s own mail function, as HTML. The plugin does not connect to a mail service itself. If WordPress cannot send mail on your host, or messages land in spam, install an SMTP plugin and send through a proper mail service. Use a From email on your own domain.
The plugin does not keep a log of sent emails and does not retry a message that fails.
Changing the wording or the design
There are no template fields in Settings. The text of every email uses the
plugixa-chauffeur text domain, so it can be changed with a translation, see
Multilingual.
The layout comes from one template file inside the plugin,
includes/Modules/Notifications/views/booking.php. Version 1.0.0 does not look for a copy in your
theme, and a change made to the file itself is lost when the plugin is updated.
Developers can send their own messages on the plugin’s actions, see Hooks Reference.
Things that are not bugs
“The customer got a confirmation but never paid.” The first email says the booking was received, not that it was paid. A Stripe booking is confirmed by the “Your booking is confirmed” email, sent once payment arrives.
“I marked a booking Paid and no email went out.” Payment status does not trigger an email. Change the Booking status to send one.
“The Payment row is missing.” The method the customer chose has since been switched off in Settings.
What to do next
- Write the payment instructions that appear in emails in Payments.
- Trigger status emails from Bookings.
- If nothing arrives, see Troubleshooting.