Back to Virginia Unemployment

Max Knight

Can't verify phone number unemployment gov2go - Virginia VEC issue

Two weeks into my claim and I've been stuck at the same wall every single day. I got laid off from my warehouse supervisor job at the end of last month, filed my initial claim through the Virginia VEC CSS portal, everything seemed to go fine until I hit the identity verification step in the gov2go app. It asks me to verify my phone number and no matter what I do it just won't go through. I've tried my cell, tried using my landline at my parents' place, tried removing and re-adding my number like four times. The app just spins and then gives me a generic error that says something like 'verification could not be completed.' My email verified just fine which is what's confusing me. I even uninstalled and reinstalled the gov2go app twice. My weekly claim is technically filed but I'm worried nothing will process until this verification is complete. Has anyone actually gotten past this phone number verification problem? I need my benefits to start because my savings are almost gone.

Week three of my own claim and I ran into something similar with gov2go verification dragging everything out, so I know how stressful this is. Before I figured out the phone issue I needed to actually talk to a Virginia VEC agent to get my claim moving again, and after spending two full days redialing and getting nowhere I found a service called Claimyr. You go to claimyr.com and they basically get you into the VEC phone queue so you're not sitting there hitting redial for hours. There's a video showing how it works at https://youtu.be/GK1CFuX4p2k if you want to see before you try it. I finally got through to someone who could see notes on my account and that ended up being the thing that actually unstuck my claim. Even if you get the phone issue fixed yourself, having a VEC agent confirm your identity verification went through is worth doing.

0 coins

Just got to week two myself and the phone queue thing is the worst part of this whole process. Good to know there's something that helps with that.

0 coins

Thanks, I'll check the video out. Did the agent you spoke with actually fix the gov2go side of things or did they tell you to go back into the app and retry something?

0 coins

My week four now and what happened was the agent manually flagged my identity as verified on their end, and then gov2go updated on its own within about 24 hours. So the app itself didn't really need to do anything once the backend was updated.

0 coins

About five days into dealing with this exact thing on my own claim last month. The phone number verification in gov2go is linked to what carrier your number is registered under, and there's a known conflict with certain prepaid and VoIP numbers. What I'd do first if I were you is check whether your number is actually recognized as a standard mobile number. You can google a carrier lookup tool, just type your number in. If it comes back as VoIP or shows the wrong carrier, that's probably your problem. The actual rule is that gov2go's SMS verification requires a number that the system recognizes as a postpaid mobile line, and a lot of prepaid numbers don't pass that check even if they receive texts just fine normally. Landline definitely won't work for the SMS code. If that's your situation you might need to borrow someone else's number temporarily just to get past the verification step.

0 coins

Mine's through a major carrier so I wouldn't have expected that to be it, but I just ran the lookup and it's showing correctly as a postpaid mobile line. So that specific issue isn't what's blocking me, though I appreciate you explaining it because I'd never have thought to check that.

0 coins

Two weeks ago I had the same carrier issue with my prepaid number. Used my sister's number to verify and it went right through. Definitely worth trying if the carrier lookup shows something weird.

0 coins

If the carrier check is clean then the next thing I'd look at is whether your number is already associated with a different gov2go account from a previous claim. The system sometimes flags duplicates and blocks re-verification silently without telling you why.

0 coins

Halfway through my second week of fighting this verification thing and I want to add something that helped a friend of mine when she was stuck. She had already tried everything on the app side and was getting nowhere, so she used Claimyr at claimyr.com to get a VEC agent on the phone. The agent she reached checked her account and found that her gov2go verification attempt had generated an internal error on the VEC side that wasn't visible to her at all in the app. The agent submitted a ticket to get it cleared. So sometimes the problem isn't something you can fix yourself, it's something sitting in the backend that only someone with account access can see. Might be worth going that route sooner rather than waiting weeks trying app fixes.

0 coins

Okay that actually makes me feel like this is more likely a backend thing than a me thing. Every visible step looks fine from my end so it would make sense that the error is somewhere I can't see.

0 coins

First week filing here and reading this thread is making me preemptively anxious about hitting this same wall. Is gov2go verification required for everyone or only certain claimants?

0 coins

From what I gathered it's triggered based on certain flags on your account, like if something in your identity information needs an extra confirmation step. Not everyone gets it but a lot of people do.

0 coins

Got a letter about identity verification three weeks into my claim. It was confusing because nothing in the letter said anything about gov2go specifically, it just said to verify my identity through the official portal. Took me days to figure out gov2go was even involved.

0 coins

Eleven days since I submitted my initial claim and I hit this problem in a slightly different form. Mine wasn't the SMS code failing, it was the app recognizing my number but then never sending the code at all. What I'd try in your position first is going into your phone's message settings and making sure short codes aren't blocked. Carriers sometimes block short code SMS by default. The verification text from gov2go comes from a short code number, not a regular number, so if you have any kind of spam filter or carrier-level message filtering turned on it might be intercepting the code before it ever reaches you. The way it works is that gov2go sends to that short code and if your carrier or your phone's native filter blocks it, you'll see the spinner on the app end but no message ever arrives. Turning off those filters temporarily and retrying the verification fixed it for me.

0 coins

Short codes, I had not even thought of that. Just checked and I do have some carrier-level filtering turned on. Going to turn it off right now and try again.

0 coins

Same fix worked for me about a month ago. I was going insane thinking my phone was broken and it was just a spam filter eating the code the whole time.

0 coins

Also worth checking if your phone has a separate filter app installed, some people set those up and forget about them. Android in particular sometimes has Google Messages doing its own filtering on top of whatever the carrier does.

0 coins

Just got past my own adjudication notice this week so I'm back to dealing with weekly claims now, but I remember the gov2go nightmare from the start of my claim. One thing that tripped me up was that I was trying to verify using wifi calling. If your phone is set to prefer wifi calling, the number your carrier registers for outbound SMS might not match what you think your number is, and gov2go can reject it for that reason. What I did was turn wifi calling completely off in my phone settings before trying the verification step, so it was going through the actual cellular network. Sounds like a weird fix but it made a difference for me.

0 coins

Worth a shot, I do have wifi calling enabled. Never would have connected that to an SMS verification issue.

0 coins

Didn't know wifi calling could affect SMS routing like that. Learning so much from this thread about stuff that should just work automatically.

0 coins

The frustrating part is nothing in gov2go's instructions mentions any of this. You just get a generic error and have to figure out the actual cause yourself.

0 coins

Three failed attempts at verification behind me and I tried the wifi calling thing and it actually helped. Not the full fix for me but it got the code to deliver at least.

0 coins

About four weeks since my layoff and I want to share what ultimately resolved my situation because I think it's the most direct path for anyone who's been stuck more than a few days. After trying every app-side fix I could find, I used Claimyr, which you can find at claimyr.com, and the demo video at https://youtu.be/GK1CFuX4p2k shows exactly how it works. The VEC agent I reached through that was able to pull up my account and see that there was a mismatch between the phone number I had on file with VEC from a previous claim years ago and the number I was trying to verify with now. The system was silently rejecting the verification because of that old number conflict. The agent updated my contact info on the VEC side and within about half a day gov2go accepted the verification. Turned out it was never a phone or app issue at all.

0 coins

Old number conflict is something I hadn't considered at all. I did file a claim a couple years back and had a different number then. That could genuinely be what's happening here.

0 coins

So the VEC system still has records from previous claims linked to the account? I assumed each claim was kind of a fresh start in terms of personal info.

0 coins

From what the agent told me, your contact info from previous claims can persist in certain parts of the system even if you updated it in the CSS portal for the new claim. It's one of those backend inconsistency things.

0 coins

Got my first weekly claim payment approved last week after a rough start, and looking back I think calling VEC directly was the single most useful thing I did even though it was the hardest to actually accomplish. I'd been on hold so long in the regular queue that I eventually tried Claimyr at claimyr.com and it got me to an agent in a fraction of the time. The video at https://youtu.be/GK1CFuX4p2k explains it well. That agent explained to me that the gov2go app and the VEC internal system don't sync in real time. So even if gov2go shows your verification as pending or failed on your end, it's possible VEC's system shows something different, and the resolution often requires someone on the VEC side to manually reconcile the two. That's not something any amount of app reinstalling will fix on its own.

0 coins

Real-time sync being absent between gov2go and VEC's own system explains so much about why this feels like shouting into a void.

0 coins

Got an adjudication hold last week and I had no idea the two systems weren't synced. I've been blaming myself for doing something wrong in the app.

0 coins

Yeah the agent I spoke with basically said gov2go is a third-party identity verification layer and VEC has to manually act on what comes from it. It doesn't automatically resolve anything on the VEC claim side.

0 coins

That is genuinely terrible design for something this important. People are waiting on benefits and the fix requires a human to manually connect two systems that should just talk to each other.

0 coins

Somewhere around day nine of my claim and I went through something adjacent to this. Mine was that gov2go kept asking me to verify my number even after I had already done it successfully. What I'd check in your situation first is whether you have multiple gov2go accounts accidentally created under different email addresses. If you verified on one account but your VEC portal is linked to a different account, the verification status never carries over. I've seen a few people describe this in other forums. The way it plays out is you think you verified but VEC's system is looking at a different gov2go profile entirely. Logging out of gov2go completely, clearing app data, and logging back in with the exact email tied to your CSS portal can sometimes reveal if you've been working in the wrong account.

0 coins

Just checked and I do only have one email address used anywhere in this process, so probably not the dual account thing, but I appreciate the thought because I know I could have easily made that mistake.

0 coins

This happened to me exactly. I had used a different email to sign up for gov2go originally and then created a CSS account with my main email and they never connected. Took forever to figure out.

0 coins

It's such an easy mistake to make because nothing in the initial setup process warns you that the emails have to match precisely.

0 coins

Received my disqualification notice during week three of my claim and while I'm dealing with appealing that now, I remember the verification step being its own headache at the start. One thing I didn't see mentioned yet is that some phones throttle or delay SMS during certain hours if battery saver is set too aggressively. When I first tried verifying I was at like 12 percent battery and the code never came. Tried again the next morning with the phone fully charged and battery saver off and the code came through instantly. Dumb fix but it's worth eliminating.

0 coins

Low battery throttling affecting SMS delivery is not something I'd ever think to consider but I'll absolutely try this with a full charge.

0 coins

This is wild, I had no idea battery saver could block incoming texts. Learned something today.

0 coins

It doesn't block them exactly, more like it delays background processes including certain app wake-ups that trigger SMS notifications. Result is the same though, code doesn't arrive.

0 coins

Just filed my claim for the first time last week so I'm very new to all of this, but I work in mobile software and the gov2go verification issue you're describing sounds like it could be related to how the app handles rate limiting. If you've tried to verify multiple times in a short window, the system may have flagged your number as suspicious and put a temporary hold on sending codes to it. What I'd try first is waiting a full 24 hours without attempting any verification and then trying once, cleanly. Rate limiting cooldowns vary but most identity verification systems reset within 24 hours. This wouldn't explain why the first attempt failed but it could explain why subsequent attempts keep failing even if the original issue has been resolved.

0 coins

Rate limiting is a really good point and I'll admit I've been hammering the retry button multiple times a day which is probably exactly the wrong thing to do.

0 coins

This tracks. I've seen people make it worse by trying over and over. Give it the full 24 and try once.

0 coins

Also try it on a different network when you do retry, like switch from wifi to cellular data or vice versa. Sometimes rate limiting is IP-based rather than number-based.

0 coins

Somewhere in week five now and I want to share that my verification issue turned out to be nothing I could have fixed myself at all. VEC had an incorrect digit in my phone number on file, carried over from when I first registered years ago and updated everything but the underlying contact record. No matter what I did in gov2go it was trying to match against a number that didn't exist. What I'd do first if the app-side stuff hasn't worked for you is request a full account review through the VEC contact form specifically asking them to confirm the phone number on file matches what you submitted on your current claim. Getting that discrepancy corrected by a VEC agent was the only thing that actually resolved it.

0 coins

An incorrect digit on their end would explain everything. I'm going to try reaching someone at VEC to confirm what number they actually have on file for me.

0 coins

How do you even request an account review through the contact form? Is that a specific option in the CSS portal or is it a separate form?

0 coins

In the CSS portal there's a message center where you can send a secure message to VEC. I sent mine explaining the issue and asking them to verify my contact info. Response took a few days but it got there.

0 coins

Few weeks into my claim and I didn't even know there was a message center in the portal. I've just been calling. Good to know there's another way to reach them.

0 coins

Got to week two of my claim before hitting a completely different wall but I've been lurking here reading about the gov2go stuff. One thing I want to point out for anyone reading later is that the gov2go phone verification and the job search activity requirement are two separate things, but they both have to be satisfied before your weekly claims pay out. I've seen a few people on this thread and elsewhere assume that once verification is done everything flows automatically. Make sure your four job search contacts per week are logged while you're dealing with the technical side of this, because even when verification resolves, if your job search log has gaps from the weeks you were focused on troubleshooting, those weeks can get flagged for review.

0 coins

Keeping up with the job search log even while fighting the verification issue, good reminder. I've been logging but I'll double-check the entries are showing correctly in the portal.

0 coins

This is a really important point. I lost a week of benefits because I let the job search log slide while dealing with an adjudication issue. Learned that lesson the hard way.

0 coins

The VEC system doesn't pause the job search requirement while your claim is in a technical hold state, which is a frustrating reality a lot of people don't find out until it's too late.

0 coins

Several weeks out from getting laid off and just finally got my verification sorted, so I want to leave the specific sequence that worked for me in case it helps anyone else who finds this thread later. First, I confirmed my carrier type using a lookup tool. Second, I turned off wifi calling and all SMS filtering. Third, I waited 24 hours without touching the app. Fourth, I did the verification attempt on cellular data with the phone plugged in and battery saver completely disabled. Fifth, when I still got an error, I sent a message through the VEC portal message center asking them to confirm my phone number on file. They corrected a digit, and the next verification attempt went straight through. Total time from first attempt to resolution was about two and a half weeks. The VEC portal message took four days to get a response so factor that in if you go that route.

0 coins

This is the clearest summary of what to actually try in order. Going to follow this sequence starting today and see where it breaks down.

0 coins

Saving this comment specifically. The step-by-step format is exactly what I needed to see.

0 coins

Two and a half weeks is brutal but at least it did eventually resolve. Good of you to come back and document what worked.

0 coins

The four-day response time on the portal message is worth flagging. If someone is in a financial emergency that timeline is too slow. Trying to call with Claimyr or some other route to get a faster answer makes more sense in that case.

0 coins

Just past my first week certified and I'll admit I still don't fully understand what gov2go is or why it's separate from the main VEC website. Can someone explain why Virginia VEC uses a separate app for identity stuff instead of just handling it in the CSS portal directly?

0 coins

Gov2go is a third-party identity verification service that VEC contracts out to rather than building identity verification in-house. It's common across different government agencies to use outside providers for this. The CSS portal handles your actual claim management, gov2go just handles the initial identity confirmation step.

0 coins

Okay that makes more sense. So gov2go doesn't actually have anything to do with my weekly certification or job search log, it's just the front door essentially?

0 coins

Exactly that. Once you're through the door the CSS portal is where everything else lives. Gov2go's only job is confirming you are who you say you are at the start.

0 coins

Three weeks of back-to-back issues with my claim and I want to validate everyone here saying this is genuinely a broken part of the system. The fact that VEC depends on a third-party app for identity verification but those two systems don't sync automatically, and that an agent has to manually reconcile discrepancies, is not a user problem. It's an infrastructure problem that falls on claimants to navigate and diagnose themselves. For people who are already stressed about losing income this is an unreasonable burden.

0 coins

Got my adjudication notice at week two and the technical barriers on top of the financial stress are genuinely overwhelming. It shouldn't be this hard.

0 coins

And the people calling the VEC help line are dealing with hold times of an hour or more because so many people are stuck on issues exactly like this one. The whole thing compounds.

0 coins

Agreed completely. I burned through almost all my savings while dealing with claim holds that turned out to be technical errors, not actual eligibility issues. The system is not built with any urgency about people's financial situations.

0 coins

Just filed last week and reading all of this is terrifying. I really hope I don't hit the same walls.

0 coins

Virginia Unemployment AI

Expert Assistant
Secure