If your Sales Navigator InMails suddenly stop sending, it’s easy to assume LinkedIn restricted your account, but start with the simplest explanation: you may be out of InMail credits. In practice, most of these cases are normal product limits or a tooling issue, not enforcement. This guide gives you a 3-step diagnostic to tell whether you hit a commercial cap, a behavioral block, or a setup failure. The goal is to get you back to a stable outreach workflow without guessing.
Step 1: Check your InMail credit counter first
Open your Sales Navigator inbox and look for the credit counter. You’ll see it in the InMail compose experience or near the top-right of the messaging area. The exact placement shifts with LinkedIn UI updates, so if you don’t see it immediately, open a new InMail compose window from a prospect profile and look for a credits or allowance indicator. If the counter shows 0, you’ve hit the commercial cap. You’re out of credits until they refresh, or until you earn some back through replies.
How InMail credits work:
- Sales Navigator plans include a monthly allocation of InMail credits.
- Credits refresh on your billing cycle date.
- Some plans allow credit rollover up to a defined limit. Check your plan details or the LinkedIn Help Center for your exact rollover rules.
- LinkedIn returns a credit when the recipient replies to your InMail. Confirm this in your plan details or the LinkedIn Help Center, as policies can change.
Step 2: Run the manual parity test
The parity test compares native sending versus your automation to isolate platform issues from setup issues. If you still have credits but you’re seeing “send failed,” send one InMail manually inside Sales Navigator—not through automation or a third-party tool.
If the manual send also fails: You’re dealing with a platform-side constraint. That can be a commercial state you missed (credits, plan, or account prompts) or a behavioral block (next step).
If the manual send works but automation fails: This indicates a session or execution problem (expired session cookie, authentication prompt, configuration drift, or a UI change). In PhantomBuster, refresh your LinkedIn session cookie and re-run a small test batch.
Session friction is often an early warning, not an automatic ban. — PhantomBuster Product Expert, Brian Moran
Treat repeated re-auth prompts or unusual-activity banners as early signals to slow down and stabilize.
Step 3: Use the CAP, BLOCK, FAIL framework to diagnose the cause
Once you’ve checked credits and run the manual parity test, categorize the issue:
| Symptom | Diagnosis | What to do |
| Credit counter = 0 | CAP | Wait for renewal, earn credits back via replies, or use Open Profile (free messaging) |
| Credits > 0, but manual InMail still fails | BLOCK | Pause outreach for 24–48 hours, look for LinkedIn prompts or warnings, then restart with a steadier pattern |
| Credits > 0, manual works, automation fails | FAIL | Refresh your session, check the configuration, then re-test on a small sample |
CAP means you hit a product-level limit. The fix is operational: wait for credits to reset, earn credits back through replies, or route around the cap with another channel (for example, Open Profile (free messaging) or connection-first outreach).
BLOCK means LinkedIn’s systems are adding friction based on activity patterns. Watch for prompts like re-authentication, unusual activity warnings, or repeated failures despite available credits.
LinkedIn doesn’t behave like a simple counter. It reacts to patterns over time. — PhantomBuster Product Expert, Brian Moran
If LinkedIn shows a prompt (verification, re-auth, “unusual activity,” or a warning), treat that as a signal to slow down and stabilize your pattern.
FAIL means the workflow didn’t execute. Common causes: expired session cookie, MFA prompt, or UI changes. In PhantomBuster, reconnect your LinkedIn session and confirm the automation targets the correct page before retrying.
Safety note: Before you assume enforcement, separate the layers. Check credits, then run a one-message manual parity test. When teams report “throttling,” it maps to CAP, BLOCK, or FAIL.
What to do next
If CAP: Work around the credit limit
Prioritize Open Profile (free messaging) where available, pivot to connection requests plus follow-ups after acceptance, or wait for your credits to refresh. If you want credits back sooner, focus on prospects with clear intent and a reason to reply.
If BLOCK: Pause and stabilize your pattern
Pause for 24–48 hours to let rate-limit counters cool and resolve prompts. Review LinkedIn for prompts or warnings. Look for recent pattern changes: sudden spikes, repeated actions, or running multiple high-velocity activities at once. When you resume, ramp gradually and avoid sudden spikes. Increase daily sends by 10–15% every 2–3 days while monitoring prompts. Example: 20 → 22 → 25 → 28, holding steady if you see re-auth prompts. Keep your outreach focused on relevance, not throughput.
Avoid slide and spike patterns. Gradual ramps outperform sudden jumps. — PhantomBuster Product Expert, Brian Moran
If FAIL: Troubleshoot your session and configuration
In PhantomBuster, reconnect your LinkedIn session cookie (Accounts > Reconnect), verify your automation’s input selectors match the current UI, then test on 10–20 profiles. If it persists, contact PhantomBuster Support with the automation name, run time, error text, and a screenshot/URL of the page. Switch to a connection-first workflow.
PhantomBuster Automations let you sequence connection requests and timed follow-ups in one place, so you keep outreach moving without InMail credits. You control targeting and messaging; PhantomBuster Automations handle the scheduling and sending so you can focus on relevance and replies.
Conclusion
Most InMail “throttling” is a credit cap or an execution issue, not a hidden penalty. Use CAP, BLOCK, FAIL to keep the diagnosis clean. Check your credit counter first. If credits are available, run the manual parity test. Then take the next step based on the bucket you’re in. Use CAP, BLOCK, FAIL to resolve most send failures in minutes and keep your outreach calendar predictable.
Next: Set up a connection-first sequence in PhantomBuster Automations and start with a 20–30 per day ramp to maintain steady outreach while you wait for credits to refresh.
Frequently asked questions
How can I tell if Sales Navigator InMail “send failed” is a credit cap or a real LinkedIn restriction?
Start by checking your Sales Navigator InMail credit balance, then run a one-message manual parity test. If credits are at zero, it’s a commercial cap (CAP). If a manual InMail also fails and LinkedIn shows prompts or warnings, it may be a behavioral block (BLOCK). If manual works but automation fails, it’s FAIL.
Where do I check my Sales Navigator InMail credit counter?
You’ll see remaining InMail credits in the Sales Navigator messaging or InMail compose experience, often near the top-right of the inbox or compose panel. Placement changes with LinkedIn UI updates. If you don’t see it, open a new InMail compose window from a prospect profile and look for a credits or allowance indicator.
What does CAP, BLOCK, FAIL mean for Sales Navigator InMail problems?
CAP, BLOCK, FAIL is a triage framework. CAP = commercial caps (credits). BLOCK = behavioral enforcement. FAIL = automation or execution failure. Once you identify the bucket, the fix is clearer: adjust workflow or wait for credits, pause and stabilize behavior, or troubleshoot your session and tooling.
What are the visible signs of a behavioral block (BLOCK) vs. a credit cap (CAP)?
CAP shows an explicit “out of credits” state or a visible counter hitting zero. BLOCK comes with prompts or friction, like forced re-authentication, unusual activity warnings, verification requests, or repeated send failures even when credits remain.
If I still have InMail credits but sending fails, what should I do first?
Run the manual parity test: send one InMail manually in Sales Navigator, not through any tool. If manual fails too, look for LinkedIn prompts or warnings (possible BLOCK) or a plan or credit state you missed (CAP). If manual succeeds, troubleshoot FAIL—session expiry, authentication prompts, or UI drift.
Can LinkedIn “silently throttle” InMails so they look sent but don’t deliver?
PhantomBuster hasn’t observed reliable evidence that LinkedIn routinely blocks InMails in the native UI without any prompt or visible state. When teams report “silent throttling,” it’s an execution failure (FAIL) caused by UI drift, surface variance, or incomplete error handling. Verify by following these steps: 1. Open the conversation in Sales Navigator and confirm the status badge (Sent/Delivered/Responded). 2. Send a manual follow-up to the same profile to confirm send capability. 3. Check for prompts or warnings in the UI and your email inbox for LinkedIn notices.
How do I keep outreach moving if I’m out of InMail credits (CAP)?
Pivot to channels that don’t consume InMail credits. Prioritize Open Profile (free messaging) where available and connection-first outreach with follow-ups after acceptance. If your plan returns credits on replies, focus on prospects with a clear reason to respond.
How can I reduce the chances of triggering a real LinkedIn block when scaling messaging?
Manage patterns, not “magic limits.” Enforcement is pattern-based: sudden spikes, repetitive actions, and combining multiple high-velocity activities at once tend to create friction. A more reliable approach is to automate LinkedIn outreach without getting penalized by building the workflow first, then ramp volume gradually while watching for early signals like repeated re-auth prompts or verification flows.