A practical reply-triage workflow with clear intent categories, illustrative responses and a handoff checklist for your sales team.
A LinkedIn reply is the start of a decision, not proof that a lead is ready for a sales call. “Send me something,” “try our operations team,” and “please stop” all count as replies, but they require very different actions.
For an outreach team, the useful question is: who owns the next step, and what did the prospect actually agree to? This guide offers a practical reply-handling workflow you can use in a shared tracker or CRM. It is an editorial operating template, not a claim about a built-in AllProfiles feature or a promised conversion rate.
Start with the conversation, not the calendar link
LinkedIn's InMail writing guidance recommends treating a message as a conversation starter, keeping it brief and making it relevant to the recipient. Those principles are useful when composing a reply too: answer the question the person asked before introducing a new request.
InMail guidance is not a specification for every LinkedIn messaging feature. The workflow below is our suggested process for human review of outreach conversations; it does not depend on a particular subscription, inbox integration or automated sequence.
Before answering, read the original outreach and the full response. Check whether a colleague has already replied, whether the contact is already a customer, and whether there is a previous request to stop. Assign one conversation owner so two operators do not send competing answers.
Use six practical reply categories
Keep intent separate from the sales stage. Someone can ask a useful question without being qualified, and a qualified contact can still decline a meeting.
| Reply category | What it means | Next action | Do not assume |
|---|---|---|---|
| Interested | Wants to discuss a relevant problem or next step | Answer, clarify the need, then offer a suitable next step | Interest equals a booked meeting |
| Information request | Asks about price, scope, proof or a resource | Send a direct answer or the specific material requested | “Send details” means permission for a long sequence |
| Referral | Identifies another person or team | Clarify the introduction and record the new contact separately | The referred person has agreed to a pitch |
| Later | Gives a timing constraint or asks to reconnect | Record the stated timing and an agreed follow-up | Every “not now” is a future opportunity |
| Not a fit | Declines or describes a mismatch | Close the conversation and record the relevant reason | An objection must always be overcome |
| Stop request | Asks not to be contacted again | Stop outreach and make the instruction visible to the team | Another operator should try a different angle |
These labels are suggestions. Write a one-sentence definition for each in your team's playbook, and use a separate “needs review” queue when a message is ambiguous. Do not force sarcasm, an unclear one-word answer or an out-of-office response into “interested.”
Ask only what is needed for the next decision
HubSpot's sales qualification guide describes qualification as assessing whether a prospect fits your offering. For a short messaging exchange, that does not mean sending a full discovery questionnaire.
Our suggested minimum before proposing a call is:
- Need: What problem or outcome did the person identify?
- Fit: Does your actual service cover it, and what is still unknown?
- Next step: Did they ask for information, agree to a discussion, or request a later conversation?
Record unknowns as unknowns. A job title does not prove purchasing authority; a large company does not establish budget. If the prospect has already answered a question in the thread, carry that answer forward instead of asking again.
Five illustrative replies you can adapt
The examples below are fictional. They are not customer conversations or tested performance claims. Replace the details with truthful information about your offer, and use only the example that fits the response.
“Can you send pricing?”
“Of course. For the scope you described, the price is [verified price and billing period], including [actual scope]. [Relevant extra cost or limitation] is separate. Are you considering this for one team or several?”
Give the requested price if you can. If pricing needs clarification, explain exactly which missing detail changes the quote instead of making a call the only way to get an answer.
“We already have a provider.”
“Understood. Is there a specific gap you are looking to solve, or are you happy with the current setup?”
If there is no gap and no interest, close the conversation. Do not invent a weakness in their provider or promise that switching will produce better results.
“Talk to our head of operations.”
“Thanks for pointing me in the right direction. Would you prefer to introduce us, or should I contact them and mention that you suggested their team?”
Only describe the referral as an endorsement if that is actually what happened. LinkedIn's own template guidance also cautions against invoking a mutual connection without checking the relationship and getting permission.
“Come back next quarter.”
“Understood. Would a short message in the first week of [month] be useful, or would you rather reach out when the timing changes?”
Put the prospect's answer into the tracker. A scheduled task should reflect that answer, not restart an unrelated sequence.
“Yes, let's speak.”
“Happy to. We can use the call to discuss [their stated problem] and check whether [actual service] fits. Would [option one with timezone] or [option two with timezone] work? I can send a booking link if easier.”
Confirm the timing and purpose. Treat “yes” as agreement to arrange a meeting; mark it booked only once there is a confirmed date and time.
Make the handoff useful to the person taking the call
A calendar entry alone leaves the next person guessing. Use this compact handoff record:
| Field | What to capture |
|---|---|
| Contact and company | Name, role and relevant account identifier |
| Conversation owner | Who is responsible until the handoff is accepted |
| Stated need | A short, faithful summary of the prospect's words |
| Relevant context | Which offer they saw and what you have already answered |
| Commitments | Any price, deliverable or timeline already communicated |
| Unknowns | What the call still needs to establish |
| Meeting | Confirmed date, timezone, attendees and purpose |
| Source | A permitted conversation reference or a relevant excerpt |
Share only the context needed with the people handling the conversation. Avoid copying an entire personal inbox into a client-facing report. If your tools cannot provide suitable access controls, use a limited handoff note rather than exposing the full thread.
The receiving salesperson should acknowledge the handoff. Until then, the original owner remains responsible for an unanswered prospect question or a changed meeting time.
Review the queue without inflating the results
At the end of a working day, check conversations that have no owner, questions awaiting an answer, agreed follow-ups without a date, and meetings awaiting confirmation. Choose an internal response target your staffing and time zones can support; do not advertise an instant-response promise you cannot maintain.
For client reporting, keep replied, interested, meeting booked and meeting held separate. A stop request remains a reply, but never an interested lead. Our outreach reporting guide explains how to keep the underlying counts and denominators clear.
If the inbox is full of wrong-person or wrong-company responses, revisit the lead-list criteria. Better reply handling cannot fix a consistently irrelevant audience. Start with a small queue, agree on the categories, and review a few ambiguous conversations together before expanding the workflow.
