LinkedIn campaigns with Accept / Reply branches

Manual LinkedIn work dies when reps forget follow-ups. Lynkin campaigns keep the next step queued. Branching on accept/reply means interested prospects get a different path than silent connections.

Build invite → wait → message → branch trees that match how real conversations unfold. Keep sequences short enough that copy stays fresh and caps stay human.

If your current tool only fires linear drips, expect a redesign session — not a paste import — when you move to Accept/Reply logic.

Write the operating rule down so the next hire does not reopen the architecture debate. Companion-first Lynkin keeps LinkedIn authentication on the operator machine while the app owns campaigns, lists, inbox CRM, warm-up, risk caps, and lifecycle analytics. That story is easier to explain to security than a remote browser farm, but it still requires available live sessions during send windows, conservative pacing, and humans who own replies the same day.

Refuse ban-rate theater when vendors pitch restriction percentages nobody can verify. Measure accepts, replies, and time-to-first-human-response. Pause on LinkedIn warnings with Activity Control, fix targeting and copy, and restore volume only after the seat looks healthy again. See /linkedin-automation-safety, /security, and /pricing for the honest companion-first frame — free trial, then Personal $10 or Business $149.

Campaign logic lives in the app; sends happen on your live LinkedIn tab. That keeps sequencing powerful without requiring a remote LinkedIn password vault.

Jobs claim when the companion is available. Laptop-closed overnight sending is not the model — daytime paced windows are. Document that constraint before you promise agency SLAs.

See /features/chrome-companion for pairing and security narrative.

Write the operating rule down so the next hire does not reopen the architecture debate. Companion-first Lynkin keeps LinkedIn authentication on the operator machine while the app owns campaigns, lists, inbox CRM, warm-up, risk caps, and lifecycle analytics. That story is easier to explain to security than a remote browser farm, but it still requires available live sessions during send windows, conservative pacing, and humans who own replies the same day.

Refuse ban-rate theater when vendors pitch restriction percentages nobody can verify. Measure accepts, replies, and time-to-first-human-response. Pause on LinkedIn warnings with Activity Control, fix targeting and copy, and restore volume only after the seat looks healthy again. See /linkedin-automation-safety, /security, and /pricing for the honest companion-first frame — free trial, then Personal $10 or Business $149.

Enroll ICP lists into campaigns with clear ownership. Avoid double-touching the same prospect across seats by keeping enrollment in one workspace.

Clean titles, geographies, and exclusion rules before volume. A branched sequence on a bad list still burns trust.

Agencies should separate client lists per workspace and forbid dual automation of the same LinkedIn account in another tool.

Write the operating rule down so the next hire does not reopen the architecture debate. Companion-first Lynkin keeps LinkedIn authentication on the operator machine while the app owns campaigns, lists, inbox CRM, warm-up, risk caps, and lifecycle analytics. That story is easier to explain to security than a remote browser farm, but it still requires available live sessions during send windows, conservative pacing, and humans who own replies the same day.

Refuse ban-rate theater when vendors pitch restriction percentages nobody can verify. Measure accepts, replies, and time-to-first-human-response. Pause on LinkedIn warnings with Activity Control, fix targeting and copy, and restore volume only after the seat looks healthy again. See /linkedin-automation-safety, /security, and /pricing for the honest companion-first frame — free trial, then Personal $10 or Business $149.

Campaigns respect warm-up and daily risk caps. Volume is a dial you set — not a firehose that ignores LinkedIn soft limits.

New seats and recovering accounts should enroll smaller cohorts. Do not import your entire TAM on day one to “test the product.”

Details: /features/warmup-risk-caps, /guides/linkedin-warmup, /guides/linkedin-connection-limits.

Write the operating rule down so the next hire does not reopen the architecture debate. Companion-first Lynkin keeps LinkedIn authentication on the operator machine while the app owns campaigns, lists, inbox CRM, warm-up, risk caps, and lifecycle analytics. That story is easier to explain to security than a remote browser farm, but it still requires available live sessions during send windows, conservative pacing, and humans who own replies the same day.

Refuse ban-rate theater when vendors pitch restriction percentages nobody can verify. Measure accepts, replies, and time-to-first-human-response. Pause on LinkedIn warnings with Activity Control, fix targeting and copy, and restore volume only after the seat looks healthy again. See /linkedin-automation-safety, /security, and /pricing for the honest companion-first frame — free trial, then Personal $10 or Business $149.

Pair campaigns with lifecycle analytics — enrolled → invited → accepted → messaged → replied — so you improve copy and pacing with evidence.

Low accepts → tighten ICP and invite copy. High accepts, low replies → improve first messages. High replies, low meetings → fix inbox ownership and handoff SLAs.

See /features/analytics. Refuse vanity “sends today” as the only KPI.

Write the operating rule down so the next hire does not reopen the architecture debate. Companion-first Lynkin keeps LinkedIn authentication on the operator machine while the app owns campaigns, lists, inbox CRM, warm-up, risk caps, and lifecycle analytics. That story is easier to explain to security than a remote browser farm, but it still requires available live sessions during send windows, conservative pacing, and humans who own replies the same day.

Refuse ban-rate theater when vendors pitch restriction percentages nobody can verify. Measure accepts, replies, and time-to-first-human-response. Pause on LinkedIn warnings with Activity Control, fix targeting and copy, and restore volume only after the seat looks healthy again. See /linkedin-automation-safety, /security, and /pricing for the honest companion-first frame — free trial, then Personal $10 or Business $149.

Sequences that send without owners recreate spam patterns. Assign inbox owners before you raise campaign caps.

Tags, notes, assignees, and snooze live beside campaign context so Accept/Reply branches do not dump into an unowned LinkedIn tab pile.

Product page: /features/inbox-crm. Authority explainer: /guides/linkedin-inbox-crm.

Write the operating rule down so the next hire does not reopen the architecture debate. Companion-first Lynkin keeps LinkedIn authentication on the operator machine while the app owns campaigns, lists, inbox CRM, warm-up, risk caps, and lifecycle analytics. That story is easier to explain to security than a remote browser farm, but it still requires available live sessions during send windows, conservative pacing, and humans who own replies the same day.

Refuse ban-rate theater when vendors pitch restriction percentages nobody can verify. Measure accepts, replies, and time-to-first-human-response. Pause on LinkedIn warnings with Activity Control, fix targeting and copy, and restore volume only after the seat looks healthy again. See /linkedin-automation-safety, /security, and /pricing for the honest companion-first frame — free trial, then Personal $10 or Business $149.

Sales: short invite + value-first message + break-up path for silence. Recruiting: role-specific first touch + soft follow-up + nurture tag for later reqs. Founders: ultra-tight ICP with personal proof points — fewer seats, sharper copy.

Avoid seven-step novels. Long sequences amplify weak targeting. Prefer two strong touches and fast human reply over endless automation.

Review templates quarterly the same way you review caps.

Write the operating rule down so the next hire does not reopen the architecture debate. Companion-first Lynkin keeps LinkedIn authentication on the operator machine while the app owns campaigns, lists, inbox CRM, warm-up, risk caps, and lifecycle analytics. That story is easier to explain to security than a remote browser farm, but it still requires available live sessions during send windows, conservative pacing, and humans who own replies the same day.

Refuse ban-rate theater when vendors pitch restriction percentages nobody can verify. Measure accepts, replies, and time-to-first-human-response. Pause on LinkedIn warnings with Activity Control, fix targeting and copy, and restore volume only after the seat looks healthy again. See /linkedin-automation-safety, /security, and /pricing for the honest companion-first frame — free trial, then Personal $10 or Business $149.

Trial at /signup, pair the companion, build one campaign with Accept/Reply branches, enroll a small list, enable warm-up, and review analytics after a week.

Migrate from Expandi, Dripify, Waalaxy, or Dux-Soup by rebuilding logic — not by expecting a perfect one-click clone. Alternatives hubs: /alternatives.

Pricing: /pricing — free trial, Personal $10, Business $149.

Write the operating rule down so the next hire does not reopen the architecture debate. Companion-first Lynkin keeps LinkedIn authentication on the operator machine while the app owns campaigns, lists, inbox CRM, warm-up, risk caps, and lifecycle analytics. That story is easier to explain to security than a remote browser farm, but it still requires available live sessions during send windows, conservative pacing, and humans who own replies the same day.

Refuse ban-rate theater when vendors pitch restriction percentages nobody can verify. Measure accepts, replies, and time-to-first-human-response. Pause on LinkedIn warnings with Activity Control, fix targeting and copy, and restore volume only after the seat looks healthy again. See /linkedin-automation-safety, /security, and /pricing for the honest companion-first frame — free trial, then Personal $10 or Business $149.