Expectation: when an appointment is booked, {{appointment.start_time}} (and other similar time-related fields) for use in workflows includes the time zone so it is clear to the client when their appointment is when they receive confirmation emails and reminder/emails and texts generated through workflows, regardless of where they happen to be physically (in the time zone where they booked the appointment, in a different time zone than where they booked the appointment (i.e., the time zone of the business), etc.).

Problem: Because GHL autodetects time zone of the client when they are booking an appointment, it is causing confusion. This autodetection is using the assumption that the client will attend the appointment in the time zone in which they booked the appointment. It is not taking into account appointments that are for the physical location of the business that were booked in a different time zone. This issue has already caused problems/confusion with appointments several times.

Example: Client booked an appointment with the business (which is on Central time) while they were in the Mountain time zone. They then returned to the Central time zone when the appointment was to occur, but all of the reminders that were being sent from the workflow were for Mountain time without specifying the time zone. The client appointment was supposed to be at 2:45 pm Central, but everything they were being sent said that it was 1:45 pm Central, which thus lead to confusion.

If this is not fixed: this problem causes loss of revenue, confusion, and business reputation problems. This is unacceptable.

Also, I realize that there are a couple of other tickets that touch on this, but the acceptance criteria is less direct.