Skip to main content

Booking emails

CoreHue sends emails around bookings so you don't have to. There are two directions: what your clients get, and what you get.

What you write​

Bookings → Settings → Emails holds two things, both switched on by default and both with a Message you write yourself:

Booking confirmation, "Send an email when a booking is confirmed."

Inquiry auto-reply, "Send an automatic reply when a new inquiry is received."

Each has a rich text editor with a Variables menu in its toolbar, so one message greets everyone properly. See Filling in names automatically.

These are your account-wide defaults. Any service can replace them with its own words in the last step of its booking flow. That step is 6 Confirmation on a direct booking or mini session, and 3 Confirmation on an inquiry service. Leave the service's message blank and the default here is used.

Don't confuse this with your own notifications

The Booking confirmation switch here controls whether your client is emailed. Turning it off to quieten your own inbox stops your clients being confirmed.

Your own notifications live under Settings → Notifications.

What clients get​

An inquiry auto-reply, subject "Thank you for your inquiry, their name". Sent the moment someone submits an inquiry. This is the single most useful email here, because the gap between inquiring and hearing back is where people go elsewhere. Say when you'll reply and what happens next.

Switching the auto-reply off doesn't silence this. The client still gets a plain receipt so they know the inquiry arrived. What they lose is your words.

A booking received note, when a booking is made but still pending. Its subject names what's missing: "Waiting for payment", "Waiting for requirements", or "Your booking is being reviewed". The button reads Complete your booking and takes them to their booking page.

A booking confirmation, subject "Your booking is confirmed", with the date, time, location and an add-to-calendar link. Your confirmation message is the body: the service's own if it has one, otherwise your account-wide default.

Reminders before the session, if you switch them on. See below.

A reschedule notice, subject "Your booking was rescheduled", and a cancellation notice, "Your booking has been cancelled". Both only go out if you turn the notify switch on when you make the change. Both are off by default.

A late payment note, "We received your payment", when money arrives after a booking has already expired.

Reminders​

Booking reminders are set under Settings → Reminders, not per service, so they apply across your bookings.

Booking reminders, "Send automatic reminders before a confirmed booking", is off by default. Turn it on and tick any of four points: 7 days before, 3 days before, 1 day before and Day of booking. Switching it on for the first time starts with 3 days before and the day of booking ticked.

They go only to confirmed bookings, and stop when a booking is completed or cancelled.

What you get​

Your own notifications live under Settings → Notifications, in a Bookings section:

  • New inquiry, "A client sends an inquiry from a booking page."
  • Booking confirmed, "A client confirms a booking."
  • Booking cancelled by client
  • Booking rescheduled by client
  • Core publication changes, when a plan change unpublishes services

Two more sit under Payments:

  • Booking payment proof, when a client uploads proof of payment
  • Payment received after booking expiry

All are on by default. Notification emails at the top of that page turns the lot off if you'd rather work from your Home screen than your inbox.

Writing them well​

Answer the question they're about to ask. For an auto-reply, that's "when will I hear back?". For a confirmation, it's "where do I go and what do I bring?".

Keep it short. These are read on a phone, usually while doing something else.

Say what happens next. Every one of these emails should leave the client knowing what comes after it.

Checking what was sent​

Every booking keeps its Email history in its three-dot menu, showing what went out and whether it was delivered. Inquiries have the same entry. When a client says they never received something, that's where you find out whether it could not be delivered, was delayed, or was never sent.