Visitor
•
13 Messages
Text message not received from Account authentication codes and Android Users
I am close to calling 7 on Your Side on Xfinity Mobile. The Customer Tech Support is ineffective. Tech Support people are reading off a script and have no clue what is happening. Since October 4th, my husband and I switched from Verizon to Xfinity Mobile. I cannot receive text messages from Android users and any Account Authentication Codes from Amazon, Banks, my Website Supports, my Square Account, etc. I spoke to 10 Tech Support personnel today, including managers, who could not fix the issue.
I had to explain everything 10 times to each person I spoke to, which got tiresome. Why can't they review my account and understand the issues before asking me over and over again to explain what my problem is? The last person I talked to was at Comcast Advanced Tier 2 support, and I asked for them to disable "Premium Text Blocking" (an anti-SPAM feature), and they said it wasn't enabled. I thought this may have been the issue, but they told me it was not activated, so that wasn't the problem.
I am speechless at this point and will look for another service provider. The Tech Support person at the Comcast Advanced Tier 2 level told me this would be passed on to the engineers for review, and I will have to give them 72 hours to fix the issue. In addition, it took the agent 45 minutes to generate a ticket for this issue. The call took 2 hours and 9 minutes. In addition to the 4 hours and 5 minutes, I had already been on the phone with various tech support personnel at Xfinity Mobile. Not only is this personal incontinent, but I am losing business over this as an artist and find Xfinity mobile unprofessional about their service and handling these types of problems. My husband and I were considering switching our ADT security over to Xfinity. However, that is not happening now. I can only imagine if we had a break-in, they would claim there was no service at our house, I have no trust in their ability to provide any good service.
If you are an Xfinity employee and are reading this, do not reply by telling me to SMS Text Message to 1 (888) 936-4968 or call: 1 (888) 936-4968.
I have done all that without any help; as stated above, my next step is to call 7 on your side News to bring light to an issues that has been left unaddressed over several years. It is clear Comcast has become too large and does not train its employees well to assist.
However, if you are a higher-level employee and have the know-how to fix the issue, I like to speak to you.
AppleTechAlin
Contributor
•
14 Messages
3 years ago
Probable best bet is to go to an xFinity store or call and go directly to Advanced Support Representative. There's clearly some sort of VTEXT IN network problem that xFinity is not aware of that is causing a mass outage, I am another affected user by this issue. Got an iPhone 14 Pro Max to replace an iPhone 10, texts worked fine on it. Outbound texting to non iPhones works fine because VTEXT OUT is configured correctly. This is clearly something to do with xFinity's network and eSIMs / other new technology.
UPDATE: Spoke to advanced support, what happens when you take out the physical and go to fully embedded chips is quite a complex process, especially if you're going from a 4G device to a 5G device.
Going from a physical SIM phone to an eSIM phone triggers a port within the network, even though you're not porting your phone number or anything there's still a full on PORT.
When I say PORT I mean a movement of your device within the networks infrastructure, on their servers. Your iPhone with an eSIM runs on a completely different network than the old physical SIM devices, so after you activate it, even though you can make & receive calls and iMessages and eat all the data you want getting that VTEXT IN pipe to be rerouted from the old infrastructure to the new infrastructure can take anywhere between 24-72 hours.
If it doesn't work after 3 days of being activated, probably time to take it to a xFinity retail store for a technician to physically look at.
(edited)
1
0