Fix sheet: Account was restricted in the last 90 days

This sheet appended when your report flagged the `restricted` weakness.

What just happened to your account

A LinkedIn restriction marks the account in LinkedIn's internal risk model. The first restriction is typically 24-72 hours and feels like a warning. The second one — within 90 days of the first — is usually 7 to 30 days, sometimes permanent. The third is almost always permanent.

The interval between restrictions shrinks each time. If your account just came off restriction, the next one comes faster, lasts longer, and is more likely to be permanent.

The 3 things to do THIS WEEK

Stop outbound from that account for at least 14 days. Continuing to run volume from a recently-restricted account is the single most expensive thing you can do — every accepted request right now is a request the algorithm is watching. Pause; the pipeline pause is cheaper than losing the account permanently.

Provision a backup account NOW, before you need it. A new account takes 4-6 weeks of warmup before it can run real outbound. Most teams provision the backup after the first 30-day restriction, which means the backup is not ready when the second restriction hits. Start it now.

Audit what triggered it. Common causes, in order: (a) volume spike — sending 40+ requests on a single day after weeks of 10; (b) acceptance crash — letting acceptance dip below 10% for a week; (c) duplicate templates — sending the exact same string to >100 people in a week; (d) automation tool fingerprint. Fix the root cause before you resume.

What "fixed" looks like

The account stays restriction-free for 6+ months. New requests stay under 15/day for the first 30 days post-restriction, acceptance recovers to 25%+ in week 2-3, no third restriction occurs.

How BIGM solves it

We provision and warm 4-6 aged accounts on day 1 for every tenant, specifically so a single restriction is invisible to your pipeline. When one gets flagged, traffic routes through the others while it heals; you do not even see the disruption. This is what "managed outbound" actually means.