What to say after someone accepts your LinkedIn request

If your invitation mentioned a specific article, event or business question, the first message after connecting should make sense as its continuation. Do not restart with an unrelated opener because a template says to. If you sent a blank invitation, supply the missing reason now. If you already had a conversation elsewhere, acknowledge that context without pretending you met on LinkedIn.

Check who initiated the invitation. Some popular advice answers the opposite question. Ashley Leeds's video, for example, describes responding to people who asked to connect with him. Asking what brought them to his profile fits that situation. Asking the same question of someone who merely accepted your request makes them explain a contact that you initiated.

The distinction also matters when a recruiter sends an invitation. You can ask whether there is a particular role they wanted to discuss. If you contacted the recruiter about a listed vacancy, name that vacancy and your relevant background instead. Don't make the recruiter reconstruct your original purpose.

Acceptance can create an opportunity for a conversation. It does not create an obligation to have one. The following choices are editorial guidance, not a prediction of how any individual will respond.

A message can be short and still ask for too much. 'What are your biggest challenges this year?' asks a stranger to choose a topic, explain their business and decide how much to disclose. A narrower question about whether they handle a particular responsibility is easier to assess. An open-ended question is not automatically a low-pressure one.

You also do not need to hide that you sell something. Explain the relevant work you do, without turning the first exchange into a list of services or an assumed appointment. The recipient should understand your purpose before spending time replying. If they have already requested a proposal, demo or call, responding to that request is appropriate; a blanket 'never sell in the first message' rule would get in the way.

Use enough words to establish context and make the request clear, then remove the rest. Two or three readable sentences are a useful editing starting point, not a LinkedIn rule or an experimentally proven optimum. Keep technical details when they help someone judge relevance. Cut the biography, decorative praise and extra questions.

These are fictional situations and original sample messages, not customer results or templates tested for a particular reply rate. Adapt only the facts that are true for you. A named resource, meeting or introduction must exist before you mention it.

A potential customer, with a clear business reason: 'Hi Ellis, thanks for connecting. I reached out because your role includes client onboarding. I help teams document the handoff from sales to delivery. Is reviewing that handoff part of your remit?' The question checks responsibility; it does not claim that Ellis's process is broken. If the current role is uncertain, check it before writing.

A resource they already requested: 'Hi Noor, here's the ownership checklist you asked for. The second page has the handoff questions we discussed.' In this fictional setup, Noor requested the checklist and the sender can share it. Attach or link the document when you send the message. Do not hold a promised resource behind an unexpected demo requirement.

A relevant resource they have not requested: 'Hi Kira, your question in the operations discussion was about recording who accepts a handoff. I have a short worksheet for that review. Would a copy be useful?' This asks about one identifiable asset, rather than offering unspecified value. If the useful answer fits in a sentence, consider giving it directly instead of making the person ask for it.

A conversation at an event: 'Hi Tomas, we spoke after the operations panel about keeping exceptions out of the standard onboarding checklist. You asked which questions belong in the exception log. I can send the outline here if that still helps.' Use this only when the conversation happened. Attending the same event does not establish that you met.

A recruiter you contacted: 'Hi Nia, thanks for accepting. I applied for the sales-operations analyst role advertised on your careers page. My recent work includes maintaining CRM reports. Are you handling that vacancy?' Check that the vacancy is current and follow its application instructions. If the posting already identifies the right contact, use that information rather than asking a recruiter to find it for you. Acceptance is not an interview invitation, and a LinkedIn message does not replace the application.

A senior peer whose expertise you want: 'Hi Omar, I connected because your article distinguishes account ownership from deal ownership. I'm setting up that distinction for a small team. Would you be willing to answer one question here about how you handle shared accounts?' A bounded question makes the commitment clearer than asking for indefinite mentorship. If Omar agrees, ask the question you described rather than switching to a calendar link.

A quiet introduction with no immediate request: 'Hi Luz, thanks for connecting. I follow your work on customer education and look forward to reading more.' That can be the entire message. It is a greeting, not a failed sales opener because it has no question. Send it only if the interest is genuine, and don't follow it with repeated requests for acknowledgment.

An incoming invitation: 'Hi Remy, thanks for reaching out. Was there something about our onboarding work you wanted to discuss?' This belongs after Remy initiated contact. If their note already contains a question, answer it instead of asking them to repeat their reason.

What ties these examples together is continuity. Each message follows something known about the exchange. None needs an invented compliment, a claim of knowing the recipient's priorities or a fixed sequence of greetings before the sender can state a purpose.

If someone is waiting for a document you promised, send it promptly. If you are introducing yourself without a prior commitment, reviewing new connections during your normal workday is a manageable starting practice. Consider the recipient's time zone and the sensitivity of the subject, but do not imply they must be online or respond immediately.

The source advice does not establish a universal best time. Pursue recommends a 24-48-hour window and discourages immediate messaging. Other guides encourage responding right after acceptance. The reviewed pages do not provide enough comparative evidence to settle that difference for your audience. An arbitrary delay is less important than avoiding a premature or irrelevant message.

A connection made weeks ago is not automatically unusable. Introduce a current reason and describe the timing honestly: 'We connected last month. Your new article raises a question about account handoffs that I wanted to ask.' Do not thank someone as though they accepted this morning, or invent a recent event to make an old record feel fresh.

A reply that says 'thanks, you too' acknowledges your greeting. It is not evidence that someone wants a sales call. If the person asked a question, answer it. If they requested a resource, provide it. Do not resume a prewritten sequence that ignores what they just said.

The table below separates outcomes that can look identical in a simple reply count. These are manual handling choices. A polite refusal is useful information, even though it is not the commercial outcome you wanted.

After silence, first check whether your message required a response. A greeting with no question needs no chase. A person who accepted a request may not have read the message, may not be interested or may be busy. The notification alone cannot tell you which explanation is correct.

For a relevant unanswered question, one later clarification can be reasonable if it makes the request easier or supplies missing information. For example: 'To clarify my earlier question, I'm asking who owns the handoff checklist, not proposing a software replacement.' Use a clarification only when it is accurate and useful. Repeating the same pitch with a new opening line does not supply new information.

There is no response guarantee and no universal number of attempts that earns one. Do not chase a plain greeting, switch channels just because LinkedIn was quiet, or treat an explicit refusal as a wording problem to solve. Public comments should address the content on their own merits, not pressure someone to answer a private message.

LinkedIn says you can message first-degree connections for free. In the native interface, open the person's profile and choose Message, or use Messaging and Compose. Check that you selected the right person before sending. If the interface does not show the expected connection or message option, verify the account and connection state rather than assuming an old notification still reflects the current state.

Read the finished message once with the actual name, company and document inserted. Confirm that no one on your team is already discussing the same subject with this person. Check any earlier refusal or agreed contact date. Keep the source of the conversation and the next action in your CRM record so a teammate does not restart with an inappropriate introduction.

In OutreachGenie, prospect notes and custom fields can hold that context alongside the person's profile URL, title and company. Your team still needs to keep those records accurate and act on them; a note is not an automatic permission or suppression control. Use a named list to organize review work only when it helps the person handling the next exchange.

Do not interpret thoughtful wording as permission to automate sending. LinkedIn prohibits third-party software or extensions that scrape, modify or automate activity on its website. Personalization, low volume and delays do not guarantee compliance or account safety. The decision about what to say and the decision about how to send it both need review.