LA PREGUNTA
Why do complaints keep rising while the product improves?
¿Influye una significativamente en la otra? Deciden tres cuartas partes de los votos emitidos.
cerrada · volver a Acciones
Viendo como invitado. Escribe un nombre de usuario para unirte y participar.
Las preguntas se reparten entre los grupos, así que recibes las que le tocaron al tuyo — no las 180.
resueltas: 177 / 180 por responder: 0 por qué
Nadie podría responder varios cientos de pares. Cada par va a un grupo; un par que se divide se deriva después a otros grupos, así que puede aparecer más tarde en tu lista aunque empezara en otro sitio. La cifra de resueltas incluye el trabajo de todos los grupos, y por eso sube más rápido de lo que se acorta tu propia lista.
Último recuento: decididas: 177 · derivadas a paneles entre grupos: 2 · disputadas: 0 · sin quórum: 1 — los paneles necesitan al menos max(2, 75 % del panel) votos emitidos; tu panel más pequeño tiene 15 miembros.
Escalations go to a team that does not read the ticket history → ¿influye en? → Customers repeat their problem to every person they are passed to
Nadie ha dicho nada aún.
Fase terminada — el registro de pares y votos queda arriba.Comprobar la lógica ↗
| Refund policy is different on the website, in the app and in the script | → | … | abierto derivado | discutir |
| The phone line closes at five and the emails start at five past | → | … | abierto derivado | discutir |
| The best agents leave within a year | → | The phone line closes at five and the emails start at five past | abierto | discutir |
| Most complaints are about waiting, not about the answer | → | Complaints are counted only when someone uses the word complaint | ✓ sí | discutir |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints about one feature spike after every release | ✓ sí | discutir |
| 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í | discutir |
| Most complaints are about waiting, not about the answer | → | A customer who complains twice gets the same first reply both times | ✓ sí | discutir |
| A customer who complains twice gets the same first reply both times | → | Most complaints are about waiting, not about the answer | ✓ sí | discutir |
| 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í | discutir |
| 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í | discutir |
| A customer who complains twice gets the same first reply both times | → | Complaints are counted only when someone uses the word complaint | ✓ sí | discutir |
| 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í | discutir |
| 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í | discutir |
| Survey requests go out before the problem is solved | → | The same question is answered a hundred times because the help page is wrong | ✓ sí | discutir |
| Survey requests go out before the problem is solved | → | Templates make every reply sound like nobody read the message | ✓ sí | discutir |
| Nobody from product reads the ticket tags | → | Survey requests go out before the problem is solved | ✓ sí | discutir |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Survey requests go out before the problem is solved | ✓ sí | discutir |
| Nobody from product reads the ticket tags | → | The best agents leave within a year | ✓ sí | discutir |
| Nobody from product reads the ticket tags | → | The same question is answered a hundred times because the help page is wrong | ✓ sí | discutir |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints are counted only when someone uses the word complaint | ✓ inferido | discutir |
| Complaints are counted only when someone uses the word complaint | → | A customer who complains twice gets the same first reply both times | ✗ no | discutir |
| Refund policy is different on the website, in the app and in the script | → | Most complaints are about waiting, not about the answer | ✗ no | discutir |
| … | → | Complaints are counted only when someone uses the word complaint | ✗ no | discutir |
| The knowledge base is written by people who have never taken a call | → | Complaints are counted only when someone uses the word complaint | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| Complaints are counted only when someone uses the word complaint | → | Agents who take the time to fix a problem properly miss their numbers | ✗ no | discutir |
| The knowledge base is written by people who have never taken a call | → | Most complaints are about waiting, not about the answer | ✗ no | discutir |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Most complaints are about waiting, not about the answer | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| 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 | discutir |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | … | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| Most complaints are about waiting, not about the answer | → | Complaints about one feature spike after every release | ✗ no | discutir |
| Most complaints are about waiting, not about the answer | → | Agents who take the time to fix a problem properly miss their numbers | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| Complaints are counted only when someone uses the word complaint | → | Most complaints are about waiting, not about the answer | ✗ no | discutir |
| Most complaints are about waiting, not about the answer | → | Angry customers are moved to the back of the queue by the priority rules | ✗ no | discutir |
| … | → | A customer who complains twice gets the same first reply both times | ✗ no | discutir |
| 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 | discutir |
| Complaints about one feature spike after every release | → | Complaints are counted only when someone uses the word complaint | ✗ no | discutir |
| A customer who complains twice gets the same first reply both times | → | … | ✗ no | discutir |
| Complaints about one feature spike after every release | → | Agents who take the time to fix a problem properly miss their numbers | ✗ no | discutir |
| Angry customers are moved to the back of the queue by the priority rules | → | Most complaints are about waiting, not about the answer | ✗ no | discutir |
| … | → | Angry customers are moved to the back of the queue by the priority rules | ✗ no | discutir |
| Agents who take the time to fix a problem properly miss their numbers | → | … | ✗ no | discutir |
| 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 | discutir |
| Complaints about one feature spike after every release | → | Refund policy is different on the website, in the app and in the script | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| Complaints about one feature spike after every release | → | The knowledge base is written by people who have never taken a call | ✗ no | discutir |
| 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 | discutir |
| … | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ no | discutir |
| Complaints about one feature spike after every release | → | Most complaints are about waiting, not about the answer | ✗ no | discutir |
| … | → | The knowledge base is written by people who have never taken a call | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| Most complaints are about waiting, not about the answer | → | … | ✗ no | discutir |
| Agents who take the time to fix a problem properly miss their numbers | → | Most complaints are about waiting, not about the answer | ✗ no | discutir |
| 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 | discutir |
| Angry customers are moved to the back of the queue by the priority rules | → | … | ✗ no | discutir |
| Most complaints are about waiting, not about the answer | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ no | discutir |
| Complaints are counted only when someone uses the word complaint | → | … | ✗ no | discutir |
| 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 | discutir |
| … | → | Complaints about one feature spike after every release | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| The knowledge base is written by people who have never taken a call | → | Complaints about one feature spike after every release | ✗ no | discutir |
| Complaints are counted only when someone uses the word complaint | → | The knowledge base is written by people who have never taken a call | ✗ no | discutir |
| 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 | discutir |
| Agents cannot issue a refund without a manager, and the manager is in meetings | → | Complaints about one feature spike after every release | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| 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 | discutir |
| Complaints about one feature spike after every release | → | Angry customers are moved to the back of the queue by the priority rules | ✗ no | discutir |
| Refund policy is different on the website, in the app and in the script | → | Complaints about one feature spike after every release | ✗ no | discutir |
| Angry customers are moved to the back of the queue by the priority rules | → | Complaints about one feature spike after every release | ✗ no | discutir |
| 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 | discutir |
| Complaints are counted only when someone uses the word complaint | → | Complaints about one feature spike after every release | ✗ no | discutir |
| Complaints about one feature spike after every release | → | A customer who complains twice gets the same first reply both times | ✗ no | discutir |
| 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 | discutir |
| … | → | Most complaints are about waiting, not about the answer | ✗ no | discutir |
| Complaints about one feature spike after every release | → | … | ✗ no | discutir |
| A customer who complains twice gets the same first reply both times | → | Complaints about one feature spike after every release | ✗ no | discutir |
| … | → | Agents who take the time to fix a problem properly miss their numbers | ✗ no | discutir |
| 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 | discutir |
| Most complaints are about waiting, not about the answer | → | The knowledge base is written by people who have never taken a call | ✗ no | discutir |
| Most complaints are about waiting, not about the answer | → | Refund policy is different on the website, in the app and in the script | ✗ no | discutir |
| Complaints about one feature spike after every release | → | Agents cannot issue a refund without a manager, and the manager is in meetings | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| … | → | Refund policy is different on the website, in the app and in the script | ✗ no | discutir |
| The knowledge base is written by people who have never taken a call | → | … | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| Escalations go to a team that does not read the ticket history | → | Survey requests go out before the problem is solved | ✗ no | discutir |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | The best agents leave within a year | ✗ no | discutir |
| Survey requests go out before the problem is solved | → | The best agents leave within a year | ✗ no | discutir |
| 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 | discutir |
| The best agents leave within a year | → | Survey requests go out before the problem is solved | ✗ no | discutir |
| Nobody from product reads the ticket tags | → | Templates make every reply sound like nobody read the message | ✗ no | discutir |
| Survey requests go out before the problem is solved | → | Nobody from product reads the ticket tags | ✗ no | discutir |
| … | → | Survey requests go out before the problem is solved | ✗ no | discutir |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Templates make every reply sound like nobody read the message | ✗ no | discutir |
| 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 | discutir |
| Customers repeat their problem to every person they are passed to | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discutir |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | … | ✗ no | discutir |
| Nobody from product reads the ticket tags | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discutir |
| Escalations go to a team that does not read the ticket history | → | Nobody from product reads the ticket tags | ✗ no | discutir |
| Survey requests go out before the problem is solved | → | Escalations go to a team that does not read the ticket history | ✗ no | discutir |
| 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 | discutir |
| … | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| The best agents leave within a year | → | Nobody from product reads the ticket tags | ✗ no | discutir |
| The same question is answered a hundred times because the help page is wrong | → | … | ✗ no | discutir |
| Nobody from product reads the ticket tags | → | Customers repeat their problem to every person they are passed to | ✗ no | discutir |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Nobody from product reads the ticket tags | ✗ no | discutir |
| Customers repeat their problem to every person they are passed to | → | Templates make every reply sound like nobody read the message | ✗ no | discutir |
| Survey requests go out before the problem is solved | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discutir |
| The phone line closes at five and the emails start at five past | → | Nobody from product reads the ticket tags | ✗ no | discutir |
| 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 | discutir |
| The best agents leave within a year | → | Customers repeat their problem to every person they are passed to | ✗ no | discutir |
| The phone line closes at five and the emails start at five past | → | The best agents leave within a year | ✗ no | discutir |
| 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 | discutir |
| Templates make every reply sound like nobody read the message | → | The phone line closes at five and the emails start at five past | ✗ no | discutir |
| The best agents leave within a year | → | The same question is answered a hundred times because the help page is wrong | ✗ no | discutir |
| Templates make every reply sound like nobody read the message | → | Nobody from product reads the ticket tags | ✗ no | discutir |
| … | → | Escalations go to a team that does not read the ticket history | ✗ no | discutir |
| Templates make every reply sound like nobody read the message | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discutir |
| Nobody from product reads the ticket tags | → | The phone line closes at five and the emails start at five past | ✗ no | discutir |
| Customers repeat their problem to every person they are passed to | → | Escalations go to a team that does not read the ticket history | ✗ no | discutir |
| Customers repeat their problem to every person they are passed to | → | Nobody from product reads the ticket tags | ✗ no | discutir |
| The same question is answered a hundred times because the help page is wrong | → | The best agents leave within a year | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| The same question is answered a hundred times because the help page is wrong | → | Nobody from product reads the ticket tags | ✗ no | discutir |
| 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 | discutir |
| The phone line closes at five and the emails start at five past | → | Templates make every reply sound like nobody read the message | ✗ no | discutir |
| The best agents leave within a year | → | Templates make every reply sound like nobody read the message | ✗ no | discutir |
| The phone line closes at five and the emails start at five past | → | Survey requests go out before the problem is solved | ✗ no | discutir |
| Templates make every reply sound like nobody read the message | → | Customers repeat their problem to every person they are passed to | ✗ no | discutir |
| Survey requests go out before the problem is solved | → | … | ✗ no | discutir |
| 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 | discutir |
| Escalations go to a team that does not read the ticket history | → | Templates make every reply sound like nobody read the message | ✗ no | discutir |
| … | → | The best agents leave within a year | ✗ no | discutir |
| The same question is answered a hundred times because the help page is wrong | → | Survey requests go out before the problem is solved | ✗ no | discutir |
| 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 | discutir |
| Templates make every reply sound like nobody read the message | → | The best agents leave within a year | ✗ no | discutir |
| Customers repeat their problem to every person they are passed to | → | Survey requests go out before the problem is solved | ✗ no | discutir |
| Templates make every reply sound like nobody read the message | → | Survey requests go out before the problem is solved | ✗ no | discutir |
| Templates make every reply sound like nobody read the message | → | … | ✗ no | discutir |
| … | → | The same question is answered a hundred times because the help page is wrong | ✗ no | discutir |
| Escalations go to a team that does not read the ticket history | → | The best agents leave within a year | ✗ no | discutir |
| Nobody from product reads the ticket tags | → | … | ✗ no | discutir |
| 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 | discutir |
| … | → | Nobody from product reads the ticket tags | ✗ no | discutir |
| Survey requests go out before the problem is solved | → | The phone line closes at five and the emails start at five past | ✗ no | discutir |
| 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 | discutir |
| 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 | discutir |
| Escalations go to a team that does not read the ticket history | → | Customers repeat their problem to every person they are passed to | ✗ no | en foco ↑ · cerrar ✕ |
| 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 | discutir |
| Customers repeat their problem to every person they are passed to | → | … | ✗ no | discutir |
| … | → | Customers repeat their problem to every person they are passed to | ✗ no | discutir |
| Survey requests go out before the problem is solved | → | Customers repeat their problem to every person they are passed to | ✗ no | discutir |
| 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 | discutir |
| Managers see the dashboard, agents see the queue, nobody sees the customer | → | Customers repeat their problem to every person they are passed to | ✗ no | discutir |
| Templates make every reply sound like nobody read the message | → | Escalations go to a team that does not read the ticket history | ✗ no | discutir |
| … | → | The phone line closes at five and the emails start at five past | ✗ no | discutir |
| Customers repeat their problem to every person they are passed to | → | The best agents leave within a year | ✗ no | discutir |
| The best agents leave within a year | → | Escalations go to a team that does not read the ticket history | ✗ no | discutir |
| The best agents leave within a year | → | Managers see the dashboard, agents see the queue, nobody sees the customer | ✗ no | discutir |
| Nobody from product reads the ticket tags | → | Escalations go to a team that does not read the ticket history | ✗ no | discutir |
| The best agents leave within a year | → | … | ✗ no | discutir |
| Escalations go to a team that does not read the ticket history | → | … | ✗ no | discutir |
| … | → | Templates make every reply sound like nobody read the message | ✗ no | discutir |
| 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 | discutir |