Issues with interpreting DateTimeV2 values in CLU application being converted from LUIS.

Question

We are trying to convert an appointment scheduling application from using LUIS to CLU. I don't see where CLU has a setting equivalent to the "datetimeReference" in LUIS that allows you to specify an offset to use when resolving any DateTimeV2 entities. This is causing us some issues in CLU that we don't currently have with LUIS.

Does such a setting exist in CLU that I've missed or is it on the roadmap for the near future? If not, are there any suggestions on how to handle situations like the examples below?

Here are a couple of examples of the struggles we are having:

1. If someone says, "contact me this afternoon at 2:00" CLU will return something like "2023-12-07 14:00:00". If instead the person said (at noon) "contact me in 2 hours", CLU will return something like "2023-12-07 19:00:14". Both results refer to the same time but 1 is in local time while the other is UTC. The entities, resolutions, etc. look the same except for the value. So, I'm not sure how to know that one result needs converted to local time or UTC and the other doesn't.
2. Assume it is 12/7/23 where a user is located but UTC time has already rolled over to 12/8/23. If the person says, "Contact me tomorrow at 3:00", CLU returns something like "2023-12-09 15:00:00" when tomorrow from the user's standpoint is 12/8.

Thank you!