I too had the exact same problem. I called late last night and got through
to customer service. The agent told me that they are not able to offer
Blackberry service after hours and on Sunday and that I would have to call
back on Monday morning. I explained that I was leaving for Washington, DC
early Monday morning and had to fix the problem before I left on Monday.
Early Sunday morning I got a phone call from Cingular Customer Service (They
contacted a Blackberry Specialist on his day off) and they told me that they
had a network problem. The agent verified all of my settings and told me
that she would call me back to make sure that I had service. She didn't
even have to call back because I had service in less than a half hour. I
got an email from her thanking me for being patient.
I follow this newsgroup and all I hear is complaining. I switched from
Verizon to Cingular about 3 months ago and have nothing but praise for
Cingular Customer Service. They really went out of their way for me.
Bruce D. Brown
PS. My problem is solved and I hope your problem receiving email is also
solved.
> I've been having a problem since yesterday, where the Blackberry is not
> receiving e-mail messages, and only reads "GSM", instead of "GPRS". Is
> this completely a carrier problem, or does anyone know any hints that
> may "reset" a problem?
Bob - 20 Jun 2005 02:00 GMT
Well, I'm going to try after hours support tonight, and if not, call in
tomorrow. It briefly worked today, but then is mostly going back to
GSM only.
I hope they figure this out. I've been a very happy customer of
Cingular, and I'm glad I switched to them. I just wish they had the
24x7 customer service like AT&T did. That is the only disadvantage of
the merger I have noticed. The big advantage of Cingular to me is
their coverage is great in my area.
> I too had the exact same problem. I called late last night and got through
> to customer service. The agent told me that they are not able to offer
[quoted text clipped - 21 lines]
> > this completely a carrier problem, or does anyone know any hints that
> > may "reset" a problem?