SPØRSMÅLET
Why do complaints keep rising while the product improves?
Påvirker det ene det andre i betydelig grad? Tre firedeler av de avgitte stemmene avgjør.
stengt · tilbake til fasen Tiltak
Du ser på som gjest. Skriv inn et brukernavn for å bli med og delta.
Spørsmålene fordeles mellom gruppene, så du får dem gruppen din ble tildelt — ikke alle 180.
avgjort: 177 / 180 til deg å svare på: 0 hvorfor
Ingen kunne svart på flere hundre par. Hvert par går til én gruppe; et par som deler gruppen, sendes så videre til andre grupper, så det kan dukke opp i listen din senere selv om det startet et annet sted. Antallet avgjorte omfatter alle gruppenes arbeid, og derfor stiger det raskere enn din egen liste krymper.
Siste opptelling: avgjort 177 · sendt videre til paneler på tvers av grupper 2 · omstridt 0 · under kvorum 1 — paneler trenger minst max(2, 75% av panelet) avgitte stemmer; ditt minste panel har 15 medlemmer.
A customer who complains twice gets the same first reply both times → påvirker? → Complaints are counted only when someone uses the word complaint
Ingenting sagt ennå.
Fullført fase — protokollen over par og stemmer står ovenfor.Sjekk logikken ↗
| Refund policy is different on the website, in the app and in the script | → | … | åpent sendt videre | diskuter |
| The phone line closes at five and the emails start at five past | → | … | åpent sendt videre | diskuter |
| The best agents leave within a year | → | The phone line closes at five and the emails start at five past | åpent | diskuter |
| Most complaints are about waiting, not about the answer | → | Complaints are counted only when someone uses the word complaint | ✓ ja | diskuter |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints about one feature spike after every release | ✓ ja | diskuter |
| 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 | diskuter |
| Most complaints are about waiting, not about the answer | → | A customer who complains twice gets the same first reply both times | ✓ ja | diskuter |
| A customer who complains twice gets the same first reply both times | → | Most complaints are about waiting, not about the answer | ✓ ja | diskuter |
| 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 | diskuter |
| 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 | diskuter |
| A customer who complains twice gets the same first reply both times | → | Complaints are counted only when someone uses the word complaint | ✓ ja | i fokus ↑ · lukk ✕ |
| 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 | diskuter |
| 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 | diskuter |
| Survey requests go out before the problem is solved | → | The same question is answered a hundred times because the help page is wrong | ✓ ja | diskuter |
| Survey requests go out before the problem is solved | → | Templates make every reply sound like nobody read the message | ✓ ja | diskuter |
| Nobody from product reads the ticket tags | → | Survey requests go out before the problem is solved | ✓ ja | diskuter |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Survey requests go out before the problem is solved | ✓ ja | diskuter |
| Nobody from product reads the ticket tags | → | The best agents leave within a year | ✓ ja | diskuter |
| Nobody from product reads the ticket tags | → | The same question is answered a hundred times because the help page is wrong | ✓ ja | diskuter |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints are counted only when someone uses the word complaint | ✓ utledet | diskuter |
| Complaints are counted only when someone uses the word complaint | → | A customer who complains twice gets the same first reply both times | ✗ nei | diskuter |
| Refund policy is different on the website, in the app and in the script | → | Most complaints are about waiting, not about the answer | ✗ nei | diskuter |
| … | → | Complaints are counted only when someone uses the word complaint | ✗ nei | diskuter |
| The knowledge base is written by people who have never taken a call | → | Complaints are counted only when someone uses the word complaint | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Complaints are counted only when someone uses the word complaint | → | Agents who take the time to fix a problem properly miss their numbers | ✗ nei | diskuter |
| The knowledge base is written by people who have never taken a call | → | Most complaints are about waiting, not about the answer | ✗ nei | diskuter |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Most complaints are about waiting, not about the answer | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | … | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Refund policy is different on the website, in the app and in the script | → | Complaints are counted only when someone uses the word complaint | ✗ nei | diskuter |
| Most complaints are about waiting, not about the answer | → | Complaints about one feature spike after every release | ✗ nei | diskuter |
| Most complaints are about waiting, not about the answer | → | Agents who take the time to fix a problem properly miss their numbers | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Complaints are counted only when someone uses the word complaint | → | Most complaints are about waiting, not about the answer | ✗ nei | diskuter |
| Most complaints are about waiting, not about the answer | → | Angry customers are moved to the back of the queue by the priority rules | ✗ nei | diskuter |
| … | → | A customer who complains twice gets the same first reply both times | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Complaints about one feature spike after every release | → | Complaints are counted only when someone uses the word complaint | ✗ nei | diskuter |
| A customer who complains twice gets the same first reply both times | → | … | ✗ nei | diskuter |
| Complaints about one feature spike after every release | → | Agents who take the time to fix a problem properly miss their numbers | ✗ nei | diskuter |
| Angry customers are moved to the back of the queue by the priority rules | → | Most complaints are about waiting, not about the answer | ✗ nei | diskuter |
| … | → | Angry customers are moved to the back of the queue by the priority rules | ✗ nei | diskuter |
| Agents who take the time to fix a problem properly miss their numbers | → | … | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Complaints about one feature spike after every release | → | Refund policy is different on the website, in the app and in the script | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Complaints about one feature spike after every release | → | The knowledge base is written by people who have never taken a call | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| … | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ nei | diskuter |
| Complaints about one feature spike after every release | → | Most complaints are about waiting, not about the answer | ✗ nei | diskuter |
| … | → | The knowledge base is written by people who have never taken a call | ✗ nei | diskuter |
| Complaints are counted only when someone uses the word complaint | → | Refund policy is different on the website, in the app and in the script | ✗ nei | diskuter |
| Complaints are counted only when someone uses the word complaint | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ nei | diskuter |
| Most complaints are about waiting, not about the answer | → | … | ✗ nei | diskuter |
| Agents who take the time to fix a problem properly miss their numbers | → | Most complaints are about waiting, not about the answer | ✗ nei | diskuter |
| Complaints are counted only when someone uses the word complaint | → | Angry customers are moved to the back of the queue by the priority rules | ✗ nei | diskuter |
| Angry customers are moved to the back of the queue by the priority rules | → | … | ✗ nei | diskuter |
| Most complaints are about waiting, not about the answer | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ nei | diskuter |
| Complaints are counted only when someone uses the word complaint | → | … | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| … | → | Complaints about one feature spike after every release | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| The knowledge base is written by people who have never taken a call | → | Complaints about one feature spike after every release | ✗ nei | diskuter |
| Complaints are counted only when someone uses the word complaint | → | The knowledge base is written by people who have never taken a call | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Complaints about one feature spike after every release | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Complaints about one feature spike after every release | → | Angry customers are moved to the back of the queue by the priority rules | ✗ nei | diskuter |
| Refund policy is different on the website, in the app and in the script | → | Complaints about one feature spike after every release | ✗ nei | diskuter |
| Angry customers are moved to the back of the queue by the priority rules | → | Complaints about one feature spike after every release | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Complaints are counted only when someone uses the word complaint | → | Complaints about one feature spike after every release | ✗ nei | diskuter |
| Complaints about one feature spike after every release | → | A customer who complains twice gets the same first reply both times | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| … | → | Most complaints are about waiting, not about the answer | ✗ nei | diskuter |
| Complaints about one feature spike after every release | → | … | ✗ nei | diskuter |
| A customer who complains twice gets the same first reply both times | → | Complaints about one feature spike after every release | ✗ nei | diskuter |
| … | → | Agents who take the time to fix a problem properly miss their numbers | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Most complaints are about waiting, not about the answer | → | The knowledge base is written by people who have never taken a call | ✗ nei | diskuter |
| Most complaints are about waiting, not about the answer | → | Refund policy is different on the website, in the app and in the script | ✗ nei | diskuter |
| Complaints about one feature spike after every release | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Complaints are counted only when someone uses the word complaint | ✗ nei | diskuter |
| … | → | Refund policy is different on the website, in the app and in the script | ✗ nei | diskuter |
| The knowledge base is written by people who have never taken a call | → | … | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Escalations go to a team that does not read the ticket history | → | Survey requests go out before the problem is solved | ✗ nei | diskuter |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | The best agents leave within a year | ✗ nei | diskuter |
| Survey requests go out before the problem is solved | → | The best agents leave within a year | ✗ nei | diskuter |
| Escalations go to a team that does not read the ticket history | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nei | diskuter |
| The best agents leave within a year | → | Survey requests go out before the problem is solved | ✗ nei | diskuter |
| Nobody from product reads the ticket tags | → | Templates make every reply sound like nobody read the message | ✗ nei | diskuter |
| Survey requests go out before the problem is solved | → | Nobody from product reads the ticket tags | ✗ nei | diskuter |
| … | → | Survey requests go out before the problem is solved | ✗ nei | diskuter |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Templates make every reply sound like nobody read the message | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Customers repeat their problem to every person they are passed to | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nei | diskuter |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | … | ✗ nei | diskuter |
| Nobody from product reads the ticket tags | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nei | diskuter |
| Escalations go to a team that does not read the ticket history | → | Nobody from product reads the ticket tags | ✗ nei | diskuter |
| Survey requests go out before the problem is solved | → | Escalations go to a team that does not read the ticket history | ✗ nei | diskuter |
| Customers repeat their problem to every person they are passed to | → | The phone line closes at five and the emails start at five past | ✗ nei | diskuter |
| … | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| The best agents leave within a year | → | Nobody from product reads the ticket tags | ✗ nei | diskuter |
| The same question is answered a hundred times because the help page is wrong | → | … | ✗ nei | diskuter |
| Nobody from product reads the ticket tags | → | Customers repeat their problem to every person they are passed to | ✗ nei | diskuter |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Nobody from product reads the ticket tags | ✗ nei | diskuter |
| Customers repeat their problem to every person they are passed to | → | Templates make every reply sound like nobody read the message | ✗ nei | diskuter |
| Survey requests go out before the problem is solved | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nei | diskuter |
| The phone line closes at five and the emails start at five past | → | Nobody from product reads the ticket tags | ✗ nei | diskuter |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Escalations go to a team that does not read the ticket history | ✗ nei | diskuter |
| The best agents leave within a year | → | Customers repeat their problem to every person they are passed to | ✗ nei | diskuter |
| The phone line closes at five and the emails start at five past | → | The best agents leave within a year | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Templates make every reply sound like nobody read the message | → | The phone line closes at five and the emails start at five past | ✗ nei | diskuter |
| The best agents leave within a year | → | The same question is answered a hundred times because the help page is wrong | ✗ nei | diskuter |
| Templates make every reply sound like nobody read the message | → | Nobody from product reads the ticket tags | ✗ nei | diskuter |
| … | → | Escalations go to a team that does not read the ticket history | ✗ nei | diskuter |
| Templates make every reply sound like nobody read the message | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nei | diskuter |
| Nobody from product reads the ticket tags | → | The phone line closes at five and the emails start at five past | ✗ nei | diskuter |
| Customers repeat their problem to every person they are passed to | → | Escalations go to a team that does not read the ticket history | ✗ nei | diskuter |
| Customers repeat their problem to every person they are passed to | → | Nobody from product reads the ticket tags | ✗ nei | diskuter |
| The same question is answered a hundred times because the help page is wrong | → | The best agents leave within a year | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| The same question is answered a hundred times because the help page is wrong | → | Nobody from product reads the ticket tags | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| The phone line closes at five and the emails start at five past | → | Templates make every reply sound like nobody read the message | ✗ nei | diskuter |
| The best agents leave within a year | → | Templates make every reply sound like nobody read the message | ✗ nei | diskuter |
| The phone line closes at five and the emails start at five past | → | Survey requests go out before the problem is solved | ✗ nei | diskuter |
| Templates make every reply sound like nobody read the message | → | Customers repeat their problem to every person they are passed to | ✗ nei | diskuter |
| Survey requests go out before the problem is solved | → | … | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Escalations go to a team that does not read the ticket history | → | Templates make every reply sound like nobody read the message | ✗ nei | diskuter |
| … | → | The best agents leave within a year | ✗ nei | diskuter |
| The same question is answered a hundred times because the help page is wrong | → | Survey requests go out before the problem is solved | ✗ nei | diskuter |
| Templates make every reply sound like nobody read the message | → | The same question is answered a hundred times because the help page is wrong | ✗ nei | diskuter |
| Templates make every reply sound like nobody read the message | → | The best agents leave within a year | ✗ nei | diskuter |
| Customers repeat their problem to every person they are passed to | → | Survey requests go out before the problem is solved | ✗ nei | diskuter |
| Templates make every reply sound like nobody read the message | → | Survey requests go out before the problem is solved | ✗ nei | diskuter |
| Templates make every reply sound like nobody read the message | → | … | ✗ nei | diskuter |
| … | → | The same question is answered a hundred times because the help page is wrong | ✗ nei | diskuter |
| Escalations go to a team that does not read the ticket history | → | The best agents leave within a year | ✗ nei | diskuter |
| Nobody from product reads the ticket tags | → | … | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| … | → | Nobody from product reads the ticket tags | ✗ nei | diskuter |
| Survey requests go out before the problem is solved | → | The phone line closes at five and the emails start at five past | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| The phone line closes at five and the emails start at five past | → | Customers repeat their problem to every person they are passed to | ✗ nei | diskuter |
| Escalations go to a team that does not read the ticket history | → | Customers repeat their problem to every person they are passed to | ✗ nei | diskuter |
| The same question is answered a hundred times because the help page is wrong | → | Templates make every reply sound like nobody read the message | ✗ nei | diskuter |
| Customers repeat their problem to every person they are passed to | → | … | ✗ nei | diskuter |
| … | → | Customers repeat their problem to every person they are passed to | ✗ nei | diskuter |
| Survey requests go out before the problem is solved | → | Customers repeat their problem to every person they are passed to | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Customers repeat their problem to every person they are passed to | ✗ nei | diskuter |
| Templates make every reply sound like nobody read the message | → | Escalations go to a team that does not read the ticket history | ✗ nei | diskuter |
| … | → | The phone line closes at five and the emails start at five past | ✗ nei | diskuter |
| Customers repeat their problem to every person they are passed to | → | The best agents leave within a year | ✗ nei | diskuter |
| The best agents leave within a year | → | Escalations go to a team that does not read the ticket history | ✗ nei | diskuter |
| The best agents leave within a year | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ nei | diskuter |
| Nobody from product reads the ticket tags | → | Escalations go to a team that does not read the ticket history | ✗ nei | diskuter |
| The best agents leave within a year | → | … | ✗ nei | diskuter |
| Escalations go to a team that does not read the ticket history | → | … | ✗ nei | diskuter |
| … | → | Templates make every reply sound like nobody read the message | ✗ nei | diskuter |
| 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 | ✗ nei | diskuter |