Using ACT! as an Email Marketing Tool

by John Kaufman on May 30, 2009

Our Objective:
Send 4,000 full-color newsletters and 4,000 Lunch and Learn ACT! Online Training schedules per month.
Send occasional surveys to our clients.
Track Opt-outs, bounces, clicks by link and opens.

The Challenge:
The ACT! Mail-Merge to email takes a long time to send this many emails.
Managing Opt Outs and Bounces is very time consuming.
No ability to track opens and clicks.

The Solution:
We are using a $59.92/month SwiftPage Email Account with a 4,000 email per day send limit – www.swiftpage.com.  First we create our newsletters and other templates using Microsoft FrontPage 2003 because of the advanced flexibility it provides.  Then we create a look up in ACT!, click the E icon on the ACT! icon tool bar, select our template and click send.  SwiftPage then uploads our list in the background and sends all the emails from their white-listed servers.   What used to take hours now takes 5 minutes.  Anyone who opts-out is on a list maintained by SwiftPage so we don’t unintentionally broadcast to them.  And finally, their software works!

My Conclusion:
If you want to do CAN/SPAM Compliant email broadcasting with ACT!, SwiftPage Email is the way to go!

John Kaufman
Sales and Marketing Manager
The CRM Connection
www.thecrmconnection.com

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • LinkedIn
  • MSN Reporter
  • MySpace
  • PDF
  • RSS
  • Yahoo! Bookmarks
  • StumbleUpon
  • Technorati
  • Twitter
  • Yahoo! Buzz
  • email

{ 1 comment… read it below or add one }

Renee PJ Cronin June 1, 2009 at 8:20 am

John,
Well stated…we at Capitol Computer Systems, Inc. do the same using SwiftPage Email. We have 8 different Product line newsletters and what used to take hours is now accomplished in a few minutes! I will often create the newsletters and publish them in SwiftPage Email to the admin staff’s account for them to send to our clients and prospects.

Leave a Comment

Previous post:

Next post: