Most “AI replies” are auto-responders that fire the same CTA on every reply. LinkedReach’s agent reads the lead’s role, skills, and recent posts, builds the conversation, scores warmth on every turn, and only fires the meeting CTA once the lead is genuinely warm. Then it offers real calendar slots and books.
On every inbound, the agent runs the same loop. Read the lead’s profile, recent posts, and full thread context. Score warmth on a 0–100 scale with explicit rubrics that resist drift. Decide whether to keep building rapport or fire the meeting CTA — gated on a per-CTA warmth threshold you set. Write in the lead’s tone and length when configured to mirror, with a different angle than every previous message in the thread.
The CTA only fires when the lead has earned it. Before that, the agent keeps the conversation going. After it, the agent pulls real open slots from your calendar (Microsoft 365 supported), proposes them in the message, and books on confirmation. No static booking links. No premature pitch.
New campaigns ship with the reply-preview / approval flow on by default. The agent does the reading, scoring, deciding, and writing — and stops at “awaiting approval”. You read the draft, edit if you want, and one click sends. Once you trust the agent on a campaign, flip auto-send on.
Every drafted, edited, approved, rejected, and sent message is logged with the warmth score, the intent label, and the reasoning the agent used. Review thread-by-thread, audit any time, see the full reasoning trail behind any sent reply.
LinkedIn caps you at 25 connection requests per sender per day. That cap is the most expensive resource in the system. Sending one to someone who is obviously not in your ICP — the wrong title, the wrong company size, the wrong region — is a waste of a slot you cannot get back.
Before any campaign action fires, Pilot reads the lead's profile against your ICP brief. It returns a fit score, the reasoning behind the score, and a recommended action: send, skip, or flag for review. Bad-fit leads never reach the queue. Edge cases get human eyes.
A sender hand-personalising thirty messages a day burns out at week two. Pilot takes that job — producing one or two lines per lead that reference the prospect's role, company, and recent activity, dropped into the message via tokens.
Same model, your voice. The campaign-level ICP brief tells Pilot what your offer is and what tone to use. Reply rates do not come from cleverness in the opener — they come from sounding human at scale, which is exactly what Mad Libs templates can't do.
Building a five-step LinkedIn sequence from scratch is the highest-friction setup task in outreach. Most teams ship a passable v1 and never edit it again. Pilot solves the cold-start problem: give it your offer, your ICP, and your pod's voice, and it drafts the whole sequence — connect note, follow-up, message two, the InMail, the bump — in one pass.
Each step is tuned with the right level of variance for its job. The InMail and the first connect note get tighter, more deterministic generation because they're high-stakes single-shot moments. The follow-ups get looser variance because Pilot has more chances to land.
Give an LLM a prompt a thousand times and a few stock phrases will appear in 80% of the outputs. "Hope this finds you well." "Wanted to reach out about." "Quick question." Every recipient who has been targeted by a campaign before recognises the smell.
Every generated message is checked against the pod's prior sends with a phrase-overlap score. Above the threshold, Pilot regenerates once with explicit "do not reuse phrasing" instructions. The result is messaging that stays fresh as the pod scales from one sender to ten to thirty.
Triage of inbound replies is where the time goes. A campaign at scale produces hundreds of replies a week, and a meaningful share of them are not real opportunities — they're polite passes, OOO notices, "wrong person" referrals, or genuinely negative.
Every inbound is classified the moment it arrives: interested, objection, not now, wrong person, negative, OOO, or auto-reply. Each one is routed to the right queue. The closer sees only the queue that matters. The pod sees aggregate signal — which titles convert, which industries push back, where the funnel is leaking.
Reply latency kills conversion. A reply that lands at 11pm and gets answered at 9am the next morning has already lost a meaningful share of intent. Agent Mode drafts a response within seconds — surfaced for one-click approval or sent automatically, depending on the campaign setting.
On a warming reply, the agent drafts a contextual response, asks the qualifying questions you specified at campaign setup, and proposes real calendar slots when warmth crosses the threshold. Operators choose whether replies are sent automatically or surfaced for one-click approval. New campaigns ship with approval-by-default; flip to auto-send once you trust the agent.
The cost of an autonomous reply going wrong is not symmetric. A clumsy reply to "what's your pricing?" costs you a meeting. A clumsy reply to a GDPR request, a contract objection, or a legal threat costs you a brand — and possibly a regulator letter.
Every inbound is keyword-scanned against a list of high-stakes phrases — legal, GDPR, contract, pricing, refund, complaint, "remove me", lawyer, and the rest. On a match, auto-send is disabled for that thread, an alert is filed, and a human picks it up. The agent gets to do the easy 80% and is locked out of the dangerous 20%.
LLMs lose the plot in long conversations. The topic that was set in message one drifts as new messages pile up, and by message twelve the agent is replying to the immediate previous message with no memory of what the original outreach was actually about.
When a thread runs past ten messages, Pilot keeps the very first message (which sets the topic), the most recent nine (which carry the live context), and replaces the dropped middle with a single elision marker. No extra LLM call. The agent stays anchored to what the conversation was originally about.
Most outreach tools ask you to trust the AI on day one — with your real LinkedIn account, your real prospects, and your real reputation on the line. Pilot doesn’t. Open the simulator on any campaign and the agent runs the full sequence against synthetic-but-realistic leads. You read every message the AI would write, watch how it responds to five different reply personas (warm, curious, busy, hostile, ghosted), see the warmth scores, and check that the calendar slot picker is hitting your actual Microsoft or Google calendar — all without burning a single connection request.
Four objections most operators have about AI outreach, defused in one screen:
The simulator runs as fast or as slow as you want it — 1x to step through every action, 5000x to watch a 14-day sequence collapse into 30 seconds. Pause, rewind, change the persona, run again. Real prospects don’t enter the picture until you’ve seen the AI behave on synthetic ones.
Outreach buyers in 2026 are being marketed at with model names. We think that's the wrong unit of decision — the leading model will change four times in the next two years, and you will care about the workflow that ships, not the badge on the box.
Does the system qualify before it spends a daily-cap action? Does it refuse to auto-reply on legal phrases? Does it stay on-topic in a 30-message thread? Does it learn from every reply the pod sends, or does each sender train its own Pilot in isolation? These questions outlast any model release schedule.
Invite-only early access. Hand-reviewed within one business day. Watch the agent score warmth, draft replies, and book meetings — with operator approval where you want it.