Transactional Email That Reads Like a Robot

The messages everybody opens

Confirmations, receipts, booking notices, and password resets are opened at rates no marketing message approaches, because the recipient is waiting for them.

They are also the messages nobody at the business has read, because they were configured once when a system was set up.

Which produces a strange asymmetry: enormous care goes into a newsletter a fifth of the list opens, and none goes into a confirmation almost everybody reads.

Rewriting them is an afternoon and the improvement applies to every customer from then on.

What the defaults sound like

Recognisable once pointed out.

Your request has been received and assigned reference 4471-B. Kind regards, The Team.

Or worse, wording written for the software vendor rather than for you: your ticket has been logged, a representative will action it in due course.

None of that is wrong and all of it is written in the voice of a system rather than a business.

For a small local business, that is the one moment where the impression of being large and impersonal is entirely unnecessary, since the whole advantage is being neither.

Why tone matters more here

Because of when the message arrives.

Somebody has just committed: booked, paid, or handed over their details. That is the moment of highest uncertainty, when people wonder whether they chose correctly.

A warm, clear confirmation reduces that uncertainty. A cold, automated one adds to it fractionally.

It is also frequently the first written communication a customer receives from you, and it sets the expectation for everything after.

A message that sounds like a person suggests a business where a person will answer the phone.

The four things to change

• The greeting and sign-off, in your own words.
• What happens next, stated plainly.
• How to reach a person, with a real address.
• Anything internal, removed.

The second is the one customers actually want. Most confirmations confirm and stop, leaving the recipient to wonder when somebody will call and what they should do meanwhile.

Say what happens next

The single most useful addition, and it prevents a category of phone call.

We will confirm your slot by Thursday. Somebody will call the day before. Please leave the side gate unlocked.

Each of those answers a question the customer would otherwise ask, and answering it in the confirmation is free where answering it on the phone is not.

Write it as the sequence of things that will happen, in order, with rough timings.

Where you do not know, say what they should do if they have not heard by a particular day, which is nearly as reassuring.

A worked example

A business used their booking system's default confirmation, which stated the appointment details, a reference number, and a line saying this is an automated message, do not reply.

They received several calls a week asking what to expect and whether somebody needed access.

They rewrote it: a sentence thanking the customer, the appointment details, three lines on what would happen and when, what to have ready, and a real address and telephone number.

It took about forty minutes including testing.

The calls asking what to expect largely stopped, and two customers mentioned the confirmation as the reason they had felt confident about the booking.

The message had been sent to every customer for four years in its original form.

Remove what is internal

The part that reads as sloppiness rather than as coldness.

Reference numbers that mean nothing to the customer, system names, status codes, and internal terminology all appear in default templates because a developer needed them.

Keep a reference if the customer will genuinely need to quote it, and explain that it is what to quote.

Remove the rest, along with anything mentioning the software vendor, which is advertising for somebody else in your customer's inbox.

Also remove double greetings, empty placeholder fields, and the artefacts of a template where a field was left blank, which are the details that make a message look unmaintained.

Find all of them first

The step that makes this an afternoon rather than an ongoing annoyance.

List every automated message any of your systems sends: booking confirmation, reminder, cancellation, payment receipt, form acknowledgement, password reset, review request.

Most small businesses find between four and eight across two or three systems, and have read none of them.

Trigger each one yourself and read what arrives, which is the only reliable way to see them.

Then rewrite them in one sitting so they sound like the same business, which is a benefit beyond the individual improvements.

Note who can edit each, since that determines what is actually changeable and what needs a request to a supplier.

Check they arrive at all

Worth doing while you have each one triggered, since the wording is irrelevant if the message never lands.

Send each to accounts at two or three different providers rather than only your own, and check whether any are filtered or filed away.

Confirmations are the messages people most expect and most complain about not receiving, and a customer who did not get one assumes the booking failed.

Check the sending address is one that belongs to your domain rather than the software vendor's, since a confirmation arriving from an unfamiliar sender is both less trusted and more likely to be filtered.

That check takes ten minutes for the whole set and is worth more than any amount of rewriting.

The counter-case

Warmth can be overdone here.

A receipt is a document, and somebody looking for an amount and a date does not want three paragraphs of personality in front of it.

Put the facts first, in a clear block, and the human wording around them rather than instead of them.

Some messages should also stay plain for practical reasons: a password reset should be short, unambiguous, and free of anything that resembles marketing, since customers are rightly suspicious of those.

And there are systems where the template genuinely cannot be edited, in which case a follow-up message from a person is the workaround.

Keep the facts prominent, add the human part around them, and leave security messages alone.

The afternoon

1. List every automated message your systems send.
2. Trigger each one and read what arrives.
3. Rewrite the greeting and sign-off.
4. Add what happens next, with timings.
5. Give a real address and telephone number.
6. Remove reference codes nobody needs.
7. Keep the facts at the top.

Step four is the one that reduces phone calls, since most confirmations confirm and then leave the customer wondering what to do next.

The order confirmation specifically is covered in the order confirmation email nobody wrote.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.