Quiet hours: send at times that convert and comply

Configure send windows so automations text at 10 AM, never 3 AM, across every workflow, and understand the timezone mechanics that make or break this.

1. 1

   Fix the account timezone first

   Settings, then Business Profile. Every send window and wait step calculates from this. Wrong timezone means every window is wrong.

2. 2

   Decide contact vs account time

   GHL can respect each contact’s timezone when it knows it. For local businesses, account time is fine; for national lists, enable contact-timezone handling so a 10 AM send means 10 AM for everyone.

3. 3

   Set windows in every messaging workflow

   In workflow settings, restrict sending to your window (9 AM to 7 PM is a safe default; TCPA expects 8 AM to 9 PM local at the outermost). Messages queued outside the window hold until it opens.

4. 4

   Mind the wait-step math

   A "wait 4 hours" step after a 6 PM trigger lands at 10 PM. Windows catch the send, but design sequences so the message arrives when a human would plausibly be texting.

5. 5

   Test the edge

   Trigger a test at 8:55 PM and confirm the message holds until morning instead of firing at midnight.