X

The Modern Marketing Blog covers the latest in marketing strategy, technology, and innovation.

How to Avoid Sending the Worst Sales Email

Jody Mooney
Product Marketing Manager

Has your inbox ever been plagued by a poorly made “sales email”?

You’re not alone.

Most of us have received one of those cringe-worthy emails from some anonymous seeming sales rep. The wrong name, the impersonal subject line (“XYZ” placeholder, anyone?), the comic sans font, we all know it when we see it.

In fact, a quick Google search for “worst sales email” yields a strong sampling of entertaining emails and customer rants. Sales emails play a critical role in finding opportunities, but not if the recipient is left shaking their head.

So here are three tips for how you can avoid ranking at the top of that “worst sales email” search.

1. Be Timely
“Time kills deals.” The faster you can get those leads to sales, the faster they can reach out, the more relevant you are. The formula is that simple. Setting up alerts that inform your reps when a prospect performs a specific action can help shorten the time it takes to respond.

2. Give Them Content
Whether it’s serving up a set of email templates or even sending them copy in a Word document, pre-formatted responses save sales from going to far afield.  Whitepapers, videos, case studies, and invitations – save them time and hassle of trying to create ‘marketing-messages’ on the fly.

3. Build Relationships
Serve up all of that juicy insight on how a buyer interacts with your website and marketing campaigns right within the CRM. The sales team will have the upper hand, and can tailor their conversations and build credibility.

Luckily, there are tools that enable sales to act fast without delivering emails with funky fonts. Why not help them make a good impression from the start!

Oh, and please share your “worst sales email” story. I know you have one.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.