Sellium · Handoff to a sales rep

Handing off to a sales rep:from the agent to a person, without losing the sale

"My customers want to talk to someone" is the objection you hear most before putting an AI agent on WhatsApp. It is only half right: what customers do not want is to get stuck. A good agent handles what it can and, when a person is needed, hands the conversation to the rep with the full history. Here is when to hand off, what the rep receives and how to measure it.

The short answer

How does a conversation move from an AI agent to a sales rep?

A conversation moves from an AI agent to a sales rep through a handoff: the agent recognizes that the case needs a person, because the customer asks or because a business rule is met, lets the customer know, picks the right rep and passes along the chat with the full history and a summary of what came up. The rep continues the same conversation without asking again.

What decides whether the sale survives is not the handoff itself: it is the context that travels with it and how long the person takes to reply. Sellium hands off when the customer asks or when the case falls outside its rules, and logs everything in the CRM.

The objection

"My customers want to talk to someone": what is behind it

The objection has a basis. In a Gartner survey of customers, the top concern about AI in customer service is that it will be harder to reach a person: 60% name it (Gartner, 2024).

That does not mean customers want to wait for a rep on every question. In another Gartner survey, of B2B buyers, 61% generally prefer buying without a rep involved, and the same buyers prefer talking to one for decisions that need context (Gartner, 2025). The answer is not agent or person: it is an agent that knows when to pass the conversation on and does not hide the way out.

In practice, customers are asking for four things:

  • A fast answer: price, stock or order status in seconds, at any hour.
  • Not repeating themselves: whoever helps them knows what they already said.
  • A visible way out: being able to ask for a person without fighting a menu.
  • Someone who can decide: for a discount, a complaint or a large purchase, a person with authority.
When to hand off

When the agent hands off to a sales rep

Handoffs are not improvised chat by chat: they are defined during implementation, with rules your team knows. These are the usual triggers in a WhatsApp sale.

TriggerExampleWhat the agent does
Explicit request"I want to talk to someone" or "put me through to Martin"Hands off right away, without pushing back or asking why
Commercial exceptionA discount outside the price list, an order over the credit limit or a strategic accountPrepares what it can (quote or order) and passes it to the account rep to decide
Out of scopeA special or off-catalog product, or a technical question that needs a specialistDoes not improvise an answer: hands off to whoever knows, with the question already laid out
Lead ready to move forwardHigh volume, short timeline and the decision maker in the conversationAssigns it to the rep based on your rules, with the qualification done
Complaint or sensitive issueA delivery that never arrived or an invoice with an errorPasses it to the person in charge before the customer gets upset, with the order identified
Data it does not haveA question your systems cannot answerDoes not make anything up: says it will check with the team and hands off

Each company sets the rules (amounts, accounts, products and hours) during implementation, and they are tuned with data from the first few weeks.

Neither everything nor nothing: an agent that hands off at the first doubt leaves the team just as swamped, and one that never hands off frustrates the customer. You find the right balance by measuring the reason for each handoff, not by eye.

What the rep receives

What the rep receives when the agent passes the conversation

A handoff without context is a sale that starts from scratch. The rep has to be able to read what happened in thirty seconds and pick it up from there, without asking the customer what they already answered.

  • Who it is: contact, company, whether they are already a customer, their assigned rep and their latest purchases.
  • What they want: the question or the order summed up in two lines.
  • What came up: quantities, timeline, budget and who decides.
  • What was offered: price, stock, a quote or an order built as far as it got.
  • Why it is handed off: the specific reason, so the rep knows what to solve.
  • The full chat: the history, in case a detail is needed.

In the CRM: the summary and the history stay on the customer's record in Salesforce or on the contact in HubSpot, so the context is still there even if someone else takes the conversation.

After hours

What happens when no rep is available

Handoffs carry a risk almost nobody plans for: the customer asks for a person on a Saturday night and the agent replies "someone will be right with you". Nobody helps them until Monday, and that broken promise does more damage than not handing off at all.

The rule is to be honest about timing and keep helping with whatever is possible in the meantime.

  • It tells the customer when the rep will contact them, based on your team's hours.
  • It moves forward what it can: it quotes, takes down the details or leaves the order ready, so the rep starts with everything in place.
  • It books the contact on the rep's calendar for the next business day.
  • If the assigned rep does not reply within the agreed time, it passes the conversation to someone else or to a manager.
Mistakes to avoid

Six mistakes when passing the conversation from the agent to a person

A bad handoff shows in the chat: the customer repeats themselves, waits or gets two different answers to the same question.

  • Hiding the way out: an agent that does not let customers reach a person, or makes them ask three times. It is exactly what customers fear.
  • Handing off without context: the rep says hello and asks how they can help. The customer already said.
  • Two people answering: the agent keeps replying while the person types. While the rep owns the conversation, the agent stays quiet.
  • A queue with no owner: the conversation goes to a group nobody watches, and the customer waits longer than before the agent.
  • Handing off for lack of data: sending everything the agent does not know to sales instead of giving it the data to answer. An agent that does not make up prices or stock needs your systems, not a shortcut to the rep.
  • Not logging the reason: without knowing why conversations get handed off, there is no way to tune the rules.
How to measure it

How to measure whether the handoff works

Measure from the first week. These five metrics show whether the agent hands off what it should and whether the sale survives the handoff. The rest of the agent's indicators are in KPIs to measure an AI sales agent.

MetricWhat it measuresHow it is calculated
Handoff rateHow many conversations need a personHanded-off conversations over the total, per week
Handoff reasonWhere to adjust rules or fill in dataHandoffs by trigger: explicit request, exception, out of scope, complaint or missing data
Time to human responseWhether the person gets there in timeMinutes between the handoff and the rep's first message, during and after business hours
Conversion of handed-off chatsWhether the sale survives the handoffSales or orders closed over conversations handed off because of a sales opportunity
Repeat questionsWhether the context arrived completeHandoffs where the rep asked again for something the customer had already given, over a reviewed sample

The ideal handoff rate is not zero, and it depends on the industry and the type of sale. Set the baseline in the first few weeks and track it by reason.

Step by step

How Sellium hands a conversation to a sales rep

The full handoff, from the moment the agent recognizes the case to the moment the outcome is logged.

1

It recognizes the reason

A customer request, a business rule that is met or a question outside its scope. It does not wait for the customer to insist.

2

It tells the customer

It says it is passing them to a person, to whom and how soon, based on your team's hours.

3

It picks who

The rep who owns the account, or the one that fits your territory, rotation, specialty or schedule rules.

4

It passes the context

Summary, details gathered, what was offered and the reason, in the CRM and in the alert to the rep, with the full history.

5

The rep continues in the same chat

From the company's number, without asking again. While the person owns the conversation, the agent does not reply.

6

It is logged and picked back up

The outcome stays in the CRM. If the rep says so, the agent takes the conversation back, for example to enter the agreed order.

Benchmarks

What customers say about AI and people

Third-party figures with a published source, to understand the objection. None of them is a Sellium result.

60%

Of customers say their top concern about AI in customer service is that it will be harder to reach a person

Source: Gartner (2024)

64%

Of customers would prefer that companies did not use AI in customer service

Source: Gartner (2024)

61%

Of B2B buyers generally prefer a buying experience without a sales rep involved

Source: Gartner (2025)

7x

More likely to qualify a lead when you contact it within the first hour than an hour later

Source: Harvard Business Review (2011)

Caveats: the Gartner survey on AI in customer service covered 5,728 customers and measures customer service in general, not selling on WhatsApp; it is used because it shows the fear behind the objection. The B2B buyer survey covered 632 people. The Harvard Business Review study measures web leads contacted by phone or email, and serves as a benchmark for what it costs when the person is slow to reply after the handoff.

Frequently asked questions

Frequently asked questions about AI agent to human handoff

What sales teams ask before letting an AI agent answer first.

Can customers ask to talk to a person at any time?

Yes. When someone asks to talk to a person, Sellium transfers the conversation to the rep with the full history, without pushing back or asking for reasons. If nobody on the team is available at that moment, it says so clearly and books the contact.

What does the rep see when they receive the conversation?

A summary of who the customer is, what they want, what details came up, what they were offered and why it was handed off, plus the full chat history. It all stays on the customer's record in the CRM, so nobody asks them the same thing twice.

Does the rep reply from their own phone?

They do not need to, and it is better if they do not: the rep continues the conversation from the company's number, so the history stays complete and in the CRM. If they reply from their personal phone, the chat splits in two and the record is lost.

How does it decide which rep to hand off to?

With the rules you define during implementation: the account owner if the customer already exists, or whoever fits your territory, rotation, specialty or schedule rules. The same rules define which cases go to a specialist or a manager.

What if the agent hands off too much?

You measure it and adjust. Every handoff is logged with its reason, and that data is used to fix the rules or fill in the information the agent was missing. A high rate almost always points to data the agent does not have, not a limit of the AI.

How much does an AI agent that hands off to sales reps cost?

Sellium is priced in two parts: an initial implementation quoted for each company, which includes defining the handoff rules, and a monthly subscription with AI credits that scale up, with no lock-in. You pay for WhatsApp messages directly to Meta, on your own account and with no markup from us. For your number, request a quote.

See how Sellium would hand off your conversations

Tell us how your sales team is set up, who handles what and during which hours. We will show you how Sellium would resolve each inquiry and when it would pass the conversation to each rep, with the full context.