If LinkedIn shows a phone or ID verification screen, treat it like a temporary access issue, not a catastrophe. The goal is to restore access through the official flow, then remove whatever pattern triggered the prompt. When automated verification works, it completes in minutes. When it fails, submit a single manual appeal and pause unusual activity until access is restored. Plan for several business days on manual review.
This guide covers why verification happens, what to do first, how to complete verification, how to escalate if verification fails, and how to reduce the chance of a repeat prompt.
Why did LinkedIn trigger verification on your account?
What triggers a phone or ID verification prompt?
LinkedIn flags pattern changes—sudden spikes, stacked workflows, or unusual logins—relative to your historical behavior baseline. LinkedIn evaluates patterns over time, not one-off counts. Our product team sees this pattern across recoveries: accounts respond differently based on their history, so a sudden jump in activity is riskier than steady volume. Examples of behavior changes that trigger flags:
- Rapid activity spikes after a quieter period
- Unusual login locations or devices
- Multiple workflows running at the same time
- Timing or repetition that deviates sharply from your normal usage
LinkedIn compares your recent behavior to your historical behavior baseline—your typical timing, volume, and device patterns. Accounts respond differently based on this history, so evaluate changes against each account’s baseline before increasing volume.
Where does verification fit in LinkedIn’s enforcement sequence?
Treat verification as a mid-stage response. Expect this progression:
- Session friction: Forced logouts, cookie expiry, extra logins.
- Warning prompts: “Unusual activity detected”.
- Identity checks: Phone or ID verification.
- Stronger limits: Lower send limits, temporary feature restrictions, or—after repeat flags—permanent account restriction.
Complete verification first. Retrying actions, repeated reconnects, or creating a new profile adds risk and can prolong the restriction.
Verification is recoverable. Treat it as a stop signal: pause unusual activity until access is fully restored.
What should you avoid right now?
What mistakes escalate a temporary flag?
- Avoid creating a new LinkedIn account: LinkedIn can interpret this as evasion and restrict both profiles.
- Avoid retrying automation or reconnecting sessions repeatedly: That creates more anomalies while your account is already under review.
- Don‘t ignore the verification prompt: Your access won’t return until you complete verification or submit an appeal.
- Don‘t submit multiple tickets for the same issue: One clear case with the right attachments tends to move faster than a flood of requests.
If you’re running any LinkedIn automation, pause it now. Wait until verification is complete and you can access the account normally again before you reconnect anything. Pause all scheduled Automations in the PhantomBuster dashboard to prevent new runs while your session is under review. This freezes activity across your workspace and avoids additional anomalies.
Step-by-step: How do you complete LinkedIn verification?
Phase 1: Complete verification in the mobile app
- Prepare your ID: Use a valid government-issued ID, such as a passport, driver’s license, or national ID. Some verification flows require an NFC-enabled passport, which has a chip symbol on the cover.
- Start in the LinkedIn mobile app: LinkedIn routes most identity checks to mobile and the flow is designed for it. If LinkedIn shows a QR code on desktop, scan it and continue on your phone.
Follow the verification sequence:
- Take a clear photo of the front and back of your ID, if requested. Avoid glare and blur.
- If prompted, scan the NFC chip by holding your phone against the passport cover and moving slowly until it reads.
- Take a selfie so LinkedIn can match your face to the ID.
Phase 2: Fix common verification failures
- Update the LinkedIn app: Outdated apps are a common cause of verification errors.
- Check NFC setup: Remove your phone case, then move the phone slowly over the passport cover. Different phones read the chip in slightly different spots.
- Try a different browser: If you use desktop, test another browser or a private browsing window to avoid cache and cookie conflicts.
- Control lighting: Use natural, indirect light to reduce glare, especially on plastic IDs.
| Error or symptom | Likely cause | What to do |
| “Something unexpected happened” | App or browser issues | Update the app, then retry. If on desktop, use a private browsing window. |
| NFC scan fails | Phone case or poor chip alignment | Remove the case, then move the phone slowly across the passport cover. |
| ID photo rejected | Glare, blur, or cropped text | Retake in indirect light and keep all edges and text visible. |
| Verification page won’t load | Cache or cookie conflicts | Clear cache, switch browser, or use a private browsing window. |
What should you do if automated verification fails?
Phase 3: Manual appeal process
If automated verification fails, submit a manual appeal. Don’t create a new account—that adds risk and can trigger broader restrictions. Direct support links:
- Identity verification appeal
- General account access
What to write in your appeal:
- Subject: Unable to complete identity verification — [Full Name]
- Description: Unable to complete identity verification due to [exact error]. Requesting manual review. Attached: clear images of a government-issued ID (front and back if applicable).
- Attachment: Clear photo of your ID, front and back if applicable
Tip: Keep it simple and provide clear documentation.
Phase 4: Public escalation when support is unresponsive
If you don’t get a response within 3 to 5 business days, escalate once with your ticket number. Escalate once via @LinkedInHelp with your ticket number. This reaches a separate support channel and can prompt a response on stalled tickets.
Example: “@LinkedInHelp My account is restricted and the ID verification tool is failing. I submitted ticket #[Number] and haven’t heard back. Can you help?”
Recovery checklist: What should you do after verification completes?
Immediate actions after LinkedIn restores access
- Don‘t resume outreach at prior maximums on day one: Start at 20–30% of your previous daily actions. After a flag, LinkedIn watches the account more closely for a period.
- Update your session cookie once: If you use PhantomBuster, update your LinkedIn session cookie once in the dashboard (Account → Cookies), then stop. This refresh prevents login loops without creating new anomalies.
- Review what changed: Look for volume spikes, stacked workflows, unusual sending hours, or device and location changes.
How should you ramp activity back up?
Start at 20–30% of your prior daily activity and ramp over 1–2 weeks. Our product team observes that warm-up is about building believable behavior, not chasing limits.
- Spread actions across normal work sessions: Avoid bursts. Consistent pacing is easier to defend and easier to troubleshoot.
- Avoid parallel runs: In PhantomBuster, chain Automations (e.g., profile visit → connection request) with scheduled gaps instead of running them simultaneously.
- Watch for early warning signals: If you see forced logouts, cookie expiry, or warning prompts, pause and reduce activity.
Post-recovery should look like a warm-up period. You’re rebuilding a predictable pattern, not trying to “make up” for lost time.
Keep in mind: When in doubt, choose predictability over speed. It’s easier to keep an account healthy than to recover it repeatedly.
Conclusion
Treat phone/ID verification as a serious signal—and a recoverable one when you follow the official flow. Complete the official verification process, avoid extra anomalies while you’re restricted, and escalate through a single appeal if the automated system fails. Once access is restored, ramp back up gradually and remove the behavior patterns that caused the mismatch in the first place. That’s the difference between a one-off interruption and repeated restrictions.
Use PhantomBuster schedules to spread actions across your normal work hours, and set conservative daily caps until the account remains stable for 7–14 days. One workflow at a time, steady pacing, and clear intent for each action you run. If you use PhantomBuster, set conservative schedules, avoid parallel LinkedIn Automations, and update your session cookie once after recovery. Use the dashboard to pause and resume safely without creating additional flags.
FAQ: LinkedIn phone and ID verification recovery
Why did LinkedIn ask for verification if I wasn’t using automation?
Verification can follow unusual logins, device changes, travel, or account security events. LinkedIn reacts to patterns, not just automation.
How long does verification take?
Automated verification completes in minutes. Manual appeals typically require several business days; plan your outreach schedule accordingly.
Will my account be fully restored after verification?
Yes—verification restores access. Repeat flags or policy issues can extend or harden restrictions.
Should you create a new account if you can’t recover quickly?
No. A new profile created during a restriction can look like evasion. A safer path is to complete verification or submit a single, well-documented appeal.
Which verification provider does LinkedIn use, and does it change the approach?
LinkedIn uses different identity providers depending on region and device. Your approach doesn’t change: follow the in-app prompts, then appeal if the flow fails.
How do you tell whether automation contributed to the flag?
Focus on pattern changes—spikes, parallel runs, and compressed windows—rather than blaming a single tool. Look for a sharp increase in actions, multiple workflows running at once, or activity compressed into short windows.
My tool says actions ran, but I don’t see results. Am I throttled?
Before you assume throttling, separate the three possible cases: a product cap, platform enforcement, and execution failure. Run a quick parity test: perform the same action manually in LinkedIn, compare to your PhantomBuster run logs, and check the Automation’s execution report for blocks or caps before assuming platform throttling.
Why did PhantomBuster disconnect after the verification prompt?
Verification resets your LinkedIn session and invalidates the session cookie used for logged-in Automations. Complete verification first, then reconnect your session once after access is restored.