Search results for

#TechSupport

#1 Click this link to see Blog page --> 03/04/2012

I called the phone company #TechSupport twice yesterday. They were kind enough to give me a Case Number. It is almost as if this small validation is supposed to make up for the loss of service.

I got a call back around 3 p.m. yesterday and they assured me they might get around to looking into it today - would anybody be home? I told the lady that wouldn’t be necessary because the problem wasn’t in my house or anywhere near it.

MjL

#2 Click this link to see Cartoons page --> 02/01/2019 #12

THIS.
I would call #TechSupport to tell them my DSL was down and had to listen to the stupid machine telling me to go to their web site and make a trouble ticket. Then the first thing they would ask for when a person finally answered the phone was what was the ticket number I got when I went to the Internet. How stupid is that?

MjL

#3 Click this link to see Blog page --> 05/27/2020



#TechSupport #Yahoo #Blog
I can’t tell you how much dread I feel at this announcement. EVERY time these idiots improve, upgrade, etc. it turns into a major pain in the ass for me. I have never dealt with a more inept bunch of people and each time I wonder why I don’t move the Blog to a different web host. The last time they did this they turned off the backward-compatibility and I had to rewrite a lot of code. Hard telling what they will screw up this time.

This might also explain the sluggishness and down time of late.

I suspect they have a bunch of teenagers in India doing the transfer of data to this new system.

So if the Blog disappears (again) on or after June 9 you will know why.

Update: 05/27/23
Almost three years later and another selloff to a new outfit (#Turbify). This time they really hosed everything up and my site was FUBAR for weeks. Still not completely repaired.

MjL

#4 Click this link to see Blog page --> 08/24/2022

It appears the only casualty of yesterday’s #Blog database crash was my Wordle entry and I put that back in again.

It also looks like they got the database fixed (knock on wood).
I am so glad I didn’t call #TechSupport and I’m hoping whomever did call didn’t get their database destroyed.

I say that because the poorly trained non-English speaking techs ALWAYS presume the problem is caused by the customer. They then try to repair the customers (unbroken) data with a broken system and will only realize the problem is not the customer’s AFTER they have really messed up his data. Been there, been trashed. Fortunately I have learned to back up my data regularly and not rely on them.

MjL

#5 Click this link to see Cartoons page --> 06/24/2025 #42

#TechSupport

MjL