CÂU HỎI
Why do complaints keep rising while the product improves?
Liệu cái này có ảnh hưởng đáng kể đến cái kia không? Ba phần tư số phiếu đã bỏ sẽ quyết định.
đã đóng · quay lại giai đoạn Biện pháp
Đang xem với tư cách khách. Nhập tên người dùng để vào và tham gia.
Các câu hỏi được chia cho các nhóm, nên bạn nhận những câu được giao cho nhóm mình — không phải cả 180 câu.
177 / 180 đã ngã ngũ 0 câu chờ bạn trả lời vì sao
Không ai trả lời nổi vài trăm cặp thẻ. Mỗi cặp được giao cho một nhóm; cặp nào bị chia rẽ sẽ được chuyển sang các nhóm khác, nên nó có thể xuất hiện trong danh sách của bạn sau này dù bắt đầu ở nơi khác. Số đã ngã ngũ tính cả công việc của mọi nhóm, vì vậy nó tăng nhanh hơn tốc độ danh sách của bạn ngắn lại.
Lần kiểm phiếu gần nhất: 177 đã quyết · 2 chuyển lên hội đồng liên nhóm · 0 còn tranh cãi · 1 chưa đủ số người tối thiểu — hội đồng cần ít nhất max(2, 75% hội đồng) phiếu đã bỏ; hội đồng nhỏ nhất của bạn có 15 thành viên.
A customer who complains twice gets the same first reply both times → ảnh hưởng? → Refund policy is different on the website, in the app and in the script
Chưa ai nói gì.
Giai đoạn đã xong — hồ sơ các cặp thẻ và phiếu bầu nằm ở trên.Kiểm tra lập luận ↗
| Refund policy is different on the website, in the app and in the script | → | … | đang mở đã chuyển lên | thảo luận |
| The phone line closes at five and the emails start at five past | → | … | đang mở đã chuyển lên | thảo luận |
| The best agents leave within a year | → | The phone line closes at five and the emails start at five past | đang mở | thảo luận |
| Most complaints are about waiting, not about the answer | → | Complaints are counted only when someone uses the word complaint | ✓ có | thảo luận |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints about one feature spike after every release | ✓ có | thảo luận |
| Angry customers are moved to the back of the queue by the priority rules | → | Complaints are counted only when someone uses the word complaint | ✓ có | thảo luận |
| Most complaints are about waiting, not about the answer | → | A customer who complains twice gets the same first reply both times | ✓ có | thảo luận |
| A customer who complains twice gets the same first reply both times | → | Most complaints are about waiting, not about the answer | ✓ có | thảo luận |
| Refund policy is different on the website, in the app and in the script | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✓ có | thảo luận |
| Refund policy is different on the website, in the app and in the script | → | A customer who complains twice gets the same first reply both times | ✓ có | thảo luận |
| A customer who complains twice gets the same first reply both times | → | Complaints are counted only when someone uses the word complaint | ✓ có | thảo luận |
| Agents who take the time to fix a problem properly miss their numbers | → | Refund policy is different on the website, in the app and in the script | ✓ có | thảo luận |
| Angry customers are moved to the back of the queue by the priority rules | → | Agents who take the time to fix a problem properly miss their numbers | ✓ có | thảo luận |
| Survey requests go out before the problem is solved | → | The same question is answered a hundred times because the help page is wrong | ✓ có | thảo luận |
| Survey requests go out before the problem is solved | → | Templates make every reply sound like nobody read the message | ✓ có | thảo luận |
| Nobody from product reads the ticket tags | → | Survey requests go out before the problem is solved | ✓ có | thảo luận |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Survey requests go out before the problem is solved | ✓ có | thảo luận |
| Nobody from product reads the ticket tags | → | The best agents leave within a year | ✓ có | thảo luận |
| Nobody from product reads the ticket tags | → | The same question is answered a hundred times because the help page is wrong | ✓ có | thảo luận |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints are counted only when someone uses the word complaint | ✓ suy ra | thảo luận |
| Complaints are counted only when someone uses the word complaint | → | A customer who complains twice gets the same first reply both times | ✗ không | thảo luận |
| Refund policy is different on the website, in the app and in the script | → | Most complaints are about waiting, not about the answer | ✗ không | thảo luận |
| … | → | Complaints are counted only when someone uses the word complaint | ✗ không | thảo luận |
| The knowledge base is written by people who have never taken a call | → | Complaints are counted only when someone uses the word complaint | ✗ không | thảo luận |
| The knowledge base is written by people who have never taken a call | → | Refund policy is different on the website, in the app and in the script | ✗ không | thảo luận |
| Angry customers are moved to the back of the queue by the priority rules | → | A customer who complains twice gets the same first reply both times | ✗ không | thảo luận |
| Complaints are counted only when someone uses the word complaint | → | Agents who take the time to fix a problem properly miss their numbers | ✗ không | thảo luận |
| The knowledge base is written by people who have never taken a call | → | Most complaints are about waiting, not about the answer | ✗ không | thảo luận |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Most complaints are about waiting, not about the answer | ✗ không | thảo luận |
| Angry customers are moved to the back of the queue by the priority rules | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ không | thảo luận |
| The knowledge base is written by people who have never taken a call | → | Agents who take the time to fix a problem properly miss their numbers | ✗ không | thảo luận |
| Angry customers are moved to the back of the queue by the priority rules | → | Refund policy is different on the website, in the app and in the script | ✗ không | thảo luận |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | … | ✗ không | thảo luận |
| Agents who take the time to fix a problem properly miss their numbers | → | The knowledge base is written by people who have never taken a call | ✗ không | thảo luận |
| Refund policy is different on the website, in the app and in the script | → | Complaints are counted only when someone uses the word complaint | ✗ không | thảo luận |
| Most complaints are about waiting, not about the answer | → | Complaints about one feature spike after every release | ✗ không | thảo luận |
| Most complaints are about waiting, not about the answer | → | Agents who take the time to fix a problem properly miss their numbers | ✗ không | thảo luận |
| Agents who take the time to fix a problem properly miss their numbers | → | Angry customers are moved to the back of the queue by the priority rules | ✗ không | thảo luận |
| The knowledge base is written by people who have never taken a call | → | Angry customers are moved to the back of the queue by the priority rules | ✗ không | thảo luận |
| Complaints are counted only when someone uses the word complaint | → | Most complaints are about waiting, not about the answer | ✗ không | thảo luận |
| Most complaints are about waiting, not about the answer | → | Angry customers are moved to the back of the queue by the priority rules | ✗ không | thảo luận |
| … | → | A customer who complains twice gets the same first reply both times | ✗ không | thảo luận |
| A customer who complains twice gets the same first reply both times | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ không | thảo luận |
| Complaints about one feature spike after every release | → | Complaints are counted only when someone uses the word complaint | ✗ không | thảo luận |
| A customer who complains twice gets the same first reply both times | → | … | ✗ không | thảo luận |
| Complaints about one feature spike after every release | → | Agents who take the time to fix a problem properly miss their numbers | ✗ không | thảo luận |
| Angry customers are moved to the back of the queue by the priority rules | → | Most complaints are about waiting, not about the answer | ✗ không | thảo luận |
| … | → | Angry customers are moved to the back of the queue by the priority rules | ✗ không | thảo luận |
| Agents who take the time to fix a problem properly miss their numbers | → | … | ✗ không | thảo luận |
| A customer who complains twice gets the same first reply both times | → | Agents who take the time to fix a problem properly miss their numbers | ✗ không | thảo luận |
| Complaints about one feature spike after every release | → | Refund policy is different on the website, in the app and in the script | ✗ không | thảo luận |
| A customer who complains twice gets the same first reply both times | → | Refund policy is different on the website, in the app and in the script | ✗ không | đang mở ↑ · đóng ✕ |
| Refund policy is different on the website, in the app and in the script | → | The knowledge base is written by people who have never taken a call | ✗ không | thảo luận |
| Complaints about one feature spike after every release | → | The knowledge base is written by people who have never taken a call | ✗ không | thảo luận |
| Agents who take the time to fix a problem properly miss their numbers | → | A customer who complains twice gets the same first reply both times | ✗ không | thảo luận |
| … | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ không | thảo luận |
| Complaints about one feature spike after every release | → | Most complaints are about waiting, not about the answer | ✗ không | thảo luận |
| … | → | The knowledge base is written by people who have never taken a call | ✗ không | thảo luận |
| Complaints are counted only when someone uses the word complaint | → | Refund policy is different on the website, in the app and in the script | ✗ không | thảo luận |
| Complaints are counted only when someone uses the word complaint | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ không | thảo luận |
| Most complaints are about waiting, not about the answer | → | … | ✗ không | thảo luận |
| Agents who take the time to fix a problem properly miss their numbers | → | Most complaints are about waiting, not about the answer | ✗ không | thảo luận |
| Complaints are counted only when someone uses the word complaint | → | Angry customers are moved to the back of the queue by the priority rules | ✗ không | thảo luận |
| Angry customers are moved to the back of the queue by the priority rules | → | … | ✗ không | thảo luận |
| Most complaints are about waiting, not about the answer | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ không | thảo luận |
| Complaints are counted only when someone uses the word complaint | → | … | ✗ không | thảo luận |
| The knowledge base is written by people who have never taken a call | → | A customer who complains twice gets the same first reply both times | ✗ không | thảo luận |
| … | → | Complaints about one feature spike after every release | ✗ không | thảo luận |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Refund policy is different on the website, in the app and in the script | ✗ không | thảo luận |
| Refund policy is different on the website, in the app and in the script | → | Angry customers are moved to the back of the queue by the priority rules | ✗ không | thảo luận |
| The knowledge base is written by people who have never taken a call | → | Complaints about one feature spike after every release | ✗ không | thảo luận |
| Complaints are counted only when someone uses the word complaint | → | The knowledge base is written by people who have never taken a call | ✗ không | thảo luận |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | A customer who complains twice gets the same first reply both times | ✗ không | thảo luận |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Complaints about one feature spike after every release | ✗ không | thảo luận |
| Refund policy is different on the website, in the app and in the script | → | Agents who take the time to fix a problem properly miss their numbers | ✗ không | thảo luận |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | The knowledge base is written by people who have never taken a call | ✗ không | thảo luận |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Agents who take the time to fix a problem properly miss their numbers | ✗ không | thảo luận |
| Complaints about one feature spike after every release | → | Angry customers are moved to the back of the queue by the priority rules | ✗ không | thảo luận |
| Refund policy is different on the website, in the app and in the script | → | Complaints about one feature spike after every release | ✗ không | thảo luận |
| Angry customers are moved to the back of the queue by the priority rules | → | Complaints about one feature spike after every release | ✗ không | thảo luận |
| A customer who complains twice gets the same first reply both times | → | Angry customers are moved to the back of the queue by the priority rules | ✗ không | thảo luận |
| Complaints are counted only when someone uses the word complaint | → | Complaints about one feature spike after every release | ✗ không | thảo luận |
| Complaints about one feature spike after every release | → | A customer who complains twice gets the same first reply both times | ✗ không | thảo luận |
| Angry customers are moved to the back of the queue by the priority rules | → | The knowledge base is written by people who have never taken a call | ✗ không | thảo luận |
| … | → | Most complaints are about waiting, not about the answer | ✗ không | thảo luận |
| Complaints about one feature spike after every release | → | … | ✗ không | thảo luận |
| A customer who complains twice gets the same first reply both times | → | Complaints about one feature spike after every release | ✗ không | thảo luận |
| … | → | Agents who take the time to fix a problem properly miss their numbers | ✗ không | thảo luận |
| The knowledge base is written by people who have never taken a call | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ không | thảo luận |
| Most complaints are about waiting, not about the answer | → | The knowledge base is written by people who have never taken a call | ✗ không | thảo luận |
| Most complaints are about waiting, not about the answer | → | Refund policy is different on the website, in the app and in the script | ✗ không | thảo luận |
| Complaints about one feature spike after every release | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ không | thảo luận |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Angry customers are moved to the back of the queue by the priority rules | ✗ không | thảo luận |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Complaints are counted only when someone uses the word complaint | ✗ không | thảo luận |
| … | → | Refund policy is different on the website, in the app and in the script | ✗ không | thảo luận |
| The knowledge base is written by people who have never taken a call | → | … | ✗ không | thảo luận |
| A customer who complains twice gets the same first reply both times | → | The knowledge base is written by people who have never taken a call | ✗ không | thảo luận |
| Agents who take the time to fix a problem properly miss their numbers | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ không | thảo luận |
| Escalations go to a team that does not read the ticket history | → | Survey requests go out before the problem is solved | ✗ không | thảo luận |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | The best agents leave within a year | ✗ không | thảo luận |
| Survey requests go out before the problem is solved | → | The best agents leave within a year | ✗ không | thảo luận |
| Escalations go to a team that does not read the ticket history | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ không | thảo luận |
| The best agents leave within a year | → | Survey requests go out before the problem is solved | ✗ không | thảo luận |
| Nobody from product reads the ticket tags | → | Templates make every reply sound like nobody read the message | ✗ không | thảo luận |
| Survey requests go out before the problem is solved | → | Nobody from product reads the ticket tags | ✗ không | thảo luận |
| … | → | Survey requests go out before the problem is solved | ✗ không | thảo luận |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Templates make every reply sound like nobody read the message | ✗ không | thảo luận |
| The phone line closes at five and the emails start at five past | → | Escalations go to a team that does not read the ticket history | ✗ không | thảo luận |
| Customers repeat their problem to every person they are passed to | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ không | thảo luận |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | … | ✗ không | thảo luận |
| Nobody from product reads the ticket tags | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ không | thảo luận |
| Escalations go to a team that does not read the ticket history | → | Nobody from product reads the ticket tags | ✗ không | thảo luận |
| Survey requests go out before the problem is solved | → | Escalations go to a team that does not read the ticket history | ✗ không | thảo luận |
| Customers repeat their problem to every person they are passed to | → | The phone line closes at five and the emails start at five past | ✗ không | thảo luận |
| … | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ không | thảo luận |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | The same question is answered a hundred times because the help page is wrong | ✗ không | thảo luận |
| The same question is answered a hundred times because the help page is wrong | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ không | thảo luận |
| The best agents leave within a year | → | Nobody from product reads the ticket tags | ✗ không | thảo luận |
| The same question is answered a hundred times because the help page is wrong | → | … | ✗ không | thảo luận |
| Nobody from product reads the ticket tags | → | Customers repeat their problem to every person they are passed to | ✗ không | thảo luận |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Nobody from product reads the ticket tags | ✗ không | thảo luận |
| Customers repeat their problem to every person they are passed to | → | Templates make every reply sound like nobody read the message | ✗ không | thảo luận |
| Survey requests go out before the problem is solved | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ không | thảo luận |
| The phone line closes at five and the emails start at five past | → | Nobody from product reads the ticket tags | ✗ không | thảo luận |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Escalations go to a team that does not read the ticket history | ✗ không | thảo luận |
| The best agents leave within a year | → | Customers repeat their problem to every person they are passed to | ✗ không | thảo luận |
| The phone line closes at five and the emails start at five past | → | The best agents leave within a year | ✗ không | thảo luận |
| The same question is answered a hundred times because the help page is wrong | → | The phone line closes at five and the emails start at five past | ✗ không | thảo luận |
| Templates make every reply sound like nobody read the message | → | The phone line closes at five and the emails start at five past | ✗ không | thảo luận |
| The best agents leave within a year | → | The same question is answered a hundred times because the help page is wrong | ✗ không | thảo luận |
| Templates make every reply sound like nobody read the message | → | Nobody from product reads the ticket tags | ✗ không | thảo luận |
| … | → | Escalations go to a team that does not read the ticket history | ✗ không | thảo luận |
| Templates make every reply sound like nobody read the message | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ không | thảo luận |
| Nobody from product reads the ticket tags | → | The phone line closes at five and the emails start at five past | ✗ không | thảo luận |
| Customers repeat their problem to every person they are passed to | → | Escalations go to a team that does not read the ticket history | ✗ không | thảo luận |
| Customers repeat their problem to every person they are passed to | → | Nobody from product reads the ticket tags | ✗ không | thảo luận |
| The same question is answered a hundred times because the help page is wrong | → | The best agents leave within a year | ✗ không | thảo luận |
| Escalations go to a team that does not read the ticket history | → | The same question is answered a hundred times because the help page is wrong | ✗ không | thảo luận |
| The phone line closes at five and the emails start at five past | → | The same question is answered a hundred times because the help page is wrong | ✗ không | thảo luận |
| The same question is answered a hundred times because the help page is wrong | → | Nobody from product reads the ticket tags | ✗ không | thảo luận |
| Customers repeat their problem to every person they are passed to | → | The same question is answered a hundred times because the help page is wrong | ✗ không | thảo luận |
| The phone line closes at five and the emails start at five past | → | Templates make every reply sound like nobody read the message | ✗ không | thảo luận |
| The best agents leave within a year | → | Templates make every reply sound like nobody read the message | ✗ không | thảo luận |
| The phone line closes at five and the emails start at five past | → | Survey requests go out before the problem is solved | ✗ không | thảo luận |
| Templates make every reply sound like nobody read the message | → | Customers repeat their problem to every person they are passed to | ✗ không | thảo luận |
| Survey requests go out before the problem is solved | → | … | ✗ không | thảo luận |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | The phone line closes at five and the emails start at five past | ✗ không | thảo luận |
| Escalations go to a team that does not read the ticket history | → | Templates make every reply sound like nobody read the message | ✗ không | thảo luận |
| … | → | The best agents leave within a year | ✗ không | thảo luận |
| The same question is answered a hundred times because the help page is wrong | → | Survey requests go out before the problem is solved | ✗ không | thảo luận |
| Templates make every reply sound like nobody read the message | → | The same question is answered a hundred times because the help page is wrong | ✗ không | thảo luận |
| Templates make every reply sound like nobody read the message | → | The best agents leave within a year | ✗ không | thảo luận |
| Customers repeat their problem to every person they are passed to | → | Survey requests go out before the problem is solved | ✗ không | thảo luận |
| Templates make every reply sound like nobody read the message | → | Survey requests go out before the problem is solved | ✗ không | thảo luận |
| Templates make every reply sound like nobody read the message | → | … | ✗ không | thảo luận |
| … | → | The same question is answered a hundred times because the help page is wrong | ✗ không | thảo luận |
| Escalations go to a team that does not read the ticket history | → | The best agents leave within a year | ✗ không | thảo luận |
| Nobody from product reads the ticket tags | → | … | ✗ không | thảo luận |
| The same question is answered a hundred times because the help page is wrong | → | Escalations go to a team that does not read the ticket history | ✗ không | thảo luận |
| … | → | Nobody from product reads the ticket tags | ✗ không | thảo luận |
| Survey requests go out before the problem is solved | → | The phone line closes at five and the emails start at five past | ✗ không | thảo luận |
| Escalations go to a team that does not read the ticket history | → | The phone line closes at five and the emails start at five past | ✗ không | thảo luận |
| The phone line closes at five and the emails start at five past | → | Customers repeat their problem to every person they are passed to | ✗ không | thảo luận |
| Escalations go to a team that does not read the ticket history | → | Customers repeat their problem to every person they are passed to | ✗ không | thảo luận |
| The same question is answered a hundred times because the help page is wrong | → | Templates make every reply sound like nobody read the message | ✗ không | thảo luận |
| Customers repeat their problem to every person they are passed to | → | … | ✗ không | thảo luận |
| … | → | Customers repeat their problem to every person they are passed to | ✗ không | thảo luận |
| Survey requests go out before the problem is solved | → | Customers repeat their problem to every person they are passed to | ✗ không | thảo luận |
| The phone line closes at five and the emails start at five past | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ không | thảo luận |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Customers repeat their problem to every person they are passed to | ✗ không | thảo luận |
| Templates make every reply sound like nobody read the message | → | Escalations go to a team that does not read the ticket history | ✗ không | thảo luận |
| … | → | The phone line closes at five and the emails start at five past | ✗ không | thảo luận |
| Customers repeat their problem to every person they are passed to | → | The best agents leave within a year | ✗ không | thảo luận |
| The best agents leave within a year | → | Escalations go to a team that does not read the ticket history | ✗ không | thảo luận |
| The best agents leave within a year | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ không | thảo luận |
| Nobody from product reads the ticket tags | → | Escalations go to a team that does not read the ticket history | ✗ không | thảo luận |
| The best agents leave within a year | → | … | ✗ không | thảo luận |
| Escalations go to a team that does not read the ticket history | → | … | ✗ không | thảo luận |
| … | → | Templates make every reply sound like nobody read the message | ✗ không | thảo luận |
| The same question is answered a hundred times because the help page is wrong | → | Customers repeat their problem to every person they are passed to | ✗ không | thảo luận |