B
Bill Sanderson
That sounds about par for the course. I'm impressed that they have the
remote capability--this is a Good Thing, 'cause it cuts out a lot of
listening through accents and trying to do what they say, etc... Level 1
can be quite tedious, but once they are sure they can't solve it with the
basic script, the level 2 people should be quite sharp.
I've actually had one paid support incident that didn't solve my
problem--which was pretty annoying--but the free folks have had a good track
record, but mostly once the problem is bounced to the next level.
I'm glad you were able to do this.
There are a bunch of reasons for calling Microsoft on issues like this. One
is that it gets the issue on their radar screen--they may never have seen it
before. Minimally, it'll get some statistics about how often x is
happening, which may get budget $ behind fixing it. It also gives the techs
some training, at the expense of your time.... My preference when an issue
is easily described is to go for email support, which can happen on MY
schedule--that has been pretty effective for me over time, again, mostly
once level 2 kicks in--but your issue really isn't one that I'd do that
way--they really need to see it and hear it described to understand the
issue.
Let us know how it turns out--and thanks for coming here for help and being
persistent!
--
remote capability--this is a Good Thing, 'cause it cuts out a lot of
listening through accents and trying to do what they say, etc... Level 1
can be quite tedious, but once they are sure they can't solve it with the
basic script, the level 2 people should be quite sharp.
I've actually had one paid support incident that didn't solve my
problem--which was pretty annoying--but the free folks have had a good track
record, but mostly once the problem is bounced to the next level.
I'm glad you were able to do this.
There are a bunch of reasons for calling Microsoft on issues like this. One
is that it gets the issue on their radar screen--they may never have seen it
before. Minimally, it'll get some statistics about how often x is
happening, which may get budget $ behind fixing it. It also gives the techs
some training, at the expense of your time.... My preference when an issue
is easily described is to go for email support, which can happen on MY
schedule--that has been pretty effective for me over time, again, mostly
once level 2 kicks in--but your issue really isn't one that I'd do that
way--they really need to see it and hear it described to understand the
issue.
Let us know how it turns out--and thanks for coming here for help and being
persistent!
--