The best time to send LinkedIn connection requests, according to the published guidance, is Tuesday through Thursday, mid-morning on the recipient’s clock, with a secondary window in the early afternoon. Hold that default loosely. The same guides have trained thousands of senders to fire in the same windows, and a request triggered by something the prospect actually did, a post, a job change, an event, beats any hour you could pick off a chart.
That caveat comes from sending at volume, not from contrarianism. Our parent agency, Referral Program Pros, has run more than 4,000 outbound campaigns and booked over 7,000 meetings for B2B clients, and GTM Bud is built on the playbook that agency runs daily, backed by a written guarantee: 5 percent positive replies on LinkedIn, 1.5 percent on email, or a full refund. Across those campaigns, send-time tweaks have moved results at the margin, while trigger-based targeting and steady daily volume have moved them materially. This article gives you the published windows, the reasons to trust them less than their authors do, and the timing signals that actually earn the accept.
What is the best time to send LinkedIn connection requests?
The best time to send LinkedIn connection requests, according to the published guidance, is Tuesday through Thursday, mid-morning in the recipient’s time zone. PhantomBuster’s guide recommends 8:30 to 10:30am or 2 to 4pm on the recipient’s clock, while Bardeen’s answer page points to 10 to 11am and 5 to 6pm on the same midweek days. Monday mornings and Friday afternoons are the most commonly named windows to avoid. Treat those hours as a reasonable default, not a proven rule: none of the vendors publish the underlying data, and the windows disagree with each other more than they admit. The stronger timing signal is a recipient-relevant moment. A request sent because the prospect just published a post, changed jobs, or registered for the same event outperforms any fixed window, because it arrives with a reason attached. Set the default window once, then build your campaigns around moments.
That is the compressed answer. The rest of this article unpacks the sources behind those windows, why the consensus is weaker than it looks, and what to schedule instead.
What do the published timing guides actually recommend?
Mid-week and daytime, with the specifics varying by vendor. Here is how the most-cited guidance on connection request timing compares:
| Source | Recommended days | Windows, recipient’s clock | The rest of the advice |
|---|---|---|---|
| PhantomBuster’s timing guide | Tuesday to Thursday | 8:30 to 10:30am, or 2 to 4pm | Avoid Monday mornings and Friday afternoons; warm the prospect up by liking a post a few hours beforehand |
| Bardeen’s answer page | Tuesday to Thursday | 10 to 11am, and 5 to 6pm | Attributes the windows to unnamed studies |
| GetFuzzy’s best-practices piece | No fixed day promoted | None promoted | Argues the consensus window has become the noisiest moment in a prospect’s notifications |
| Sales Gravy’s prospecting guide | Any day with a trigger | No fixed hours | Names six moments when requests work, such as the weeks before an event or right after a strong call |
Read that table with the right level of trust. The two vendors that give hours disagree with each other, neither publishes the dataset behind its numbers, and the overlap between them reduces to something unexciting: midweek, during the recipient’s waking hours, not Monday morning, not Friday afternoon. That overlap is worth configuring. It is not worth optimizing.
The warm-up sequence deserves a separate note, because it is the one piece of vendor timing advice with a mechanism behind it. The pattern, recommended by PhantomBuster among others, is to visit the profile and like a recent post a few hours before the request, so your name is faintly familiar when the invitation arrives. Done by hand for a shortlist of real targets, it works. Scripted across a whole list, it becomes the same herd behavior as the 10am Tuesday send: recipients who get prospected regularly now recognize the visit-like-invite choreography on sight.
Why the consensus window is now the noisiest
Because everyone reads the same advice. GetFuzzy’s best-practices piece makes the point directly: when every SDR, founder, and recruiter schedules for the same midweek mid-morning, that window becomes the most crowded moment in a prospect’s notification tray, and whatever edge it once carried gets competed away. Timing guidance is self-defeating in a way list quality and message quality are not. A better list stays better when your competitors copy the tactic. A better hour stops being better the moment they do.
Cold email went through the same cycle, and the parallel is instructive. The midweek morning consensus there rests on far more published data, including HubSpot’s survey of more than 150 marketers, where Tuesday was the most-cited best day at 27 percent, and even with that stronger evidence base, the measured gap between the best and worst weekday is small next to the gap between average and great targeting. We walk through that full dataset in our guide to the best time to send cold emails, and the conclusion transfers cleanly: the window is a default to configure, not a dial to keep turning.
LinkedIn adds one more reason the clock matters less here than in email. An email competes for attention in the minute it lands, then sinks. A connection request sits in the invitations tab until the recipient deals with it, and most people clear that tab in batches whenever they happen to open the app. Your send time barely decides when the request is seen. It mostly decides which other requests it is sitting next to when it is.
Why do recipient moments beat clock-based timing?
Recipient moments beat clock-based timing because a moment gives the request a reason to exist, while a clock only gives it a delivery slot. When a prospect publishes a post, starts a new role, comments on a topic you work in, or registers for an event you will attend, a connection request arrives as a natural next step instead of an interruption. Sales Gravy’s prospecting guidance makes the same argument from the field: it lists moments, like the weeks before an event or the hour after a good call, as the times connection requests actually work, with no fixed hour anywhere in the list. Across our own agency campaigns, the pattern holds qualitatively. Requests tied to a trigger convert noticeably better than requests tied to a schedule, and they keep converting after the popular windows get crowded. The clock decides when a request is seen. The moment decides whether it is welcome.
The moments worth building campaigns around:
- They posted or commented in the last few days. An active profile means the invitations tab gets checked, and recent content gives the eventual conversation a genuine opening.
- They changed jobs in the last quarter. New role, new priorities, new vendor decisions, and a window where connecting reads as congratulation rather than cold approach.
- They are attending or speaking at the same event. Sales Gravy’s advice is to connect in the weeks before, when the shared context is forward-looking, not after the fact.
- They engaged with a competitor, a peer, or a topic in your category. Interest in the problem is the strongest pre-qualification a free signal can give you.
This is signal-based outreach applied to a single send decision, and the broader framework is in our guide to what signal-based outreach is. Once a moment puts a prospect in the queue, the request still has to clear two older questions: whether to attach a note at all, which we settle in note or no note, and what the note should say when you spend one, covered in how to write LinkedIn connection messages.
Consistency beats precision
Consistency matters more than precision because LinkedIn’s invite allowance is a weekly budget, and an unspent budget is the most expensive timing mistake available. A sender who spreads requests across every sending day, inside sensible daytime windows on the recipient’s clock, reaches the full weekly allowance with low daily volume and a human-looking pattern. A sender who chases the perfect Tuesday hour tends to burst, skip days, and finish the week under budget. Across the campaigns our agency runs, steady daily sending with randomized gaps is the configuration that compounds: the same list, the same copy, and the same windows produce more accepted connections per month simply because more requests actually go out. Pick daytime windows, spread the sends, keep the cadence through the whole week, and let the published peak hours remain a tiebreaker rather than a strategy.
The mechanics of that weekly budget, and how hard you can push it by account age and tier, are in LinkedIn connection request limits, explained. And judge the output against numbers, not feel: the operating targets our agency runs are 30 percent acceptance minimum, 35 percent solid, 40 percent great, and the full set of bands lives in our LinkedIn outreach benchmarks. A campaign accepting below that range has a targeting or profile problem, and no send-time change will paper over it.
Timing is configuration. Set the windows once, spend your optimization hours on the list and the trigger, and let the schedule run.
How to put connection request timing on autopilot
Everything this article recommends is schedulable. Daytime windows on the recipient’s clock, sends spread across all seven days with randomized gaps, pending requests withdrawn on a schedule, and campaigns pointed at profiles with recent activity so more requests land near a real moment: all of it is configuration, and configuration is what software is for.
That is how GTM Bud treats it. Campaigns send connection requests inside daytime windows in the recipient’s time zone by default, pace them with human-looking spacing across the week, and prioritize active profiles, which is the closest thing to moment-based timing that runs without a human watching feeds all day. If you are still choosing tooling, our rundown of the best LinkedIn automation tools compares which schedulers respect recipient time zones and which just fire on yours.
Frequently asked questions about LinkedIn connection request timing
Should I send LinkedIn connection requests on weekends?
Yes, as part of the weekly spread rather than as a special play. Requests sit in the invitations tab until the recipient next opens the app, so a Saturday send is simply read whenever they return, often Monday. The real argument for weekend sending is budget math: spreading the weekly invite allowance across seven days keeps daily volume lower and more human-looking, and it is often the difference between finishing the week at full volume or under it.
Does the best time to send connection requests change by seniority or role?
At the margins. In our agency campaigns, executives and founders tend to check LinkedIn at the edges of the workday and on weekends, while individual contributors skew toward working hours. No published dataset settles this, so treat role-based timing as a hypothesis: after a few hundred sends per segment, read your own acceptance timing and shift the windows toward where the accepts actually happen.
Is it better to send connection requests in one burst or spread through the day?
Spread them, always. A burst of invitations at a single timestamp is the signature of a script, both to LinkedIn and to any prospect who notices the pattern, and burst behavior is a known trigger for account restrictions. Dripping requests across a daytime window with randomized gaps looks like a person using the platform, protects the account, and costs nothing, since no study shows a burst outperforming a spread.
When should I send the first message after someone accepts my request?
Within a day, on a human delay. The moment of acceptance is the warmest the thread will ever be: you are briefly visible in their notifications and the context of the request is still fresh. Waiting a week squanders that window, while messaging within seconds of the accept reads as automated. A LinkedIn DM automation layer that detects the accept and queues the first message after a short natural gap captures the warmth without the robot tell.
Should I withdraw connection requests that sit pending too long?
Yes, on a schedule. We clear pending invitations after three to four weeks, because a large pile of ignored requests signals weak targeting and keeps those invite slots tied up. Withdraw deliberately, though: LinkedIn blocks you from re-inviting the same person for up to three weeks after a withdrawal, a restriction we cover alongside the weekly caps in our limits guide, so only withdraw requests you do not plan to retry soon.
Set the window once, then sell to moments
The best time to send LinkedIn connection requests is the midweek daytime default every guide quotes, and the honest version of that answer is that it buys a little less every year, because the whole market is reading the same guides. What compounds instead is the system around the send: requests spread across the full week in recipient-time daytime windows, pointed at prospects in the middle of a real moment, with the first message landing while the accept is still warm.
If you would rather not run that system by hand, LinkedIn outreach automation from GTM Bud schedules every request inside recipient-relevant windows, paces the week automatically, and times the follow-up message where the real conversation starts. Setup takes about 15 minutes, it runs on your own LinkedIn account, and it carries the same written guarantee as our agency work: 5 percent positive replies on LinkedIn or a full refund. The clock is a default. The moment is the strategy.