3d • General discussion
Check the Time Zone Before You Schedule
Command note: an automation that fires at the right hour in your time zone can still land at 3am in the client's.
I learned this on a reactivation campaign. The sequence was set to send at 9am. It sent at 9am. Just not the client's 9am. The sub-account was still on the default time zone from when it was created, and nobody had touched it since.
Where the mismatch hides:
• The sub-account setting, still on whatever the template shipped with
• The user profile time zone, which is separate from the account's
• The calendar, which carries its own setting again
• The contact record, which may have none at all
Four places, one clock, and no warning when they disagree.
The check I run now on every account before a single scheduled send goes live:
1) Confirm the sub-account time zone matches where the business actually operates, not where you built it
2) Confirm the calendar's time zone separately, because it does not inherit
3) Send one test to yourself with a wait step, and read the actual delivery timestamp instead of trusting the preview
4) For anything going out overnight, add a send window so a delayed step cannot drift into the small hours
None of this is clever. It takes four minutes, and it is the difference between a campaign that looks professional and one that wakes somebody's customers up.
The automation was never wrong about the time. It was wrong about whose time.
0
0 comments
Check the Time Zone Before You Schedule
Suggested communities
Powered by