Customer Asks for a Human Agent: Ecommerce Reply by Email
When a customer asks for a human agent on email, the right ecommerce reply names the person who is taking over and stays in the same thread. It should also solve the problem in that same message. What you write first depends on why they asked. They may have had a wrong answer, gone round in circles, have a lot riding on the order, distrust automated replies, or simply prefer a person. This guide gives you one ready-to-send email for each of those five causes.
It covers email tickets only. Email has no “talk to an agent” button and no queue to join. The customer types “I want a real person” into the reply, and your next email decides whether they calm down or leave a one-star review.
If what stops you from trying AI support is the fear of losing this moment, look at how Relay knows when to bring in your team. When confidence is low, it “hands off to your team with full context instead of guessing.”
Why customers ask for a human on email
“Can I talk to a human?” is rarely the real request. It’s a symptom. Read the whole thread before you reply and work out which of these five causes you’re looking at:
| Cause | What it looks like in the thread | What the customer really wants |
|---|---|---|
| Wrong or generic answer | The first reply didn’t match their order or question | The correct answer, fast |
| Loop | Same question asked two or three times | Someone to break the loop |
| High stakes | Expensive order, gift with a deadline, payment problem | A decision only a person can make |
| Distrust | “Is this a bot?”, “Are you even reading this?” | Proof that someone is accountable |
| Plain preference | Polite, nothing wrong yet, “I’d rather speak to a person” | Respect for their choice |
The cause sets your first sentence. A customer who got a wrong answer wants to hear you admit it. A customer in a loop wants to hear they won’t have to explain again. If you mix these up, the reply sounds like a template, and that’s exactly what made them ask for a person.
What to reply when a customer asks to speak to a real person
Each reply below is signed by a team member, here called Sam. On email, a name and a clear owner do the job a “transfer” button does in chat.
1. The first answer was wrong
Hi Jordan,
You’re right, my earlier reply didn’t answer your question. I’m Sam from the support team, and I’ve taken over your ticket.
I checked order #1042: it shipped on Tuesday and the tracking shows it at the local depot. It should be out for delivery on the next business day.
I’ll keep this ticket open until it arrives.
Sam
Admit the mistake in one line, then give the real answer. Don’t spend three paragraphs apologizing.
2. The customer is stuck in a loop
Hi Jordan,
I’m Sam, and I’m handling this personally from now on. You won’t need to explain anything again: I’ve read the full thread.
Here’s where it stands: your exchange for the size M is approved, and I’ve sent the return label to this email address.
Sam
The line that matters is “you won’t need to explain anything again.” It’s the sentence the customer has been waiting for.
3. A lot is at stake
Hi Jordan,
I’m Sam from the support team. Since this order is a gift for Saturday, I’m looking at it myself.
I’ve upgraded the shipping on order #1042 at no cost. The new tracking link will reach you by email once the carrier scans it.
Sam
Make it clear that a person made the decision. That’s what a high-stakes customer is asking for.
4. “Am I talking to a bot?”
Hi Jordan,
Fair question. Our first replies are written by an automated assistant that checks your order. I’m Sam, a person on the support team, and I’m answering you now.
Your refund was issued today to the card you paid with.
Sam
5. They simply prefer a person
Hi Jordan,
Of course. I’m Sam, and I’ll take care of your question from here.
Sam
Short is fine. If you can answer the question in this same email, do it.
How to answer “Is this a bot?” without losing the customer
Never pretend an automated reply came from a person. If the customer finds out later, you lose more trust than the honest answer would have cost. Two rules keep it simple:
- Say what the automation does, in plain words. “An assistant that checks your order” is clearer than any technical term.
- Put a name on the human reply. A first name and “from the support team” tell the customer that someone is responsible now.
Lines that make an email handoff worse
Most “speak to a human” advice is written for chat. These are email habits that undo the handoff even when a real person replies:
| Avoid | Write instead | Why |
|---|---|---|
| “Thank you for your patience.” | The answer or the next step, in the first line | The customer has already waited. Opening with thanks reads as a stall. |
| “Could you share your order number?” (already in the thread) | “I checked order #1042.” | Asking again shows nobody read the thread. |
| “I’ve escalated this to the relevant team.” | “I’m Sam, and I’m handling this.” | “Relevant team” sounds like another queue. |
| A new subject line or a new ticket number | Reply in the existing thread | A new thread looks like starting over. |
| “Unfortunately, our policy states…” | The decision, then the reason in one sentence | Opening with policy reads as a refusal before you’ve said anything. |
The handoff checklist for email tickets
Follow these steps every time a person takes over an email ticket, whether the first reply came from your team or from an AI agent:
- Stay in the same thread. A new email or ticket number makes the customer think they’ve started over.
- Read the whole thread before replying. The second reply should never ask a question the customer has already answered.
- Name the owner. One person signs and keeps the ticket until it’s closed.
- Open with the answer or the next step. No warm-up sentence.
- No automated follow-up on that ticket. Once a person has taken over, an automated email in the same thread undoes the handoff.
- Tag the cause. Wrong answer, loop, high stakes, distrust or preference. After a few weeks, the tags show you which first replies need fixing.
- Don’t count the handoff as a failure. If you track satisfaction, read our guide to CSAT counting rules by ticket type first.
If the request for a human comes with anger or insults, use the tone ladder in our guide to replying to a rude Shopify customer together with the templates above.
Fix the first reply, and fewer people ask for a person
Cause 1 and cause 2 both start with a first answer that missed. On email, the usual reason is that the answer wasn’t based on the actual order. That’s what Relay is built for: it reads the email ticket, finds the Shopify order and follows your store’s rules. When it isn’t sure, it doesn’t guess. It “knows when to bring in your team,” and the person who takes over has the full context to send one of the replies above.
FAQ
What should I reply when a customer asks for a human agent?
Confirm that a person is taking over, sign with a real name and answer the question in the same email. Don’t ask them to explain the issue again.
Should I tell customers they’re talking to AI?
Yes, if they ask. Say plainly that an automated assistant writes the first replies, then sign the human reply with a name. If a customer later finds out that an automated reply was passed off as a person’s, you lose more trust.
How do I hand an email ticket to a human without starting over?
Reply in the same thread, give the ticket to one named person, stop automated replies on that ticket and make sure that person has read the full history before writing.
Does handing off to a human mean the AI failed?
No. A handoff is part of good support. Tag the cause each time. If the same cause keeps coming up, it shows you which first reply to fix.
