Someone replied. That is the moment outbound stops being a volume game and starts being a conversation, and it is where most outbound falls apart. Not because the opener was bad, but because the follow-up was slow, generic, or never happened.
The frameworks below are the same ones good reps have always used: read the reply type, respond to what was actually said, and move toward a next step without pushing. What changed is who executes them. In Alsona you teach the agent how you would handle each reply type, and it handles the volume while you handle the exceptions.
That is the shift this playbook is built around. Your job is no longer to type every follow-up. It is to define the plays, hand them to the agent, and know when to step in.
Step 1: Decide who handles replies
Every agent runs in one of three outreach modes, set in step 3 of the wizard and changeable afterward.
Co-pilot. The agent drafts every message and waits for you to approve it. Nothing sends without you.
Outbound autopilot. The agent sends the outbound sequence on its own and hands every reply to you.
Full autopilot. The agent sends and replies, working conversations toward your goal without you.
Most people should walk up this ladder rather than jumping to the top.
Run a new agent on co-pilot for the first week. You are not checking whether the AI can write. You are checking whether it writes the way you would, and every draft you edit teaches you what to put in your instructions. Once you find yourself approving drafts unchanged, move to outbound autopilot so sending runs itself while replies still come to you. Move to full autopilot when you have seen the agent handle enough real replies that you trust it with the ones you have not anticipated.
For agencies, the same ladder applies per client. A new client account starts on co-pilot regardless of how much you trust the setup, because their voice is not your voice.
Step 2: Teach the agent your playbook
Additional outreach instructions are the free-text field where you tell the agent how to behave. This is the highest-leverage field in the product for nurturing, and it is where the rest of this playbook actually gets implemented.
Write instructions the way you would brief a new rep on their first day. Be specific about behavior, not personality. "Be friendly" does nothing. "If they ask for pricing, give the starting number and offer a call rather than deflecting entirely" is a rule the agent can follow.
A few principles that make instructions work:
Name the situation, then the response. Conditional instructions land better than general ones.
Say what not to do. "Never send a calendar link before they have shown interest" prevents a specific failure.
Include your actual constraints. Pricing you will and will not quote, competitors you will not name, claims you cannot make.
Tell it when to stop. The agent will keep going unless you define an exit.
The three sections below each end with instruction text you can adapt and paste in.
Positive replies
"Sounds good." "Yes, tell me more." "Open to chatting."
These are the highest-intent replies you will get, and they are not closed deals. The job is to convert stated interest into a booked slot before the moment cools.
Strategy: validate the response, reconfirm what they are interested in, make scheduling frictionless, and give a little context so the call has a shape.
Formula: appreciation, confirmation, scheduling CTA, and optionally a value tease.
Casual:
"Awesome, glad this caught your attention. Happy to dive in. How's early next week for a quick chat? Here's my calendar: [link]. Totally flexible if you have a better time."
More consultative:
"Thanks for the reply, [Name]. Based on what you mentioned, sounds like there could be a good fit. I'd love to walk you through a few quick wins we're seeing with teams like yours. Here's a link to grab time: [link]."
What to tell the agent:
When a prospect expresses interest or agrees to talk, thank them, restate the specific thing they showed interest in, and offer the meeting link right away. Do not add new pitch material at this stage. Keep it under four sentences. If they ask a qualifying question before booking, answer it in one or two sentences and then offer the link again.
Set your conversation goal to "book a meeting" and fill in the meeting link field on the agent profile, otherwise the agent has nothing to send.
When the agent should hand it to you: a positive reply that comes with a hard question about contracts, security, procurement, or anything you would not want answered from a template.
Neutral replies
"Maybe later." "Send me info." "Not sure this fits."
Neutral is a maybe wearing a disguise. The job is to find out what is actually behind it without pitching into the gap.
Strategy: ask rather than pitch, offer something genuinely useful, and make it easy to say "circle back later" without ending the thread.
Formula: acknowledge, ask an open question, optionally drop a resource, and offer to reconnect.
If they say "send me info":
"Happy to. Out of curiosity, are you exploring anything in [area] right now? That'll help me send something relevant rather than a generic overview. In the meantime, here's a short piece on how we're helping similar teams."
If they say "maybe later" or "not sure it's a fit":
"Appreciate the honesty, [Name]. Is that a timing thing or a priorities thing? No pressure either way, happy to reconnect down the line."
If the reply is vague:
"Got it. So I don't make assumptions, what are you most focused on right now when it comes to [business goal]? If it helps I can send a quick case study and you can tell me if any of it maps."
What to tell the agent:
When a prospect gives a soft or non-committal reply, do not pitch. Ask one open question that distinguishes timing from fit. If they ask for information, send the relevant resource and pair it with a question. Never send a calendar link to a neutral reply until they have shown a second signal of interest. If they say "not right now," ask when would be better and confirm you'll follow up then.
That last instruction matters more than it looks. "Ask when would be better" turns a dead end into a dated follow-up, and it is the single highest-return line you can add to your instructions.
When the agent should hand it to you: any reply where the objection is specific to your product or their situation rather than to timing. Those are worth a human answer.
Negative replies
"Not interested." "We're good." "No thanks."
Negatives are not failures, they are information. Handle them well and you keep a door open that most of your competitors have slammed.
Strategy: be gracious, thank them, ask permission to reconnect, and leave.
Formula: acknowledge, thank, ask about reconnecting, and optionally leave something useful behind.
Polite no:
"Thanks for the quick response, [Name], totally understand. If things shift or you're looking at [area] down the road, I'd love to reconnect. Okay if I check back in a few months?"
Firm no:
"Appreciate the clarity. Sounds like you've got this handled. I'll step back, but if you ever want to see how others in your space are approaching [topic], just say the word."
What to tell the agent:
When a prospect declines, respond once with a short, gracious acknowledgment and ask if you can reconnect in a few months. Do not attempt to overcome the objection. Do not send more than one message after a decline. If the decline is firm or the tone is annoyed, respond with a brief thank you and nothing else.
The instruction to stop is the important one. An AI that argues with a no will cost you more than the deal was worth.
When the agent should hand it to you: an angry reply, a request to be removed, or anything that reads like a complaint. Take those over yourself and add the contact to your blacklist so no other agent picks them up.
When they go quiet
Ghosting after a warm reply is the most common thing that happens in nurturing, and it is the thing an agent is genuinely better at than you are, because it never forgets and never feels awkward about it.
After a positive reply with no booking:
Bump 1, two to four days later. "Just wanted to bump this up. Still good to connect this week or next? Calendar's here again: [link]."
Bump 2, five to seven days after that. "No worries if timing's been tight. Want me to circle back in a few weeks instead?"
Bump 3, ten to fourteen days later. "I'll pause here so I'm not crowding your inbox. If this becomes relevant, reach out any time."
After a neutral reply with no response:
Bump 1, three to five days later. "Did that land okay? Curious whether anything in it felt relevant to what you're working on."
Bump 2, about a week later. "Happy to circle back in a month if now's not the moment. Or if there's a specific thing you're wrestling with, I can send something more targeted."
Bump 3, ten to fourteen days later. A low-pressure exit with one useful link.
What to tell the agent:
If a prospect goes quiet after showing interest, follow up a maximum of three times, spaced roughly three days, one week, and two weeks. Each follow-up should be shorter than the last. Never repeat the previous message. On the third, close the loop politely and stop.
Build the timing into the workflow itself rather than relying only on instructions. The workflow canvas has conditions for whether a profile has replied and whether an email was replied to, so you can branch a sequence into a nurture path for people who engaged and a different path for people who never did.
Working the inbox alongside your agents
The inbox is where you and the agent share the work.
Threads are split by sender and by channel, with separate LinkedIn and email tabs.
Eleven labels are available for categorizing threads, and you can filter by agent, by label, and by read status.
Any thread an agent is handling shows a Take over button. Click it and the conversation is yours.
Take over is the control that makes full autopilot safe. You are not choosing between full automation and full manual work. You are letting the agent run the volume and pulling out the conversations that need you.
Take over when you see a named account you care about, a question the agent should not answer, a reply that misreads the conversation, or a thread where someone has said something the agent is not equipped to handle.
If you want to know about replies without watching the inbox, point Alsona's reply webhooks at Slack. Two of the four webhook events fire on replies, one for LinkedIn and one for email, so a warm reply can land in a channel the moment it arrives. See "How to set up webhooks."
What still needs a human
Automation handles the pattern. You handle the exception. Step in for:
Named target accounts where a generic reply costs you the relationship
Pricing negotiations and anything contractual
Technical questions where a wrong answer is worse than a slow one
Any reply where someone is unhappy
Introductions and referrals, which deserve a real response
Anything where the prospect has clearly worked out they are talking to software and says so
Cheat sheet
Reply type | Goal | Agent's job | Your job |
Positive | Book the meeting | Thank, confirm, send the link | Take over if the question is hard |
Neutral | Start a real conversation | Ask one open question, offer value | Take over if the objection is specific |
Negative | Leave the door open | Acknowledge once, ask to reconnect, stop | Take over if they are annoyed, then blacklist |
Silence | Stay present without nagging | Three spaced follow-ups, then exit | Nothing, unless it is a target account |
Tuning it
Read what your agents actually send. For the first couple of weeks, open the inbox and read full threads rather than skimming reply counts. Every awkward message is a missing instruction, and the fix belongs in additional instructions rather than in a one-off correction.
Watch where conversations die. If threads consistently stall after the same beat, that beat is the problem. Usually it is asking for the meeting too early or too late.
Adjust tone per agent. Professional, friendly, and bold read very differently in a reply than in an opener. If the agent's replies feel pushy, tone is often the lever before instructions are.
Change one thing at a time. Rewriting your instructions and switching outreach mode in the same week tells you nothing about which one moved your booking rate.