LA DOMANDA
Why do complaints keep rising while the product improves?
Una influisce in modo significativo sull’altra? Decidono i tre quarti dei voti espressi.
chiusa · torna alla fase Azioni
Stai guardando come ospite. Inserisci un nome utente per entrare e partecipare.
Le domande sono distribuite tra i gruppi, quindi ricevi quelle assegnate al tuo gruppo — non tutte e 180.
risolte: 177 / 180 da rispondere: 0 perché
Nessuno potrebbe rispondere a diverse centinaia di coppie. Ogni coppia va a un gruppo; una coppia su cui il gruppo si divide passa poi ad altri gruppi, quindi può comparire più tardi nel tuo elenco anche se è partita altrove. Il numero delle risolte include il lavoro di tutti i gruppi, ed è per questo che sale più in fretta di quanto si accorci il tuo elenco.
Ultimo conteggio: decise: 177 · passate ai panel tra gruppi: 2 · contese: 0 · sotto il quorum: 1 — i panel richiedono almeno max(2, 75% del panel) voti espressi; il tuo panel più piccolo ha 15 membri.
… → influisce su? → Agents who take the time to fix a problem properly miss their numbers
Ancora nessun intervento.
Fase conclusa — lo storico delle coppie e dei voti è qui sopra.Verifica la logica ↗
| Refund policy is different on the website, in the app and in the script | → | … | aperta passata oltre | discuti |
| The phone line closes at five and the emails start at five past | → | … | aperta passata oltre | discuti |
| The best agents leave within a year | → | The phone line closes at five and the emails start at five past | aperta | discuti |
| Most complaints are about waiting, not about the answer | → | Complaints are counted only when someone uses the word complaint | ✓ sì | discuti |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints about one feature spike after every release | ✓ sì | discuti |
| Angry customers are moved to the back of the queue by the priority rules | → | Complaints are counted only when someone uses the word complaint | ✓ sì | discuti |
| Most complaints are about waiting, not about the answer | → | A customer who complains twice gets the same first reply both times | ✓ sì | discuti |
| A customer who complains twice gets the same first reply both times | → | Most complaints are about waiting, not about the answer | ✓ sì | discuti |
| 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 | ✓ sì | discuti |
| 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 | ✓ sì | discuti |
| A customer who complains twice gets the same first reply both times | → | Complaints are counted only when someone uses the word complaint | ✓ sì | discuti |
| 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 | ✓ sì | discuti |
| 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 | ✓ sì | discuti |
| Survey requests go out before the problem is solved | → | The same question is answered a hundred times because the help page is wrong | ✓ sì | discuti |
| Survey requests go out before the problem is solved | → | Templates make every reply sound like nobody read the message | ✓ sì | discuti |
| Nobody from product reads the ticket tags | → | Survey requests go out before the problem is solved | ✓ sì | discuti |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Survey requests go out before the problem is solved | ✓ sì | discuti |
| Nobody from product reads the ticket tags | → | The best agents leave within a year | ✓ sì | discuti |
| Nobody from product reads the ticket tags | → | The same question is answered a hundred times because the help page is wrong | ✓ sì | discuti |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints are counted only when someone uses the word complaint | ✓ per deduzione | discuti |
| Complaints are counted only when someone uses the word complaint | → | A customer who complains twice gets the same first reply both times | ✗ no | discuti |
| Refund policy is different on the website, in the app and in the script | → | Most complaints are about waiting, not about the answer | ✗ no | discuti |
| … | → | Complaints are counted only when someone uses the word complaint | ✗ no | discuti |
| The knowledge base is written by people who have never taken a call | → | Complaints are counted only when someone uses the word complaint | ✗ no | discuti |
| 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 | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Complaints are counted only when someone uses the word complaint | → | Agents who take the time to fix a problem properly miss their numbers | ✗ no | discuti |
| The knowledge base is written by people who have never taken a call | → | Most complaints are about waiting, not about the answer | ✗ no | discuti |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Most complaints are about waiting, not about the answer | ✗ no | discuti |
| 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 | ✗ no | discuti |
| 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 | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | … | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Refund policy is different on the website, in the app and in the script | → | Complaints are counted only when someone uses the word complaint | ✗ no | discuti |
| Most complaints are about waiting, not about the answer | → | Complaints about one feature spike after every release | ✗ no | discuti |
| Most complaints are about waiting, not about the answer | → | Agents who take the time to fix a problem properly miss their numbers | ✗ no | discuti |
| 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 | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Complaints are counted only when someone uses the word complaint | → | Most complaints are about waiting, not about the answer | ✗ no | discuti |
| Most complaints are about waiting, not about the answer | → | Angry customers are moved to the back of the queue by the priority rules | ✗ no | discuti |
| … | → | A customer who complains twice gets the same first reply both times | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Complaints about one feature spike after every release | → | Complaints are counted only when someone uses the word complaint | ✗ no | discuti |
| A customer who complains twice gets the same first reply both times | → | … | ✗ no | discuti |
| Complaints about one feature spike after every release | → | Agents who take the time to fix a problem properly miss their numbers | ✗ no | discuti |
| Angry customers are moved to the back of the queue by the priority rules | → | Most complaints are about waiting, not about the answer | ✗ no | discuti |
| … | → | Angry customers are moved to the back of the queue by the priority rules | ✗ no | discuti |
| Agents who take the time to fix a problem properly miss their numbers | → | … | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Complaints about one feature spike after every release | → | Refund policy is different on the website, in the app and in the script | ✗ no | discuti |
| 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 | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Complaints about one feature spike after every release | → | The knowledge base is written by people who have never taken a call | ✗ no | discuti |
| 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 | ✗ no | discuti |
| … | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ no | discuti |
| Complaints about one feature spike after every release | → | Most complaints are about waiting, not about the answer | ✗ no | discuti |
| … | → | The knowledge base is written by people who have never taken a call | ✗ no | discuti |
| Complaints are counted only when someone uses the word complaint | → | Refund policy is different on the website, in the app and in the script | ✗ no | discuti |
| Complaints are counted only when someone uses the word complaint | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ no | discuti |
| Most complaints are about waiting, not about the answer | → | … | ✗ no | discuti |
| Agents who take the time to fix a problem properly miss their numbers | → | Most complaints are about waiting, not about the answer | ✗ no | discuti |
| Complaints are counted only when someone uses the word complaint | → | Angry customers are moved to the back of the queue by the priority rules | ✗ no | discuti |
| Angry customers are moved to the back of the queue by the priority rules | → | … | ✗ no | discuti |
| Most complaints are about waiting, not about the answer | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ no | discuti |
| Complaints are counted only when someone uses the word complaint | → | … | ✗ no | discuti |
| 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 | ✗ no | discuti |
| … | → | Complaints about one feature spike after every release | ✗ no | discuti |
| 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 | ✗ no | discuti |
| 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 | ✗ no | discuti |
| The knowledge base is written by people who have never taken a call | → | Complaints about one feature spike after every release | ✗ no | discuti |
| Complaints are counted only when someone uses the word complaint | → | The knowledge base is written by people who have never taken a call | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Complaints about one feature spike after every release | ✗ no | discuti |
| 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 | ✗ no | discuti |
| 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 | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Complaints about one feature spike after every release | → | Angry customers are moved to the back of the queue by the priority rules | ✗ no | discuti |
| Refund policy is different on the website, in the app and in the script | → | Complaints about one feature spike after every release | ✗ no | discuti |
| Angry customers are moved to the back of the queue by the priority rules | → | Complaints about one feature spike after every release | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Complaints are counted only when someone uses the word complaint | → | Complaints about one feature spike after every release | ✗ no | discuti |
| Complaints about one feature spike after every release | → | A customer who complains twice gets the same first reply both times | ✗ no | discuti |
| 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 | ✗ no | discuti |
| … | → | Most complaints are about waiting, not about the answer | ✗ no | discuti |
| Complaints about one feature spike after every release | → | … | ✗ no | discuti |
| A customer who complains twice gets the same first reply both times | → | Complaints about one feature spike after every release | ✗ no | discuti |
| … | → | Agents who take the time to fix a problem properly miss their numbers | ✗ no | in primo piano ↑ · chiudi ✕ |
| 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 | ✗ no | discuti |
| Most complaints are about waiting, not about the answer | → | The knowledge base is written by people who have never taken a call | ✗ no | discuti |
| Most complaints are about waiting, not about the answer | → | Refund policy is different on the website, in the app and in the script | ✗ no | discuti |
| Complaints about one feature spike after every release | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Complaints are counted only when someone uses the word complaint | ✗ no | discuti |
| … | → | Refund policy is different on the website, in the app and in the script | ✗ no | discuti |
| The knowledge base is written by people who have never taken a call | → | … | ✗ no | discuti |
| 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 | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Escalations go to a team that does not read the ticket history | → | Survey requests go out before the problem is solved | ✗ no | discuti |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | The best agents leave within a year | ✗ no | discuti |
| Survey requests go out before the problem is solved | → | The best agents leave within a year | ✗ no | discuti |
| Escalations go to a team that does not read the ticket history | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discuti |
| The best agents leave within a year | → | Survey requests go out before the problem is solved | ✗ no | discuti |
| Nobody from product reads the ticket tags | → | Templates make every reply sound like nobody read the message | ✗ no | discuti |
| Survey requests go out before the problem is solved | → | Nobody from product reads the ticket tags | ✗ no | discuti |
| … | → | Survey requests go out before the problem is solved | ✗ no | discuti |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Templates make every reply sound like nobody read the message | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Customers repeat their problem to every person they are passed to | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discuti |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | … | ✗ no | discuti |
| Nobody from product reads the ticket tags | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discuti |
| Escalations go to a team that does not read the ticket history | → | Nobody from product reads the ticket tags | ✗ no | discuti |
| Survey requests go out before the problem is solved | → | Escalations go to a team that does not read the ticket history | ✗ no | discuti |
| Customers repeat their problem to every person they are passed to | → | The phone line closes at five and the emails start at five past | ✗ no | discuti |
| … | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discuti |
| 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 | ✗ no | discuti |
| 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 | ✗ no | discuti |
| The best agents leave within a year | → | Nobody from product reads the ticket tags | ✗ no | discuti |
| The same question is answered a hundred times because the help page is wrong | → | … | ✗ no | discuti |
| Nobody from product reads the ticket tags | → | Customers repeat their problem to every person they are passed to | ✗ no | discuti |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Nobody from product reads the ticket tags | ✗ no | discuti |
| Customers repeat their problem to every person they are passed to | → | Templates make every reply sound like nobody read the message | ✗ no | discuti |
| Survey requests go out before the problem is solved | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discuti |
| The phone line closes at five and the emails start at five past | → | Nobody from product reads the ticket tags | ✗ no | discuti |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Escalations go to a team that does not read the ticket history | ✗ no | discuti |
| The best agents leave within a year | → | Customers repeat their problem to every person they are passed to | ✗ no | discuti |
| The phone line closes at five and the emails start at five past | → | The best agents leave within a year | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Templates make every reply sound like nobody read the message | → | The phone line closes at five and the emails start at five past | ✗ no | discuti |
| The best agents leave within a year | → | The same question is answered a hundred times because the help page is wrong | ✗ no | discuti |
| Templates make every reply sound like nobody read the message | → | Nobody from product reads the ticket tags | ✗ no | discuti |
| … | → | Escalations go to a team that does not read the ticket history | ✗ no | discuti |
| Templates make every reply sound like nobody read the message | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discuti |
| Nobody from product reads the ticket tags | → | The phone line closes at five and the emails start at five past | ✗ no | discuti |
| Customers repeat their problem to every person they are passed to | → | Escalations go to a team that does not read the ticket history | ✗ no | discuti |
| Customers repeat their problem to every person they are passed to | → | Nobody from product reads the ticket tags | ✗ no | discuti |
| The same question is answered a hundred times because the help page is wrong | → | The best agents leave within a year | ✗ no | discuti |
| 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 | ✗ no | discuti |
| 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 | ✗ no | discuti |
| The same question is answered a hundred times because the help page is wrong | → | Nobody from product reads the ticket tags | ✗ no | discuti |
| 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 | ✗ no | discuti |
| The phone line closes at five and the emails start at five past | → | Templates make every reply sound like nobody read the message | ✗ no | discuti |
| The best agents leave within a year | → | Templates make every reply sound like nobody read the message | ✗ no | discuti |
| The phone line closes at five and the emails start at five past | → | Survey requests go out before the problem is solved | ✗ no | discuti |
| Templates make every reply sound like nobody read the message | → | Customers repeat their problem to every person they are passed to | ✗ no | discuti |
| Survey requests go out before the problem is solved | → | … | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Escalations go to a team that does not read the ticket history | → | Templates make every reply sound like nobody read the message | ✗ no | discuti |
| … | → | The best agents leave within a year | ✗ no | discuti |
| The same question is answered a hundred times because the help page is wrong | → | Survey requests go out before the problem is solved | ✗ no | discuti |
| Templates make every reply sound like nobody read the message | → | The same question is answered a hundred times because the help page is wrong | ✗ no | discuti |
| Templates make every reply sound like nobody read the message | → | The best agents leave within a year | ✗ no | discuti |
| Customers repeat their problem to every person they are passed to | → | Survey requests go out before the problem is solved | ✗ no | discuti |
| Templates make every reply sound like nobody read the message | → | Survey requests go out before the problem is solved | ✗ no | discuti |
| Templates make every reply sound like nobody read the message | → | … | ✗ no | discuti |
| … | → | The same question is answered a hundred times because the help page is wrong | ✗ no | discuti |
| Escalations go to a team that does not read the ticket history | → | The best agents leave within a year | ✗ no | discuti |
| Nobody from product reads the ticket tags | → | … | ✗ no | discuti |
| 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 | ✗ no | discuti |
| … | → | Nobody from product reads the ticket tags | ✗ no | discuti |
| Survey requests go out before the problem is solved | → | The phone line closes at five and the emails start at five past | ✗ no | discuti |
| 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 | ✗ no | discuti |
| The phone line closes at five and the emails start at five past | → | Customers repeat their problem to every person they are passed to | ✗ no | discuti |
| Escalations go to a team that does not read the ticket history | → | Customers repeat their problem to every person they are passed to | ✗ no | discuti |
| The same question is answered a hundred times because the help page is wrong | → | Templates make every reply sound like nobody read the message | ✗ no | discuti |
| Customers repeat their problem to every person they are passed to | → | … | ✗ no | discuti |
| … | → | Customers repeat their problem to every person they are passed to | ✗ no | discuti |
| Survey requests go out before the problem is solved | → | Customers repeat their problem to every person they are passed to | ✗ no | discuti |
| 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 | ✗ no | discuti |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Customers repeat their problem to every person they are passed to | ✗ no | discuti |
| Templates make every reply sound like nobody read the message | → | Escalations go to a team that does not read the ticket history | ✗ no | discuti |
| … | → | The phone line closes at five and the emails start at five past | ✗ no | discuti |
| Customers repeat their problem to every person they are passed to | → | The best agents leave within a year | ✗ no | discuti |
| The best agents leave within a year | → | Escalations go to a team that does not read the ticket history | ✗ no | discuti |
| The best agents leave within a year | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discuti |
| Nobody from product reads the ticket tags | → | Escalations go to a team that does not read the ticket history | ✗ no | discuti |
| The best agents leave within a year | → | … | ✗ no | discuti |
| Escalations go to a team that does not read the ticket history | → | … | ✗ no | discuti |
| … | → | Templates make every reply sound like nobody read the message | ✗ no | discuti |
| 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 | ✗ no | discuti |