# How to sort LinkedIn replies by intent
> Sort LinkedIn replies by what the person actually wants, answer buyers first, and park the rest with a dated follow-up. A triage routine you can run today.
- HTML: https://getkinlead.com/managing-ai-sdr-inbox-intent
- Markdown: https://getkinlead.com/managing-ai-sdr-inbox-intent.md

**Short answer:** Read every new LinkedIn reply, tag it with what the person wants, and answer in that order instead of by timestamp. Interested buyers who ask about pricing or a call go first, curious replies get one clear next step, and refusals or wrong-person notes get archived with a date to revisit. The sorting takes a few minutes a day and stops your best conversations from waiting behind noise.

## Stop answering in the order messages arrive

A LinkedIn inbox sorts by time. It has no idea which of the people who replied this week can sign a contract, and it will happily put a refusal above a pricing question because the refusal landed eleven minutes later. Work from the top and your order of work reflects when someone happened to open your message.

The cost is quiet. A 'no thanks' gets a careful reply because it's new, while the person who asked for numbers on Tuesday waits until Thursday. By Thursday they've talked to someone else or lost the thread, and neither of those shows up as a lost deal in any report you keep.

Sorting by intent costs nothing and needs no new tool. You read each new reply, decide what the person wants, and answer in the order of what each answer is worth. The forty minutes you save go into conversations that can pay.

This is the whole idea, and it survives contact with a busy week because it doesn't ask you to be more disciplined about time. It asks you to look at one thing per message: what does this person want from me.

**Working by timestamp**

- Answer whatever sits at the top of the list
- Give a long reply to a 'not interested' note
- Reach the pricing question two days after it lands

**Working by intent**

- Tag every new reply before answering any of them
- Answer pricing and call requests first
- Park refusals with a date to come back to

## Pick four buckets and keep them

Choose a small set of categories and use the same ones for months. If you invent a new label for every message, sorting takes longer than replying and you'll stop by the second week. The point is a quick decision, not a filing system.

Four buckets cover nearly every reply you'll get on LinkedIn. The names matter less than the habit of putting each reply in exactly one of them and moving on.

| | Bucket | What it means | Example reply |
| --- | --- | --- | --- |
| Interested | Asks for a call, a price, or whether the product fits their case | Can you send times for a call this week? |
| Curious | Asks a general question or wants detail before deciding anything | How does this compare to doing it by hand? |
| Not now | Refuses, defers, or sends an out-of-office reply | We're under contract until March |
| Wrong person | Says they aren't the buyer or have left the company | I've moved teams, try Dana in ops |

## Run one triage pass in the morning and one in the afternoon

Triage and writing are separate jobs and mixing them is what slows people down. If you write as you read, a polite refusal pulls you into a five minute exchange while the pricing question waits. Clear the inbox first, then write.

Twice a day covers most inboxes. A morning pass catches everything from overnight and books meetings for the same day. An afternoon pass empties the queue so tomorrow starts clean.

Turn notifications off between passes. A reply that arrives at 11:04 doesn't need you at 11:05, and every interruption restarts the sorting you were halfway through.

1. **Scan without typing.** Open every new reply and drop it into a bucket. No answers in this pass, however easy one looks.
2. **Answer the interested ones.** Send two or three concrete times or your scheduling link. The goal of this message is a slot in the calendar, not a conversation.
3. **Give the curious ones a next step.** Answer their question in two sentences, then name what happens next: a call, a short video, a one page summary. Interest without a specific ask fades in a day.
4. **File the rest with a date.** Archive refusals and wrong-person replies, and write down the date you'll revisit them. A refusal with no date is a lead you've thrown away.

## Write the reply the intent calls for

A buyer asking about price wants a number or a call. A curious reader wants one useful detail and a reason to keep talking. Send both the same template and the thread dies after two messages, which people then blame on LinkedIn.

Keep replies under about sixty words. Long messages on a phone screen get skimmed, and a skimmed message earns a 'thanks, will think about it' that goes nowhere.

For a wrong-person reply, ask for the right name once, in one line. 'Who runs this now?' gets an answer often enough to be worth asking, and then you archive with a date.

- **them:** Interesting. We tried something like this last year and nobody used it after week two.
- **you:** That's the usual failure. What broke, the setup or the rollout?
- **them:** Honestly, the rollout. No owner on our side.
- **you:** Then it's worth 15 minutes to see whether that changes here. Thursday at 10 or 2?
- **draft:** Template for a curious reply: 'Fair question. Most teams hit [problem] in the first month and fix it by [specific thing]. Worth a short call to see if it applies to you? Thursday 10 or 2.'

> Never open a reply with a question about how their week is going. It hands them an easy exit and delays the one thing you want to ask.

## Put a date on every parked lead

Most people who say 'not now' mean it. That doesn't make them worthless. It means the useful moment is later, and the only thing that makes later work is a date written somewhere you'll see it.

Put the date in the note or the tag, not in your memory. When it arrives, send one short message that mentions the reason they gave. Don't re-pitch and don't attach anything.

```
Hi [name], you said [reason] back in [month]. If that's cleared, is a 15 minute call worth it? If not, no problem, I'll close the loop.
```

## Doing this with Kinlead

Kinlead puts replies from every campaign into one [unified inbox](/features/unified-inbox) and sorts them by intent, with interested replies first. You also get an email when someone replies, so the inbox doesn't need watching all day.

Each campaign chooses how replies are handled. You can take over at the first reply, have the AI answer until there's real interest, or let it book meetings on your scheduling link. If you want to read every reply before anything sends, take the option that hands the conversation to you at the first reply.

Kinlead sends at most one action every 5 minutes per LinkedIn account, inside the daily limits and send window you set, and it pauses invites on an account and emails you when LinkedIn pushes back.

## Related

- [Reply handoff workflow](https://getkinlead.com/ai-reply-handoff-workflow.md)
- [Book demos from LinkedIn](https://getkinlead.com/use-cases/book-linkedin-demos.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

**What if one reply fits two buckets?**

Use the bucket that decides your next move. 'Interesting but no budget until Q3' is a timing refusal, so it gets a date in Q3 even though the wording sounds warm.

**How long should one triage pass take?**

A few minutes on a normal day. If it takes longer, you have too many buckets or you're writing replies during the pass instead of after it.

**Should I put every reply into a CRM?**

Only the interested ones. Copying curious and refused replies into a CRM fills it with records nobody will work, and the pipeline stops meaning anything.

**What do I do with out-of-office replies?**

Treat them as a refusal with a date. Set the date for the day after they're back and send one short note then.

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