
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
When responding to an email from inside the Salesforce Service Console using an HTML email template and adding additional content to the email body, the additional body content is stripped and the email is sent without it. The email is sent successfully (no error is received), but the custom content added to the template body is not included in the delivered email.
This issue is specific to the Service Console email composer. When the same email with additional body content is sent from outside the console, the additional content is delivered correctly.
Use the standard Salesforce email send interface outside of the Service Console. Navigate to the related record and send the email from the standard email action. This avoids the console email composer issue and delivers the full body content.
While still inside the Service Console, open the related Case record and locate the Activity History related list. Click Send Email from the Activity History section. This approach uses a different email composer pathway within the console that does not strip the body content.
Update the code behind the "Send Email" button on the Case (or relevant) object. The legacy email composer URL is: /email/author/emailauthor.jsp?retURL=[your retURL parameter]
Replace it with the Lightning-compatible email author URL: /_ui/core/email/author/EmailAuthor?retURL=[your retURL parameter]
This change updates the button to use the newer email composer, which handles HTML template body content correctly in the console.
000387401