# Checklist for AI to human handover criteria
> Learn when a human should take over from an AI SDR on LinkedIn. Set intent signals and boundaries so leads move from qualification to a real conversation.
- HTML: https://getkinlead.com/checklist-for-ai-sdr-handover-criteria
- Markdown: https://getkinlead.com/checklist-for-ai-sdr-handover-criteria.md

**Short answer:** A human should take over from an AI SDR when a lead asks for pricing, a call, a comparison, or describes a specific problem the AI cannot answer. Let the AI confirm interest and gather context, then move the thread to a person who can quote numbers, handle objections and book the meeting.

## Identify your handover triggers

The gap that loses deals sits between a lead typing 'I'm interested' and you actually booking the call. If the AI keeps qualifying after someone has shown intent, the thread stalls, and the lead starts to feel like they are talking to a script. The fix is a small set of triggers that move the conversation to a person at the right moment.

A trigger is a specific phrase or request that maps to a real buying step. 'Can you send pricing?' is a trigger. 'Interesting' is not. Write your triggers as sentences a lead would actually type, then decide what happens when one appears. Do not use single keywords like 'price' on their own, because a researcher asking whether you publish pricing is not the same as a buyer asking for a quote.

Keep the list short enough to remember. Six to eight triggers cover most LinkedIn conversations, and each one needs an owner: the AI replies, the AI hands over, or you take it from here. Anything outside the list stays with the AI until it qualifies the lead or the lead goes quiet.

| | Signal type | Trigger example | Action |
| --- | --- | --- | --- |
| Direct request | Can we jump on a call this week? | Hand over now |
| Price question | What does this cost for 20 seats? | Human sends a real number |
| Comparison | How are you different from the tool we use now? | Human handles the nuance |
| Specific pain | Our SDRs are drowning in manual list building | Human replies with a relevant example |
| Proof request | Do you have a customer like a 40-person agency? | Human shares one story |
| Security or legal | Where is the data stored? | Human or a specialist, never the AI |
| Bot check | Am I talking to a bot? | Human takes over, no debating |

## Set the AI's boundary

Give the AI a job it can finish. On LinkedIn that job is usually to confirm the lead has the problem you solve and is willing to talk about it. The AI should not negotiate, promise features, explain your roadmap or guess at a price.

Write a stop list of topics the AI cannot touch. Pricing details, contract terms, custom SLAs, security questionnaires and anything about a named competitor belong to a person. When a lead raises one, the AI uses a fixed exit line and stops replying. That pause is the handover.

The exit line has to sound like something a person would type, because a person is about to type it. 'I'll get Sam, who handles pricing, into this thread' works. 'I am escalating your query to a human agent' does not. Test the line on a colleague before it goes live.

1. **Write the qualifier job in one sentence.** Example: find out whether the lead manages outbound for a team of five or more and wants to compare tools this quarter.
2. **List the topics the AI cannot discuss.** Pricing, contracts, security, roadmap, competitor comparisons and anything that needs a custom answer.
3. **Set one fixed exit line.** The AI uses the same sentence every time it hits the stop list, then stops replying until you pick up the thread.
4. **Turn on a notification you will see.** A handover is useless if it sits in a dashboard you check on Fridays. Route it to email or your phone.
5. **Run a fake thread.** Send the AI a test reply asking for a discount and confirm it exits with the line instead of inventing an answer.

```
You are replying to LinkedIn messages for [your name] at [company].

Your job is to find out whether the lead has [problem] and wants to talk about it. Ask one question at a time. Do not ask more than two questions in a row without a reply.

If the lead asks about pricing, contracts, security, competitors or the roadmap, stop and reply: 'I'll get [name] into the thread, they handle that side.'

If the lead asks whether you are a bot, reply: 'I'm an assistant working with [name], and they'll pick this up from here.'

Never invent a feature, a discount, a customer name or a delivery date.
```

## Write the transition message

The first message you send after the handover decides whether the lead sees a person or a system. Do not open with an apology or a comment about automation. Open with the thing they asked about.

Reference the exact detail from the thread. If they mentioned a 30-person team, say 30. If they mentioned a competing tool, say the tool's name. This proves the thread was read and gives the lead a reason to keep going.

Keep the first message short and end with one question. You are not restarting the conversation. You are continuing it with better information.

**Reads like a bot**

- I am taking over from the AI now. Let's talk about pricing.
- The bot told me you are interested. When can we meet?
- Hi, I'm the human here. How can I help?

**Reads like a person**

- Hey Priya, I handle pricing for teams your size. For 30 seats it's a flat per-seat number, and I can send the breakdown today. Are you the one signing off, or is your ops lead in the loop?
- You mentioned Northwind is the tool you use now. I've moved three teams off it this year, and the switch usually takes a week. What's driving the look?

- **them:** What does this cost for a 30-person team?
- **draft:** Good question. Pricing depends on seats and the modules you need. Before I send a number, are you comparing us with anything else right now?
- **them:** We're looking at two other tools. Budget is the main thing.
- **you:** Hey Priya, I handle pricing for teams your size. For 30 seats it's a straight per-seat number, and I can send the breakdown today. Are you the one signing off, or is someone else in the loop?
- **them:** I am, but my ops lead wants to see it too.
- **you:** Send me their name and I'll put together a one-page summary you can forward. If it looks right, we can do 20 minutes Thursday.

## Handle the replies that break the rules

Not every reply fits a trigger. Someone might send a one-word answer, ask a question about your company, refer you to a colleague, or complain about being automated. Decide now what happens in each case so you are not improvising at 11pm.

- One-word replies: the AI can ask one follow-up, then stop. Do not chase.
- Referrals: ask for the colleague's name and whether they want an intro. A person sends the intro.
- Angry replies: a person replies within the day, without a template, and removes them from the campaign.
- Out of office: pause the sequence and set a reminder for the return date.
- Questions about the company: the AI can answer facts that are already public, then return to qualification.

> If a lead asks whether they are talking to a bot, answer the question. A denial that gets caught ends the deal and can get the account restricted. The safe reply names the assistant and brings in a person.

## Audit the handover every week

Set a weekly review of 20 threads. You are looking for three failure types: a handover that came too late, one that came too early, and one that never happened.

Late handover looks like a lead asking for a price and getting two more qualifying questions. Early handover looks like a polite 'thanks' being routed to you as a hot lead. Missing handover looks like a question sitting unanswered because no trigger caught it.

The review takes 30 minutes. It is the only way to know whether your triggers match how leads actually write.

1. **Pull 20 threads that involved a handover.** Mix leads who booked, leads who went quiet and leads who asked for a person.
2. **Mark each one as good, late or early.** Use the first message you sent as the marker. If it answered a question the lead had already asked twice, the handover was late.
3. **Count the manual messages it took to recover.** If you needed more than two messages to get back on track, a trigger is missing or the transition message is weak.
4. **Rewrite one trigger or one line.** Change one thing per week. Changing five things at once tells you nothing about which one worked.

## Doing this with Kinlead

Kinlead handles the switch with reply modes. Hand-off mode gives you the conversation at the first reply. The other modes let the AI keep replying until there is real interest or until a meeting is booked with your scheduling link.

Replies from every campaign land in one [unified inbox](/features/unified-inbox), sorted by intent with interested replies first, and you get an email when someone answers. That is where you pick up the handover and send the first human message.

## Related

- [Unified inbox features](https://getkinlead.com/features/unified-inbox.md)
- [AI outreach templates for demo requests](https://getkinlead.com/ai-sdr-templates-for-demo-requests.md)
- [Lead scoring validation checklist](https://getkinlead.com/checklist-for-ai-lead-scoring-validation.md)

## Common questions

**Should the AI try to book the meeting itself?**

Yes, if the lead is already asking for a time or the campaign is set to book meetings. Use a scheduling link so the lead picks a slot without another round of messages.

**What if a lead ignores my first human message?**

Wait two working days, then send one follow-up that adds something: a price range, a relevant example or a straight answer to their last question. If they still do not reply, leave it.

**How do I handle a lead who wants a human immediately?**

Treat phrases like 'real person' or 'human' as an instant handover. The AI should not try to persuade them to keep chatting with an assistant.

**How many handover triggers should I set?**

Six to eight is enough for most LinkedIn campaigns. More than that and the AI hands over too often, which wastes your time on leads who are only browsing.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
