The Turbo Messenger for LinkedIn

Inbox-Zero principles. Split inboxes, follow-ups and sequences, snippets, cleared from the keyboard in a beautiful and snappy desktop app. Built to keep your account within LinkedIn’s rules on automation.

E archives·H reminds·L labels·; snippets·S sequences

Hey! Loved your post on outbound sequencing. We are wrestling with the same thing.

Quick one: do you have 20 minutes next week to compare notes on pipeline?

We just hit 50 customers 🎉 and I remembered you asked about our onboarding flow.

Saw you are hiring. Happy to send over two people who would be a great fit.

Sending the deck over now. Curious what you think of the pricing page.

Thanks for the intro. We are talking to them on Thursday.

Inbox zero

Nothing left here. Archived threads come back on their own when someone replies.

Sofia, great meeting you at the summit. Happy to compare notes any time.

MonHey! Loved your post on outbound sequencing. We are wrestling with the same thing.

3mWrite a reply… Type ; for snippets

Pick a conversation

KJ to move · ↵ to open · ? for shortcuts

LinkedIn's inbox was built for people who get five messages a week.

No triage. No follow-ups. No search worth the name. So the good conversations sink, and the ones you meant to return to are three screens down by Thursday.

Built for people who get far more than five

- FoundersInvestors, hires and customers in one list.

- Sales repsEvery open deal, and the ones you meant to nudge.

- RecruitersForty candidates, each at a different step.

- InvestorsDeal flow that arrives as DMs and deserves a reply.

- PartnershipsIntros that go quiet after the first exchange.

- ConsultantsLeads that come from a post and vanish into the feed.

One inbox per topic

Label a conversation and it gets its own view. Hiring in one, fundraising in another, and the noise nowhere near either.

Hey! Loved your post on outbound sequencing. We are wrestling with the same thing.

Quick one: do you have 20 minutes next week to compare notes on pipeline?

We just hit 50 customers 🎉 and I remembered you asked about our onboarding flow.

Saw you are hiring. Happy to send over two people who would be a great fit.

Sending the deck over now. Curious what you think of the pricing page.

Thanks for the intro. We are talking to them on Thursday.

Are you around at the summit next month? Would be good to catch up in person.

Would love your take on our hiring plan for the platform team.

Your hands never leave the keyboard

E archives. H sets a reminder. L labels.J and K move, ↵ opens, ; pulls in a snippet, ⌘K does everything else. An inbox you can clear in one pass, without aiming at anything.

Archive

Done with it? Gone. It comes back on its own if they reply.

Quick one: do you have 20 minutes next week?

Remind me

“Tomorrow”, “next wednesday”, “in 4 days”. It resurfaces when you said.

Sending the deck over now. Curious what you think.

Label

A label is an inbox of its own. File it and it lives there.

Saw you are hiring. Happy to send two people over.

Everything, without looking down

EArchive

Rather press them yourself? Take the tour, on conversations that are not real.

The thread comes back. It does not send.

Put someone in a follow-up sequence and the conversation resurfaces when the next step is due, with the message already drafted from your snippet and the blanks still blank. You read it, you finish it, you send it. Gatling never messages anyone for you.

- A reminder that remembers which step you are on

- Drafted from your snippet, never sent from it

- Any reply stops the sequence on the spot

Warm intro

Nothing sends on its own- Opening message - Aug 26

- 2Gentle nudge - +3 days · today

- 3Last follow-up, then leave it - +7 days

Sending the deck over now. Curious what you think of the pricing page.

Hi Mei, circling back on the deck. The bit I would most like your read on is {the part you are unsure about}. Any chance of 15 minutes this week?

A plan for one conversation

Build a sequence once: a few steps, each a few sending days after the last, each starting from a snippet you wrote. Put a conversation in it withS and it moves across the board as you send each step.

- Delays count sending days, so “three days” from a Friday means Wednesday

- Due times stay inside working hours, each moved by up to ninety minutes, so a cohort never lands at once

- The first reply moves the card to Stopped. That is the point of it.

Sofia Martins

Head of Growth · Northwind Robotics

- ;introHi {{firstName}}, I came across {what they are building}…

- ;intro callWould 20 minutes {day} work?

- {{firstName}} fills itself in

- {blank} waits for you

- Tab jumps to the next one

Templates that cannot go out generic

;intro expands.{{firstName}} fills itself in.{what they are building} does not, and the send button stays disabled until you write it. The fastest way to send a message that is actually about the person receiving it.

- Send the outbound postSofia Martins

- Intro to SableMarcus Bell

- Chase the CFO introMia Chen

- Ask for the hiring planGrace Liu

The things you owe people

A todo belongs to a person, not a thread. Add one from a conversation, from Connections, or from an invitation, and it waits in its own view until you pressX. Done ones stay: a finished todo is the record that you did the thing.

Your LinkedIn inbox, without LinkedIn

Gatling lives in your dock. It reads your inbox through your own LinkedIn session, shows what is unread on the icon, and never puts the feed between you and a reply.

- In your dock, not in a tabA window of its own. ⌘Tab to it like any app, and close the browser without losing your inbox.

- Unread, on the iconThe badge counts the conversations waiting on you, and drops as you clear them.

- No detour through LinkedInNo feed, no profile views, no people you may know. You open Gatling to answer someone and leave when you have.

Built to keep your account

LinkedIn restricts accounts that behave like software. Gatling is built not to.

Nothing sends on its own, ever

LinkedIn bars software that automates activity, and this is the line it draws hardest. Every message leaves through the same composer a manual reply uses, when you press ⌘↵. A sequence schedules a reminder, not a send: the draft waits for you.

No way to send the same message to several people

Sending one message to many is the surest way to get an account restricted, so the product has no path for it: no multi-select send, no bulk queue. Snippets with blanks cannot go out until each blank is written, so what you send is about the person receiving it.

Reminders are jittered and kept to working hours

Forty reminders due at exactly 09:00 on Thursday would be a signature, and a pile of threads you would rush through. Each is moved by up to ninety minutes and kept inside 08:00 to 19:00 on working days. A follow-up at 03:00 is one you either miss or answer at 03:00.

A daily ceiling you set, that tells you when you are near it

What LinkedIn watches for is activity that suddenly changes shape: ten messages a day, then a hundred. That check cannot see who pressed the button, so a ceiling is what keeps the pattern ordinary. It is a rolling 24-hour meter in the status bar, and it warns rather than greying out the button, because a limit you cannot see looks like a broken app.

Any reply stops the follow-up immediately

The point of a follow-up is to stop the moment it works. When the other person replies, the enrolment ends: no further step comes due, the draft is dropped, and the card moves to Stopped on the board.

17 of 25 sent

8 left. Steady volume is what keeps an account ordinary, so the meter is on the screen rather than in a settings page.

Forty follow-ups due on Thursday do not all land at 09:00. Each is moved by up to ninety minutes, and none outside your working day.

The point of a follow-up is to stop the moment it works.

Your inbox stays on your machine

Conversations and messages are cached inside the Gatling app on your Mac and never reach our servers. What syncs is your organising layer: labels, notes, snippets and sequences. We could not read your DMs if we wanted to.

No password, either. You sign in to LinkedIn once, inside Gatling, and it reads that session. Sign out of LinkedIn and it stops working.

Your own session, your own machine, your own IP. Nothing in between.

- Conversations

- Messages

- Contacts

Cached here, and only here.

- Labels

- Notes

- Snippets

- Sequences

Only your labels, notes, snippets and sequences. No message bodies, in any form.

Clear your LinkedIn inbox before your coffee goes cold

Not on a Mac yet? Leave an address and we will write when there is a build for you.

One email. No newsletter.