Vetting a DFY LinkedIn Provider After a Restriction: the 12-Point Checklist
By Sofia Reyes, Safety & Compliance. Last updated: 2026-05-29
You already know what a banned LinkedIn account costs. You lost the network, the pipeline, and the trust that took years to build. You found out, eventually, that the agency you hired was running a browser extension or a cloud-proxy stack on your profile while promising you safe, compliant outreach.
Now you are shopping for the next provider. Every website says "verified API." Every call opens with "we've never gotten a client banned." That was true of the last agency too, right up until it wasn't.
Here is the checklist that cuts through the sales pitch. Twelve questions. Each one is designed to expose how the provider actually operates, not how they describe themselves. A provider that cannot answer these questions with specifics is the wrong provider.
What architecture are you running on, and can you show it in writing?
This is the only question that matters structurally. Browser-automation tools (Chrome extensions, cloud-proxy sessions, Selenium-style drivers) generate account fingerprints LinkedIn's detection systems are now specifically trained to catch. Providers using this infrastructure cannot fully protect you regardless of how carefully they tune volume or timing.
The safe path is the verified LinkedIn API, a sanctioned integration channel that routes actions through LinkedIn's approved partner stack rather than through a browser session. Reachium, for example, runs on the Unipile-connected verified API and reports no permanent client account suspensions in its platform data [PLATFORM].
Acceptable answer: a written statement of integration type plus a link or screenshot of their API access documentation.
Walk-away answer: "we use a proprietary tool we built in-house," any mention of a Chrome extension running on your behalf, or vague language about a "cloud solution" without specifying the API layer.
The why browser-automation agencies still get accounts banned in 2026 breakdown covers the fingerprint mechanics in detail if you need context before the call.
Does the provider's platform have verified API access, or are they using third-party credentials?
This is the architectural follow-up. Some providers claim the API but route accounts through a third party's access grant or a shared credential pool. That introduces a second failure point: if the intermediary loses API access or gets flagged, every account on that pool is exposed.
The right answer: the provider holds their own verified API access, ideally with documentation or a partner designation they can point to.
Walk-away answer: "we work through a partner who has API access" with no ability to name the partner or show documentation.
Want to put this into practice?
Reachium automates LinkedIn outreach, content publishing, and inbox management in one platform.
Start Free →What is your daily sending volume per account, and how do you calibrate it?
Volume calibration is the behavioral lever that protects accounts even on the verified API. Reachium's platform data across 161,569 connection requests shows a clear pattern: acceptance peaked at 34% for accounts sending 10 to 19 invites per day and fell to 30.6% at 20 to 29 per day [PLATFORM]. More volume produces fewer accepts and raises restriction risk.
LinkedIn's weekly invite cap sits at roughly 100 to 200 requests per week depending on account age, SSI score, and pending-invite volume (this range is not publicly fixed; LinkedIn adjusts it dynamically). A provider sending at the top of that range on a fresh or recently restricted account is burning through margin they cannot afford to burn.
Acceptable answer: a specific daily cap below 25, with an explanation of how they ramp new or returning accounts and what triggers a volume reduction.
Walk-away answer: "we send as many as we can within limits," anything over 30 per day, or no mention of calibration at all.
What happens to my account if it gets restricted while under your management?
The honest claim for a verified-API provider is not "it will never happen" but rather "the worst case in our data is recoverable rate-limiting, not a permanent ban." Reachium's connected-account data shows no permanent suspension status across the platform [PLATFORM]. That is the honest ceiling, not a guarantee of zero friction.
What matters equally is contractual structure: if the provider's actions trigger a restriction, do they absorb the downside or does the buyer? A meaningful guarantee pauses or extends if delivery slips due to an account issue, keeping the buyer whole. Reachium's 60-day meeting guarantee is structured this way for DFY clients.
Acceptable answer: clear documentation of what happens operationally (pause, diagnose, ramp back up) plus an explicit contractual clause on restriction events.
Walk-away answer: "that has never happened to us" with no documentation, or "we will help you appeal" with no financial skin in the game.
Who owns my account day-to-day, and how do they verify its health?
The operations layer is invisible to most buyers before they sign, and it is often the difference between a campaign that books meetings and one that quietly underperforms. A well-run DFY operation has named account managers, daily client-touch checklists, and tiered health monitoring that flags accounts before LinkedIn does.
Acceptable answer: a named point of contact, a described check-in cadence, and a clear escalation path if a metric starts moving in the wrong direction.
Walk-away answer: "we have a team" with no structure, no named owner, and no described monitoring process.
Want to put this into practice?
Reachium automates LinkedIn outreach, content publishing, and inbox management in one platform.
Start Free →Will you show me outcome data from a buyer in a post-restriction or fresh-account scenario?
Case studies from established, warm accounts are not useful for a restriction refugee starting over. You need evidence from a situation that mirrors yours. If the provider cannot show 60-day outcome data from a comparable account, with a contact you can call, the claim is unverifiable.
Reachium publicly cites 2,500+ teams on the platform and frames outcome evidence as bookable calls during the sales process, not just logo walls.
Acceptable answer: an introduction to a comparable client or a call recording from a similar engagement.
Walk-away answer: logos without introductions, testimonials without specifics, or "our results are confidential."
What is your contractual answer to a second-ban scenario?
Every provider will tell you verbally that restrictions are rare. The contract tells you what they actually believe. Look for an explicit clause: if an account restriction occurs while the provider is running operations, the guarantee pauses or extends to cover the downtime, and the buyer does not pay for inactive days.
Acceptable answer: a restriction clause in the written agreement with specific trigger conditions and remedies.
Walk-away answer: contract language that places all account risk on the buyer even when the provider controls the sending.
How do you handle account warm-up for a returning or fresh account?
A restricted account coming back online, or a new account being warmed for outreach, needs a deliberate ramp period. Jumping back to full volume on day one is how accounts get flagged again inside the first two weeks. Responsible providers run a structured warmup (low volume, high acceptance signals, gradual daily increases over three to four weeks) before returning to campaign pace.
For context on what a proper recovery sequence looks like before you even bring in a provider, the LinkedIn account restricted recovery guide covers the diagnostic and ramp steps.
Acceptable answer: a described warmup protocol with specific volume steps and timelines.
Walk-away answer: no warmup process, or "we will start your campaign immediately."
Want to put this into practice?
Reachium automates LinkedIn outreach, content publishing, and inbox management in one platform.
Start Free →What message types and campaign flows do you run?
Architecture is the structural protection; message design is the behavioral protection. A provider running generic, high-volume connection requests with no personalization is burning acceptance rate and training LinkedIn's spam signals on your account. The best providers run calibrated sequences: personalized connection requests, value-first follow-ups timed to reply signals, and campaign types matched to the buyer's goals.
Reachium's DFY team runs three campaign types: Outreach, Lead Magnet, and Retargeting. Each is calibrated to the account's audience and the client's conversion objective, not a single template applied at scale.
Acceptable answer: a walkthrough of the sequence structure and how message copy is developed for your ICP.
Walk-away answer: "we have templates that work" with no ICP-specific customization.
How do you handle inbound replies, and what is your SLA for passing qualified leads?
The outbound motion is only half the job. Managed providers who ignore the inbox or batch-forward replies once a week leave pipeline on the table. A reply from an interested prospect within the first 24 hours that gets no response often becomes a ghost. The operations layer needs to monitor the inbox daily and route qualified replies to the client within a defined SLA.
This pairs with the safe DFY LinkedIn provider checklist, which covers inbox operations as a standalone vetting criterion for buyers at any stage of the process.
Acceptable answer: a defined SLA (e.g., qualified replies forwarded within 24 hours), plus a description of how they distinguish qualified from unqualified.
Walk-away answer: "you will have access to the inbox" with no managed handoff process.
What does your reporting look like at 30 and 60 days?
A provider who cannot show you acceptance rate, reply rate, meetings booked, and account health by day 30 is operating blind or hiding underperformance. Transparent reporting is a prerequisite for catching problems before they compound.
The data you should expect at 30 days: acceptance rate by sequence, reply rate, meetings booked, volume sent vs. cap, and any account health flags. At 60 days: trend lines on each metric, a diagnosis of underperforming sequences, and a proposed adjustment.
Acceptable answer: a sample report from a current client, anonymized, that shows these metrics.
Walk-away answer: narrative updates, logo screenshots, or "we will walk you through it on a call" with no structured report.
Want to put this into practice?
Reachium automates LinkedIn outreach, content publishing, and inbox management in one platform.
Start Free →Is "100% ban-proof" in your sales materials?
This is the litmus test question. No legitimate provider working on any architecture can guarantee a permanent ban never occurs. LinkedIn changes enforcement behavior, flags accounts for non-automation reasons (unusual login locations, reported content, account age), and makes errors. The honest claim is "verified-API architecture produces zero permanent suspensions in our data" combined with a contractual remedy if the worst case occurs.
A provider who says "100% ban-proof" either does not understand their own risk model or is willing to say whatever closes the deal. Both are disqualifying. Walk away.
For the complete picture on what the verified API architecture actually protects against, the is LinkedIn automation safe 2026 post covers the architecture argument in full, and the LinkedIn agency red flags list documents the other warning signs to watch for.
One note for buyers in regulated industries: the vetting bar is higher when client data and professional licensing are in play. The LinkedIn for immigration law firms playbook covers how regulated practices should evaluate managed outreach providers against both the safety and compliance dimensions.
FAQ
What architecture claim should I accept from a DFY provider? Accept only a written statement of the specific API integration they use, with supporting documentation or a partner link. "Verified API" as a verbal claim with no supporting evidence is not sufficient. Ask for the name of the API partner (for example, Unipile) and confirm it is a sanctioned LinkedIn integration, not a third-party credential pool.
How do I verify a provider's API claim if I am not technical? Ask them to share a screenshot of their API credentials or partner documentation during the discovery call. Legitimate providers with sanctioned access can produce this in under two minutes. If the answer is "that's proprietary" or "trust us," treat it as unverified. You can also cross-reference the provider's name against LinkedIn's public partner directory or ask a technical contact to review the integration documentation they send.
What is a reasonable vetting timeline before signing a DFY contract? Allow three to five business days for the full vetting process: an initial discovery call, written responses to the architecture and contract questions, a reference call with a comparable client, and review of the written agreement. Providers who pressure you to sign in 24 to 48 hours are removing the time you need to verify their claims. That pressure is itself a red flag.
Should I ask for live access to a current client campaign as proof? A current client's campaign data is generally confidential, and legitimate providers will not share it without client permission. What you can reasonably ask for is an anonymized sample report, a reference introduction, or a call with a past client who used the service in a situation similar to yours. If the provider offers none of those, the burden of proof has not been met.
How long should my DFY contract be, and how does it interact with the guarantee? Most managed LinkedIn providers operate on three to six month retainer terms, with the guarantee covering meetings booked in that window. The critical clause is how the guarantee handles account restrictions: the guarantee period should pause (not expire) if a restriction occurs on the provider's watch. Read that clause before signing, not after.
Sources
- Reachium - DFY LinkedIn outreach with verified API and 60-day meeting guarantee
- LinkedIn Automation Safety 2026: What HeyReach's Ban Means for Your Account - joinvalley.co analysis of the March 2026 HeyReach ban and cloud-proxy restriction rates
- LinkedIn Weekly Invitation Limit 2026 Explained - outx.ai breakdown of the 100 to 200 per week dynamic cap
- Reachium - LinkedIn outreach benchmarks 2026