Forum Discussion
Guidelines for different email types
ConorIrvine is bang-on with my logic as well.
The biggest distinction is often asking yourself "Does the user REALLY need to see this to have a functional experience?" For payment, downtime, and password reset, yes, but for most other things, likely not. As marketers, we run the risk of wanting to say yes way more than is required. We love to think people want to see everything 😆.
Out of curiosity, you noted that you are deciding what should and shouldn't live in Braze. Is there a reason it can't all live in Braze or are you using a separate transactional platform? I have been in businesses that have them split and others that have been all in Braze, but I have had no issue having all emails in Braze if that helps.
- juliettec12302 years agoPractitioner
DavidO Thank you for your answer and for that question. We actually have been discussing this more internally and I think we are now realizing that everything CAN live in Braze - we just have so many transactional emails, it's a beast to wrap our heads around how our small team can support it! Plus, I myself have not used API-triggered campaigns, which seems key for setting up a lot of our transactional sends. Have you built any API-triggered?
Related Content
- 28 days ago
- 2 years ago
- 2 years ago