Item: Litmus
Rating: 10
Author: Verified User

Use Cases and Deployment Scope

We are using Litmus as a cohesive method to QA our emails before deployment and test rendering within different email hosts. Our marketing department uses it and has proof reviewer provisions for many individuals across the company. Previously we sent emails to be QA'd via Outlook as an attachment to an email and if there was a team that needed to review, if there were multiple responses at a time they would get mixed up. Litmus has allowed us to organize the edits that we receive from a team.

Pros and Cons

Organize email revisions.
Create a single avenue to receive email feedback.
Render emails in different email host environments.

Setting up proof review access for users could be easier.
Accessing Litmus analytics for email sends needs to be simpler.
The preview function with Marketing Cloud versus the browser view could be explained better.

Return on Investment

Made our QA process much more efficient.
Increase email deliverability.
Decreased the amount of time we spend reviewing emails.

Key Insights

Do you think Litmus delivers good value for the price?

Yes

Are you happy with Litmus's feature set?

Yes

Did Litmus live up to sales and marketing promises?

Yes

Did implementation of Litmus go as expected?

Yes

Would you buy Litmus again?

Yes

Likelihood to Recommend

Litmus is exceptional if you have a large organization and need to have emails proofed and reviewed by a large number of people. The platform allows you to receive feedback in a single way while also showing you exactly where they would like to place their edits. If you have a smaller team and your email recipients do not use many different email hosts, Litmus may not be as necessary for your team.

Litmus: We are ALL IN!

Overall Satisfaction with Litmus