📜 ⬆️ ⬇️

Transactional letters (online store, service, and so on)



Hello! And I continue the cycle (in the blog of a wonderful person Michael, the owner of Textbroker) about the letters, and which of them can be collected.

Transactional letters are, roughly speaking, confirmation letters that everything is going fine. For example, in the two thousandth online stores had only one transaction letter: "Your order is confirmed." After Amazon convincingly proved that the buyer should be kept informed, a whole chain appeared:
- Yes, we accepted your order
- Order processed
- Received payment
- The order began to gather in stock
- The goods went to you, tomorrow
- In an hour, wait for the courier (this is usually SMS, not email)
“The order has arrived, is everything okay?”
')
The approach to writing these letters is the same as designing UI / UX models. And the principles used are the same as in navigation.

What is important


Transaction letters are needed to ensure that a person (for example, an online store buyer) is aware of what is happening. Amazon in its time made a small revolution, having taught the industry to immediately respond to an order, plus notify about all movements on it. Because if you do not do this, then it is not clear for a person - he, like, pressed “order”, but there is no action.

The main principles of navigation are control and predictability. Need to answer the questions:

Let's look again at a couple of letters from the online store:
- Yes, we have accepted your order - here you need an order number in the subject line and in the letter body, the exact order structure and amount, information about the applied discounts, the next step is to wait for the operator's call, wait for picking, pay, etc.
- The order is being processed - everything is the same, but it is necessary to designate the previous and next steps. It can be this way: “Now we will check whether there are 50,000 arrows with suckers that you ordered in stock and form an account. It usually takes 5-10 minutes. ”

The same principles apply to all other information letters , for example:

And so on.

From whom to send transactional letters?


  1. Not from noreply @ These letters will often be answered, so you need at least a common company box like sales @ or opt @.
  2. There must be a personal signature or an explanation that this letter is automatically generated — plus someone’s contact. From the client’s point of view, each transaction should be responsible on your part - if you are customer-oriented, of course. If not, just give general support contacts.
  3. The “from whom” or at the beginning of the topic should be a company. Even if the letter comes directly from your employee, the person should immediately associate it with the place where he just did the action. The transaction is usually not expected to be personal.
  4. Do not send transactional letters from the same services as your advertising or content distribution. I know a travel agency whose clients did not receive tickets because they unsubscribed from the main mailing. Or add it to the spam list.


One main action


Ideally, the action for the user should be only one. In half of the cases, it’s just to wait (you need to designate an approximate time when the waiting is over, for example, like this: “Your order was sent by mail to Russia, usually it takes 3-4 days to send your city”). In this example, you can immediately give a tracking number to track and show how to use it, but not in priority. And even more so do not need to frighten a person with what to do if the package has not reached. Better in 4 days to send another letter on the subject "The package should have already reached, if you want - call the mail on this phone here." In moments like: “Your order is almost complete: only 10 out of 10 ordered books are in stock, will the latter arrive tomorrow — divide into two orders or wait?” Choose the default action correctly. That is, a conscious effort - to divide, and if nothing is done and ignore the appeal - to act as it was.

Therefore, the current status and, sometimes, the next step is put into the topic.

Bad: "The status of your order number 12456"
Good: “Your order # 12456 just took a courier and took it to you”
Bad: Apple Receipt
Good: "You put 100 rubles on + 7123-456-78-90"
Bad: “Service 351, account status”
Good: “Tomorrow megamozg.ru domain will be delineated, don't forget to pay, please”

The main action is taken to the top of the letter. For example, AWAD does as a password reminder:
Sender and Subject: AWAD - Password Reminder
Large: "Here is your new password - ****" (yes, they sent it directly in the letter)
This is all that the user needs in a normal scenario. Further, exceptions that are needed in a few percent of actions, for example:
Smaller: How to change the password ...
Smaller and lower: If you did not request a password change, then ...,
Below: contact support.

Check list:



Other materials


Source: https://habr.com/ru/post/297808/


All Articles