I’m trying to understand your issue. I think it is perfectly fine to create different email Templates for every step in your clients journey. Each Email-Template will have a fitting text for a given purpose along with some Placeholders maybe.
Transactional Email Templates are ideal for scenarios like e.g.:
Account Creation Confirmation: When a user signs up for a new account on your website or platform, you can send them a confirmation email to verify their email address and welcome them to the platform.
Password Reset: If a user forgets their password and requests a reset, you can send them an email containing a link to reset their password securely.
Subscription Confirmation: When a user subscribes to a newsletter, blog updates, or any other recurring content, you can send them a confirmation email to verify their subscription.
Booking Confirmation: For businesses like hotels, airlines, or event venues, sending a confirmation email after a user makes a booking is crucial to provide them with details about their reservation.
Appointment Reminders: For service-based businesses such as doctors’ offices or salons, sending reminders about upcoming appointments helps reduce no-shows and keeps clients informed.
Feedback Requests: After a user interacts with your product or service, you can send them an email requesting feedback to gather insights for improvement.
Account Activity Notifications: Inform users about important activities on their account, such as changes to their profile, security-related events, or updates on their submitted content.
Shipping Updates: If your business involves shipping physical goods, sending email updates about the status of an order, including tracking information, is essential for keeping customers informed.
Policy Updates: Notify users about changes to your terms of service, privacy policy, or any other important policies that affect their interaction with your platform.
Event Reminders: For webinars, workshops, or other events, sending reminders with event details and access links helps ensure attendees don’t miss out.
The word ‹ Template › means… well… template!
A preformed framework
i am expecting to set up one template and then edit parts of it for each sequential message
But I am copying the Template each time, renaming it, saving it then editing it
That’s cumbersome
And I’ve already saved 6 templates in this sequence - the Template section is going to be huge as I create new sequences?
Hi @MemberGate , indeed: on Brevo, when you want to send an email, either as a newsletter email or as a transactional email, you have to create templates.
Once created, you can find them all in your Templates section, and manage them: edit them, duplicate them, deactivate them, etc etc
And what you’re saying is that you find the steps needed to create a new template from the automation a bit too time consuming?
I would expect a template to be something you craft once and then copy, edit and save the new version as a title in it’s own right, then post that message to the Automation
That way - when I start a new campaign, I can use the campaign name for the Automation Sequence Template and the messages a re sub-document’s or ‹ children ›
But I can see a time when I need to be really smart about naming Templates and the Template selection getting challenging to navigate
Indeed, I see what you mean. It could have been a different way for us to implement templates.
On Brevo each new email is stored as a new template, so that you can find them all in one place, and if need be re-use it somewhere else: for example, if you created a template for a newsletter, but for any reasons you need to use it inside an automation as well, you can do it easily.