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.

All,

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.

That's the beauty of open-source.

You can!

https://docs.useplunk.com/working-with-contacts/metadata

I use the built-in capabilities of AWS and Vercel.

https://vercel.com/docs/concepts/projects/domains

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.

That's a great question. The 3 email categories IMO are the following.

- Transactional: one-time emails, sent through an API on-demand (e.g. password resets, magic links...)

- Automations: Repeatable sequences such as onboarding flows with delays and follow-ups

- Broadcasts: Emails sent to a segment of contacts (e.g. newsletters, changelogs...)

Thanks! I might be good to write some content (blog posts) about those different categories and which existing solution could be replaced with your tool.

You do have something covered at https://www.useplunk.com/use-cases but a lot more could be added.

That's actually good feedback. I've been chatting with people who switched providers and am building out comparison pages at the moment!

Thank you so much for the interaction and feedback.

Sure, no problem. I don't have a use case where I could test your app so this kind of feedback is all that I can do :)

Thank you very much for the kind words!

Thank you very much for this, I wasn't aware of that!

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!

The fact that you don't need to set up and manage your own SMTP server is a big advantage I believe.