North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

AT&T DSL Support IVR issue

  • From: Jason Gurtz
  • Date: Wed Jan 23 11:54:42 2008
  • Domainkey-signature: s=sgs; d=npumail.com; c=nofws; q=dns; h=X-IronPort-AV:Received:Content-class:MIME-Version: Content-Type:Content-Transfer-Encoding:Subject:X-MimeOLE: Date:Message-ID:X-MS-Has-Attach:X-MS-TNEF-Correlator: Thread-Topic:Thread-Index:From:To; b=FG/D8J6o+lU2AZ4vglPW2q1xwp+2vzd2jGNTEH/OTOm3M8WbtGO54r36 TvYAkIA1aByNaaTqOoskKDxbQg+imc2L2S4vzsgi/2HetGL5OccZY1iom eGLiOvUPqkPrc7V86g+Tzbs2Y3rYEAaaHbwuy4f+6p4YN9Sv548MhH/8x 4=;
I'm posting under the assumption that many larger orgs may be involved
with dsl at remote sites and would potentially need vendor support when a
problem occurs with their AT&T adsl.

Since the middle of December 2007 we have been unable to obtain support by
following these steps:

Call AT&T national support line at 1.877.722.3755

Say "no"
Enter <DSL Line#> on keypad
Say "tech support"
Say "no"
Say "yes"
Say "Connection Problem"

At this point the IVR reports that it will transfer to a customer support
rep....followed by a pause...Followed by this announcement: "You've
reached a non-working number at teletech. Please hang up and try your call
again."  Then it hangs up.

Just today, after a month of contacting AT&T and being told we were crazy
at multiple levels we may have someone who can help but we're interested
if anyone at other locations in the U.S. has experienced the same issue.

Yes, it would be great if the system could be changed to support keypad
phone tree entry in addition or instead of voice input.  kthx

O yes, calling sales to get support did the trick.

~JasonG

--