For agencies
Outbound for every client, from one dashboard.
Each client keeps its own LinkedIn seats, its own messaging, its own numbers. You see all of them.
Gelee runs LinkedIn outbound for agencies that sell it as a standing service. Every client is a separate workspace with its own LinkedIn accounts, its own targeting, its own approved messaging, its own Slack channel and its own report, and anyone who belongs to several workspaces switches between them in one sidebar. Nothing is shared across clients. One client’s restricted account cannot slow another’s, and one client’s blacklist never touches another’s list.
Fit
Who it is for, and who it is not.
A fit
- You run outbound for clients as an ongoing service and the client expects you to answer the replies, not only to send.
- Your clients sell to businesses, so the buyer can be named by title, company size, industry and location before a message goes out.
- Your clients run more than one LinkedIn seat each, or will, and you need each seat warmed and paced on its own rather than the whole fleet moving together.
- You want the same numbers your client sees, per workspace, without building a reporting layer yourself.
Not a fit
- An agency that signs a client for one four-week campaign. A new seat spends its first two weeks ramping and the team does not judge a campaign before 100 invitations have gone out, so there is nothing fair to show inside a month.
- An agency whose own team writes every message and answers every reply, and wants a cheaper sender. HeyReach or Expandi fits that better; the switching guides are honest about it.
- An agency that promises clients a fixed number of meetings. The platform will not set a goal above 20 booked calls a month for any workspace, however many seats it runs, and nobody here will promise a number above it either.
- Clients who sell to consumers or to local trades. Their buyers are not reachable by title on LinkedIn and the filters have nothing to hold on to.
How it runs
What the system does, and what it refuses to do.
One workspace per client
Every table in the platform is scoped to one organisation, and a client is one organisation. Seats, campaigns, prospects, replies, blacklist and bookings for Client A live under Client A and nowhere else. Your people are added as members of each workspace they work on, and a member of more than one sees a workspace switcher in the sidebar.
The practical effect is isolation by default. A seat that LinkedIn restricts stops sending and re-warms on its own; the other seats in that workspace and every other workspace carry on. A person on one client’s do-not-contact list is still contactable for a different client, unless you add them there too.
Seats warm up and pace themselves, one at a time
A newly connected seat sends at 25% of its budget for days 1 to 3, 50% through day 7, 75% through day 14 and full rate after that. The ramp covers invitations, messages, comments, InMails, profile views and searches together. A seat that LinkedIn flags is re-warmed rather than resumed, and after any cooldown it comes back at 25, 50 and 75% over six days.
The engine caps a standard seat at 35 invitations a day and a Sales Navigator seat at 50, inside a weekly ceiling of 200, and the client can set any of those lower from the seat settings. Between actions the gaps are drawn from a long-tailed distribution around a minute, with reading pauses every 8 to 12 actions, inside the seat’s own working hours. Each seat starts its day at a different minute and stops at a different, non-round number, so ten seats for one client do not look like one dispatcher.
Pending invitations are withdrawn after seven days by default, because invitations left pending is one of the three behaviours LinkedIn names as a cause of restriction. Withdrawal is paced too, with caps per seat and per run.
Three ways to build each client’s list, and hard filters on all of them
A search list is a fixed list built by title, location, company size and industry; it runs out and gets refreshed. A tracked-accounts campaign watches a few LinkedIn people the client’s buyers already follow and adds whoever likes or comments on their posts, refilling itself as they keep posting; when you add an account, the platform reads its last three posts and tells you within a couple of minutes whether 60% or more of the engagers match the client’s buyer. A post-keywords campaign watches posts for up to eight phrases you choose, checked weekly, and adds whoever wrote one, with the post saved so the opener can mention it.
Everyone found goes through the same filters before anyone is messaged: job title, required or blocked keywords, location picked from LinkedIn’s own place list, company size and industry. A person who fails is parked in the leads list and never contacted. The rule the team works to is that not a single message should be a bad message, and an agency feels it first, because a bad message goes out in a client’s name.
Approval first, autonomy earned
Nothing launches without the client’s written approval of the targeting and the message sequence. Once live, every reply a prospect sends is drafted in the client’s voice and posted to that client’s Slack channel with three buttons: Approve & Send, Edit, Skip. An edit feeds back into the voice.
Autonomy is earned per class of message. When the last 20 verdicts on, say, follow-up bumps are 90% approved without edits, that class goes to autopilot; two dissents in the next ten bring it back to approval. Hot leads, objections, factual questions and anything the guardrails flag are always held for a person. Before any approved reply goes out, the system checks again that the person is not blocked and has not asked to stop.
Onboarding a new client takes under a week
The client fills in the sign-up form; the workspace, the voice profile and the blacklist are built from it the same minute, and market research on their competitors and buyers starts running in the background. A growth strategist runs a 30 to 45 minute onboarding call between day 2 and day 5: confirm the buyer, review three draft openers, connect the seats, the booking link and Slack, and set a launch date out loud. First campaigns go live between day 3 and day 7, after written sign-off.
Expectations are set on that call and they are not guarantees. Accounts ramp for two to four weeks, results are not judged before 100 invitations, and an acceptance rate of 15 to 30% once settled is treated as healthy. Below 15% after 100 invitations, the list or the seat’s own profile is what gets fixed.
Day to day
What each client sees.
Their own dashboard, their own numbers
Calls booked this week, invitations, replies and positive replies, pipeline generated at the deal value they agreed, the best campaigns by booked calls, and recent conversions. Invitations, messages and replies count people rather than rows, so a prospect who writes back three times is one reply. The weekly recap appears as a strip on the dashboard, a Friday email and a Slack card, all read from one stored snapshot so the three can never disagree.
Two Slack channels
One channel for the conversation with you and the team, one for the SDR bot where every drafted reply lands with its Approve, Edit and Skip buttons. The client can sit in both or leave the second to you. A monthly report is generated for each workspace from the same event log the dashboard reads.
Bookings on their calendar, with the source attached
The booking link is Cal.com, Calendly, iClosed or GoHighLevel, connected during onboarding. A booked call lands on the client’s calendar and in the dashboard as a conversion tied to the campaign and the message that produced it. For agencies that keep their own reporting, every workspace exposes the same data through the API and webhooks, including reply_received, reply_positive, call_booked and account_rate_limited.
Can one of my clients see another client’s data?
No. Every record carries the organisation it belongs to and every query is scoped to the signed-in user’s current workspace. A client is a member of their own workspace only. Your team members are added to each workspace they handle and switch between them from the sidebar.
What happens when one client’s LinkedIn account is restricted?
Sending on that seat stops and it is re-warmed from 25% rather than resumed at the rate that caused the problem. The client’s other seats keep running, and other clients are unaffected. The seat’s status and the reason are visible on the accounts page, and a disconnect posts once to that client’s channel.
Who approves the messaging, me or the client?
The client, in writing, before launch; a verbal yes on a call is not enough for the team to switch a campaign on. Day to day, replies are drafted and whoever sits in the SDR channel approves, edits or skips them. Which classes of message run without approval is decided by the approval record itself, as described above.
How many meetings should I promise a client?
Do not promise a count. The platform’s default monthly goal is 5 booked calls for one seat, 8 for two, 10 for three and 20 for four or more, and it refuses to store a goal above 20 for any workspace. What we publish is measured: see the benchmarks page for accept, positive reply and booking rates with the period and sample attached.
Do my clients need Sales Navigator?
No. A free account can send invitations and messages. Sales Navigator raises the daily invitation ceiling from 35 to 50, removes the commercial-use limit on search, and gives Gelee a larger share of the seat’s monthly searches (750 instead of 125) for building lists.
Can my team answer the replies ourselves and only use the sending?
Yes. Every draft is a suggestion until someone approves it; your team can edit or skip any of them, or reply directly in the inbox. If that is all you want, though, a per-seat sender is cheaper, and we say so on the switching guides.
Discovery call
See it on your own accounts.
A short call. We learn about your market, and if it is a fit we set it up with you on the next one.