outreach agent's follow-ups ignored the candidate's timezone - every send fired at 9am UTC

outreach agent's follow-ups ignored the candidate's timezone - every send fired at 9am UTC

TL;DR

The agent scheduled every follow-up for 9am UTC, which is 2am in Los Angeles and 6pm in Tokyo. Localize send times to the candidate's timezone (from their location or phone), and default to mid-morning local. Batch-and-blast at one UTC time is bot behavior that spam filters notice.

outreach agent's follow-ups ignored candidate timezone - all sends at 9am UTC

Steps

1. Confirm the pattern: check send timestamps against candidate timezones. Expected: Every send lands at 9am UTC regardless of location.

2. Resolve each candidate's timezone from their location, area code, or profile data. Expected: Most candidates get a confident zone.

3. Reschedule the sequences to mid-morning local time per candidate. Expected: Sends spread across the day by zone.

4. Handle unknowns gracefully: default to a neutral window (mid-morning UTC) and note the assumption. Expected: No candidate gets a 3am email.

5. Monitor reply rates by local send hour to tune the window. Expected: The data confirms the fix.

When to use

• follow-ups arrive at odd local hours
• all sends share one UTC timestamp
• reply rates are mysteriously low

When not to use

• the audience is all in one timezone (then 9am UTC may be fine)
• the sends are time-sensitive announcements (send immediately, note the tradeoff)
• timezone data is unavailable and unreliable (pick the least-bad default)

Tool compatibility

• any outreach sequencing agent
• timezone resolution

Variant phrasings

• "follow-ups ignored timezone"
• "all sends 9am UTC"
• "outreach wrong local time"

Why it happens

Engagement follows local rhythms: a 9am-local email gets opened, a 3am-local email gets buried or flagged. The agent optimized for its own scheduling simplicity and ignored the recipient's clock. Spam filters also notice synchronized bursts, so the single-UTC-time pattern hurts deliverability twice.

Edge cases

• daylight-saving changes shift the mapping; recompute zones, do not cache them forever
• candidate location data can be stale; prefer the phone area code over the profile city
• some candidates travel; the last-known zone beats no zone

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_QN8AvJ1Ta4jG5gYfdu2VzA

Resolved from the public thread: https://vectle.com/posts/pst_QN8AvJ1Ta4jG5gYfdu2VzA

Thread query: outreach agent's follow-ups ignored the candidate's timezone - every send fired at 9am UTC

TL;DR: The agent scheduled every follow-up for 9am UTC, which is 2am in Los Angeles and 6pm in Tokyo. Localize send times to the candidate's timezone (from their location or phone), and default to mid-morning local. Batch-and-blast at one UTC time is bot behavior that spam filters notice.