How to Route LinkedIn Inbox Replies to Pipeline Stages with Claude MCP
· how-to
Your connect agent worked — replies are in. Now classify intent, move pipeline stages, and hand warm leads to AEs without living in LinkedIn.com. Claude MCP reads mirrored threads in Item 12 and updates CRM records; you stay in control of every outbound send via Review.
Define reply categories
- Interested — wants meeting or demo → move to Discovery, AE handoff
- Timing — not now, follow up next quarter → add task, keep in Nurture
- Referral — points to colleague → add note with referral URL, new contact import
- Hard no — unsubscribe tone → Closed Lost tag, stop agent
- Ghost — single word or emoji → no stage change, optional bump task
Triage prompt (copy-paste)
Ask Claude with Item 12 MCP:
- "List unread LinkedIn threads from list_inbox. For each, read_thread, summarize intent, and suggest: pipeline stage, tag, and next action. Do not send messages — read only. Output a table: contact name, intent category, suggested stage, suggested note."
Batch update prompt
After you review Claude's table, confirm updates explicitly:
- "For contacts [paste profile URLs]: move_deal to Discovery for interested replies; add_note with AE handoff template; add_task due in 2 days for timing replies. Stop outbound agent for hard-no contacts."
- Always pass profile URLs — prevents wrong-contact updates
AE handoff note template
Note text: "SDR: positive reply [date]. Thread summary: [one line]. Suggested opener for AE: reference [topic from reply]. Deal moved to Discovery." AEs open contact → full mirrored thread + note → pre-call brief via MCP get_contact.
Metrics
Filter pipeline by campaign tag (e.g. outbound-q3). Track reply-to-meeting conversion weekly. Compare against How to Build an SDR Agent connection-request accept rates — low replies mean fix connection note before inbox routing volume.
Can MCP send follow-up DMs during routing?
MCP can queue send_message actions — they land in Review like agent sends. Many teams route stages first, approve sends separately.
What if Claude misclassifies intent?
Triage prompt is read-only. You approve batch updates contact-by-contact or edit the confirmation list before move_deal runs.
Does this work for email replies?
This guide covers mirrored LinkedIn inbox. Email integration is separate; pipeline stages are shared on the contact record.