AI Giọng nói Doanh nghiệp Không Cần Thêm Cá tính. Nó Cần Sự Đồng cảm Theo Thiết kế

Tôi đã làm việc trong lĩnh vực giọng nói từ năm 2017, đủ thời gian để trải qua một chu kỳ hào nhoáng và chứng kiến làn sóng thứ hai thực sự tăng tốc. Mặc dù làn sóng thứ hai này về mặt kỹ thuật ấn tượng hơn, nhưng các cuộc thảo luận quanh nó đã thu gọn lại thành các con số. Rất ít điều liên quan đến cách mọi người thực sự nói và tôi cho rằng chúng ta đã mất đi mối liên kết đam mê với ngôn ngữ học và tâm lý học mà đã đặc trưng cho nhiều giai đoạn đầu của công nghệ giọng nói.

Khi xem qua các thông báo, bạn sẽ thấy các con số về độ trễ, tỷ lệ giải quyết và những tuyên bố đầy tham vọng về những gì các đại lý có thể thực hiện. Tất cả những yếu tố này đều quan trọng, nhưng một đại lý nói chuyện mượt mà sẽ vô dụng nếu không thể hoàn thành nhiệm vụ. Đáng chú ý, các sản phẩm giọng nói doanh nghiệp ngày càng dựa trên cùng một nhóm mô hình nền tảng, đồng nghĩa với việc tốc độ chỉ là tiêu chuẩn tối thiểu.

Sự khác biệt lại nằm ở một khía cạnh hoàn toàn khác. Đại lý biết gì? Nó có thể làm gì? Tương tác cảm giác như thế nào khi đang thực hiện? Quan trọng nhất, khách hàng có phải thực hiện thêm công việc nào vì đại lý là một máy móc không?

Đó là nơi thiết kế giọng nói dựa trên sự đồng cảm bắt đầu. Tôi không có ý nói thêm một giọng nói ấm áp hay một câu nói cảm thông. Tôi muốn nói đến việc thiết kế dựa trên mục đích của người gọi, tải nhận thức và trạng thái cảm xúc dự đoán. Đại lý nên biết những gì doanh nghiệp đã biết, giải thích những gì nó đang làm, khôi phục một cách sạch sẽ khi gặp lỗi và ngừng nói khi công việc đã hoàn thành.

A warm synthetic voice that asks for the same account number three times has not made the call any easier and the warmth is not doing any work.

Sự Đồng cảm Không Phải Là Một Cài Đặt Âm Thanh

A voice can sound thoughtful without the system behind it understanding the problem or being able to do anything useful. A customer may be calling about an outage, a disputed invoice, or an implementation blocker that cuts across several teams. If the agent only knows the FAQ, a warm or polished tone will not make the experience empathetic. The agent needs to know who is calling, what they have bought, what the last interaction on their account was, and what it is allowed to do to help the customer.

An enterprise voice agent needs the right customer and product context, with the right permissions, so it can answer and act while the person is still on the line. The caller does not need search results read aloud. They may need the refund issued, the record corrected, or the right specialist brought in.

I see empathy as both a design discipline and a systems requirement. Conversation design determines how the agent behaves. The underlying architecture determines whether it knows enough to be useful. I think of the combined result as the product texture of voice: what the system knows, how it uses that knowledge, how it handles uncertainty, and how the person feels when the conversation ends.

Giọng nói Tạo ra Một Hợp đồng Xã hội

Voice is not a neutral interface. I was on a call with a client recently and the demo agent had a female voice. Within a minute, people in the room were calling it “she.” Nobody announced that decision, it was just a natural extension of the conversation.

This effect predates generative AI. In 1994 research on computers as social actors, Clifford Nass, Jonathan Steuer and Ellen Tauber showed that people apply social responses to computers even when they know they are interacting with a machine. Voice intensifies that response through timing, confidence and tone.

That changes how failure feels. For example, a text box that returns the wrong link is irritating, and a voice that talks over you, misunderstands the same point twice, and insists it has solved the issue feels rude. The technology has not developed feelings. The caller has.

Trust is already thin. A 2025 global study led by the University of Melbourne with KPMG surveyed more than 48,000 people across 47 countries. It found that 66 percent use AI regularly, but only 46 percent are willing to trust it. Every voice interaction either earns a little trust or spends it.

There is also an ethical tension. The industry often treats the most human-sounding agent as the best one. But people do not want to be tricked. When I design an agent, I want it to identify itself, explain what it can access, and state what it is going to do before it does something consequential. Transparency must be part of the conversation.

Thiết Kế Dành Cho Tai, Không Phải Mắt

A screen is forgiving. People can scan, reread, and scroll back. Speech disappears as it is heard, which makes cognitive load a practical design constraint rather than an academic footnote.

Nelson Cowan’s review of working memory describes a central store limited to roughly three to five meaningful items in young adults. Yet voice systems still read out long menus and stack several questions into one turn. Most people cannot hold all of that in place, especially when they are distracted, driving, or already annoyed.

A text chatbot cannot simply be given text-to-speech and called a voice product. Native voice design uses shorter turns, puts important information first, and gives the caller room to interrupt. It also recognizes that not every gap in a conversation needs filling, so while speed matters, native voice design can “read” when a conversation is finished.

My background includes sociocultural linguistics, which looks at how language works between people and within social settings. That is useful in voice design because it gives us precise language for things like pacing, prosody, turn-taking and repair. “Make it sound natural” is not a design instruction. Being able to describe how a conversation should work gives teams something they can actually build against.

Thiết Kế Dựa Trên Đồng Cảm Trông Như Thế Nào

Empathy-led design is not about making an agent sound warmer or more human. It means shaping the conversation around the person’s situation, reducing the effort required to carry out a task, and handling failure without adding to their frustration. In practice, that starts with a few basic design choices.

Bắt Đầu Với Lý Do Người Gọi

People do not call to navigate a company’s taxonomy. They call because something is broken, late, or confusing. A caller who says, “I need to stop this delivery,” should not be pushed through a generic order-status script. The agent should establish which delivery and whether it can still intervene.

Sử Dụng Ngữ Cảnh Để Loại Bỏ Sự Lặp Lại

Empathy is often most visible in what the system does not ask. If the business already knows who the customer is, which product they use, and what happened previously, the agent should use that approved context rather than making the caller reconstruct it.
The same applies inside the business. A salesperson between meetings should be able to ask what changed in an account, dictate the follow-up and have the update written back to the right system. The value is staying in motion without losing context or creating more administration.

Thiết Kế Cách Sửa Chữa Trước Khi Đến Đường Đua Hạnh Phúc

Every voice system will mishear someone. Accents, background noise, unfamiliar names, and interruptions make that unavoidable. The product is defined by what happens next. The worst recovery pattern is to repeat the same question in the same words. A better response explains what the agent understood and narrows the uncertainty. If the issue requires judgment or access the agent does not have, it should involve a person before the caller has to demand one.

Tôn Trọng Việc Chuyển Giao Và Kết Thúc

Handing a caller to a person is not a failure. Handing them over without the context of the conversation is. If the agent transfers the call without passing on what the customer said, what it identified, and what it has already tried, the customer has to start again. That is exactly the work AI should remove.
The same applies when the issue is resolved. Sometimes the best voice experience is one question, one accurate answer, and a click. Callers will not necessarily thank the agent or confirm that their query has been resolved before hanging up. If they have what they need, the interaction has worked.

Đo Lường Nỗ Lực, Không Phải Sân Khấu Hiệu Suất

A perfectly resolved one-shot call can look like a bounce because the customer hangs up without confirming satisfaction. If success means completing a long script, teams will optimize for longer conversations and call it engagement.

I would rather measure repeat calls, corrections, avoidable transfers, and whether the requested action was completed. Broader satisfaction scores like NPS still matter, but the conversation itself reveals where the customer had to work harder than they should have.

In tháng 2 2026, Gartner reported that 91 percent of customer service and support leaders were under executive pressure to implement AI. That pressure makes it even more important to measure whether automation is actually removing work. A voice agent that creates repeat calls, unnecessary transfers or longer interactions may look efficient on paper while simply moving cost elsewhere. The economics improve when the system resolves the right work, avoids unnecessary turns and keeps customers from returning through a more expensive channel.

Năng Lực và Đồng Cảm Đi Cùng Nhau

The enterprise voice market is moving beyond natural speech. What matters now is whether an agent can understand the caller’s needs, access the right business context, act precisely and safely, and respond appropriately when the conversation goes off script.

Empathy-led design should not make an agent more talkative. Done properly, it removes repetition, shortens explanations and prevents the caller from having to manage the machine. Sometimes delight is simply the feeling that something difficult became easy.

The most important question I ask when building any AI product is brutally simple: why would anybody bother? Voice earns its place when it makes something noticeably easier, rather than giving people more work to finish.

Before launching a voice agent, listen to failed conversations, not just polished demos. Did it understand why the person called? Did it know enough to solve the problem? When it failed, did it make the next step easier or harder?

If the answer is unclear, more personality, lower latency, and a more human voice will not rescue it.