The secret to dealing with ISPs

What is the secret to dealing with ISPs?
The short answer is: Don’t do it if at all possible. Talking to ISP reps generally isn’t going to magically improve your reptuation.  There is no place in the reputation systems where delivery can be modified because the delivery specialist knows or is liked by the postmaster at an ISP.
With my clients, I work through delivery issues and can solve 80 – 90% of the issues without ever having to contact anyone at the ISPs. 90% of the remaining issues can be handled using the publicly available contacts and websites provided by the ISPs.
In the remaining cases, the “secret” to getting useful and prompt replies is to:

  1. *Briefly* describe the issue. The folks handling senders on the ISP side are dealing with queues that have tens or hundreds of emails in them. The easier you make your ticket to handle the better.
  2. Provide all the information they need. At the bare minimum include the sending IPs, any domains in the rejected email and full copies of the rejection message. Pull this information out in a way that someone skimming the message can easily pick out.
  3. Ask clear questions. Don’t ramble on for 4 paragraphs talking about your business and meandering around the issue. Say: I don’t know why we’re getting this, what are you seeing? or I have made these changes and would like my reputation reset so we can create a new one. Or my mail is being bulk foldered and I can’t fix it, what are you seeing causing our reputation scores to be so low?
  4. Don’t waste time providing all the details of your business model. Really. Everyone tries to do it, and your business model isn’t usually relevant to your reputation. “Let me tell you about my business model…” is a complete cliche and causes massive amounts of eye rolling among ISP reps. If you feel there is something relevant (this is confirmation email, we’re only mailing registered users, or similar) then feel free to include that. But the full details of your business model aren’t going to help, and may hurt. The ISPs care about are what your stats and numbers look like.
  5. Do (briefly!) describe what steps you have taken (and how long you have tried them) to resolve the issue yourself. The bigger ISPs are getting very good at providing feedback to senders through FBLs, block messages and postmaster websites. Show them that you respect their time and have attempted to solve your problem without contacting them.
  6. Give them time (at least 24 hours) before following up. One of my good friends handles the postmaster desk at a major ISP and one of her biggest annoyances is someone who opens a ticket, sends her a personal email and then IMs her all within 20 minutes. It does not make her deal with your issue any faster, I can promise you that.
  7. Provide IP addresses, domains, any bounce messages you’re getting from the ISP. This is critical. Provide all the information the ISP needs. I know I mentioned this above, but it seems to need repeating as there are a lot of emails to the ISPs that never provide the IP addresses or any relevant information, which wastes time.
  8. Go to the appropriate person. Calling your best friend the VP of whatever actually slows down handling of issues more often than not. It also results in overhead that no one really wants to deal with (placating managers outside your management chain is a pain and takes a lot of time). Finally, it will not endear you to the folks handling the day-to-day filtering decisions which will make future issues more difficult to deal with.
  9. When you get an answer, take the information provided and make changes. Spending 3 days arguing back and forth about how they’re wrong while doing nothing to actually change your mail practices doesn’t fix anything. If you have proof that their data is wrong, provide it and why you think it is wrong. Sometimes you may be right but you’ll need to explain it clearly and provide the data you have. Sometimes you won’t and you’ll need to accept that, too.
  10. SAY THANK YOU! You asked for help or answers, you got the time and attention of an ISP rep, say thank you for that. Even if it’s not what you wanted to hear, the person on the other end still took time to answer you.

The biggest secret can be summed up as: act as if you value the time of the person on the other end of the ticket / email / IM more than you value your own. Spend an extra 20 minutes to collect the information they’re going to need. Edit that email to make it short and sweet, paragraph upon paragraph of text explaining your business model will not make the ISP person sit up and take notice. List what you’ve done and changed and ask for what they are seeing that is causing your delivery problems. Often if you’ve made changes and they see recent improvements they will make adjustments for you, but this is because it’s clear you’ve taken steps to mitigate things all on your own.

Related Posts

AOL changes bounce behaviour

A couple other bloggers have commented on the recent AOL blog post talking about changes to the MAILER-DAEMON string on bounce messages.

Read More

Problems at Excite

I’ve been chasing an intermittent and inconsistent delivery problem at Excite for a week or so. Excite is accepting email, but mail is not getting to the recipient’s inbox or bulk folder. Al tweeted he’s seeing a similar problem with his customers’ mail and had contacted Excite.
Excite does appear to be aware of the issue, but I have no ETA on a fix.
EDIT: Comments are closed

Read More

Winning friends and removing blocks

I do a lot of negotiating with blocklists and ISPs on behalf of my clients and recently was dealing with two incidents. What made this so interesting to me was how differently the clients approached the negotiations.
In one case, a client had a spammer slip onto their system. As a result the client was added to the SBL. The client disconnected the customer, got their IP delisted from the SBL and all was good until the spammer managed to sweet talk the new abuse rep into turning his account back on. Predictably, he started spamming again and the SBL relisted the IP.
My client contacted me and asked me to intercede with Spamhaus. I received a detailed analysis of what happened, how it happened and how they were addressing the issue to prevent it happening in the future. I relayed the info to Spamhaus, the block was lifted and things are all back to normal.
Contrast that with another client dealing with widespread blocking due to a reputation problem. Their approach was to ask the blocking entity which clients they needed to disconnect in order to fix the problem. When the blocking entity responded, the customer disconnected the clients and considered the issue closed. They didn’t look at the underlying issues that caused the reputation problems, nor did they look at how they could prevent this in the future. They didn’t evaluate the customers they disconnected to identify where their processes failed.
The first client took responsibility for their problems, looked at the issues and resolved things without relying on Spamhaus to tell them how to fix things. Even though they had a problem, and is statistically going to have the occasional problem in the future, this interaction was very positive for them. Their reputation with the Spamhaus volunteers is improved because of their actions.
The second client didn’t do any of that. And the people they were dealing with at the blocking entity know it. Their reputation with the people behind the blocking entity was not improved by their actions.
These two clients are quite representative of what I’ve seen over the years. Some senders see blocking as a sign that somehow, somewhere there is a flaw in their process and a sign they need to figure out how to fix it. Others see blocking as an inconvenience. Their only involvement is finding out the minimum they need to do to get unblocked, doing it and then returning to business as usual. Unsurprisingly, the first type of client has a much better delivery rate than the second.

Read More