Swimlane inbox: LinkedIn conversations with the contact beside them

LinkedIn’s own messaging is fine for reading messages. What it cannot tell you is whose turn it is, what you promised this person three weeks ago, or which of forty threads needs an answer before lunch. The Swimlane inbox is a LinkedIn inbox built around those three questions: every conversation from your account, cut into views by who spoke last, with the contact record open beside the thread.

This is a tour of what it does today, and of what it deliberately does not do.

What LinkedIn’s messaging does, and where it stops

Credit where it is due. LinkedIn lets you filter conversations by Unread, My Connections, InMail or Starred, mark a thread as unread, star it, archive it and search by name or keyword. For a personal network, that is enough.

For selling, three things are missing:

• Whose turn it is. Unread only tells you what you have not opened. A message you glanced at on your phone becomes “read” and drops out of the filter, even though you never answered it.
• Context on the thread. No note, no tag, no pipeline stage. The history of the relationship lives in your head, a spreadsheet or another tab.
• A way to bring a thread back. When someone says “ask me again after the budget meeting”, nothing puts them back in front of you on that date.

A LinkedIn inbox organised by who spoke last

Once your LinkedIn account is connected, every conversation syncs into Messaging. There is nothing to import. The list can be cut five ways:

• All: every conversation, minus archived contacts.
• Unread: threads you have not opened.
• Last message by contact: the ball is in your court, whether you have read the message or not.
• Last message by me: you spoke last. These are your follow-up candidates.
• Never replied: the contact wrote last and you have not even opened the thread.

If you only use one, use Last message by contact. Unread stops telling the truth the moment you open a message; this view does not, because only your reply (or archiving the contact) takes a thread out of it.

The rest of the sidebar

Next to Messaging, the sidebar holds the pages that turn a list of threads into a working queue:

• Archived: conversations with the contacts you have archived.
• Reminders: every contact with a reminder, filtered by To do, Future or Done.
• A page per tag (plus No tag) and a page per pipeline, so you can work one segment, say “partners” or “demo booked”, without the rest of the noise.
• Invitations: sent, received and declined.

How fresh the list is

When you open the inbox, Swimlane pulls your latest conversations from LinkedIn, then checks again every 15 to 30 seconds while you are active. It is not an instant push, so a new message can take up to half a minute to show. That is a choice: a live connection held open all day was harder on the LinkedIn session than gentle, regular checks.

The contact record beside the thread

Open a conversation and the contact’s record sits next to it. You answer with the context in view instead of rebuilding it from memory.

• Quick actions: set the pipeline stage, create a reminder, archive the contact.
• Swimlane Analysis: once there is enough history, a summary of the relationship, a recommended next step with a button to turn it into a reminder, and a suggested pipeline stage you can apply in one click.
• ICP fit: the contact’s level against the ideal customer you described, from very low to excellent, with a one-line reason. A level, not a number.
• Source: the lists the contact came from.
• Notes: free text your teammates can read and the contact never sees. The AI draft reads it too.
• Tags and Campaigns: the segments they belong to and the sequences they are in.
• Activity tab: profile visits, invitations sent and accepted, messages, and clicks on the links you sent, all logged without you typing anything.

Writing replies

Templates with variables

Save the messages you write every week (the pricing answer, the calendar link, the polite no) under Manage templates. Each template has one of two types:

• Static: sent as written, with variables filled in from the contact record: {{firstName}}, {{lastName}}, {{fullName}}, {{company}}, {{title}}, {{headline}} and {{location}}.
• AI: your text is the example, and the AI reworks it for this contact from their name, headline and location, the last five messages of the thread, your business context and your tone of voice.

One trap with static templates: a variable takes whatever the profile holds. If the company field is empty, {{company}} goes out empty. Write sentences that still read well when a variable is blank.

The AI draft

When the contact has written last with a real message, in a thread where you have both spoken, a draft reply appears in grey in the message box before you type anything. It has read the conversation, the contact analysis, your notes and your pending reminders, and it writes in the tone of voice Swimlane learns from the messages you write yourself. Accept it, edit it, or ignore it and type your own. When there is nothing useful to say, no draft appears, which beats a filler one.

The icebreaker

On an empty thread, the same box offers an icebreaker drafted from the contact’s profile. Read it as a first line to rework, not as a message to send blind.

Images, GIFs and reactions

The composer sends text, emoji, images and GIFs, with a GIF search built in. You can react to a message with an emoji, delete one of your own messages, and links show a preview. Files, videos and voice notes that people send you are displayed in the thread, but you cannot send them from Swimlane; use LinkedIn for those.

The poke

A poke only works in an existing conversation. Swimlane sends a short message and recalls it a moment later: LinkedIn has already delivered the notification, so the contact gets a nudge without a message to read. Use it rarely. A nudge that repeats becomes noise.

When a campaign writes for you

Messages sent by a sequence land in the same thread as everything else, so the inbox is where automated and handwritten messages meet. The automated ones follow a few rules:

• With virtual office hours turned on, they only go out on the days and at the hours you set.
• They are spaced at random intervals, never on a fixed rhythm.
• Daily ceilings cap them. You can lower a ceiling, never raise it past the plan, and Swimlane refuses to send rather than exceed one.
• A sequence does not stop on its own when someone replies. Put a Replied to message condition in front of every follow-up so people who answered leave the automated path.

The guide on building LinkedIn follow-ups that respect replies covers the setup, and the LinkedIn automation page lists every step and condition.

What the inbox does not do

Knowing the limits saves you from hunting for buttons that are not there:

• No ranking. There is no “priority” or “smart” sort by fit or intent. The views filter by whose turn it is and you decide the order; tag and pipeline pages are how you narrow the list.
• No engagement score on the contact. You get an ICP fit level and the analysis, nothing counted in points.
• No sending of files or voice notes, only images and GIFs.
• No instant push, as explained above.

For a daily routine built on these views and reminders, read LinkedIn inbox zero for sales conversations. For what to write once you are in the thread, see LinkedIn messaging best practices. The LinkedIn inbox feature page has the short version.