New problem solver
•
9 Messages
This is ridiculous
I am unable to log in to my comcast account via my comcast domain email address (seeve@seevehome.net), or use any of my email account services. This is unacceptable. As soon as my contract is up, I will be moving to another ISP. This has not been resolved even after repeated communications over the last month.
BrandXCustoms
New Member
•
4 Messages
10 years ago
I had the same problem yesterday after getting exchange mail set up for our domain, a call to customer service reset the password and I was able to log in. I also find the URL matters, I have to use http://businessclass.comcast.net for one of our email names, http://comcast.com/myaccount for another. Yet both are associated with the same business account.
0
0
rw_hardin
New problem solver
•
9 Messages
10 years ago
I haven't been able to log in to any comcast services with that account. I was able to manually reset the password today with this account for the first time. For a month now, it has failed with a non-descriptive error every time I have attempted to do it. Magically, as soon as I posted this complaint, I was able to go back and reset it and it worked.
I have had a number of communications with CS about this, as well as being unable to use the SiteBuilder tool.
0
0
CC_John
Retired Employee
•
1.9K Messages
10 years ago
Hi rw_hardin. I apologize for the continued problems you've encontered while attempting to resolve this issue. I have re-engaged the Business Service Center in order resolve this issue.
Thank You
0
0
BrandXCustoms
New Member
•
4 Messages
10 years ago
I experienced the same thing. Apparently the first-tier support folks use different tools to access our accounts, and do not have actual internet access with an actual browser, so they don't know what we're talking about. It's a bit frustrating for both the poor support person and customer.
0
0
rwhardin
Contributor
•
15 Messages
10 years ago
Well, luckily, the login issues are fixed. However, I still do not have access to Site Builder, which was the original issue I was seeking support for. Apparently, "fixing" that issue led to the login issues. Or something. I don't know.
0
0