if/else update to contact timezone
T
Tommy Loch
Currently if/else defaults to account timezone.If user is working in another timezone they are having to adjust the times to work in accordance for the market timezone. For instance est 9am would have to update to 12noon for 9am pst. With users selecting under settings to use the contact timezone would be good if the timeframes would also work like this. If all events worked off the Contact timezone when selected would make things more fluid and efficient in running.
Log In
D
Divyam Bhadoria
Merged in a post:
if/else conditions should run in the contact time if the automation also runs in the contact time.
T
Tracey Lipnicki
If you give us the option to use time based conditions in automations then they need to operate in the SAME time as the rest of the workflow, its absolutely ridiculous to have a workflow operating in contact time but any if/else conditions within that workflow operating in a completely different timezone. Like for example if i have a condition that says only send a particular message after 8am and before 8pm, but that the account timezone is pacific and the contact timezone is eastern it could be sent at 11pm or at 5am and in both cases this is illegal and against communication regulations.
Please fix this ASAP its a big problem.
T
Tracey Lipnicki
use case: i want to send an appointment reminder in the morning of an appointment, but ONLY if the appointment is after 12noon for the contact, otherwise the before appointment time reminder will run and be sufficient. however its later or evening then i want to have an extra reminder to help them show up more.