Incorrect SSN/DOB Error - Unable to Add New Line for a Month

I'm reaching out here because I've hit a wall with Xfinity Mobile and am hoping someone in the community can help. For nearly a month, I've been trying to add a new line to my account, but every single time I get to the last step, I'm hit with the same error: "The Social Security Number and Date of Birth provided do not match our records."

This has been a complete nightmare and a frustrating loop. I've been to two different Xfinity stores multiple times, bringing my IDs to prove my information is correct. The store reps see everything is right on my account and have even tried to put the order through themselves, but it always fails. They just tell me to call customer support.

Of course, when I call, the representatives on the phone tell me to go to a store, sending me right back where I started. It's an endless cycle that's wasted so much of my time. I even reached out to the three credit bureaus, as one of the reps suggested, to see if there was a problem there. All of them confirmed there are no issues. I also opened a ticket with the Xfinity Privacy Center, thinking it might be a data problem, but they closed it, saying they couldn't help with an incorrect SSN and DOB.

The most confusing part is that I used the exact same SSN and DOB to successfully add my first line back in July 2025. This should be a simple process, but for some reason, it's completely broken for my account. I'm hoping someone here has experienced this exact problem and can offer a solution or a way to get this escalated past the standard support channels.

A quick search of the forums shows I'm not the only one dealing with this. I've seen other posts from people running into the same problem, like this one about an ‎https://forums.xfinity.com/conversations/plan/invalid-ssn-dob/675efd4d702e6f479364dbe1 and another about the ihttps://forums.xfinity.com/conversations/plan/incorrect-dobssn-when-upgrading-my-phone/628901e5855f616353ae62bencorrect DOB/SSN when upgrading. I'm hoping someone here has experienced this exact problem and can offer a solution or a way to get this escalated past the standard support channels.