This problem is a bit more complicated at Ford as far as I can tell. There appear to be many application teams that do things at Ford from what I can see. The website, Ford Credit applications, Ford parts/accessories, dealership apps, and FordPass are what I can see as a customer. All of these apps seem to run on various platforms, and have app teams that handle customer support issues like any other company. What I'm guessing is happening here is that Ford is using a single provider for identity management. This means that even though there are lots of app teams and support folks, they all call back into someone (internal or external) who manage the user IDs and data for the users of these apps. It provides a sort of single sign-on capability for the company. My login for FordPass is the same as the login for Ford.com. The problem as I see it is that the various app teams don't have access to infrastructure level parts of their stack, and the IT team at Ford has a security group or team that controls what is and isn't a trigger to lock out the SSO user from the identity backend. During my attempt to get unlocked, the app team seemed to have no control over the SSO system, and had to reach out to the IT security people to review and unblock locked out SSO level accounts. FordPass can use the SSO system, but does not control it. My guess is that Ford does this for cost savings, unified user experience, and security. Security is key as these systems have access to credit data and other PII info for the users, as well as access to APIs that can physically start your vehicle (EV and non EV alike). I'm unsure what Ford needs to do to protect users from these painful lockouts, but they need to do something and have it integrate with their SSO solution. At the very least, the 'repair' of these lockouts can't take 2-4 weeks. It's bad for business and it's pissing off their EV customers. Likely the first customers that need access to these APIs for more than the occasional remote start.