I’ve talked frequently about permission on this blog, and mentioned over and over again that senders should correctly set expectations at the time they collect permission. Permission isn’t permission if the recipient doesn’t know what they’re agreeing to receive.
Read MoreThere was a recent question on a mailing list during a discussion of spam and delivery problems. A number of folks who work in delivery were discussing how a bad address got on a list. Someone who works on the spam blocking end of things asked why do you care how a bad address got onto a mailing list?
For recipients, they usually don’t care. They just want the unsolicited mail to stop. It’s a position I have no problem with; I want the unsolicited mail to stop, too. But understanding why a particular sender is sending mail to addresses that never asked for it can be an important step in making it stop. Not by the receivers and the spam filters, they’ll just block the bad sender and move on. Or if they’re an ISP or ESP they’ll just throw the sender off for AUP violations and let the sender be somebody else’s problem.
In the broader context, though, this only changes the source of the spam. It doesn’t help the victim; the bad sender can always find another host and they will continue to mail people who never asked for that mail. And, in fairness to these senders, often they are mailing lists of mixed sources. Some of the addresses didn’t opt-in, and don’t want the mail, but a lot of addresses on their list did opt-in and do want their mail. Fixing their problem means they can mail people who want their mail. The sender is happy, the recipients are happy and the receivers are happy; everybody wins!
Everybody winning is something I can get fully behind.
Despite what some email marketers may tell you there are times when it’s really not appropriate to try and add someones email address to your list.
I just opened a pot of yogurt and instead of a smooth, creamy dessert there was a sticky brown slurry dotted with firm white chunks – looking like hot-and-sour soup, and not in a good way. No, this isn’t an email marketing metaphor, it’s just background to the story.
Food is a fairly delicate product, and supply-chain problems happen – it doesn’t take leaving yogurt out in the sun all day to turn it into something unpleasant. I’m not too concerned, but I thought I’d drop them a line and tell them that they had a problem (not because I want the traditional coupon for a free yogurt but because I want them to fix their problem and reduce the odds of the yogurt I buy next month trying to kill me).
They have a web site. I dodge past the full-screen pop-up “subscribe to our newsletter!” and go to their contact us link. Comment, complaint or question? Complaint, I guess.
They ask for a lot of information, almost all of it “required”. UPC Code, Plant Number, Production Line, Use By Date, Time Stamp, Store where it was purchased, city, state, comments. And my title, first name, last name, email address. And my email address again (no, people, that is *not* what double opt-in means). Phonenumber, Street Address, Building/Suite/Unit, City/Town, State, Zip Code, Country.
And whether I “Would you like to receive news, information and other offers from Brennan’s” – with the tempting options of “Accept” or “Not Accept”.
Skipping over the question of whether 23 fields ever makes sense for a subscription capture form, someone who’s contacting you to complain that your product looks like last months chinese take-out isn’t someone you have a close relationship with, someone who wants to receive your email. Odds are pretty good that they’re either going to decline your tempting offers and be slightly annoyed, or (accidentally?) sign up for them and hit the this-is-spam button when you mail them.
Neither is a good result, for you or them. Maybe you should wait to offer the opportunity to sign up for your yogurt mailing list until after you’ve resolved the complaint to their satisfaction, rather than when they’re making the complaint?