DIE FRAGE
Why do complaints keep rising while the product improves?
Beeinflusst das eine das andere maßgeblich? Es entscheiden drei Viertel der abgegebenen Stimmen.
geschlossen · zurück zu Maßnahmen
Ansicht als Gast. Benutzernamen eingeben, um beizutreten und mitzumachen.
Die Fragen werden auf die Gruppen verteilt, daher bekommen Sie die, die Ihre Gruppe erhalten hat — nicht alle 180.
177 / 180 entschieden 0 für Sie zu beantworten warum
Niemand könnte mehrere hundert Paare beantworten. Jedes Paar geht an eine Gruppe; ist sie uneinig, wird das Paar an andere Gruppen weitergegeben, daher kann es später in Ihrer Liste auftauchen, obwohl es woanders begonnen hat. Die Zahl der entschiedenen Fragen enthält die Arbeit aller Gruppen, deshalb steigt sie schneller, als Ihre eigene Liste schrumpft.
Letzte Auszählung: 177 entschieden · 2 an gruppenübergreifende Panels weitergegeben · 0 umstritten · 1 unter dem Quorum — Panels brauchen mindestens max(2, 75 % des Panels) abgegebene Stimmen; Ihr kleinstes Panel hat 15 Mitglieder.
The best agents leave within a year → beeinflusst? → Customers repeat their problem to every person they are passed to
Noch nichts gesagt.
Abgeschlossene Phase — das Protokoll der Paare und Stimmen steht oben.Logik prüfen ↗
| Refund policy is different on the website, in the app and in the script | → | … | offen weitergegeben | diskutieren |
| The phone line closes at five and the emails start at five past | → | … | offen weitergegeben | diskutieren |
| The best agents leave within a year | → | The phone line closes at five and the emails start at five past | offen | diskutieren |
| Most complaints are about waiting, not about the answer | → | Complaints are counted only when someone uses the word complaint | ✓ ja | diskutieren |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints about one feature spike after every release | ✓ ja | diskutieren |
| Angry customers are moved to the back of the queue by the priority rules | → | Complaints are counted only when someone uses the word complaint | ✓ ja | diskutieren |
| Most complaints are about waiting, not about the answer | → | A customer who complains twice gets the same first reply both times | ✓ ja | diskutieren |
| A customer who complains twice gets the same first reply both times | → | Most complaints are about waiting, not about the answer | ✓ ja | diskutieren |
| 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 | ✓ ja | diskutieren |
| 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 | ✓ ja | diskutieren |
| A customer who complains twice gets the same first reply both times | → | Complaints are counted only when someone uses the word complaint | ✓ ja | diskutieren |
| 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 | ✓ ja | diskutieren |
| 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 | ✓ ja | diskutieren |
| Survey requests go out before the problem is solved | → | The same question is answered a hundred times because the help page is wrong | ✓ ja | diskutieren |
| Survey requests go out before the problem is solved | → | Templates make every reply sound like nobody read the message | ✓ ja | diskutieren |
| Nobody from product reads the ticket tags | → | Survey requests go out before the problem is solved | ✓ ja | diskutieren |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Survey requests go out before the problem is solved | ✓ ja | diskutieren |
| Nobody from product reads the ticket tags | → | The best agents leave within a year | ✓ ja | diskutieren |
| Nobody from product reads the ticket tags | → | The same question is answered a hundred times because the help page is wrong | ✓ ja | diskutieren |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints are counted only when someone uses the word complaint | ✓ abgeleitet | diskutieren |
| Complaints are counted only when someone uses the word complaint | → | A customer who complains twice gets the same first reply both times | ✗ nein | diskutieren |
| Refund policy is different on the website, in the app and in the script | → | Most complaints are about waiting, not about the answer | ✗ nein | diskutieren |
| … | → | Complaints are counted only when someone uses the word complaint | ✗ nein | diskutieren |
| The knowledge base is written by people who have never taken a call | → | Complaints are counted only when someone uses the word complaint | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Complaints are counted only when someone uses the word complaint | → | Agents who take the time to fix a problem properly miss their numbers | ✗ nein | diskutieren |
| The knowledge base is written by people who have never taken a call | → | Most complaints are about waiting, not about the answer | ✗ nein | diskutieren |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Most complaints are about waiting, not about the answer | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | … | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Refund policy is different on the website, in the app and in the script | → | Complaints are counted only when someone uses the word complaint | ✗ nein | diskutieren |
| Most complaints are about waiting, not about the answer | → | Complaints about one feature spike after every release | ✗ nein | diskutieren |
| Most complaints are about waiting, not about the answer | → | Agents who take the time to fix a problem properly miss their numbers | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Complaints are counted only when someone uses the word complaint | → | Most complaints are about waiting, not about the answer | ✗ nein | diskutieren |
| Most complaints are about waiting, not about the answer | → | Angry customers are moved to the back of the queue by the priority rules | ✗ nein | diskutieren |
| … | → | A customer who complains twice gets the same first reply both times | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Complaints about one feature spike after every release | → | Complaints are counted only when someone uses the word complaint | ✗ nein | diskutieren |
| A customer who complains twice gets the same first reply both times | → | … | ✗ nein | diskutieren |
| Complaints about one feature spike after every release | → | Agents who take the time to fix a problem properly miss their numbers | ✗ nein | diskutieren |
| Angry customers are moved to the back of the queue by the priority rules | → | Most complaints are about waiting, not about the answer | ✗ nein | diskutieren |
| … | → | Angry customers are moved to the back of the queue by the priority rules | ✗ nein | diskutieren |
| Agents who take the time to fix a problem properly miss their numbers | → | … | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Complaints about one feature spike after every release | → | Refund policy is different on the website, in the app and in the script | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Complaints about one feature spike after every release | → | The knowledge base is written by people who have never taken a call | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| … | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ nein | diskutieren |
| Complaints about one feature spike after every release | → | Most complaints are about waiting, not about the answer | ✗ nein | diskutieren |
| … | → | The knowledge base is written by people who have never taken a call | ✗ nein | diskutieren |
| Complaints are counted only when someone uses the word complaint | → | Refund policy is different on the website, in the app and in the script | ✗ nein | diskutieren |
| Complaints are counted only when someone uses the word complaint | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ nein | diskutieren |
| Most complaints are about waiting, not about the answer | → | … | ✗ nein | diskutieren |
| Agents who take the time to fix a problem properly miss their numbers | → | Most complaints are about waiting, not about the answer | ✗ nein | diskutieren |
| Complaints are counted only when someone uses the word complaint | → | Angry customers are moved to the back of the queue by the priority rules | ✗ nein | diskutieren |
| Angry customers are moved to the back of the queue by the priority rules | → | … | ✗ nein | diskutieren |
| Most complaints are about waiting, not about the answer | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ nein | diskutieren |
| Complaints are counted only when someone uses the word complaint | → | … | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| … | → | Complaints about one feature spike after every release | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| The knowledge base is written by people who have never taken a call | → | Complaints about one feature spike after every release | ✗ nein | diskutieren |
| Complaints are counted only when someone uses the word complaint | → | The knowledge base is written by people who have never taken a call | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Complaints about one feature spike after every release | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Complaints about one feature spike after every release | → | Angry customers are moved to the back of the queue by the priority rules | ✗ nein | diskutieren |
| Refund policy is different on the website, in the app and in the script | → | Complaints about one feature spike after every release | ✗ nein | diskutieren |
| Angry customers are moved to the back of the queue by the priority rules | → | Complaints about one feature spike after every release | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Complaints are counted only when someone uses the word complaint | → | Complaints about one feature spike after every release | ✗ nein | diskutieren |
| Complaints about one feature spike after every release | → | A customer who complains twice gets the same first reply both times | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| … | → | Most complaints are about waiting, not about the answer | ✗ nein | diskutieren |
| Complaints about one feature spike after every release | → | … | ✗ nein | diskutieren |
| A customer who complains twice gets the same first reply both times | → | Complaints about one feature spike after every release | ✗ nein | diskutieren |
| … | → | Agents who take the time to fix a problem properly miss their numbers | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Most complaints are about waiting, not about the answer | → | The knowledge base is written by people who have never taken a call | ✗ nein | diskutieren |
| Most complaints are about waiting, not about the answer | → | Refund policy is different on the website, in the app and in the script | ✗ nein | diskutieren |
| Complaints about one feature spike after every release | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Complaints are counted only when someone uses the word complaint | ✗ nein | diskutieren |
| … | → | Refund policy is different on the website, in the app and in the script | ✗ nein | diskutieren |
| The knowledge base is written by people who have never taken a call | → | … | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Escalations go to a team that does not read the ticket history | → | Survey requests go out before the problem is solved | ✗ nein | diskutieren |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | The best agents leave within a year | ✗ nein | diskutieren |
| Survey requests go out before the problem is solved | → | The best agents leave within a year | ✗ nein | diskutieren |
| Escalations go to a team that does not read the ticket history | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nein | diskutieren |
| The best agents leave within a year | → | Survey requests go out before the problem is solved | ✗ nein | diskutieren |
| Nobody from product reads the ticket tags | → | Templates make every reply sound like nobody read the message | ✗ nein | diskutieren |
| Survey requests go out before the problem is solved | → | Nobody from product reads the ticket tags | ✗ nein | diskutieren |
| … | → | Survey requests go out before the problem is solved | ✗ nein | diskutieren |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Templates make every reply sound like nobody read the message | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Customers repeat their problem to every person they are passed to | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nein | diskutieren |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | … | ✗ nein | diskutieren |
| Nobody from product reads the ticket tags | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nein | diskutieren |
| Escalations go to a team that does not read the ticket history | → | Nobody from product reads the ticket tags | ✗ nein | diskutieren |
| Survey requests go out before the problem is solved | → | Escalations go to a team that does not read the ticket history | ✗ nein | diskutieren |
| Customers repeat their problem to every person they are passed to | → | The phone line closes at five and the emails start at five past | ✗ nein | diskutieren |
| … | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| The best agents leave within a year | → | Nobody from product reads the ticket tags | ✗ nein | diskutieren |
| The same question is answered a hundred times because the help page is wrong | → | … | ✗ nein | diskutieren |
| Nobody from product reads the ticket tags | → | Customers repeat their problem to every person they are passed to | ✗ nein | diskutieren |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Nobody from product reads the ticket tags | ✗ nein | diskutieren |
| Customers repeat their problem to every person they are passed to | → | Templates make every reply sound like nobody read the message | ✗ nein | diskutieren |
| Survey requests go out before the problem is solved | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nein | diskutieren |
| The phone line closes at five and the emails start at five past | → | Nobody from product reads the ticket tags | ✗ nein | diskutieren |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Escalations go to a team that does not read the ticket history | ✗ nein | diskutieren |
| The best agents leave within a year | → | Customers repeat their problem to every person they are passed to | ✗ nein | im Fokus ↑ · schließen ✕ |
| The phone line closes at five and the emails start at five past | → | The best agents leave within a year | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Templates make every reply sound like nobody read the message | → | The phone line closes at five and the emails start at five past | ✗ nein | diskutieren |
| The best agents leave within a year | → | The same question is answered a hundred times because the help page is wrong | ✗ nein | diskutieren |
| Templates make every reply sound like nobody read the message | → | Nobody from product reads the ticket tags | ✗ nein | diskutieren |
| … | → | Escalations go to a team that does not read the ticket history | ✗ nein | diskutieren |
| Templates make every reply sound like nobody read the message | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nein | diskutieren |
| Nobody from product reads the ticket tags | → | The phone line closes at five and the emails start at five past | ✗ nein | diskutieren |
| Customers repeat their problem to every person they are passed to | → | Escalations go to a team that does not read the ticket history | ✗ nein | diskutieren |
| Customers repeat their problem to every person they are passed to | → | Nobody from product reads the ticket tags | ✗ nein | diskutieren |
| The same question is answered a hundred times because the help page is wrong | → | The best agents leave within a year | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| The same question is answered a hundred times because the help page is wrong | → | Nobody from product reads the ticket tags | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| The phone line closes at five and the emails start at five past | → | Templates make every reply sound like nobody read the message | ✗ nein | diskutieren |
| The best agents leave within a year | → | Templates make every reply sound like nobody read the message | ✗ nein | diskutieren |
| The phone line closes at five and the emails start at five past | → | Survey requests go out before the problem is solved | ✗ nein | diskutieren |
| Templates make every reply sound like nobody read the message | → | Customers repeat their problem to every person they are passed to | ✗ nein | diskutieren |
| Survey requests go out before the problem is solved | → | … | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Escalations go to a team that does not read the ticket history | → | Templates make every reply sound like nobody read the message | ✗ nein | diskutieren |
| … | → | The best agents leave within a year | ✗ nein | diskutieren |
| The same question is answered a hundred times because the help page is wrong | → | Survey requests go out before the problem is solved | ✗ nein | diskutieren |
| Templates make every reply sound like nobody read the message | → | The same question is answered a hundred times because the help page is wrong | ✗ nein | diskutieren |
| Templates make every reply sound like nobody read the message | → | The best agents leave within a year | ✗ nein | diskutieren |
| Customers repeat their problem to every person they are passed to | → | Survey requests go out before the problem is solved | ✗ nein | diskutieren |
| Templates make every reply sound like nobody read the message | → | Survey requests go out before the problem is solved | ✗ nein | diskutieren |
| Templates make every reply sound like nobody read the message | → | … | ✗ nein | diskutieren |
| … | → | The same question is answered a hundred times because the help page is wrong | ✗ nein | diskutieren |
| Escalations go to a team that does not read the ticket history | → | The best agents leave within a year | ✗ nein | diskutieren |
| Nobody from product reads the ticket tags | → | … | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| … | → | Nobody from product reads the ticket tags | ✗ nein | diskutieren |
| Survey requests go out before the problem is solved | → | The phone line closes at five and the emails start at five past | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| The phone line closes at five and the emails start at five past | → | Customers repeat their problem to every person they are passed to | ✗ nein | diskutieren |
| Escalations go to a team that does not read the ticket history | → | Customers repeat their problem to every person they are passed to | ✗ nein | diskutieren |
| The same question is answered a hundred times because the help page is wrong | → | Templates make every reply sound like nobody read the message | ✗ nein | diskutieren |
| Customers repeat their problem to every person they are passed to | → | … | ✗ nein | diskutieren |
| … | → | Customers repeat their problem to every person they are passed to | ✗ nein | diskutieren |
| Survey requests go out before the problem is solved | → | Customers repeat their problem to every person they are passed to | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Customers repeat their problem to every person they are passed to | ✗ nein | diskutieren |
| Templates make every reply sound like nobody read the message | → | Escalations go to a team that does not read the ticket history | ✗ nein | diskutieren |
| … | → | The phone line closes at five and the emails start at five past | ✗ nein | diskutieren |
| Customers repeat their problem to every person they are passed to | → | The best agents leave within a year | ✗ nein | diskutieren |
| The best agents leave within a year | → | Escalations go to a team that does not read the ticket history | ✗ nein | diskutieren |
| The best agents leave within a year | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nein | diskutieren |
| Nobody from product reads the ticket tags | → | Escalations go to a team that does not read the ticket history | ✗ nein | diskutieren |
| The best agents leave within a year | → | … | ✗ nein | diskutieren |
| Escalations go to a team that does not read the ticket history | → | … | ✗ nein | diskutieren |
| … | → | Templates make every reply sound like nobody read the message | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |