...snip... But oddly when they emailed me to tell me that they thought they had fixed it, they said that the tier 2 team was able to see the option when they logged in as me. ....
Brett,
That is very, very interesting! I had what seemed like an entirely different problem, but with the same "tier 2" inability to reproduce it. This may be a clue to the cause, and may even suggests a solution.
What fixed my other problem was to change my Tesla account login email.
Apparently both problems are caused by some detail in the account record in Teslas authentication service. Tier 2 does not need (or know) our passwords, which means they bypass the authentication process when they log in to our accounts. Apparently when the login email is chnaged, a new record is created without whatever glitch is making authentication fail.
My other problem was that I could not log in to my account on the Tesla web site. I could log in to the App, and it worked fine, but I could not work on my Model Y reservation at all. I could post that story if anyone wants the gory details.
Anyway, just maybe, if you change your account login email and then log in with the new email, the Notification problem may, just maybe, be fixed. This is done on the Tesla web site, Account page. If you wish, you can change it back to the old address after.
I have a friend with the same problem, and am waiting to hear back with permission to try this on their account. In the mean time, you could try it yourself.
I have my own internet domain, and so creating an email alias is easy for me. Many email services allow creation of alternate or alias addresses. Or you could just create new gmail account. Heck, I could create an alias for you on my domain.
If you try it, let us know if it works. Fingers crossed!
SW