I wish there was a way to let support teams know that I really do how to report a broken site or broken flow. I don’t need instructions that I already said I followed and explained where they fail.
I’m in the midst of explaining this to two different companies in different sectors. “No, no, really. What I’m saying is really a broken flow.” I don’t want to sound like a jerk but I’m paid good money to find this for my own products… This is free work I’m giving away!
kraft
Success. @JetBlue finally acknowledges that they allow a plus sign in email addresses when registering for a new account but you can’t log into an account with a plus sign…
kraft
My saga continues with the other company. Just a matter of principle now. We’re on to the “send a condescending support doc that is the most elementary explainer” phase. There is a feature of our support desk tool where you can setup automations. Pretty slick.
kraft
But, an automation must be written to only run once per ticket. The example “If the priority is High, make the priority Urgent” since once it runs once, the priority will no longer be High. Cool. Mine “If the form is X, make it Y.” where the form is an exclusive setting.
kraft
It won’t let me save it without some crummy work around (which is fine and what I set up), but it is the right structure. I don’t need a doc that tries to tell me I’m stupid… https://t.co/9QYrJPacgO
kraft
FTR, I’m fine if it is a wontfix bug. You can work around it. Whatever. I just want some acknowledgement that something is broken and it isn’t that the user doesn’t understand something.
kraft
Hey! Passed up to Tier 2 support which agrees something seems off and is passing it to their dev team.
Comments
7 responses to “”
I’m in the midst of explaining this to two different companies in different sectors. “No, no, really. What I’m saying is really a broken flow.” I don’t want to sound like a jerk but I’m paid good money to find this for my own products… This is free work I’m giving away!
Success. @JetBlue finally acknowledges that they allow a plus sign in email addresses when registering for a new account but you can’t log into an account with a plus sign…
My saga continues with the other company. Just a matter of principle now. We’re on to the “send a condescending support doc that is the most elementary explainer” phase. There is a feature of our support desk tool where you can setup automations. Pretty slick.
But, an automation must be written to only run once per ticket. The example “If the priority is High, make the priority Urgent” since once it runs once, the priority will no longer be High. Cool. Mine “If the form is X, make it Y.” where the form is an exclusive setting.
It won’t let me save it without some crummy work around (which is fine and what I set up), but it is the right structure. I don’t need a doc that tries to tell me I’m stupid… https://t.co/9QYrJPacgO
FTR, I’m fine if it is a wontfix bug. You can work around it. Whatever. I just want some acknowledgement that something is broken and it isn’t that the user doesn’t understand something.
Hey! Passed up to Tier 2 support which agrees something seems off and is passing it to their dev team.