Identify the clock explicitly
A business, a contact and an account can be associated with different timezones. Write which clock the workflow uses and why it matches the response promise. Avoid an unqualified “send at nine” instruction. If a contact’s location is unknown, do not invent it from a phone number merely to make the schedule look personalized. Use a documented fallback and disclose the operational limitation.
Inspect the governed actions
A window may affect the sequence differently from a separate wait condition. Review the actual actions inside the path, including staff notifications and customer messages. You may want an immediate acknowledgement but a reminder during staffed hours. A single broad setting is not evidence that both behaviors have been expressed correctly. Keep the distinction visible in the event map.
Treat changes as a new test case
The workflow-settings documentation warns that existing running entries are not simply retimed by every account timezone change. Before modifying a live schedule, identify which entries may already be waiting and what the change is expected to affect. Do not experiment on real customer messages to discover the behavior. Use an authorized test path and preserve the previous operating description.
Include calendar boundaries
Check closing time, reopening time, a weekend and a relevant clock-change boundary where applicable. These are scenario checks, not a promise of universal timezone handling. Keep the business-hours wording consistent with actual staffing and review it when holidays change coverage. If the team cannot maintain a complicated schedule, a simpler honest response promise can be safer than a precisely timed but unreliable sequence. A clear test note includes the event time, displayed account timezone and expected local sending time, making any later discrepancy easier to interpret.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- HighLevel workflow settings — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27
- Wait workflow action — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27