LinkedIn Messaging vs Sales Navigator: Which Context AGNURA Uses
Compare AGNURA on classic LinkedIn Messaging vs Sales Navigator inbox: separate scripts, profile depth, thread sources, rewrite/voice parity, and when to use each surface.
Classic LinkedIn Messaging and Sales Navigator inbox look similar (“type a reply, click Send”) but they are different products in the DOM. AGNURA therefore uses two content scripts so a Sales Nav UI change cannot break Messaging, and vice versa.
This page owns the context comparison. Step-by-step Write Reply on Messaging: How to Write a LinkedIn Reply From Profile and Thread Context. On Sales Nav: How to Write a Reply in LinkedIn Sales Navigator Inbox. Hub: LinkedIn Writing Workflows.
Direct answer
| Dimension | Classic Messaging | Sales Navigator inbox |
|---|---|---|
| URL area | Messaging / overlays on linkedin.com (not /sales/) | /sales/inbox/... and related /sales/ conversations |
| Content script | linkedin-compose-reply.js | linkedin-sales-nav-compose.js |
| Write Reply context | Best-effort /in/ profile + message list (may use Voyager / profile helpers) | Thread-header name/headline + InMail articles |
| Compose field | Contenteditable msg-form editor | textarea (“Type your message here…”) |
| Rewrite | Draft-only | Draft-only |
| Voice to Text | Footer mic | Actions-bar mic (left side) |
| Select Template | In AGNURA messaging menu | In AGNURA Sales Nav menu |
| Auto-send | Never | Never |
If you need deep About / Experience / birthday enrichment, prefer classic Messaging or an open /in/ profile workflow. If you are already in Sales Nav InMail, use the Sales Nav Write Reply path and edit the modal fields when the header is thin.
Why they are separate
Sales Navigator’s compose form and message list do not use classic msg-form / msg-s-* markup. Shipping both surfaces in one injection path would couple fragile selectors. AGNURA:
- Loads the Sales Nav script only on
…/sales/* - Makes classic LinkedIn compose skip
/sales/paths
That keeps Messaging stable when Sales Nav markup changes.
Context map: Write Reply
Classic Messaging
Typical OpenAI inputs:
- LinkedIn reply prompt
- Optional What I want to say
- Optional knowledge base
- Recipient profile (best-effort; may include About, experience, Activity posts, birthday when available)
- Conversation thread from the message list
Sales Navigator inbox
Typical OpenAI inputs:
- Same LinkedIn reply prompt and optional knowledge base / What I want to say
- Recipient name + headline from the conversation header (and lead URL when shown)
- Conversation thread from InMail / message articles in
section.thread-container
Not included from the Sales Nav script alone: full Voyager profile redirect to /in/…, CRM account notes, or lead-list metadata outside the open thread.
Context map: Rewrite and Voice
| Action | Classic Messaging | Sales Navigator |
|---|---|---|
| Rewrite Message | Shared rewrite prompt + compose draft | Shared rewrite prompt + textarea draft |
| Voice to Text | Browser speech; appends to editor | Browser speech; appends to textarea |
| OpenAI on Voice | No | No |
Rewrite never reloads profile or thread on either surface. If you need thread-aware wording, use Write Reply.
Decision framework
| If… | Use… | Because… |
|---|---|---|
| You are in normal LinkedIn Messaging | Classic Write Reply | Deeper profile fetch paths when available |
| You are in Sales Navigator InMail | Sales Nav Write Reply | Correct DOM; header + thread for that conversation |
| You only need to polish typed text | Rewrite Message on that same surface | Draft-only; faster; no thread reload |
| You expected full profile fields on Sales Nav | Edit the modal profile field, or continue in classic Messaging | SN script is intentionally thinner |
Common mistakes
| Mistake | Why it fails | Better approach |
|---|---|---|
Waiting for classic footer buttons on /sales/ | Different script and selectors | Look for AGNURA on the Sales Nav actions bar |
| Assuming Sales Nav = same profile enrichment as Messaging | Separate code path | Compare the two columns above |
| Using one “LinkedIn AI” mental model for invites/comments/posts | Different surfaces | Use the workflows hub |
Checklist
- You know whether your tab URL is classic Messaging or
/sales/ - You picked Write Reply vs Rewrite for the job (context vs polish)
- You reviewed inserted text before clicking Send
- You did not expect AGNURA to send InMail automatically
How this relates to AGNURA
| Capability | Classic Messaging | Sales Navigator |
|---|---|---|
| Separate content script | Yes | Yes |
| Write Reply / Rewrite / Voice | Yes | Yes |
| Select Template in compose menu | Yes | Yes |
| Auto-send | No | No |
| Differentiation | Why it matters |
|---|---|
| Surface-specific context | Prevents false confidence that every LinkedIn draft saw a full profile |
| Human review | Keeps outreach compliant with how you actually use LinkedIn and Sales Nav |
Related reading
- How to Write a Reply in LinkedIn Sales Navigator Inbox
- How to Write a LinkedIn Reply From Profile and Thread Context
- Generate vs Rewrite on LinkedIn
- How AGNURA Uses LinkedIn Profile Context, and What It May Miss
- AGNURA Feature Reference by App and Action
- AGNURA Changelog
Open one classic Messaging draft and one Sales Nav conversation. Compare what appears in each Write Reply modal’s profile and thread fields. That single side-by-side check is the fastest way to internalize this map.
Try AGNURA in Chrome
Draft in Gmail, LinkedIn, WhatsApp, and Reddit. You review every message before send.
Add to Chrome