There are date fields, such as Message Date, are displayed with a date and a time on a record, but are displayed with a date when used in an email template. This is because the field is a Date field, not a Date/Time field.
Date and date/time fields cannot be used interchangeably. The name alone doesn't indicate if a field is a date or date/time field. For example, Created Date and Last Modified Date are date/time fields, while Last Activity Date is a date field.
This explains why the time may not show up when using a merge field in a template, even though it shows the date and time in the UI.
If you need a Date/Time field to only display the date in a merge field, use the DATEVALUE function to convert a date/time field into a date field. For example, use {!DATETIMEVALUE(Case.CreatedDate)}.
For further information, you can read more here: Using Date, Date/Time
000385613

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.