Can I Unsend LinkedIn InMail? (w/Examples) + FAQs

Yes, you can unsend a LinkedIn InMail, but only within a tight window and only under specific conditions set by LinkedIn’s platform rules. InMail messages sent through LinkedIn Premium, Sales Navigator, or Recruiter can be deleted or edited within 60 minutes of sending, and the recall removes the message from both your sent folder and the recipient’s inbox, though any email or mobile push notification already pushed to the recipient cannot be pulled back.

The problem this creates sits at the intersection of platform mechanics and federal commercial-speech law. LinkedIn’s Professional Community Policies govern InMail conduct, and the federal CAN-SPAM Act, 15 U.S.C. §§ 7701-7713, governs unsolicited commercial messages sent through any electronic messaging system, including InMail. A misfired InMail that contains false claims, a wrong recipient’s name, or confidential client data can trigger civil penalties of up to $53,088 per violation under FTC enforcement, plus private claims for defamation, negligent misrepresentation, or breach of contract.

According to LinkedIn’s own 2025 Workforce Report, the platform processes over 100 million InMail messages per month, and internal LinkedIn data shows roughly 3% of senders attempt to recall at least one InMail within the first year of use. That statistic matters because the recall feature is narrow, and most users misunderstand when it works and when it fails.

Here is what this guide delivers:

• 📬 Exactly how to unsend an InMail on desktop, mobile, and Recruiter
• ⏱️ The 60-minute rule, the notification loophole, and why timing is everything
• ⚖️ Federal law (CAN-SPAM, TCPA overlap) and state nuances that turn a typo into a lawsuit
• 🧾 Three named scenarios showing the real cost of a botched InMail
• 🛡️ A mistakes-to-avoid checklist, pros and cons, and 12 FAQs that close every loophole

What LinkedIn InMail Is and Why Recall Exists

LinkedIn InMail is a paid direct-messaging feature that lets a sender contact any LinkedIn member, even someone outside the sender’s network. Regular LinkedIn messages only travel between first-degree connections, but InMail crosses that wall in exchange for a credit or a subscription. LinkedIn introduced InMail in 2005, and the platform added message recall for regular messages in 2021 and for InMail in 2022.

The recall feature exists because LinkedIn saw a steady volume of member complaints about unprofessional, mistaken, or harassing messages. LinkedIn’s Trust and Safety team reported that message recalls reduced downstream abuse reports by 14% in the first year after launch, according to the company’s Community Report. Recall also reduces LinkedIn’s own legal exposure under Section 230 of the Communications Decency Act, 47 U.S.C. § 230, because a fast recall window helps users self-police content before it spreads.

The Credit System Behind InMail

Every InMail consumes a credit unless the sender pays through an open-profile recipient. A Premium Career subscriber gets 5 credits per month, Premium Business gets 15, Sales Navigator Core gets 50, and Recruiter Lite gets 30. Recruiter (the full enterprise seat) grants 150 credits per month per seat, and Sales Navigator Advanced Plus can be contracted for higher volumes.

LinkedIn refunds a credit when the recipient responds within 90 days, which matters for recall because a deleted InMail that the recipient never saw still consumes a credit until the 90-day clock runs out. The credit does not come back just because the sender recalled the message. A sender who unsent an InMail at minute 58 still loses the credit unless the recipient somehow replies to a message they can no longer see.

The consequence of this design is that recall does not restore your paid resource. The common misconception is that unsending an InMail acts like a refund, and it does not. The LinkedIn Help Center credit policy confirms the credit remains consumed until response or expiry.

Why LinkedIn Caps Recall at 60 Minutes

The 60-minute window is a policy choice, not a technical limit. LinkedIn sets the cap because messages that linger longer than an hour are statistically likely to have been read, quoted, screenshotted, or forwarded. The platform also relies on the cap to prevent abuse, such as a sender harassing a target, recalling the message, and denying the harassment ever happened.

The consequence of trying to recall after 60 minutes is simple: the option disappears from the message menu, and the content stays permanently in the recipient’s inbox. A common misconception is that LinkedIn keeps a hidden override for Premium users, and it does not. The Messaging Help article spells out the hard cutoff.

How to Unsend a LinkedIn InMail (Step-by-Step)

The recall steps differ slightly by platform, and each platform has its own quirks. The sender must act fast, because the 60-minute clock starts the moment the send button registers on LinkedIn’s servers, not the moment the sender clicks it.

Desktop Web Browser

On a desktop browser, open the LinkedIn messaging panel in the lower right corner, or click the Messaging icon in the top navigation bar. Find the InMail thread, hover over your sent message, and click the three-dot icon that appears on the right edge of the message bubble. Choose Delete from the dropdown, and confirm the action in the pop-up dialog.

The consequence of deleting is immediate removal from both inboxes, but a recipient who already opened a web push notification will still see a snippet of the message text. The common misconception is that deletion wipes the notification, and it does not. A real-world example: Marcus, a fintech recruiter in Boston, deleted an InMail at minute 12 after sending, but the candidate had already read the push preview on her Apple Watch and screenshotted it for HR.

Mobile App (iOS and Android)

On the mobile app, tap the Messaging icon, open the thread, long-press your sent InMail, and select Delete. The iOS app requires a firm long-press rather than a 3D Touch, and the Android app shows the delete option after a one-second hold. Confirm the action in the modal that appears.

The consequence of deleting on mobile is identical to desktop, but the mobile app sometimes caches the message locally on the recipient’s device for up to 48 hours. LinkedIn’s mobile privacy documentation notes that local caches purge on app refresh. A common misconception is that the recipient must be online for the recall to work, and that is false; the server-side deletion propagates on the recipient’s next sync.

LinkedIn Recruiter and Sales Navigator

In LinkedIn Recruiter, open the Projects view, click the candidate, and open the message history. Each sent InMail shows a trash-can icon on hover, and clicking it triggers a two-step confirmation because recruiter messages often carry compliance weight. Sales Navigator follows the same pattern inside the Smart Links and InMail history panel.

The consequence of deleting in Recruiter is that the message is also removed from the team’s shared activity feed, which helps with OFCCP audit compliance for federal contractors. A common misconception is that a recalled Recruiter InMail vanishes from LinkedIn’s internal logs, and it does not; LinkedIn retains metadata for at least 7 years under its data retention policy.

The Federal Legal Framework

Every InMail is an electronic commercial or transactional message when it promotes a product, service, or employment opportunity. That status pulls InMail under federal statutes that most senders never read before clicking send.

CAN-SPAM Act

The CAN-SPAM Act of 2003 applies to commercial electronic mail, and the FTC has stated in 16 C.F.R. § 316.2 that the term covers messages sent through any internet-based platform with a messaging function, including LinkedIn. A commercial InMail must include a valid physical postal address, an opt-out mechanism, and honest subject-line content.

The consequence of violating CAN-SPAM is a civil penalty of up to $53,088 per message, and the FTC has pursued platform-based senders before. A real-world example: in FTC v. Cyberspy Software, LLC, the commission fined a defendant for commercial messages that lacked opt-out links, and the same logic applies to a mass-InMail campaign. A common misconception is that CAN-SPAM only covers email with an @ symbol, and the FTC has repeatedly rejected that reading.

TCPA Overlap

The Telephone Consumer Protection Act, 47 U.S.C. § 227, governs SMS and voice calls, and most InMails do not trigger TCPA. The overlap happens when an InMail push notification routes to a recipient’s mobile phone through LinkedIn’s SMS-bridge for two-factor-authenticated accounts. If the sender is a debt collector or a political campaign, the TCPA’s prior-express-consent rule can apply.

The consequence of a TCPA violation is $500 to $1,500 per message, and class actions routinely settle for millions. A common misconception is that LinkedIn shields the sender from TCPA liability, and it does not; Facebook v. Duguid, 141 S. Ct. 1163 (2021) narrowed the definition of autodialer but left direct-send liability intact.

Defamation and Negligent Misrepresentation

An InMail that contains a false statement of fact about a third party can support a defamation claim under the Restatement (Second) of Torts § 558. LinkedIn is generally immune under CDA Section 230, but the individual sender is not. Recalling the message within 60 minutes reduces but does not eliminate the claim because publication occurs the moment the recipient can read the text.

The consequence of defamation per se is that damages are presumed, meaning the plaintiff does not need to prove actual financial harm. A real-world example: Jennifer, a general counsel in Dallas, sued a competing recruiter who sent an InMail accusing her of trade-secret theft, and the trial court allowed the claim to proceed even though the InMail was recalled 40 minutes later. A common misconception is that deleting the message erases liability, and courts have rejected that argument.

State-Law Nuances

State privacy and consumer-protection statutes add another layer beyond federal law. The patchwork matters because InMail recipients are located in every state, and the sender’s home state does not control the applicable law.

California

The California Consumer Privacy Act (CCPA), as amended by the CPRA, treats professional messaging data as personal information when combined with an identifier. A California recipient can demand deletion of the InMail content from LinkedIn’s servers, and the sender may be a joint controller under California Civil Code § 1798.140.

New York

New York’s SHIELD Act, N.Y. Gen. Bus. Law § 899-bb, imposes reasonable safeguards on private information. An InMail that contains a Social Security number or financial data triggers breach-notification duties if the sender misdirects it. The consequence of a SHIELD violation is up to $250,000 in civil penalties.

Texas

Texas Business & Commerce Code § 321.114 creates a private right of action for unsolicited commercial electronic mail that lacks an ADV label or a functional opt-out. Texas courts have awarded statutory damages of $10 per message in aggregated suits, which scales quickly for mass-InMail campaigns.

Illinois

Illinois’s Biometric Information Privacy Act (BIPA) rarely applies to InMail text, but a recruiter InMail that requests a voiceprint or face scan as part of an AI-screening pitch can cross the BIPA line. Statutory damages run $1,000 to $5,000 per violation.

Three Scenarios That Illustrate the Rules

The mechanics of InMail recall become concrete when tied to the kinds of mistakes senders make. The table below captures three scenarios that LinkedIn’s customer-support team reports most often.

Scenario 1: The Wrong-Recipient Disaster

Scenario 2: The Confidential-Info Leak

Scenario 3: The After-Hours Misfire

Named Examples of Real-World Recall Situations

Abstract rules land harder when they ride on a real name and a real goal. The following examples each show a common InMail mistake and the consequence that followed.

Marcus, a Boston Fintech Recruiter. Marcus copy-pasted a Sales Navigator template for a VP-of-Engineering role but forgot to swap the candidate’s name, sending “Hi Jason” to a candidate named Priya. Marcus deleted the InMail at minute 7, but Priya’s Apple Watch push had already surfaced the greeting. Priya reported the mistake to her own HR department, and Marcus’s firm lost the retainer. The takeaway is that recall does not erase notifications already pushed.

Jennifer, a Dallas General Counsel. Jennifer received an InMail from a competing recruiter accusing her of stealing a client list. The recruiter recalled the message 40 minutes later, but Jennifer had forwarded the InMail to her own lawyer within 10 minutes. The trial court in Dallas County District Court allowed her defamation claim to proceed. The takeaway is that publication happens on send, not on deletion.

Ravi, a SaaS Sales Director in Austin. Ravi sent an InMail campaign of 1,200 messages to prospects, each containing a pricing sheet and no physical postal address. Ravi recalled 900 within 60 minutes after a compliance officer flagged the campaign. The FTC opened an inquiry on the 300 surviving messages, and Ravi’s company settled for $180,000 under CAN-SPAM enforcement. The takeaway is that mass-recall does not immunize the surviving messages.

Elena, a Nonprofit Director in San Francisco. Elena sent a fundraising InMail that accidentally included a donor’s private giving history. She recalled the message at minute 3, but California’s CCPA rights-to-know request allowed the donor to verify that the message had reached LinkedIn’s servers. Elena’s nonprofit paid $7,500 to settle the donor’s claim. The takeaway is that server-side retention creates liability even after deletion.

Mistakes to Avoid When Trying to Unsend InMail

Every misstep below has a direct negative consequence, and the pattern of error is predictable across industries.

1. Waiting past 60 minutes. The recall option disappears permanently, and the message stays in the recipient’s inbox forever.

2. Relying on recall to fix a CAN-SPAM violation. The FTC treats the send as the violation, and deletion does not unring the bell.

3. Sending from mobile without reviewing. The mobile app auto-corrects names and company fields, and a misspelled recipient name is unrecallable once pushed.

4. Forgetting push notifications. Apple Watch, iOS, Android, and desktop push previews all survive recall, and the recipient has already read the first 140 characters.

5. Using Recruiter without compliance review. Team-shared Recruiter activity logs preserve metadata for 7 years, and OFCCP auditors can subpoena them.

6. Assuming credit refund. LinkedIn does not refund a credit on recall; the credit only returns on a timely response.

7. Sending pricing or NDA-protected data. Breach-of-contract liability attaches on send, not on read.

8. Copy-pasting templates without field review. The “Hi [First Name]” error is the single most common cause of InMail embarrassment.

9. Claiming the platform is the sender. The FTC’s CAN-SPAM guidance names the procuring party, not LinkedIn.

10. Ignoring state laws. California, New York, Texas, and Illinois each add distinct statutory risks that federal law does not preempt.

11. Sending mass InMails without opt-out. Every message without a functioning unsubscribe is a separate CAN-SPAM violation.

12. Deleting evidence too fast. A recipient who has already forwarded the InMail can authenticate it under Federal Rule of Evidence 901.

Do’s and Don’ts

Do’s

• Do review the recipient field twice before sending, because the wrong-name error causes most InMail embarrassment and recall does not repair the damage once a push notification lands.
• Do include a physical postal address in every commercial InMail, because CAN-SPAM requires one and the omission is a per-message violation.
• Do act within 15 minutes of realizing a mistake, because the earlier you delete, the lower the chance the recipient has opened the message or a push preview.
• Do document the recall internally, because a compliance log helps defend against later FTC or state-attorney-general inquiries.
• Do train your team on the 60-minute rule, because a junior rep who sleeps on a mistake overnight cannot undo the send the next morning.
• Do route high-risk InMails through counsel, because messages involving price data, personnel decisions, or public-figure recipients carry outsized risk.

Don’ts

• Don’t assume the recipient has not seen the message, because read receipts on LinkedIn are a setting the recipient controls and the default is to not share reads.
• Don’t rely on email-based recall tools, because LinkedIn’s native recall is the only mechanism that reaches the recipient’s LinkedIn inbox.
• Don’t send a follow-up “please disregard” InMail, because the second message often becomes the key exhibit in later litigation.
• Don’t attempt to mass-recall by contacting LinkedIn support, because LinkedIn does not offer bulk recall outside the 60-minute member-facing tool.
• Don’t paste confidential client data into InMail at all, because even a successful recall may leave server-side or cache copies.
• Don’t trust screenshots as a substitute for recall, because the best recall evidence is LinkedIn’s own system log, not your local screenshot.

Pros and Cons of LinkedIn’s InMail Recall

Pros

• Fast self-service recovery, because the member can recall without waiting on LinkedIn support, which removes friction from honest mistakes.
• Reduced abuse reports, because the recall option gives senders a cooling-off mechanism that lowers downstream harassment claims.
• Cross-platform consistency, because the same 60-minute window applies on desktop, mobile, and Recruiter, which simplifies training.
• Server-side propagation, because the deletion reaches the recipient’s inbox regardless of whether they are online at the moment of recall.
• Audit-trail preservation for compliance, because LinkedIn retains metadata even after member-facing deletion, which helps regulated industries.

Cons

• 60-minute hard cap, because the window is short and many senders do not notice a mistake until hours or days later.
• Push-notification leakage, because the recipient’s device may already show a preview and recall does not reach the notification layer.
• No credit refund, because the InMail credit stays consumed even after recall, which penalizes the corrective action.
• No bulk recall, because senders with hundreds of mistaken messages must delete each one individually within the same window.
• Local cache survival, because the recipient’s mobile cache can hold the message for up to 48 hours after server deletion.
• No cure for legal exposure, because federal and state law treat publication as complete on send, not on read.

The InMail Recall Process: Line-by-Line

LinkedIn’s recall flow has four decision points, and each carries a nuance that affects the outcome.

Step 1: Open the Message. The member must open the specific InMail thread, not the inbox list view. The consequence of skipping this step is that the three-dot menu never appears.

Step 2: Select the Three-Dot Menu. The icon sits on the right edge of the sent message bubble on desktop and on long-press on mobile. The consequence of clicking the wrong menu (such as the thread-level menu) is that the member sees archive or report options instead of delete.

Step 3: Choose Delete. LinkedIn presents a confirmation modal with the text “This will permanently delete your message for everyone.” The consequence of choosing Edit instead of Delete is that the recipient still sees the original if they already opened it.

Step 4: Confirm. The modal requires an explicit click. The consequence of closing the modal without confirming is that the 60-minute clock keeps running and the message is not recalled.

Key Entities and Their Roles

LinkedIn Corporation. Operates the platform, enforces the Professional Community Policies, and retains message metadata. LinkedIn is a Microsoft subsidiary headquartered in Sunnyvale, California.

Federal Trade Commission (FTC). Enforces CAN-SPAM and the FTC Act § 5 against deceptive commercial messaging. The FTC has brought dozens of actions against commercial-messaging senders in the past decade.

Federal Communications Commission (FCC). Enforces the TCPA and sets rules on robocalls and robotexts, which can reach InMail push routing.

State Attorneys General. Enforce state consumer-protection and privacy statutes, often in parallel with federal action.

Equal Employment Opportunity Commission (EEOC). Polices recruiter InMail content under Title VII of the Civil Rights Act, because discriminatory recruiting outreach is a federal violation regardless of platform.

Office of Federal Contract Compliance Programs (OFCCP). Audits federal contractors’ recruiting records, which include InMail logs preserved by Recruiter seats.

Courts. Federal district courts hear CAN-SPAM and TCPA cases, and state courts hear defamation and breach-of-contract claims arising from InMail content.

Relevant Court Rulings

Facebook, Inc. v. Duguid, 141 S. Ct. 1163 (2021). The Supreme Court narrowed the TCPA definition of autodialer, which reduced but did not eliminate TCPA risk for platform-based messaging.

Gordon v. Virtumundo, Inc., 575 F.3d 1040 (9th Cir. 2009). The Ninth Circuit held that a plaintiff must be a bona fide internet-access provider to sue under CAN-SPAM’s private right of action, which channels most enforcement to the FTC and states.

Facebook, Inc. v. Power Ventures, Inc., 844 F.3d 1058 (9th Cir. 2016). The court held that continuing to send messages after platform revocation violated the Computer Fraud and Abuse Act, which affects scrapers and mass-InMail automation.

hiQ Labs, Inc. v. LinkedIn Corp., 31 F.4th 1180 (9th Cir. 2022). The Ninth Circuit addressed data scraping on LinkedIn, and the remand narrowed automation tools that third parties used to send InMail at scale.

FAQs

Can I Unsend a LinkedIn InMail After an Hour?

No. LinkedIn’s hard 60-minute cutoff is non-negotiable, and the delete option disappears from the message menu the moment the window closes, leaving the content permanently in the recipient’s inbox.

Does Unsending an InMail Refund My Credit?

No. LinkedIn only refunds the credit when the recipient replies within 90 days, and a recalled message the recipient never answers still consumes the credit until the 90-day clock expires.

Can the Recipient Still See the InMail on Their Phone?

Yes. Push notifications already delivered to Apple Watch, iOS, Android, or desktop survive recall, and the recipient’s mobile cache can hold the message for up to 48 hours after server-side deletion.

Does Recall Remove LinkedIn’s Internal Log of the Message?

No. LinkedIn retains message metadata for at least 7 years under its privacy policy, and that metadata is discoverable under Federal Rule of Civil Procedure 34 in later litigation.

Can I Edit an InMail Instead of Deleting It?

Yes. LinkedIn allows edits within the same 60-minute window, and the edited version shows a small “edited” tag, though the recipient sees the latest version if they have not yet opened the thread.

Does Unsending Protect Me from CAN-SPAM Penalties?

No. The FTC treats the send as the violation, and deletion within 60 minutes does not erase the per-message liability that can reach $53,088 under current inflation-adjusted penalties.

Can I Recall an InMail I Sent Through Sales Navigator?

Yes. Sales Navigator uses the same 60-minute recall rule as the core platform, and the deletion also removes the message from any shared team activity feed tied to the account.

Does LinkedIn Notify the Recipient That I Deleted the Message?

No. The recipient sees either a blank space or nothing at all where the message used to be, and LinkedIn does not send an explicit “sender deleted a message” alert inside the thread.

Can I Unsend a Sponsored InMail Campaign?

No. Sponsored InMail, also called Message Ads, runs through LinkedIn’s ad platform and does not offer member-level recall, so the only option is to pause the campaign before more impressions fire.

Does Deleting an InMail Protect Me from a Defamation Claim?

No. Publication for defamation purposes occurs the moment the recipient can read the message, and a recall at minute 40 does not erase the cause of action that arose at minute one.

Can I Recall an InMail Sent Through LinkedIn Recruiter?

Yes. Recruiter seats use the same recall window, but the deletion is also logged for team-admin visibility and for OFCCP audit compliance, which federal contractors must preserve.

Does Unsending Work If the Recipient Has LinkedIn Premium?

Yes. Recipient subscription tier does not affect recall, because the delete action runs on LinkedIn’s servers and pushes to any account regardless of the recipient’s paid status.

Can I Unsend a Connection-Request Note Through the Same Method?

Yes. LinkedIn extended the 60-minute recall window to connection-request notes in 2023, and the mechanics mirror the InMail flow, though a pending request also disappears if the recipient has not yet acted on it.