Thoughts on transactional mail

I mentioned a few weeks ago about a conversation I’d had at MAAWG about transactional email and opened up the conversation to readers here. Mike proposed a definition.

[Transactional mail is] an automated message, sent on a per-user basis, usually as the result of a direct action by the user or strongly associated with the user.

In Mike’s decision were things like sales receipts, opt-in notifications / welcome messages, social networking messages and the like.
Kelly disagreed with Mike and said she looked to the FTC and her current working definition was was mail that the user could not opt-out of.
Margaret pointed out that users should be able to unsubscribe from transactional mail.
Finally Steven posted this definition:

I think transactional email is anything which serves a functional purpose which is useful to the receiver. Shipping information is the classic example, invitations to buy are not.

I think these various comments demonstrate something I’ve been thinking for a while. Transactional email is one of the most interesting use cases of email. The traditional examples of transactional emails are those triggered by an action of the recipient; things like shipping notices and purchase receipts. Then there are transactional emails triggered by the actions of a friend of the recipient but that expect interaction or action by the recipient. Requests to connect through the various social networking sites or forward to a friend links on webpages fit into this category. Email as a command, subscription and unsubscription requests, are also a common category that fits clearly into most people’s definition of transactional email.
Then there is email as a notification. These notifications are often programatically generated and may or may not require action on the part of the recipient. Often, they are generated by monitoring scripts, and only fire when certain thresholds are crossed.
I think one of the important factors of a transactional email is that they are not generated by a person. If a mail is generated by a person then it is a one-to-one email. Of course, like most definitions, there are some exceptions, like some sales receipts are drafted and sent by hand not by an automated system.
What do you think? Are these types of messages transactional messages? Or is there some other term that would encompass this use of email?

Related Posts

CAN SPAM compliance.

Over on the ET blog, Al posted about how CAN SPAM compliance is not sufficient for you to not be spamming.
It’s a bit different perspective, but very complimentary to my post yesterday about what is and is not spam. He and I have both heard from ISP people about how many requests for whitelisting or unblocking are prefaced with, “We comply with CAN SPAM” and how meaningless that statement really is. Al has a longer discussion of why.

Read More

Do open rates matter?

Ken Magill over at DirectMag has an article deriding the reliance on ‘open rates’ as a metric for the success (or failure!) of marketing campaigns.

Read More

Permission, Part 1

Before I can talk about permission and how a mailer can collect permission from a recipient to send them email I really need to define what I mean by permission as there are multiple definitions used by various players in the market. Permission marketing was a term coined by Seth Godin in his book entitled Permission Marketing.
The underlying concept beneath permission marketing is that all marketing should be “anticipated, personal and relevant.” Others have defined permission marketing as consumers volunteering or requesting to be marketed to.
When I talk about permission in the email marketing context I mean that the recipient understood *at the time they provided the sender with an email address* that they would receive email from that sender as a result.
Let’s look at some of the relevant parts of that definition.

Read More