There are handful of reasons why email messages might not end up in their desired location of your recipient's inbox. The good news is that there are a few things you can do about it. This article addresses some settings you'll want to check, some concepts you'll want to adhere to when crafting messages and some good old fashioned do's and dont's to help improve the deliverability of your email.
How CollegePlannerPro sends email on your behalf
Email messages sent to your recipients will be "From" a CollegePlannerPro dot com email address. It used to be that we simply used your email address that you have associated with your CollegePlannerPro account to say that the email was "from" you. This isn't copacetic any longer with most major email providers as it's the same method that SPAM is sent. In other words, it's not cool to send an email and say it's physically from someone else. So, to work around the technicality, CollegePlannerPro as a system sends email with our email address as the "From" address, however we use your email address as the "Reply-to" address. The Reply-to is the email address an email program will use to send a message back to when the "Reply" button is clicked.
Ways to improve the likelihood of your email being delivered
One strategy for decreasing the likelihood that your email or broadcast will be considered SPAM and thus not actually delivered to your recipients is to encourage the "whitelisting" of two email addresses by your students and contacts: [email protected] and [email protected]. More information on this process is explained in another article in our Knowledge Base, What to do when students and parents are not receiving emails.
How SPAM filters think
When you send an email to a recipient, your message has to get past:
- their email provider's spam filters, then
- their email application/program's spam filters.
It's a lot easier than you think for an innocent, legitimate email to be mistaken as spam (this is called a "false-positive"). So it helps to understand how spam filters work, and what they look for. Spam filters analyze the following... (we'll elaborate the chart further down the page.) Some of this stuff gets a little technical, so don't feel like you should understand everything that's mentioned.
|What Spam Filters Check:||What They're Thinking:|
|Your Subject Line||"Did the sender use 'spammy' words and phrases?"|
|Who the message is addressed "To:"||"Did the sender even know the recipient's name, or is it just addressed to an email (which they could have easily guessed, or programmed a script to generate)?"|
|The content of your message||"Is HTML email coded properly? Did the sender take the time to create a plain-text alternative? Does the content contain spammy words or phrases?"|
|Your IP address||"Was the email sent from a server that is on a blackhole-list, or is known to be spam-friendly?"|
|The sender||"Friend, or foe? Is the sender in my address book or contacts list?"|
|Your "from" email address||"Is the email address faked? Is it from a free email account, or does it sound too anonymous?"|
|Your domain name||"Is the sender using a valid domain name that he owns, or is it an anonymous looking, or faked?"|
|Advice from other spam filters||"Has this same message (or sender) already been reported as spam by other recipients, or other spam filters out there?"|
Avoid these common mistakes
These are the most common mistakes we see made, which result in accidental spam filtering.
- Using spammy phrases, like "Click here!" or "Once in a lifetime opportunity!"
- Going crazy with exclamation points!!!!!!
- USING ALL CAPS, WHICH IS LIKE YELLING IN EMAIL (especially in the subject)
- Coloring their fonts bright red, or green
- Coding sloppy HTML (usually from converting a Microsoft Word file to HTML)
- Creating an HTML email that's nothing but one big image, with little or no text (since spam filters can't read images, they assume you're a spammer that's trying to trick 'em).
- Using the word "Test" in the subject line (strange, but true)
- Designing HTML email in Microsoft Word, and exporting the code to HTML (that code is sloppy, and spam filters hate it)