Hi Zeno, great project, impressive seeders.
I want to use Resend but get puzzled how to co-exist with sales reps:
1) I am a developer in a startup, I can figure out how to create React email templates.
2) I can create several initial email templates in React.
3) My colleagues are sales, they cannot code in React but they do need to adjust templates time to time (either the template itself or a one-off instance with adjustments to personalize/provide-order-specific-custom-details)
4) obviously sales are not going to edit React code in VSCode and I cannot get rid of sales reps so we need to co-exist and use the same emailing platform. I don't want to do the adjustments for sales reps but rather enable them adjust templates themselves.
What is the best way to enable sales reps to adjust existing email templates?
At this moment, Resend is tailored to the transactional email use case. This means one-to-one emails that you typically integrate into your app like reset password, weekly digests, etc. - as opposed to one-to-many email broadcasts. At some point, we'll probably expand the product to adapt to non-technical users like your sales colleagues.
2 comments
[ 2.8 ms ] story [ 16.5 ms ] thread1) I am a developer in a startup, I can figure out how to create React email templates.
2) I can create several initial email templates in React.
3) My colleagues are sales, they cannot code in React but they do need to adjust templates time to time (either the template itself or a one-off instance with adjustments to personalize/provide-order-specific-custom-details)
4) obviously sales are not going to edit React code in VSCode and I cannot get rid of sales reps so we need to co-exist and use the same emailing platform. I don't want to do the adjustments for sales reps but rather enable them adjust templates themselves.
What is the best way to enable sales reps to adjust existing email templates?