Most likely you did not answer the questions that are most important to them.
- How will you make sure that only subscribed recipients will get your emails
- How will you handle bounces and complaints
- How will you monitor your sending
Don't beat around the bush and you will be approved in less than 1 day.
Founder of Plunk here.
Yes, Plunk is designed to work with AWS SES. I was not the one that made it hard for folks to self-host their own email infrastructure. SES is simply the cheapest and most reliable option out there. Reminder, we are not talking about a private "let's send 10 emails a day" solution. This needs to deliver marketing emails at scale.
Does that mean you have to use SES, no. The code is open-source, swap it out for another provider if you truly believe that you can do it better. I'm open for contributions.
Love that one! That would definitely be the carving of my space in the market. There are so many email tools out there, really setting myself apart in the market was a difficult one! In the end, I managed to do it with affordability and DX.
It was built for in-product actions but you can use it for whatever suits your needs. It may need some extra code on your side to make that work though.
I am currently using it to check up on my users after they have either skipped or completed the onboarding so it is definitely doable!
Validating was really easy. I am really active on Twitter and saw loads of people complain about terrible APIs offered by some tools and the ridiculous pricing of others.
+ I also had this problem myself so I knew it was a big point of frustration.
I had pretty much validated the idea before creating the MVP!
Splunk is in a very different part of the landscape than Plunk so legally there isn't that much of an issue. Verbally it may be more confusing but it'll be fine!
A very big part of what Plunk does is giving you the opportunity to link multiple events together and delay emails. You can extend it to users that have clicked button A and B but not button C and send those an email after 5 days. Significantly harder to implement and a lot of code that isn't really used elsewhere!
Sorry about the confusing wording, with bounce I mean both hard bounces, rejects and complaints (they are all monitored appropriately). They are all taken into account when calculating the % because they all have impact on the domain reputation.
Thank you very much for this incredible feedback, very kind of you!
I have already made some minor changes (fixed the typo and moved dedicated support).
Tomorrow I will be looking into altering the copy because I do understand what you are saying and have heard the same feedback about the term "behavioural email tool"from a couple of people!
Thank you very much for linking Stripe Atlas' guide, seems really helpful and in-depth!
I get what you mean by this!
Let me clarify what my way of thought is behind the "completely free, no strings attached". I do not ask for your credit card info, I don't put you on a trial that magically renews at the end of the month, I don't offer you a sketchy sign-on deal with an unexpected bill at the end of the month. I try to make it as ethical as possible, unlike some other marketing/emailing tools.
That is my meaning behind no strings attached. Of course I put some features behind a subscription because they demand significant work from my side (managing the domains is one of those).
At scale this should work fine. Some parts of the dashboard are not yet prepared for that amount of data to flow in though, may be hard to navigate and monitor.
I am also looking at the pricing for that because right now I offer unlimited emails but I need a good way to compensate for power users like yourself without going completely overboard.
- How will you make sure that only subscribed recipients will get your emails - How will you handle bounces and complaints - How will you monitor your sending
Don't beat around the bush and you will be approved in less than 1 day.