Report Spam button
Cloudmark has an interesting discussion about the Report Spam button and how it’s used.
Cloudmark has an interesting discussion about the Report Spam button and how it’s used.
There are a lot of people who abuse online services and use online services to abuse and harass other people. But handling complaints and handling the abuse are often afterthoughts for many new companies. They don’t think about how to accept and process complaints until they show up. Nor do they think about how bad people can abuse a system before hand.
But dealing with complaints is important and can be complicated. I’ve written many a complaint handling process document over the years, but even I was impressed with the Facebook flowchart that’s been passed around recently.
In the email space, though, all too many companies just shrug off complaints. They don’t really pay attention to what recipients are saying and treat complaints merely as unsubscribe requests. Their whole goal is to keep complaints below the threshold that gets them blocked at ISPs. To be fair, this isn’t as true with ESPs as it is with direct senders, many ESPs pay a lot of attention to complaints and will, in fact, initiate an investigation into a customer’s practice on a report from a trusted complainant.
There are a lot of legitimate email senders out there who value quantity over quality when it comes to complaints. But that doesn’t mean their lists are good or clean or they won’t see delivery problems or SBL listings at some point.
There are a lot of different perspectives on Feedback Loops (FBLs) and “this is spam” buttons across the email industry.
Some people think FBLs are the best thing since sliced bread and can’t figure out why more ISPs don’t offer them. These people use use the data to clean addresses off their lists, lower complaints and send better mail. They use the complaints as a data source to help them send mail their recipients want. Too many recipients opted out on a particular offer? Clearly there is a problem with the offer or the segmentation or something.
Other people, though, think the existence of “this is spam” buttons and FBLs is horrible. They call people who click “this is spam” terrorists or anti-commerce-net-nazis. They want to be able to dispute every click of the button. They think that too many ISPs offer this is spam buttons and too many ESPs and network providers pay way to much attention to complaints. The argue ISPs should remove these buttons and stop paying attention to what recipients think.
Sadly, I’m not actually making up the terminology in the last paragraph. There really are who think that the problem isn’t with the mail that they’re sending but that the recipients can actually express an opinion about it and the ISPs listen to those opinions. “Terrorists” and “Nazis” are the least of the things they have called people who complain about their mail.
One of the senior engineers at Cloudmark recently posted an article talking about FBLs and “this is spam” buttons. I think it’s a useful article to read as it explains what value FBLs play in helping spam filters become more accurate.
I come up against a lot of denial when talking with people about spam and email. It makes sense, nobody likes spam. Nobody wants to send spam. And I do understand the initial denial when they hear “you’re mail looks like spam” or “you spammed me.”
It often takes overwhelming evidence to convince some senders that their mail is spam. I’ve talked before about some of my clients who insist that I just “forgot” I signed up for their mail. But these aren’t the only excuses I hear.
A sender that denies all feedback about their mailing program isn’t a very good sender, though. The best thing any sender can do when faced with information is to think about why a recipient might not want their mail.
I often describe my role as a translator between marketers and IT folks. I can translate technology to marketing and back again. One of my other major roles, though, is translating uncomfortable or unwelcome recipient feedback. Many marketing programs have been significantly improved because the program maintainers took a minute to look at the feedback and use it.