If you HAVE to Send Bacn
Some services and organizations send out bacn as part of their job. Twitter sends out follower messages. Facebook lets you pick your flavors of bacn (from like 20 possible reasons for them to mail you). My conference sends either bacn or spam, depending on whether you need to be informed of these events. So, if you have to send bacn, here’s some thoughts.
Keep it Brief
Make the actions I need to take with the bacn process brief, please? Twitter bacn takes a click, a scan, and a click, a window close, and a delete. Not (too bad). Facebook takes a click, a scan, a close and a delete, unless it’s a friend request, and then that’s horrible.
Keep it Informative
If your subject line were better, I might not even have to open some of my bacn. I’d love online financing apps to say things like: “STATEMENT, not a bill” in the subject line. Because then I could just store it to browse later (yeah, like I read those).
Keep it Opt-Outable
If I ever send you bacn, there’s a line there to say how you can stop getting it. Okay, maybe not when I invite you to the 37,814th social network because they let me add my inbox, but I vowed to do that ever since Spock screwed me over. If *I* send you mail of a bacn-ish consistency, there’s an opt-out clearly marked.
There. What else? Is there something else we should tell the future bacn makers of the world, some of whom might stop by here from time to time to better understand community and social media? Let’s talk about it.
Photo credit, Today is a good day
If you enjoyed this post, please consider leaving a comment or subscribing to the feed to receive future articles delivered to your feed reader.
Nice post, Chris. And I learned a cool & handy term!
My addition: text only. This ensures that the most basic email app can open & read it just fine. That speeds up processing (or deleting).
Take care,
Andrew