I tried to schedule service at the car dealer's website. As usual, its poor design doesn't let me choose every service I want. A new wrinkle is that there are a couple of recall notices, and scheduling that service requires a phone call. I call and listen to the automated system tell me that I can make an appointment more quickly by using the website. Knowing that's a lie, I stay on the line. [1/2]

Eventually, I’m told to leave my name, number, and a short message and they’ll get back to me. My message to them would not be short, so I just give my name and number.

I am increasingly of the opinion that most people who make user interfaces get into that line of work because they’re generally incompetent and this is the only job for which there are no standards. [2/2]

The call back from the dealer went smoothly and I now have an appointment later this week for the standard 25,000-mile service and two of the three recall items (there’s no fix for the third one yet). Remarkable how just talking with a person can handle the entire interaction quickly and correctly. [3/2]
@drdrang As an engineer, the idea of a recall with no actionable mitigation is making my eye twitch.
@localhost Yeah, I couldn't believe the mailing I got from Toyota last month. At that time, none of the recall items had a fix. Engineering aside, that doesn't fit the definition of “recall.”
@drdrang Huh. Weird that humans are good at processing natural language requests. 🤔
Website Task Flowchart

xkcd