How to automate LinkedIn connection request replies
How to move an accepted connection request to a booked call with an AI reply mode, a written sales playbook and a queue you actually read each morning.
Get startedShort answer
Automating connection request replies comes down to three settings: a written sales playbook the AI replies from, a reply mode that decides when you take over, and a queue you read before messages go out. None of it works if the playbook isn't in your own words.
Decide what a reply is supposed to achieve
An accepted connection request means someone agreed to see your posts. That's it. The message you send next decides whether it turns into a conversation, so write down the outcome you want before anything gets automated.
Most founders and SDRs can name one of three outcomes: a booked call, an answer to one qualifying question, or a clean no so the lead leaves the list. Pick one for the campaign and put it at the top of the playbook. If you can't pick, the AI defaults to being friendly and vague, and friendly and vague books nothing.
How hard you push depends on how much trust the deal needs. A tool someone can try this afternoon can be pitched in the second message. A service that changes how a team works needs the lead to describe the problem in their own words first, because you can't solve a problem the buyer hasn't admitted to.
Goals that produce small talk
- Start a conversation and see where it goes
- Build rapport first, sell later
- Send a few messages back and forth
Goals you can judge a campaign against
- Get the lead to say out loud that manual lead research is eating their week
- Confirm they control the budget for a tool like this
- Get a time on the calendar for Thursday or Friday
Write the playbook the AI replies from
A playbook is your own sales script with the thinking written down. It covers four things: who the lead is, what they struggle with, what you say when they push back, and what has to be true before you ask for time. Without it, the AI writes the average of everything it has read, which sounds like everyone and convinces nobody.
Keep it under a page. Long playbooks get diluted, and the two lines you care about most end up buried under background nobody reads.
Write it the way you'd brief a new SDR on their first morning: plain, specific, and full of the phrases you actually use on calls. The AI copies your register. If your playbook is stiff, your replies will be stiff.
- 1
Describe the buyer in one paragraph
Something like: head of sales at a 20 to 80 person software company who just hired their first SDR. The AI uses this to pick which problem to raise first.
- 2
List the objections you actually hear
Not the ones you wish you heard. Copy them from your sent folder, including the blunt ones like 'we already do this in house' and 'no budget until next year'.
- 3
Answer each one in two sentences
Use your real answer. If your answer on a call ends with a question back, keep the question, because that's what keeps the thread alive.
- 4
Name the booking trigger
The AI should ask for time only when the lead asks about price, asks how something works, or describes the problem without being prompted.
- 5
Ban the phrases you hate
Hope this finds you well, I'd be delighted, circling back, just bumping this, reaching out. Say what you want instead of only what you don't.
Paste this job
Who I'm writing to: Head of sales at a 20 to 80 person software company, first or second sales hire. The problem I solve: They have no repeatable way to find leads that look like their best customers. What I want from this conversation: A 15 minute call about where their leads come from today. Booking trigger: Ask for time only when they mention lead quality, list size or pipeline coverage. Objections and answers: We already use a tool -> Which one, and what does it miss? Not right now -> When does your next quarter start? Send me some info -> Happy to. What would make it worth reading? Never say: Hope this finds you well, I'd be delighted, circling back, just bumping this. Tone: Short sentences. No exclamation marks. One question per message.
Choose a reply mode before you switch anything on
Reply modes decide where the AI stops. Hand-off mode sends nothing on its own, so every reply lands in your inbox and you write back. Interest mode lets the AI answer until the lead shows real interest, then hands over. Booking mode lets it keep going until a meeting sits on your calendar.
Pick from deal size and how much of your day you can give the inbox. If a wrong sentence costs you a deal you needed, you want hand-off. If the deal is small and the volume is high, booking mode earns its place.
Write the choice down per campaign. A team that runs two modes across three campaigns and never records which is which ends up blaming the tool for a mess it made.
Hand-off
- Mode
- Sends nothing on its own. Every reply waits for you to answer.
- What the AI does
- From the first reply, every time
Qualify
- Mode
- Answers, separates real interest from polite interest, and handles the obvious objections.
- What the AI does
- When the lead asks something only you can answer
Book
- Mode
- Keeps replying until a meeting is on the calendar, then stops.
- What the AI does
- After the meeting is booked
One mode per campaign. If hand-off and booking run side by side in the same campaign, nobody can tell you who answered which lead.
Write the first reply after the connection is accepted
That first message gets read more than anything else you send, and it has three jobs in about 40 words: show you know who they are, name one problem worth talking about, and ask a question that takes ten seconds to answer.
Thanking them for connecting is fine. Thanking them in a way that sounds copied is not. Reference the reason you reached out, because that context is the only thing separating you from the other requests sitting in their list.
Keep the ask small. A question about their work is easy to answer from a phone. A question about their calendar is easy to ignore.
Example
- Prospect
Thanks for connecting.
- Suggested reply
Thanks for accepting. I saw Northwind is selling into mid market finance teams now. Is finding those buyers still manual?
- Prospect
Mostly yes. Referrals come in but they're unpredictable.
- Suggested reply
That's what I hear from most teams at your stage. Worth a 15 minute call Thursday or Friday to compare notes?
- Prospect
Thursday works.
Answer objections in your own words
This is where automated replies fall apart. An AI that answers 'we already have a vendor' with 'I understand, let me know if anything changes' has ended the conversation politely and permanently.
Write an answer to each objection you actually get, two sentences each, in the words you'd use on a call. Then give the AI one rule that applies to all of them: ask a question instead of conceding.
Test it yourself before the campaign goes live. Send the AI's worst objection answer to a colleague and ask whether it sounds like a person. If they pause before answering, rewrite it.
- One question per message. Two questions get one answer, and it's the easier one.
- Never apologize for following up. It's the second message, not a cold call at dinner.
- Repeat their words when you restate the problem. If they said noise, don't switch to data quality.
- Concede when the answer is a real no and close the thread without a pitch.
- Drop the qualifying questions once someone asks about price. Answer it.
Replies that end the thread
- I completely understand. Let me know if anything changes.
- Thanks for getting back to me. Would you be open to a quick call?
- Sorry to bother you, I'll follow up next quarter.
Replies that keep it going
- Fair enough. Which tool are you on, and what does it miss?
- Understood. Is that because the budget is set, or because the timing is wrong?
- Makes sense. Who else on the team feels the lead quality problem?
Read the queue and watch the account
Automation runs without you, which is why a five minute check each morning matters more than any setting. The queue is where you catch a campaign that has drifted into sounding like a brochure.
Read what's waiting, fix what's wrong, close the tab. The rest is maintenance.
- Read the first ten queued messages in a new campaign before they send, and edit the ones that sound like a press release.
- Check pending invitations. If they're stacking up faster than people accept them, slow the invites down.
- Run one campaign at a time per account until it produces conversations you can read.
- If LinkedIn pushes back on the account, pause that campaign the same day.
- Keep the send window inside the hours your buyer is at a desk, in their time zone.
Two promising replies are not a result. Judge a campaign once you have conversations to read, not at the end of day one.
Doing this with Kinlead
Kinlead runs this workflow from your own LinkedIn account, connected through Unipile. Your password is never stored. Each campaign takes a goal, a tone and an optional sales playbook, which is your own script, and writes messages and follow-ups from them. Connection notes can open with why that person became a lead, under 200 characters.
Every campaign points at a lead group and picks one of three reply modes: hand the conversation to you at the first reply, let the AI reply until there's real interest, or let the AI reply until a meeting is booked on your scheduling link. Queued campaign messages can be read and edited on the Actions page before they send, and any campaign can be paused.
Sending runs at a human pace, at most one action every 5 minutes, inside daily limits and a send window you set in the lead's time zone. Stale pending invitations get withdrawn automatically, and if LinkedIn pushes back, invites pause on that account and you get an email. Replies from every campaign land in one inbox, classified by intent. The details are on AI LinkedIn outreach.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to automate LinkedIn connection request replies.md