ПИТАННЯ
Why do complaints keep rising while the product improves?
Чи суттєво одне впливає на інше? Вирішують три чверті поданих голосів.
закрито · назад до етапу Дії
Ви переглядаєте як гість. Введіть ім’я користувача, щоб приєднатися й брати участь.
Питання розподіляються між групами, тож ви отримуєте ті, що дісталися вашій групі, — а не всі 180.
вирішено: 177 / 180 чекають вашої відповіді: 0 чому
Ніхто не зміг би відповісти на кілька сотень пар. Кожна пара дістається одній групі; пару, у якій думки розділилися, потім передають іншим групам, тож вона може пізніше з’явитися у вашому списку, хоча почалася деінде. Кількість вирішених охоплює роботу всіх груп, тому вона росте швидше, ніж скорочується ваш список.
Останній підрахунок: вирішено: 177 · передано міжгруповим панелям: 2 · спірно: 0 · нижче кворуму: 1 — панелям потрібно щонайменше max(2, 75% панелі) поданих голосів; у вашій найменшій панелі 15 учасників.
Nobody from product reads the ticket tags → впливає на? → The same question is answered a hundred times because the help page is wrong
Ще нічого не сказано.
Етап завершено — запис пар і голосів наведено вище.Перевірити логіку ↗
| Refund policy is different on the website, in the app and in the script | → | … | відкрито передано далі | обговорити |
| The phone line closes at five and the emails start at five past | → | … | відкрито передано далі | обговорити |
| The best agents leave within a year | → | The phone line closes at five and the emails start at five past | відкрито | обговорити |
| Most complaints are about waiting, not about the answer | → | Complaints are counted only when someone uses the word complaint | ✓ так | обговорити |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints about one feature spike after every release | ✓ так | обговорити |
| Angry customers are moved to the back of the queue by the priority rules | → | Complaints are counted only when someone uses the word complaint | ✓ так | обговорити |
| Most complaints are about waiting, not about the answer | → | A customer who complains twice gets the same first reply both times | ✓ так | обговорити |
| A customer who complains twice gets the same first reply both times | → | Most complaints are about waiting, not about the answer | ✓ так | обговорити |
| 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 | ✓ так | обговорити |
| 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 | ✓ так | обговорити |
| A customer who complains twice gets the same first reply both times | → | Complaints are counted only when someone uses the word complaint | ✓ так | обговорити |
| 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 | ✓ так | обговорити |
| 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 | ✓ так | обговорити |
| Survey requests go out before the problem is solved | → | The same question is answered a hundred times because the help page is wrong | ✓ так | обговорити |
| Survey requests go out before the problem is solved | → | Templates make every reply sound like nobody read the message | ✓ так | обговорити |
| Nobody from product reads the ticket tags | → | Survey requests go out before the problem is solved | ✓ так | обговорити |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Survey requests go out before the problem is solved | ✓ так | обговорити |
| Nobody from product reads the ticket tags | → | The best agents leave within a year | ✓ так | обговорити |
| Nobody from product reads the ticket tags | → | The same question is answered a hundred times because the help page is wrong | ✓ так | у фокусі ↑ · закрити ✕ |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints are counted only when someone uses the word complaint | ✓ виведено | обговорити |
| Complaints are counted only when someone uses the word complaint | → | 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 | → | Most complaints are about waiting, not about the answer | ✗ ні | обговорити |
| … | → | Complaints are counted only when someone uses the word complaint | ✗ ні | обговорити |
| The knowledge base is written by people who have never taken a call | → | Complaints are counted only when someone uses the word complaint | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Complaints are counted only when someone uses the word complaint | → | 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 | → | Most complaints are about waiting, not about the answer | ✗ ні | обговорити |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Most complaints are about waiting, not about the answer | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| 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 | → | 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 | → | Complaints are counted only when someone uses the word complaint | ✗ ні | обговорити |
| Most complaints are about waiting, not about the answer | → | Complaints about one feature spike after every release | ✗ ні | обговорити |
| Most complaints are about waiting, not about the answer | → | Agents who take the time to fix a problem properly miss their numbers | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Complaints are counted only when someone uses the word complaint | → | Most complaints are about waiting, not about the answer | ✗ ні | обговорити |
| Most complaints are about waiting, not about the answer | → | 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Complaints about one feature spike after every release | → | Complaints are counted only when someone uses the word complaint | ✗ ні | обговорити |
| A customer who complains twice gets the same first reply both times | → | … | ✗ ні | обговорити |
| Complaints about one feature spike after every release | → | 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 | → | Most complaints are about waiting, not about the answer | ✗ ні | обговорити |
| … | → | 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 | → | … | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Complaints about one feature spike after every release | → | 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 | → | Refund policy is different on the website, in the app and in the script | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Complaints about one feature spike after every release | → | 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 | → | 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 | ✗ ні | обговорити |
| Complaints about one feature spike after every release | → | Most complaints are about waiting, not about the answer | ✗ ні | обговорити |
| … | → | The knowledge base is written by people who have never taken a call | ✗ ні | обговорити |
| Complaints are counted only when someone uses the word complaint | → | Refund policy is different on the website, in the app and in the script | ✗ ні | обговорити |
| Complaints are counted only when someone uses the word complaint | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ ні | обговорити |
| Most complaints are about waiting, not about the answer | → | … | ✗ ні | обговорити |
| Agents who take the time to fix a problem properly miss their numbers | → | Most complaints are about waiting, not about the answer | ✗ ні | обговорити |
| Complaints are counted only when someone uses the word complaint | → | Angry customers are moved to the back of the queue by the priority rules | ✗ ні | обговорити |
| Angry customers are moved to the back of the queue by the priority rules | → | … | ✗ ні | обговорити |
| Most complaints are about waiting, not about the answer | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ ні | обговорити |
| Complaints are counted only when someone uses the word complaint | → | … | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| … | → | Complaints about one feature spike after every release | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| The knowledge base is written by people who have never taken a call | → | Complaints about one feature spike after every release | ✗ ні | обговорити |
| Complaints are counted only when someone uses the word complaint | → | 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 | → | 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 | → | Complaints about one feature spike after every release | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Complaints about one feature spike after every release | → | 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 | → | Complaints about one feature spike after every release | ✗ ні | обговорити |
| Angry customers are moved to the back of the queue by the priority rules | → | Complaints about one feature spike after every release | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Complaints are counted only when someone uses the word complaint | → | Complaints about one feature spike after every release | ✗ ні | обговорити |
| Complaints about one feature spike after every release | → | 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 | → | The knowledge base is written by people who have never taken a call | ✗ ні | обговорити |
| … | → | Most complaints are about waiting, not about the answer | ✗ ні | обговорити |
| Complaints about one feature spike after every release | → | … | ✗ ні | обговорити |
| A customer who complains twice gets the same first reply both times | → | Complaints about one feature spike after every release | ✗ ні | обговорити |
| … | → | 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 | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ ні | обговорити |
| Most complaints are about waiting, not about the answer | → | The knowledge base is written by people who have never taken a call | ✗ ні | обговорити |
| Most complaints are about waiting, not about the answer | → | Refund policy is different on the website, in the app and in the script | ✗ ні | обговорити |
| Complaints about one feature spike after every release | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Complaints are counted only when someone uses the word complaint | ✗ ні | обговорити |
| … | → | 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 | → | … | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Escalations go to a team that does not read the ticket history | → | Survey requests go out before the problem is solved | ✗ ні | обговорити |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | The best agents leave within a year | ✗ ні | обговорити |
| Survey requests go out before the problem is solved | → | The best agents leave within a year | ✗ ні | обговорити |
| Escalations go to a team that does not read the ticket history | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ ні | обговорити |
| The best agents leave within a year | → | Survey requests go out before the problem is solved | ✗ ні | обговорити |
| Nobody from product reads the ticket tags | → | Templates make every reply sound like nobody read the message | ✗ ні | обговорити |
| Survey requests go out before the problem is solved | → | Nobody from product reads the ticket tags | ✗ ні | обговорити |
| … | → | Survey requests go out before the problem is solved | ✗ ні | обговорити |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Templates make every reply sound like nobody read the message | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Customers repeat their problem to every person they are passed to | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ ні | обговорити |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | … | ✗ ні | обговорити |
| Nobody from product reads the ticket tags | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ ні | обговорити |
| Escalations go to a team that does not read the ticket history | → | Nobody from product reads the ticket tags | ✗ ні | обговорити |
| Survey requests go out before the problem is solved | → | Escalations go to a team that does not read the ticket history | ✗ ні | обговорити |
| Customers repeat their problem to every person they are passed to | → | 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| The best agents leave within a year | → | Nobody from product reads the ticket tags | ✗ ні | обговорити |
| The same question is answered a hundred times because the help page is wrong | → | … | ✗ ні | обговорити |
| Nobody from product reads the ticket tags | → | Customers repeat their problem to every person they are passed to | ✗ ні | обговорити |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Nobody from product reads the ticket tags | ✗ ні | обговорити |
| Customers repeat their problem to every person they are passed to | → | Templates make every reply sound like nobody read the message | ✗ ні | обговорити |
| Survey requests go out before the problem is solved | → | 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 | → | Nobody from product reads the ticket tags | ✗ ні | обговорити |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Escalations go to a team that does not read the ticket history | ✗ ні | обговорити |
| The best agents leave within a year | → | Customers repeat their problem to every person they are passed to | ✗ ні | обговорити |
| The phone line closes at five and the emails start at five past | → | The best agents leave within a year | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Templates make every reply sound like nobody read the message | → | The phone line closes at five and the emails start at five past | ✗ ні | обговорити |
| The best agents leave within a year | → | The same question is answered a hundred times because the help page is wrong | ✗ ні | обговорити |
| Templates make every reply sound like nobody read the message | → | Nobody from product reads the ticket tags | ✗ ні | обговорити |
| … | → | Escalations go to a team that does not read the ticket history | ✗ ні | обговорити |
| Templates make every reply sound like nobody read the message | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ ні | обговорити |
| Nobody from product reads the ticket tags | → | The phone line closes at five and the emails start at five past | ✗ ні | обговорити |
| Customers repeat their problem to every person they are passed to | → | Escalations go to a team that does not read the ticket history | ✗ ні | обговорити |
| Customers repeat their problem to every person they are passed to | → | Nobody from product reads the ticket tags | ✗ ні | обговорити |
| The same question is answered a hundred times because the help page is wrong | → | The best agents leave within a year | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| The same question is answered a hundred times because the help page is wrong | → | Nobody from product reads the ticket tags | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| The phone line closes at five and the emails start at five past | → | Templates make every reply sound like nobody read the message | ✗ ні | обговорити |
| The best agents leave within a year | → | Templates make every reply sound like nobody read the message | ✗ ні | обговорити |
| The phone line closes at five and the emails start at five past | → | Survey requests go out before the problem is solved | ✗ ні | обговорити |
| Templates make every reply sound like nobody read the message | → | Customers repeat their problem to every person they are passed to | ✗ ні | обговорити |
| Survey requests go out before the problem is solved | → | … | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Escalations go to a team that does not read the ticket history | → | Templates make every reply sound like nobody read the message | ✗ ні | обговорити |
| … | → | The best agents leave within a year | ✗ ні | обговорити |
| The same question is answered a hundred times because the help page is wrong | → | Survey requests go out before the problem is solved | ✗ ні | обговорити |
| Templates make every reply sound like nobody read the message | → | The same question is answered a hundred times because the help page is wrong | ✗ ні | обговорити |
| Templates make every reply sound like nobody read the message | → | The best agents leave within a year | ✗ ні | обговорити |
| Customers repeat their problem to every person they are passed to | → | Survey requests go out before the problem is solved | ✗ ні | обговорити |
| Templates make every reply sound like nobody read the message | → | Survey requests go out before the problem is solved | ✗ ні | обговорити |
| Templates make every reply sound like nobody read the message | → | … | ✗ ні | обговорити |
| … | → | 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 | → | The best agents leave within a year | ✗ ні | обговорити |
| Nobody from product reads the ticket tags | → | … | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| … | → | Nobody from product reads the ticket tags | ✗ ні | обговорити |
| Survey requests go out before the problem is solved | → | 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 | → | The phone line closes at five and the emails start at five past | ✗ ні | обговорити |
| The phone line closes at five and the emails start at five past | → | Customers repeat their problem to every person they are passed to | ✗ ні | обговорити |
| Escalations go to a team that does not read the ticket history | → | 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 | → | Templates make every reply sound like nobody read the message | ✗ ні | обговорити |
| Customers repeat their problem to every person they are passed to | → | … | ✗ ні | обговорити |
| … | → | Customers repeat their problem to every person they are passed to | ✗ ні | обговорити |
| Survey requests go out before the problem is solved | → | Customers repeat their problem to every person they are passed to | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Customers repeat their problem to every person they are passed to | ✗ ні | обговорити |
| Templates make every reply sound like nobody read the message | → | 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 | ✗ ні | обговорити |
| Customers repeat their problem to every person they are passed to | → | The best agents leave within a year | ✗ ні | обговорити |
| The best agents leave within a year | → | Escalations go to a team that does not read the ticket history | ✗ ні | обговорити |
| The best agents leave within a year | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ ні | обговорити |
| Nobody from product reads the ticket tags | → | Escalations go to a team that does not read the ticket history | ✗ ні | обговорити |
| The best agents leave within a year | → | … | ✗ ні | обговорити |
| Escalations go to a team that does not read the ticket history | → | … | ✗ ні | обговорити |
| … | → | Templates make every reply sound like nobody read the message | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |