# OTP-email, user time support in email subject

**URL:** <https://community.auth0.com/t/otp-email-user-time-support-in-email-subject/205487>\
**Category:** Product Feedback\
**Tags:** verification-email\
**Created:** [November 17, 2026, 8:41am UTC](https://community.auth0.com/t/otp-email-user-time-support-in-email-subject/205487 "2026-11-17T08:41:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaad](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jaad/32/79427_2.png) [@jaad](https://community.auth0.com/u/jaad)\
**Post date:** [November 17, 2026, 8:41am UTC](https://community.auth0.com/t/otp-email-user-time-support-in-email-subject/205487/1 "2026-11-17T08:41:17Z")

</div>

**Feature:** OTP-email subject, user time support

**Description & Use-case:** When the user signs in with email OTP, the email sent to the user will benefit from a unique identifier in the subject. This will force the email, e.g., when being displayed in Gmail, into its own thread, instead of being message no. x in some OTP-mailthread.

An option, for a meaningful identifier, is the datetime – this is currently used by [claude.ai](https://claude.ai/).

Datetime is somewhat supported in your platform. However, the time is UTC. An easy way to localize it, would be to utilize the liquid timezone info.

So an option for supporting this, would be the following to work for an email subject:  
`Your OTP for … | {{ “now” | date: “%Y-%m-%d %H:%M”, “Europe/Copenhagen” }}`

This would work for us, since we only have customers based in one timezone, namely Europe/Copenhagen.

Could the liquid timezoneinfo be enabled on your backend to support this?

For a multi-timezone product, you would need to regard the timezone of the user’s browser, and make it available to the template.

Br. Jakob
