Inbox for LinkedIn replies (human-in-the-loop)
Inbox for LinkedIn replies
Console Inbox is the human-in-the-loop surface for LinkedIn message flows. Prospects reply in LinkedIn; you answer here.

When the flow pauses
If a path uses Suggested Replies (sender), the agent waits for an operator. The composer explains that the flow is paused until you send a reply. Sending unblocks the run (operator_acted). Already-connected prospects can reach Inbox if the flow DMs them after Is connection Yes.
Suggestion chips follow the classified sentiment of the prospect's reply (the same Smart Lead / lead-outcome signal): positive (or not yet classified) shows the positive list; negative shows the negative list. If a negative reply has no negative chips, type a reply from scratch — the flow still waits until you send.
Day-to-day workflow
- Watch Replies Waiting on the Dashboard.
- Open Inbox, pick the thread, review context and suggestions.
- Edit if needed, then send.
- If LinkedIn and SMOC disagree (offline activity), use Resync flow status on the thread.
What Inbox is not
Inbox is not an unsupervised LLM that auto-sends final operator replies. Suggestions help; you stay accountable for sender reputation and tone.
From an AI client
A write-enabled MCP or REST key can send a text-only reply with inbox_threads_send (threadId, body, idempotencyKey). It cannot attach files or start a LinkedIn outreach campaign. Setup: Connecting SMOC with MCP.
Related
Stay close to the shift in AI sales
Get product updates and perspective on proactive AI agents, multichannel orchestration, and conversion—without the noise.