All LinkedIn DMs.
Every account.
One pane.
Stop logging into four LinkedIn accounts a day. Every direct message across every connected identity lands here, sorted by recency, filterable by account, linked to the lead it's about.
LinkedIn DMs only - on purpose.
Comments and engagements have their own home in the Signal Agent. Connection requests live in LinkedIn's own queue. One surface, one job.
Toggle identities on and off.
The unread count follows.
One person runs multiple LinkedIn accounts, a builder identity, a sales identity, maybe a recruiting one. The filter is built for that reality.
Two kinds of thread.
One gets linked.
A 1-on-1 maps cleanly to a lead record, automatic, by LinkedIn URL. A group chat stays on its own because it doesn't belong to one person.
Matched by LinkedIn URL. If the participant isn't a lead yet, they become one, enrichment queues within 6 hours.
Group threads don't map cleanly to a single lead, so they stay as their own thing, visible, searchable, but outside the per-lead conversation history.
When a reply lands, three ways to handle it.
Reactive nodes in a workflow park leads until a LinkedIn event fires. The inbox is the trigger point. Pick your level of automation per node.
Notify only
A notification lands in the inbox. No agent, no draft. You reply (or don't) on your own time.
Auto-respond
Agent reads the message + history + lead context + voice. Drafts and sends in one pass. Workflow continues.
Draft & review
Agent drafts, you review. Approve, edit, or reject before it's sent. The human-in-the-loop mode.
The human-in-the-loop mode, end to end.
Inbound reply → AI drafts with full context → you review → sent via the account's browser session → workflow resumes. Six steps, one of them yours.
Every conversation becomes a lead.
No 'import this thread' button, no sync step. If someone messaged you, they're in your CRM, matched to an existing record or created with enrichment queued.
Manual sends count too.
One cap per account.
Hitting 'send' in the inbox uses the same daily budget as an automated workflow message. LinkedIn sees actions, not sources, so the safety layer doesn't either.
One budget per account. Messages you type in the inbox share the daily cap with messages workflows send. LinkedIn doesn't care where the action came from, and neither does the safety layer.
Send everything through CampaignStack. We can't see messages you write directly on LinkedIn, so sends that bypass us won't count against the budget, and the account can drift over its real limit without warning. Keeping the inbox as your send path is what makes the cap accurate.
Two surfaces. Same context.
Automated drafting ships today, the reactive-node agent reads context and sends (or queues for review) on its own. Manual drafting from the inbox compose box is next up: same model, same inputs, triggered on your click.
Automated drafting
Reactive nodes trigger AI drafting on inbound reply. Runs with full context, no human prompt needed.
Manual drafting
One-click draft from the compose box. Same context the workflow agent gets \u2014 you edit and send.
Hey Sara, thanks for reaching out. Governance and auditability are squarely what we're thinking about too. Happy to jump on a quick 15 to compare notes on how D-POAF frames it.
One inbox. Every identity.
Connect your first LinkedIn account, and every reply you get lands here, with context, voice, and a workflow hook if you want one.
Start free trial