There are many times we start an email in the native editor, but we need to make adjustments in the HTML editor. This poses problems because of the divs. We've also found that it adds extra <span> tags.
Also, when we preview an email, it looks fine. However, when we send a test email the <span> create extra formatting that is not intended nor seen in the preview.
Is there a way to improve the HTML Email editor to not include the <div> or at minimum not add extra <span>?
It would also be nice to be able to do columns in the native interface.
New Idea
HTML Email Editor Improvements
+5
YES!! I find the extra span tags often change the font from what I've defined earlier.
Elizabeth Panska
+5Also, Please have emails update across everything when they are updated. We realized only after we sent several emails that when we made edits to the email it did not update across the playbooks and any CTAs that were already created with the email.
Hi Lane, Both outreaches and rules engine always updates the latest change.
For email assist flow (in playbooks), we made a decision to take a snapshot of the email at the time, since the person creating the playbook in many cases, is different from the person editing the email. There is the ability to easily refresh in the playbook. I also understand your use case. Maybe while updating the email template, we can provide that option, but we'll need to think through this.
For email assist flow (in playbooks), we made a decision to take a snapshot of the email at the time, since the person creating the playbook in many cases, is different from the person editing the email. There is the ability to easily refresh in the playbook. I also understand your use case. Maybe while updating the email template, we can provide that option, but we'll need to think through this.
Seconded!
I am finding that every Template I have must be tested and heavily edited in the HTML editor several times before I can engage an Outreach because the WYSIWYG version does not accurately display what the email is really going to look like.
Unnecessary and unseen text formatting is the biggest issue I am seeing - things like random italicized text, serif versus sans-serif font sporadically throughout, font sizes changing, etc.
Also seconding the need for tables or columns. I read elsewhere that tables were on the roadmap - is there any update for that?
Another ask would be the ability to control the visual aspect of Buttons more. Currently you can only control the size and color of the button. It would be nice if you could control the text font, size, style (bold, italic, etc.).
Has anyone been able to do this via the HTML? When I attempt to make textual changes via the HTML editor the changes work, but it renders the button un-clickable.
I am finding that every Template I have must be tested and heavily edited in the HTML editor several times before I can engage an Outreach because the WYSIWYG version does not accurately display what the email is really going to look like.
Unnecessary and unseen text formatting is the biggest issue I am seeing - things like random italicized text, serif versus sans-serif font sporadically throughout, font sizes changing, etc.
Also seconding the need for tables or columns. I read elsewhere that tables were on the roadmap - is there any update for that?
Another ask would be the ability to control the visual aspect of Buttons more. Currently you can only control the size and color of the button. It would be nice if you could control the text font, size, style (bold, italic, etc.).
Has anyone been able to do this via the HTML? When I attempt to make textual changes via the HTML editor the changes work, but it renders the button un-clickable.
Hello!
Happy to announce that your request has been considered. Email Templates are enhanced with a new UI and significant performance improvements. Changes in the feature make it more user-friendly, and also allows admins to customize the email templates to provide the best email template layout that works in various email clients.
You can find the relevant information in Release Notes.
This feature is implemented in both SFDC & NXT version.
Thanks for posting!
+7
Bringing these points back up, since there’s still ongoing issues...
There are many times we start an email in the native editor, but we need to make adjustments in the HTML editor. This poses problems because of the divs.
- Divs (and inline CSS setups) make it difficult to tell which code needs to be updated to make the template appear the way we want it. Example: rounded corners only on the top, etc.
- See second quote here:
-
I am finding that every Template I have must be tested and heavily edited in the HTML editor several times before I can engage an Outreach because the WYSIWYG version does not accurately display what the email is really going to look like.
Also, Please have emails update across everything when they are updated. We realized only after we sent several emails that when we made edits to the email it did not update across the playbooks and any CTAs that were already created with the email.
- It would be a HUGE timesaver if we were able to update a template and did NOT have to update EVERY instance where it is used.
The new email template editor continues to cause issues with the HTML editor. Are there any updates planned on the 2024 roadmap?
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.