2 min read

Slow on purpose: why agaria paces LinkedIn outreach

How queued LinkedIn actions, daily limits and your browser connection determine the pace of an automated sequence.

The question we hear first after someone connects a LinkedIn account is why agaria will not send more. The short answer is that the account is yours, and a restricted account costs you more than a slow week ever will. The long answer is below.

Your browser, your account

agaria never logs in to LinkedIn from a server. Every connection request, message, profile view and follow runs inside your own Chrome, through the agaria extension, in the session you already have open. LinkedIn sees the browser it always sees, on the network it always sees, signed in as you.

That rules out the two things that get accounts flagged fastest: a login from a data center, and a burst of activity no person could produce. It also means outreach pauses when your laptop is closed. The extension needs Chrome, Edge, Brave or Arc on a laptop or desktop, and it carries on where it stopped when you are back.

A pause between every step

Actions go out one at a time from a queue. On each page the extension waits a few seconds between steps, and the wait is varied every time, the way a person browsing would behave. Nothing is fired in one burst.

If LinkedIn puts up a checkpoint, a login wall or a captcha, the extension reports the action as blocked and does not keep pushing. You see it in the campaign, and nothing else goes out until the account is clear.

Daily action limits

Connection requests and LinkedIn messages have daily limits. When a limit is reached, the remaining actions stay queued for the next day. Keep the browser and extension connected so scheduled actions can run.

LinkedIn connection requests and messages pause when their daily limit is reached. Illustrative data.

Use the campaign’s daily send limit to control its pace. Plan comparisons focus on lead and campaign allowances; check pricing for those limits.

Why slow wins

Outreach is a numbers game only when the numbers are replies. Twenty well-chosen connection requests a day, every working day, from an account in good standing, adds up to hundreds of new contacts a month. A thousand requests in a week from a flagged account adds up to a support ticket with LinkedIn and a campaign that stopped on day three.

agaria picks the first kind of number. If outreach is producing few replies, review the audience and messages before increasing volume. The post on how agaria picks who to contact covers that side.