Who wrote last, not what is unread
The agent lists your conversations, reads the recent ones and reports the threads where the last message is not yours. That is the honest definition of waiting on you, and it surfaces exactly the ones the interface has already marked as handled.
“What LinkedIn messages have I not answered this week?”
“Anything waiting on me that mentions pricing or a demo?”
Age is the second axis
A message from this morning and one from three weeks ago are not the same problem. Asking for the oldest unanswered threads first is usually more useful than the newest, because the recent ones are still in your head and the old ones are the ones that cost you something.
Filter before you read everything
Reads count against the daily budget of about a hundred actions per account. Narrowing by recency or by keyword before reading each thread is not only cheaper, it produces a better answer: a triage of twelve relevant conversations beats a summary of two hundred.
Triage is not answering
The output is a list and a reason for each. Drafting comes next, per conversation, and sending after that — each an explicit step. An agent that answers the whole backlog automatically is how a contact gets a generic reply to a specific question.
The same question across channels
Once WhatsApp and a mailbox are connected, ask it once for everything: what is waiting on me, anywhere. That is usually the version people keep using, because the inbox that hurts is rarely only LinkedIn.
What to do with the list
A triage is only useful if it ends in actions. The natural sequence is: the list, then one draft for the two that matter, then send after you read them. Asking for drafts on all twelve produces twelve generic messages, which is worse than leaving them unanswered — a late specific reply beats a prompt vague one on LinkedIn.
Common questions
Why not just use LinkedIn’s unread filter?
Because it is unreliable: opening a notification on your phone marks a thread read without you answering. Reading who wrote last is the only accurate test.
Does reading them mark them as read?
No. Reading through the tools has no visible effect for your correspondent; marking read is a separate action.
Can it draft the answers?
Yes, one conversation at a time, and sending is still an explicit step you request.
How LinkedIn works with Nilyo
Connection. Secure hosted sign-in (your LinkedIn credentials go to LinkedIn, never to the agent). Sales Navigator and Recruiter are detected automatically when your account has them.
What your agent can do. People and company search, profile lookup from a name or URL, your network and invitations, private conversations (classic, Sales Navigator, Recruiter inboxes), posts, comments and reactions, job postings and applicants, Recruiter projects.
Pacing and safety. About 100 actions per day per account, profile views and searches included; calls are serialized so an agent can never run LinkedIn requests in parallel.
- Profile URLs are resolved to stable profile IDs before any action.
- Invitations carry an optional note of up to 300 characters.
- Private or restricted profiles return an explicit “not accessible” result instead of a retry loop.
All LinkedIn guides
Related guides
Give Nilyo to your agent.
Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.