Sienna Wolf

It's "ok". Two problems we came across: (1) We signed up for a trial based on Appstle website stating that it has Store Credit as a feature (see their pricing matrix). It doesn't. (2) We wanted to automatically award points when a customer signs up for the loyalty program. Problem is, this doesn't happen when the user is already a customer. It ONLY awards points when the person is new entirely (not a customer). 99% of our loyalty program signups are AFTER the first sale takes place, so this feature doesn't work for us. Customer support regard this as "expected behavior". I don't. So we're going with another loyalty app.

Let me preface this review by saying we're trialling Bento and haven't quite made the complete switch over to the platform just yet. We're still using Klaviyo for most things... for the moment. The length of this review reflects my overwhelming desire to do what I can to help an upstart become a viable alternative to Klaviyo. With Klaviyo's new pricing rollout this year, we've had one foot out the door. I'm sure we're not the only ones. However, there is pain in switching providers, and until now others just weren't different enough to be worth the switch. However - we believe we are about 2 months out from switching to Bento. The big difference is that Bento is at a growth stage where I can shoot the founder a message on Discord with a feature request, and it gets implemented. Usually within a week. For example, I requested the addition of a "Delivered shipment" trigger for email flows, and they're now working on it as a new feature. To us this means a lot, because we've often had to work around bugs and features in Klaviyo knowing that they were never going to get fixed (if you're a Klaviyo user, you know what I mean). Things we really like: (1) fair pricing on a per-user (not per-email) basis. (2) native survey forms that we use to segment users. (3) tracking begins before users sign up, and then that data is applied to the user profile retroactively, (4) the ability to build our own HTML forms and integrate with the Bento backend (this has become an absolute nightmare in Klaviyo). The native form builder in Bento is quite primitive currently, it doesn't affect us, but that's something for you to think about. Plus a bunch of little things that, compared to our current platform, make things better/easier. As of mid-November 2023 as I'm writing this, we're still waiting for a few things to be implemented before we can make the switch: For example, a full suite of Shopify-related triggers for email flows, and dynamic product feeds for email content like "You also viewed", "Our bestsellers", "Featured collection" etc. But it's part of Bento's roadmap, and it's just a matter of time. Also to be clear - it's a growing platform, and some of the UI/UX elements of it will leave you scratching your head for a while, but it's relatively easy to figure things out if you put your mind to it. I expect this to improve as the platform matures. We hope Bento continues to double down on features that make it a viable option for Shopify merchants to wean themselves off Klaviyo. Best of luck! Thank you so much for this honest review, your comments as you were migrating were so helpful. This year we plan to make the Shopify integration way tighter and it's users like you that help us navigate that. Thank you!