# How to sort LinkedIn sales replies by intent
> Sort LinkedIn replies into four intent buckets so the buyers who asked for a call get answered first, and the rest stop eating your afternoon.
- HTML: https://getkinlead.com/managing-linkedin-sales-replies-and-intent
- Markdown: https://getkinlead.com/managing-linkedin-sales-replies-and-intent.md

**Short answer:** Read every new LinkedIn reply and put it in one of four buckets: interested, question, not a fit, neutral. Answer interested and question replies first, archive the rest with a note of what they asked, and come back to neutral leads on a set date instead of leaving them in your inbox.

## Why the newest reply is rarely the one that pays

LinkedIn sorts your inbox by time. Time tells you nothing about money. The person who replied twenty minutes ago with "thanks, I'll keep you in mind" sits above the person from yesterday who asked what pricing looks like for six seats.

So you work top to bottom, spend your sharpest hour on people who already said no politely, and reach the buyer at four in the afternoon when you're answering on autopilot. The buyer gets a worse reply than the person who isn't buying.

Sorting by intent fixes this without a new tool. You read the message, decide what it means, and answer in that order. The rule is the same every day, which is why it survives a busy week.

**Working top to bottom**

- Open the inbox and answer whatever arrived last
- Write three paragraphs to someone who said thanks
- Reach the pricing question at 4pm with nothing left
- Lose track of who asked what

**Working by intent**

- Read every new reply before answering any of them
- Answer demo and pricing requests first
- Give question replies two sentences and a call link
- Archive the rest with a note on what they asked

## The four buckets, and how to spot each one

Four buckets is enough. Every extra category is another decision, and by week two you'll stop making it and go back to reading top to bottom.

The signal is usually in the first sentence. Buyers ask about money, timing or next steps. Curious people ask how a feature works. Polite people thank you and disappear.

When a reply could go in two buckets, put it in the lower one. Overrating a reply costs you an hour. Underrating it costs you nothing, because you can move it up the moment they say something clearer.

| | Bucket | What it sounds like | What you do |
| --- | --- | --- | --- |
| Interested | Asks for pricing, a call, a demo or a start date | Send your scheduling link in the first reply, no pitch |
| Question | Asks how something works, or compares you to another tool | Answer in two sentences, then offer a call |
| Not a fit | Wrong role, no budget, locked into something they won't leave | Say thanks, then ask who owns the problem |
| Neutral | "Thanks", "will keep you in mind", "interesting" | One line back, then a reminder in 30 days |

> If you have to reread a reply twice to classify it, put it in question. The next message will tell you more than this one did.

## A ten minute triage routine

Run triage twice a day, once in the morning and once late afternoon. Turn notifications off in between. Nothing in a LinkedIn inbox needs an answer within the hour.

Open the inbox and read. Don't type yet. You're sorting mail, not answering it, and mixing the two is how one reply eats forty minutes.

Then answer in bucket order. Once you've done it a few times the whole pass takes about ten minutes.

1. **Read everything first.** Scroll through every new reply and note the bucket next to each name. Resist answering the first one you open.
2. **Clear interested.** Send your scheduling link with one line of context. They already asked, so don't explain the product.
3. **Cap question replies at two sentences.** Give a real answer, then ask a question that points at a call. If you're on your fourth sentence, you're writing a proposal in a chat window.
4. **Close out the rest.** One line to neutral replies, one line to not-a-fit replies, then archive both. If they're at the wrong company, ask who handles this instead.
5. **Write down what they asked.** One line per lead in a notes doc or a spreadsheet. Next time you follow up, you open with their question instead of "just checking in".

## What to write for each bucket

Reply length should match intent. Interested gets the shortest reply you'll send all day, because the decision is already made and all you're doing is putting a time on the calendar.

Question gets a real answer and a redirect. Two sentences, then a question that points at a call.

Neutral gets one line. Not a fit gets one line and, if the company is big enough to hold other buyers, one question about who owns the problem.

- **them:** This looks interesting. How does pricing work for a team of six?
- **you:** Depends on seats and whether you need the API. Easier to show you than type it. Grab a time here and I'll have numbers ready for six.
- **them:** Before that, does it work with the stack we already run?
- **you:** Depends what's in it. Send me the two tools you'd hate to lose and I'll tell you straight.

```
Hi {first name},

When we last spoke you said {their words, roughly}. I'm not chasing a yes, just checking whether that's still true.

If the timing moved, tell me the month and I'll come back then. If it hasn't, say so and I'll leave it there.
```

## Where the replies go after you answer

Keep a list: name, bucket, what they asked, the date you'll come back to them. A spreadsheet is fine. The point is that your next message opens with their question, which is the only reason they'll remember you.

Neutral replies get one reminder, not a sequence. Thirty days is a reasonable default. If they told you the budget lands in Q3, come back in Q3 and say so.

Not-a-fit replies are worth one question: who owns this at your company? "Is there someone on your team who handles this?" is a question people can answer in five seconds, which is why it works.

Archive instead of deleting. The person who said no in March is sometimes the person who signs in September, and you want to know what they told you the first time.

## Doing this with Kinlead

Kinlead puts replies from every campaign into one [unified inbox](/features/unified-inbox), classified by intent, with interested replies first. You get an email when someone replies, so you're not refreshing the tab between tasks.

Each campaign picks how replies are handled. Hand the conversation to you at the first reply, let the AI reply until there's real interest, or let it reply until a meeting is booked with your scheduling link. If you want to read every reply before it goes out, use hand-off mode, because the AI modes send on their own.

You can read and edit queued messages on the Actions page before they send, and pause any campaign while you catch up.

## Related

- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)
- [Reply drafts](https://getkinlead.com/features/reply-drafts.md)
- [Classifying and drafting replies](https://getkinlead.com/ai-to-classify-and-draft-linkedin-replies.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)

## Common questions

**How many intent categories should I use?**

Four is enough. Add a fifth only if you keep finding replies that don't fit, and merge it back if you stop using it.

**Should I reply to every LinkedIn message?**

No. Neutral and not-a-fit replies can get one line and an archive. Answering everything at length is how the inbox gets away from you.

**What if someone replies on a weekend?**

Leave it until your next triage window. The reply will still be there, and you'll answer it better with a clear head.

**Do I need a CRM to track this?**

No. A spreadsheet with name, bucket, what they asked and a revisit date does the job until volume makes it painful.

**How do I tell interested from polite?**

Look for a question about money, timing or next steps. If the reply only compliments your message, it's neutral until they ask something.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
