I am in search of an alternative to LemList. At 100$ per month for one sending address, I have been looking at exploring alternatives. I have contacts that are of low importance, so I am fortunate to have some ability to play around with trying alternatives.

I have now tried

Mystrika
Clickreach
Hexospark.

Across the board, key features that are missing from all products

#1 No option to bcc each sent email. I want to be able to bcc the email to my salesforce sync email.

#2 Lemlist has a native way to sync with salesforce’s api, so it can pull the contacts natively. This is critical since it is how I manage who opts out. If I send an email in salesforce and the contact opts out, it pulls the record from the salesforce report, and thus pulls it from lemlist campaign automatically. For all 3 platforms, if someone opts out outside of the platform, I have to manually either pull the record or upload it to the universal blacklist. This is really confusing to coordinate. My current workaround that I will attempt is to hard delete the contacts from each platform respectively at the end of each campaign and then re-upload fresh from the exported SF report when I go to do a new campaign.

XXXXXXXX Mysrtika - 4 out of 5 stars XXXXXXXX

This platform by far has been the most useful between Mystrika, Clickreach, and Hexospark as it has the option for email warmup.

I also like that it has a unibox and it allows for email rotation.
The design/UIX is a little old school, but it gets the job done.

I’ve removed one star since it also has a bug like Clickreach, where it is sending the email in duplicate randomly. However, it is not duplicating it from the same sending email address, so for now I have decided to let it run its play

**|| I wrote the following to mystrika for support; ||**
Was able to successfully get a campaign up and running. Just encountered a fun bug. It seems to have sent the same email to the same end user twice, but across two different sending accounts… Fortunately the end user has an OOO set up, so your unibox feature actually caught the issue in action! I am worried that it might be occurring though more, so I'm going to pause the campaign for now.

**|| I got the following response from support; ||**
“Though the Mystrika system is completely distributed, with multiple checks in place to avoid this from happening.
There is a small chance that this is possible.
The chance of this happening should be less than 0.1%.
Also, note, this issue can only happen on the first contact email, and can never happen on the follow up email.
We are continuously improving our algorithm, and hopefully we should be able to bring the chance of this happening much lower in future.”