A campaign set to run from 9 a.m. to 5 p.m. says little until you know whose clock those hours use. A rep's screen, a sender account, a campaign, and a prospect can each be in a different time zone. Before using a LinkedIn outreach tool across regions, identify the setting that governs queued actions and check one planned action against the intended local window. Do not assume the tool converts every prospect's location automatically.
Find which setting owns the queue
HeyReach's help center describes a campaign Schedule with a time zone, active hours, and active days. Its detailed explanation says those settings apply to every sender in that campaign. Expandi documents activity days, hours, and a time zone under the connected LinkedIn account's settings. Linked Helper says its account working hours apply to all campaigns. These are vendor descriptions of different scopes, not results from a controlled comparison.
Even one help page can leave a question open: HeyReach's introduction refers to configuration for every sender per campaign, while its detailed section says there are no sender-specific hours inside a campaign. If separate senders must follow different local windows, inspect the actual campaign settings and ask support how the scope works before enrolling either audience. A time-zone field alone does not prove recipient-by-recipient scheduling.
Sources: HeyReach campaign working hours and time zone, Expandi activity schedule settings, Linked Helper working hours and limits
Separate the displayed clock from the working hours
Linked Helper explicitly warns that changing its ‘Shown for timezone’ value changes how existing working hours appear on screen; it does not move the actual start and stop times. An operator who sees a newly displayed 10 a.m. and assumes the queue has been shifted could contact the wrong region at the old time. Edit the underlying day and hour fields when the intended window changes, then inspect the resulting schedule again.
Write the intended window as a region, a local time, and a calendar date before configuring it. Convert that window to the zone the tool actually uses. Check a date on the other side of a daylight-saving change as well if the campaign will run that long; a fixed offset and a named region may not mean the same thing throughout the campaign. If the interface cannot show which zone or offset will govern a future action, ask the vendor for a dated example instead of guessing from your laptop clock.
Verify one queued action before opening the list
First decide whether the account can accept the platform-policy risk of a third-party tool. If it can, use a consenting internal contact and a campaign that can be stopped. Record the sender, campaign, recipient region, scheduled date, intended local window, and the time zone shown in the tool. Queue one action far enough ahead to inspect it before it runs. Check its displayed next-action time, then compare the observed action time with the intended window. A delayed action can still be acceptable if it stays within that window; an unexplained action outside it fails the test.
Repeat with a second sender or campaign only if your real workflow crosses that boundary. Check direct messages separately: Expandi says messages sent manually through its product use account active times by default, but it offers a switch to send them outside those times. A campaign schedule is therefore insufficient evidence about every manual send. Keep live recipients on hold when a scheduled action is hidden or when the vendor cannot explain which setting prevails.
- Pass: the governing time zone is named, the next action is visible, and the action remains within the intended local window.
- Investigate: the interface shows only an operator-local clock, or two campaigns share a sender with an unclear queue order.
- Hold: a test action fires outside the agreed window, or changing a displayed zone appears to be the only scheduling control.
Sources: Expandi activity schedule settings
For mixed regions, partition the work you can verify
When a tool documents one campaign window for several senders, a list spanning several regions needs a deliberate plan. Group prospects by the local hours you intend to respect, assign a campaign or manual owner to each group, and record the zone on that group. Do not infer a person's current time zone solely from a profile location; travel, remote work, and incomplete records make that a poor scheduling rule. If the product promises recipient-local timing, test the claim with two consented contacts in different regions before using it for real prospects.
A free workspace can help hold regional lists without settling the scheduling question. OutreachGenie's current pricing says its workspace is free with no product-side quota on invites, messages, visits, lists, or flows, while LinkedIn's limits still apply. Outreach Benchmarks and OutreachGenie share an owner. That pricing claim does not document recipient-local scheduling, so verify any sending behavior separately or use the workspace to organize a manual workflow.
Sources: HeyReach campaign working hours and time zone, OutreachGenie pricing and product limits
A suitable send window does not grant platform permission
LinkedIn says it does not permit third-party software that automates activity on its site and warns that accounts using prohibited tools risk restriction or shutdown. No choice of hours, random delay, or vendor limit establishes LinkedIn approval or removes that risk. If the account owner cannot accept it, send through LinkedIn manually during a reviewed window and keep the contact, owner, and next step in the team's own system. Revisit the scheduling tool only when both the policy decision and the clock test are explicit.