Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / How Marketing Automation Workflows Ignore Time Zones
Transcript
- Lucas: It's June 2026, and most marketing automation platforms have had time zone detection for years. You can schedule an email to send at 10 AM in the recipient's time zone. That's table stakes now. Luna: Right, so what's the problem? Sounds like it's solved. Lucas: That's what I thought too, until I looked under the hood of a B2B SaaS company's webinar registration workflow. They had a standard sequence: confirm registration immediately, send a reminder 24 hours before, and then a follow-up with the replay link two hours after the event ends. Luna: That sounds reasonable. Lucas: It is — except the 'immediately' part. That confirmation email was firing the second the lead hit submit on the form. Server time. For a prospect in Tokyo registering at 11 AM their time, that's 2 AM UTC. The confirmation lands at 2 AM local. And the replay link: the event ended at 8 PM Eastern, so the workflow fired two hours later at 10 PM Eastern — which is 11 AM the next day in Tokyo. The link arrived 13 hours late. Luna: Oof. So the time zone intelligence only applied to the scheduled sends, not the trigger-based ones. Lucas: Exactly. And that's the blind spot. Most platforms let you set a send time relative to the trigger — send immediately, send after X hours, send at a specific clock time. But 'immediately' means server timestamp. Unless you build in a conditional branch that checks the prospect's time zone and delays accordingly, you're sending at the wrong hour for a significant chunk of your audience. Luna: How significant? Do you have a number? Lucas: For that company, about 18 percent of their leads were outside their home time zone — Pacific Time. But the impact was concentrated in Asia-Pacific, where open rates on those immediate triggers were 22 percent lower than for domestic leads. Click-through rates dropped even more. Luna: So the fix is pretty straightforward: add a delay condition based on time zone before the send. Lucas: Right. You set a window — say, 8 AM to 10 AM local time — and if the trigger fires outside that window, you queue the message for the next window. A lot of platforms have a 'send during business hours' toggle, but that's often set to the sender's time zone, not the recipient's. You have to manually map the prospect's time zone field to a conditional logic node. Luna: I've seen that field. It's usually populated from IP geolocation on form submission. But not all platforms capture it automatically. Lucas: True. And if it's not captured, you're blind. One common workaround is to use a zip code or country field to infer time zone. Crude but better than nothing. But the gold standard is to pass the time zone through from your CRM or CDP as a custom property. Luna: Let me guess — that's where the data quality issue creeps in. Lucas: Every time. If your CRM has time zone data from five years ago and the prospect moved from New York to London, you're sending at 3 AM again. So part of the fix is a time zone refresh on every engagement. Luna: I want to zoom out for a second. This isn't just about email, is it? SMS and push notifications have the same problem. Lucas: Worse, actually. SMS doesn't have a 'send during business hours' toggle in most platforms. It's send now or schedule at a fixed UTC time. And push notifications from mobile apps are often triggered by in-app events — like completing onboarding — and those fire instantly. You complete onboarding at midnight, you get a push notification at midnight. Luna: And the stakes are higher with push because it's more intrusive. An email at 3 AM sits in the inbox. A push notification wakes someone up. Lucas: Exactly. And the uninstall rate on apps that send push at odd hours is brutal. Some studies show a 15 to 20 percent higher uninstall rate within a week. Luna: So if you're running a multi-channel workflow — email, SMS, push — you need a unified time zone strategy across all of them. Lucas: That's the hard part. Most platforms handle each channel separately. You might have time zone logic in your email workflow but not in your SMS workflow. Or your mobile engagement tool uses a different time zone field than your marketing automation hub. Luna: If these marketing conversations have sparked something you've actually used in your own work, let me mention something quick. A couple of dollars a month is genuinely what keeps these shows going — buy me a coffee dot com slash fexingo. It's that simple. Lucas: Yeah, and we keep it ad-free because of that. So if you've gotten value from any of these episodes, that's the place. Back to time zones — the practical takeaway for anyone listening is to audit your trigger-based sends. Not just the scheduled ones. Luna: What does that audit look like? What are they checking? Lucas: First, pull a list of all workflows that have an 'immediately' or 'after X hours' send action. Then check the send time distribution by recipient time zone. If you see a cluster of sends between 10 PM and 6 AM in any time zone, you've got a problem. Second, verify that your time zone field is populated and accurate. Sample a hundred leads and compare their time zone to their stated location. Luna: And then fix the workflows by adding conditional delays. Lucas: Right. For each trigger, define a safe send window. I recommend 8 AM to 8 PM local time for most B2B. For B2C, you might extend to 9 PM. Then use a branch: if current local time is within window, send now. If not, delay until the next window opens. Luna: One thing I've seen work is to send the immediate confirmation as a server-time send but with a gentle subject line that acknowledges it might be off-hours — like 'Your registration is confirmed — we'll be in touch during business hours.' Then the substantive content goes out in the time zone window. Lucas: That's smart. It sets expectation. The key insight here is that time zone intelligence isn't a one-time setup. It's an ongoing hygiene practice. Every time you add a new workflow or a new channel, you have to check it. Luna: And if you're using AI to generate workflow steps, does it handle time zones? Lucas: Not yet, in my experience. The AI assistants in platforms like HubSpot and Marketo will suggest sequences based on best practices, but they don't analyze your audience's time zone distribution. That's still a human oversight step. Luna: So the takeaway is: don't assume 'send during business hours' works globally. You have to test it. Lucas: Exactly. And the ROI on this fix is surprisingly high. That B2B company saw a 12 percent increase in webinar attendance just by moving the confirmation email into the recipient's morning window. No change to the offer. No change to the content. Just timing. Luna: That's the kind of quick win that makes you wonder what other assumptions are costing you conversions. Lucas: That's the question I'd leave everyone with. What else in your workflows is running on server time when it should be running on people time?