Multi-account workspace acceptance behavior
Workspaces on Enterprise and Ultimate plans can have multiple LinkedIn accounts connected at once — typically one account per sales rep, all in the same workspace. WarmySender handles a few subtle invariants for those workspaces, especially around acceptance webhooks.
Why this matters
When LinkedIn fires a 'connection accepted' event for one of your reps, our LinkedIn provider may deliver the event on a sibling LinkedIn account in the same workspace tenant rather than the originating account. This isn't a bug on our LinkedIn provider's side — it's how their tenant-wide webhook fan-out works. The platform handles this by scoping the acceptance lookup to the workspace, not just the receiving account, so the right prospect is stamped regardless of which sibling account received the webhook.
What you'll see on the dashboard
- Acceptance events are stamped on the prospect's enrollment in the campaign that owns the prospect, not on whichever account happened to receive the webhook.
- Slack / n8n / Zapier notifications fire once per acceptance, and the source path (webhook, polling, sales navigator decode, engine-already-connected) is included in the payload for traceability.
- The dashboard accept counter reads directly from the prospect's recorded acceptance time — no separate cache, no double-counting.
What happens if two sibling accounts have the same prospect
WarmySender's bridging logic abort-and-traces if a single acceptance event matches prospects spanning multiple LinkedIn accounts in the same workspace — that situation is rare (we monitor for zero rows in this shape platform-wide) but the defensive guard prevents stamping the wrong prospect. If it ever fires, an admin alert surfaces the conflicting account / prospect / member ID combination so support can investigate.
Acceptance signals — how the platform detects them
1. A real-time notification from our integration partner the moment LinkedIn records the new connection (sub-second). Primary path.
2. 30-minute account-status polling fallback (covers the case where a notification never arrived).
3. Message-received inferred acceptance (when a prospect replies before LinkedIn's relation graph reflects the acceptance).
4. Engine 'already connected' check (when WarmySender retries a step and discovers via our LinkedIn provider that the recipient is already a connection).
All four paths now produce the same outbound notification (Slack / n8n / Zapier) and the same dashboard stamp. The notification tells you which of the four routes detected the acceptance.
Multi-account safety
Each LinkedIn account in your workspace runs its own daily / weekly cap, its own 4-week ramp schedule, and its own per-account budget. Adding a second account doesn't double your sends 'instantly' — each account ramps independently. The team-multiplier benefit is realized 4 weeks after each account is added.