Verizon Case

Abstract People working at telecommunications companies believe that communication within the organization will proceed smoothly. However, it is not necessarily the case. An example is our account documentation process. There are some differences between what departments need for comments and those who can evaluate specific comments on user accounts. The purpose of this article is an overview and review of the review process for Verizon Wireless's wireless data technology support department.

In a brief sentence at the end of a memo of Monday last week, I tried to explain the clarity of the company's "What I am doing here" (Verizon in this case). However, considering the questions received from some readers, I failed to execute because I was not sure. Specifically, I forgot to obey my own "eg" rule. Royal general statements must drop to the earth through one or two examples. Ideally, the company's motto is short-lived, resonant, and memorable. This makes it more resistant to confusion and excitement. Regardless of whether you are a receptionist, an independent thinker, or a top engineer, you must be able to memorize it. Even at 3 am. Even if you are tired, you get drunk and upset. Even if your spouse is wearing underwear in the rain, you throw you on the street

The key to attack is your mobile phone number, the weak link is your mobile phone company, and in my case it is Verizon. Hacker called Verizon 13x within the next 3 hours and tried to port my number to a new device pretending to be me. Because they do not have my "password", they are often rejected, so Verizon asked them to issue a warning about switching to a new device. I personally talked to Verizon, I told them that it was not me, and I was wary of my account hit by a hacker. I requested a second level of protection based on the password code and asked me not to change my account for the next 24 hours. I am afraid, I am aware that Verizon protects me because I am aware of the threat, but this is not the end.