To message someone on LinkedIn, first confirm the person and check which control LinkedIn shows in your account. An existing connection can usually be contacted through Messaging or the person’s profile. Someone outside your network may instead be reachable through a message request, Open Profile, a connection invitation, or eligible InMail.
The route is not determined by connection degree alone. Recipient settings, shared Groups, coworker status, pending invitations, account eligibility, and LinkedIn’s safety controls can change what is available. This guide covers manual LinkedIn workflows and a proposed human-reviewed preparation process. It does not provide an automated way to reach every member.
If you want to refer to a person’s article, post, role, or professional work, verify the source before drafting. A visible Message or Connect control is the final authority for the current account, not an assumption based on the profile category.
The right way to message someone on LinkedIn depends on your relationship
LinkedIn describes 1st-degree connections as people directly connected to you, 2nd-degree connections as people connected to your 1st-degree connections, and 3rd-degree connections as people connected to your 2nd-degree connections. Followers, fellow Group members, coworkers, Open Profile members, and out-of-network members are additional relationship categories. See LinkedIn’s definitions of network degrees.
Use connection degree as a starting point, not as a permission check. Open the current profile or messaging interface, identify the available route, and only then write the message.
Choose the messaging route before you draft
| Relationship or condition | Likely route | Verify before sending |
|---|---|---|
| Existing connection | Direct message | Confirm the profile and use the available Message control. |
| Eligible coworker or fellow Group member | Message request, if offered | Check recipient settings and the control shown by LinkedIn. Group membership alone is not enough. |
| Recipient has enabled Open Profile | Message from the profile may be available | The recipient must have Premium and enable Open Profile. Do not assume a specific sender allowance. |
| Other non-connection | Connection invitation or eligible InMail | Check pending invitations, recipient settings, account eligibility, and available product credits. |
LinkedIn documents direct messaging for connections, message requests for certain coworkers and Group members, Open Profile, and InMail as separate routes. Their availability can vary by account and recipient settings. Review LinkedIn’s instructions for messaging connections, its message-request guidance, and its Open Profile explanation.
Message an existing connection
For an existing connection, open LinkedIn Messaging, an existing conversation, the Connections page, or the person’s profile. Then use the available Message control. LinkedIn documents these routes in its connection messaging instructions. Labels can vary by device and account state, so follow the live interface.
A useful first message has one verified reason for contact and one clear question or low-pressure next step. For example, if you have actually read a connection’s article about customer onboarding, you might write: “I read your article on onboarding handoffs and found the section about first-week ownership useful. How do you decide which handoff to improve first?” Keep the article URL with the draft so the sender can check the reference immediately before sending.
A proposed internal drafting workflow can accept a profile URL, a verified context source, and one purpose. An optional AI assistant can return a concise draft and identify the source used. It should not infer shared history, decide that the recipient permits contact, or send the message. The sender validates identity, relevance, tone, and destination before using LinkedIn.
Contact someone who is not connected to you
Contact without a prior connection is sometimes possible without Premium. LinkedIn documents message requests for certain current coworkers and fellow Group members, subject to recipient settings and available controls. A Premium member who enables Open Profile may allow free-to-sender messages from outside their network. If neither route is available, consider a connection invitation or eligible InMail. A shared employer, Group, or connection degree does not guarantee access.
For Group messaging, LinkedIn’s guidance says the recipient must allow private communication from Group members. Use the available Message control in the Group member list or profile rather than relying on an old interface description. See LinkedIn’s Group messaging conditions.
Message requests are not connection notes. LinkedIn’s message-request documentation says attachments cannot be sent in message requests, and the recipient may accept or privately decline. If a portfolio or file is essential, use text-only context in the request or wait for a route that supports the material.
A connection note travels with an invitation and asks the recipient to accept a connection. InMail is a separate non-connection route governed by product eligibility and credits. Choose the invitation when a short introduction is sufficient and you are willing to wait for acceptance; do not treat its note as free InMail.
Connection notes and InMail are different
A connection note accompanies an invitation. LinkedIn documents a maximum of 200 characters per note. Basic users can add personalized notes to up to three connection requests per month, while Premium members can send unlimited personalized invitations, although other invitation limits may apply. The three-note allowance is not a cap on all connection requests. Check the live invitation composer and LinkedIn’s personalized invitation guidance.
InMail is subject to account and recipient eligibility. Its credit and allowance rules depend on the LinkedIn product, as described in LinkedIn’s InMail credit guidance. LinkedIn Help pages currently give inconsistent body limits, with official pages referring to 1,900 and 2,000 characters. Check the live composer instead of hard-coding one number. General eligibility and workflow are covered in LinkedIn’s InMail guidance.
Write a first message that gives the recipient a reason to reply
Use four fields when drafting: specific context, why that context is relevant, one purpose, and a low-friction next step. A real post, shared Group, mutual connection, role, or published work can supply context. Avoid invented familiarity, irrelevant personal details, an immediate hard pitch, and several requests in one message.
Illustrative connection note
Assume you have verified the recipient’s article and want to connect before asking a detailed question: “I read your article on onboarding handoffs and would value connecting. I work on customer operations and would be glad to compare notes.” This is a pattern, not tested copy. Check the character count in the live invitation composer before sending.
Illustrative direct message
After acceptance, a direct message could say: “Thanks for connecting. Your article on onboarding handoffs raised a useful question for my team: how do you measure whether a handoff is working? I’d value your perspective if you have time.” Replace the example with a neutral opener if the source cannot be verified.
For an internal, human-reviewed preparation process, capture the profile URL, context source URL, purpose, proposed route, draft, and status. AI may organize supplied facts or suggest wording, but deterministic checks should handle character counts and route fields. A person confirms the source and message, then sends through LinkedIn.
Troubleshoot a missing Message or Connect button
A missing control does not by itself mean Premium is required. LinkedIn lists possible reasons a Connect option may not appear, including an existing connection, an invitation already sent, Follow being the default, more than 500 connections, an unconfirmed or bounced primary email, or being outside the recipient’s network. LinkedIn may also request the recipient’s email address because of recipient settings, a prior invitation, or multiple “I don’t know” responses. These are documented possibilities, not a promise that one condition produces the same result for every account. See LinkedIn’s missing Connect guidance and its explanation of email requirements for some invitations.
- Confirm that you are not already connected.
- Check whether an invitation is pending; do not submit a duplicate request.
- See whether Follow is the default profile control.
- Check your connection count and confirm that your primary email is valid.
- Review recipient, network, coworker, Group, and privacy eligibility.
- If LinkedIn requests an email address or shows no eligible control, follow the prompt or stop.
Follow up and track outreach responsibly
One polite follow-up after a reasonable interval, such as five to seven business days, is editorial guidance rather than a LinkedIn rule. If there is still no reply, move on instead of switching channels to pressure the same person.
If a team keeps internal records, define one row as one message attempt. Keep the current relationship as a separate, time-sensitive observation, and calculate campaign totals from message events rather than storing aggregate counts on a contact record. The fields below are a proposed internal design, not LinkedIn fields:
{
"event_id": "evt-illustrative-1042",
"sender_account_id": "sender-illustrative-07",
"recipient_profile_url": "https://www.linkedin.com/in/example-recipient/",
"message_route": "direct",
"message_purpose": "Ask about a published article",
"context_source_url": "https://example.com/article",
"status": "drafted",
"sent_at": null
}The event ID identifies one attempt, while the recipient URL identifies the external person. A later invitation note or follow-up should receive a different event ID and row, even when the recipient is the same. Store relationship status separately because it can change between events.
If multiple staff members or systems can write records concurrently, enforce the selected uniqueness policy with a database constraint or transactional upsert. A lookup followed by a create is not race-safe. For example, a proposed deduplication key could combine sender account, recipient profile URL, route, purpose, campaign, and a defined time window. That key is an internal implementation choice, not a LinkedIn identifier, and it should not merge legitimate separate message events.
Mark a record as sent only after the sender confirms the action. Do not treat a drafted or approved record as a delivery event. Teams considering CRM systems consulting should keep recordkeeping separate from sending and independently verify any proposed product, API, integration, browser automation, or terms.
The reviewed LinkedIn Help pages establish user-facing workflows. They do not verify a general public API for sending ordinary personal messages, connection requests, Group requests, or InMail, nor do they establish automatic CRM synchronization.
Frequently asked questions
Can I message a non-connection without Premium?
Sometimes. A message request may be available for certain coworkers or Group members, and an enabled Open Profile may allow free-to-sender contact. Otherwise, check for a connection invitation or eligible InMail.
Is a connection note the same as InMail?
No. A connection note accompanies an invitation. InMail is a separate non-connection route governed by product eligibility and credits.
Can a message request include an attachment?
No. LinkedIn’s message-request documentation says attachments cannot be sent in message requests.
Is Open Profile available to everyone?
No. The recipient must have Premium and enable Open Profile. The reviewed documentation does not establish a specific monthly allowance for senders.
Can a CRM automatically send ordinary LinkedIn messages?
The reviewed official documentation does not verify a general public sending API or supported automation workflow for ordinary personal messages. Verify the specific product, API, integration, and terms before relying on one.