Monetizing the complaint stream

What if ESPs (and ISPs, for that matter) started charging users for every complaint generated? Think of it like peak pricing for electricity. In California, businesses can opt for discounted power, with the agreement that they are the first companies shut off if electrical demand exceeds supply. What if ESPs and ISPs offered discounted hosting rates to bulk senders who agreed to pay per complaint?
I see pricing scheme something like this.

  • $5.00 per FBL message.
  • $50 for a hand written complaint.
  • $150 for a  report of a spamtrap hit.
  • $500 for an ISP temporary block.
  • $10K for a major blacklisting (SBL, other filtering company).
  • $5K per customer if the blacklisting affects other customers’ ability to send.

ESPs could give a threshold of complaints that are covered. For instance, every per-complaint customer gets 0.05% of their total volume in free FBL complaints. Hand written complaints they get one or two every billing cycle, not to exceed 12 complaints a year. 6 spam trap hits a year. There is a bit of grace in the handling. I can think of lots of ways to make this sender friendly.

Benefits to the Sender

Good senders benefit because they get lower rates and don’t risk much in the way of complaint related expenses. They don’t have to pay that hidden compliance fee that all ESPs customers currently pay.
Senders with more aggressive email programs benefit because they’re able to shoulder the risks associated with those programs directly. The ESP has less to say about buying or renting lists because instead of the ESP paying the cost of problems, the customer assumes that cost. Even better, the sender can pass the compliance cost back onto their list vendor. Imagine being able to tell a vendor they have to discount a list based on the number of complaints or delivery problems. Instead of the vendor selling a list with no incentive for that list to perform well, the vendor now has an incentive to make sure those opt-in addresses really are opt-in.

Benefits to the ESP

The ESP benefits because no longer is their abuse and compliance desk a cost center. With the right mix of clients it may even become a profit center. Plus, the compliance desk is guaranteed to be funded at a rate that covers the work needed to maintain a reasonable delivery rate for customers. The ESP can stop spending so much time telling customers they can’t do something and more time raking in the cash.
It’s a total win for everyone.
Monetize complaints. It’s the future of email.

Facts about engagement
Typo traps

Related Posts

Are FBLs required for a clean mail stream?

A few years ago I would have said that a good mailer could have a good mailing program without necessarily participating in FBL programs. I’m not convinced that’s true any longer. As the mailbox providers and ISPs develop more complex filtering methodologies, it’s important for senders to get any possible feedback from recipients. That press on the this-is-spam button may not actually mean the mail is spam, but it does mean that recipient really didn’t like the message.
Getting the feedback lets a sender fine tune their sending processes and better target what their recipients want to receive.
I do think that senders need to know what users are saying about their email. When users hit the T-i-S button then that is valuable information about how the recipients think about the mail. Senders really on top of things can use positive data (opens and clicks) and negative data (FBLs and unsubscribes) to monitor how wanted their email is and make adjustments to their sending stream.
 
 

Read More

Do you have an abuse@ address?

I’ve mentioned multiple times before that I really don’t like using personal contacts until and unless the published or official channels fail. I don’t hold this opinion just about resolving delivery issues, but also use official channels when reporting spam to one of my addresses or spam traps.
My usual complaints contain a plain text copy of the mail, including full headers and a short summary of the email address it was sent to. “This is an address that was part of a leak from…” or “This is an address scraped off my website. It’s been removed from the website since 2004” or “This address isn’t used to sign up for any mail.”
Sadly, there are a number of “legitimate” ESPs that don’t have or don’t monitor their abuse address. In some cases it’s an oversight or a break down of internal mail handling. But in most cases, it’s a sign that the ESP doesn’t actually handle abuse.
It’s frustrating to watch an ESP post long blog posts about “best practices” and “effective delivery” and “not spamming” and yet not be able to actually stop their own customers from spamming. It’s not even that I necessarily want them to disconnect their spamming customers (although that would be nice) but suppressing the address that I’ve told them was a spamtrap seems trivial. And yet, a month after my first complaint and weeks after escalating to a personal contact, I’m still getting spam.
The 5 things every ESP should do to handle spam complaints.

Read More

Yahoo FBL problems

Multiple ESPs are reporting that the volume of Yahoo! FBL reports have slowed to a trickle over the last 24 or so hours. While we don’t know exactly what is going on yet, or if it’s on track for being fixed, there does seem to be a problem.
There has been some ongoing maintenance issues with the Yahoo! FBL, where requests for updates and changes weren’t being handled in a timely fashion. Informed speculation was the resources needed to fix the FBL modification weren’t available. The interesting question is if Y! will commit the resources to fix the FBL. I could make arguments either way. But Yahoo! gets the benefit of the this-is-spam button whether or not they send a complaint back to the sender.
5/21 5pm: Both Yahoo and Return Path (who administer the Y! FBL) are aware of the problem and are working on it.
5/21 6:30pm: Reports are flowing again according to multiple sources.

Read More