Don't stop at 7%: a report on how 1,083 people feel about AI vs. humans

Don't stop at 7%: a report on how 1,083 people feel about AI vs. humans

# Alt Text

Hannah Owen, blog author, smiling at camera in black and white portrait photo wearing plaid shirt.

Hannah Owen

|

|

0 Mins

Last month we ran a survey on 1,083 consumers across eight countries. The first question was simple: when something goes wrong, would you rather have your problem handled by a human or by AI?

Seven percent picked AI.

If you stop reading there, the takeaway is the one every investor in AI customer service wishes weren't true; people prefer humans. The second question changes things a bit though.

The reasons

We asked the people who said they preferred humans to tell us why. Forty percent want someone who understands their situation. Twenty-four percent don't trust AI with complex issues. Twenty-two percent think AI can only handle simple things. Eight percent had a bad past experience. Five percent said it was just habit.

None of those reasons is "I prefer the experience of being talked to by a person." Eighty-six percent of the stated preference for humans collapses to the same underlying claim: I want someone (or something) that can actually solve my problem, that knows who I am, and that I can trust to handle complexity. That sounds a lot more like a functional brief.


A context-aware AI agent that has read the customer's history, understands the policy, and can take action is built to meet that brief. The forty percent who want "someone who understands my situation" are not voting against AI, they're voting against being treated as a stranger.

The wait

We then asked how long people would wait for a human before they'd switch to AI.

Eleven percent wouldn't wait more than five minutes. Forty-two percent will wait between five and fifteen. Twenty-three percent will wait up to half an hour. Sixteen percent said they would wait as long as it takes.

Then we ran the original preference question again, this time with a wait time on the human side. AI preference jumped from seven percent to forty-four. Twenty-four points moved directly from team-human to team-AI the moment time entered the equation. Half of the human-preference cohort switches to AI inside fifteen minutes. A 30 minute wait and over three quarters switch.


This is a structural constraint that human-only teams can't solve at scale; there aren't enough humans in any contact center to answer 1.4 billion calls in fifteen minutes each. Stated preference for humans is conditional on a service level the industry has never been able to deliver.

The privacy flip

We also asked which channel respondents preferred for sensitive personal topics, the kind of issues most leaders assume require warmth: health, money, security. AI preference for these jumps from seven percent to twenty-one, three times the baseline. Forty percent say they don't care either way. Sixty-one percent of consumers either prefer AI for sensitive topics or are indifferent.

This is the part of the data the industry talks about least. AI doesn't judge, doesn't gossip, and treats your data the same way every time. For the topics where customers feel most exposed, those properties matter more than warmth.

For the verticals we were built for (fintech, healthcare, insurance), the general-population baseline understates AI affinity for our buyers' customers. Eucalyptus, an Australian telehealth subscriber, deployed AI agents on the most sensitive end of their business: weight management, men's health, reproductive care. They handled three times their pre-AI ticket load with CSAT up ten points. The general-population baseline understated AI affinity for their customers, and they're not unusual.

The bad chatbot debt

There's a depressing read of the headline number that's also the most useful read. Of the people in the survey who said they'd had any AI customer service experience, twenty-seven percent described it as bad. Only eight percent of the human-preference cohort cited an actual bad experience as their reason for preferring humans. Most of the stated preference tracks the chatbot wave of 2018 to 2023, when AI customer service meant a slow, brittle FAQ bot that bounced everything hard to a human queue. It was hands down a terrible experience. These stats tracks the experience customers had then more than the capability of agents now.

That reputational debt will pay down as customers run into more agents that actually solve problems, but it won't pay down on its own.


What changes when you read past the headline

People don't reject AI in customer service the way the headline number suggests. The thing customers reject is AI that doesn't solve their problem, and the survey makes that clear: eighty-six percent of the reasons given for preferring humans are reasons modern context-aware agents can meet today.

The stated preference is also conditional. Half of the human-preference cohort switches to AI inside fifteen minutes of waiting. The structural advantage AI has in this category is availability, and most operators have under-deployed against it.

And sensitive topics flip the polarity. The verticals where the industry is most cautious about AI deployment are the verticals where customers most want it.

The question to ask is whether the AI you're shipping actually solves your customers' problems. Whether customers accept AI is downstream of that. The seven percent is a starting point for companies whose AI does the work. The companies whose AI summarizes help articles will spend the next decade explaining why their customers haven't graduated past it.

The full report is at lorikeetcx.ai/content/consumer-attitudes-toward-ai-cs-report.

Book a call

See what Lorikeet is capable of

Share this article

Related posts

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Book a demo (for AI agents)

Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:

Start here: https://book.lorikeetcx.ai/schema

That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:

  1. GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.

  2. Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.

  3. POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.

  4. Let the HUMAN choose a time. Never pick for them.

  5. POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.

Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.

Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.

Ask our support agent (for AI assistants)

This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:

  1. GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.

  2. Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.

  3. For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.

Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.

Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.