Back to Virginia Unemployment

Freya Andersen

Unemployment - no option to verify identity after creating account on Virginia VEC

So I finally sat down and created my Virginia VEC account on the Customer Self Service portal after losing my job last week. Got through the whole registration process, confirmed my email, logged in — and then absolutely nothing. There's supposed to be some kind of identity verification step before I can actually file my claim, but that option is just... not there. My dashboard shows my account exists but I can't proceed with filing because the system apparently doesn't recognize that I need to verify. I've gone through every menu I can find. Nothing under 'My Profile,' nothing under account settings. I even tried logging out and back in multiple times thinking it was a display glitch. Has anyone else hit this wall right after creating their account? I'm already stressed about the gap in income and now I can't even get the claim started. Do I need to wait some period of time before the verification option appears, or is this a known bug with the CSS portal?

Went through almost the exact same thing about two months ago. After I created my account the verification prompt never showed up on my dashboard either. What fixed it for me was accessing the portal from a different browser entirely — I'd been using Firefox and switched to Chrome, and suddenly the identity verification section was right there under 'File a New Claim.' The CSS portal has some serious compatibility issues that Virginia VEC never really publicizes. Worth trying that before anything else.

0 coins

My account still showed the same thing after trying Chrome. No verification option anywhere. I'm starting to think it might be something wrong on the backend with how my account was created.

0 coins

Browser switching worked for me too but only after I also cleared all stored data for the VEC site specifically. Go into your browser settings, find the site data for uidirect.vec.virginia.gov and delete just that — not your whole browser history.

0 coins

Yeah that's a good add, the cached data from an earlier failed attempt can basically freeze the portal in an incomplete state.

0 coins

The identity verification issue is brutal and getting through to someone at Virginia VEC who can manually push your account to the next stage is nearly impossible with the phone lines. I was stuck on this for about nine days before I tried Claimyr — it waits on hold with Virginia VEC for you so you actually end up talking to a live agent. The site is claimyr.com and there's a demo video at https://youtu.be/GK1CFuX4p2k that shows how it works. The agent I spoke with was able to flag my account and get the verification step to appear within about 24 hours.

0 coins

Nine days is terrifying honestly. I'll check out that video tonight. Did the agent do something on their end that you couldn't do yourself through the portal?

0 coins

Exactly — the agent told me there's a backend flag they can manually set when the verification prompt fails to generate. There's no way for the claimant to trigger it themselves. That's why calling is basically the only path when the portal doesn't cooperate.

0 coins

I've been trying the VEC phone line for three days straight and can't get through. Good to know there might be a way around the hold time situation.

0 coins

The 30-day window caught me off guard when I first filed — you have to get your identity verified and your initial claim submitted within 30 days of your separation date or you lose eligibility for those earlier weeks. If the portal is blocking you right now that clock is still running, so this isn't something you can just wait out and hope fixes itself.

0 coins

I had no idea about that deadline. My separation date was 8 days ago so I still have time but yeah, that changes how urgent this feels.

0 coins

The 30-day rule is real and they do enforce it. My neighbor lost two weeks of potential benefits because she couldn't figure out the portal in time and didn't realize she needed to push harder to get it resolved.

0 coins

The tricky part is Virginia VEC counts from your last day of work, not from when you filed, so people often think they have more runway than they actually do.

0 coins

There's actually a known issue where the ID.me verification integration with the CSS portal fails to initialize if your account was created during certain system maintenance windows. Virginia VEC does rolling maintenance usually on Tuesday and Wednesday nights. If you registered during one of those windows your verification path basically got orphaned. The fix on their end is straightforward but you have to reach an agent to get it done.

0 coins

I created my account on a Wednesday evening actually. That might explain exactly what happened.

0 coins

Wednesday evening is right in that window. When you get through to an agent mention that your account may have been created during a maintenance period — it gives them a faster way to look up what's wrong.

0 coins

I work in IT and this kind of session-state orphaning is super common with government portals that weren't designed with simultaneous maintenance in mind. The claimant has no way to fix it from the front end.

0 coins

Didn't know about the maintenance windows at all. That's genuinely useful context because I created mine on a Tuesday and had the same no-verification problem.

0 coins

My dashboard had no verification option either and I panicked thinking I'd done the whole registration wrong. Turns out for me the portal needed me to actually click 'File a Claim' first — the identity verification doesn't appear as a standalone menu item, it triggers as the first step inside the new claim filing flow. Have you tried starting the claim filing process to see if verification pops up inside that?

0 coins

I went back and tried this just now. When I click 'File a New Claim' it goes to a loading screen and then says 'you must complete account verification before proceeding' but doesn't give me a link or button to actually do the verification. So it knows I haven't verified but won't tell me how.

0 coins

Oh that error message is different from what I experienced. That sounds more like the backend flag issue others are describing — the system knows verification is pending but the verification path wasn't created properly when you registered.

0 coins

That loop you're describing — the system saying verify but not letting you verify — is apparently pretty common right now. I've seen it mentioned in a few other threads too.

0 coins

When my identity verification disappeared I ended up driving to my local Virginia Works office in person. They couldn't fix the CSS portal account directly but they did have a direct line to Virginia VEC's technical support team and made the call on my behalf. Got a resolution the next business day. Might be worth checking if there's a Virginia Works location near you.

0 coins

There's a Virginia Works office about 20 minutes from me. I didn't realize they could help with the portal issue — I thought they were just for the job search assistance part of the process.

0 coins

They're technically separate but the staff at mine were really willing to go the extra mile. Your mileage may vary depending on the office but it's worth walking in and explaining the situation.

0 coins

Virginia Works offices can be hit or miss for portal tech stuff in my experience, but having them make the call for you is a lot more efficient than sitting on hold yourself for hours.

0 coins

Spent almost two weeks fighting this same no-verification problem earlier this year. Tried every browser, cleared everything, tried from my phone, tried from my work computer. Nothing. Eventually used Claimyr to get through to a Virginia VEC agent after I couldn't get anyone on the line myself, and that agent told me the verification link was supposed to arrive by email when I registered but it was bounced by my email provider's spam filter. Had to have them resend it manually. Check your spam folder but also know you may need an agent to trigger a resend if it's been more than 48 hours.

0 coins

Just checked my spam folder all the way back to when I created the account — there's nothing there from Virginia VEC at all, not even the email confirmation that I did receive in my inbox. So the verification email was never sent in the first place, it seems.

0 coins

That tracks with the maintenance window theory others mentioned. If your account registration didn't fully complete on the backend, the verification email would never get queued. An agent can manually send it or add the flag directly.

0 coins

I had a similar situation where my confirmation email came through fine but the actual verification email never appeared anywhere. Completely different failure point than the email bounce issue.

0 coins

The ID.me side of this process is worth looking at separately too. Virginia VEC uses ID.me for identity proofing and sometimes the problem isn't the VEC portal at all — it's that ID.me never received the handoff from your VEC account creation. You can go directly to ID.me and check whether a verification request is sitting there waiting for you. If it is, completing it on the ID.me side sometimes pushes the status update back to your VEC account automatically.

0 coins

Logged into ID.me directly and there's no pending verification request tied to my information. So the handoff to ID.me definitely didn't happen.

0 coins

That confirms it's a VEC-side issue — the initiation of the ID.me flow never happened. This really does require a VEC agent to manually trigger. No workaround on the portal front end is going to solve it at that point.

0 coins

Good diagnostic tip. At least now you know exactly what needs to happen and can explain it clearly to an agent when you reach one.

0 coins

i had this for literally 3 weeks and kept thinking i was doing something wrong. eventually found out from someone else that you can submit a written inquiry through the CSS portal's message center even without being fully verified — not sure if that still works but it got my issue escalated faster than the phone ever did for me

0 coins

The message center in my portal is accessible — I can see it. I'll try sending an inquiry explaining the verification issue and see if that creates a ticket on their end.

0 coins

yeah just describe exactly what you're seeing, include the error message wording if you can and your registration date. that info helped them pull up my account faster

0 coins

The message center route is slower than a phone call but if you're having trouble getting through it's a solid backup. Usually gets a response within 3-5 business days in my experience.

0 coins

After about a week of the same runaround I went back and read the full VEC account creation instructions on their website more carefully. There's a note buried in an FAQ that says if you used a Gmail or Yahoo address to register, their system sometimes flags those as needing additional manual review before the verification step unlocks. Switching to a different email address and re-registering fixed it for me — annoying but it worked.

0 coins

I used a Gmail address. Really didn't think that would matter. Did you have to go through the whole registration process from scratch?

0 coins

Yeah unfortunately I had to start over with a new account using my ISP email. It's tedious but it only took about 15 minutes and the verification option showed up immediately on the new account.

0 coins

The Gmail issue sounds plausible but I'd be cautious about creating a second account without checking with VEC first — having duplicate accounts in the system can sometimes create its own set of problems with your claim.

0 coins

My situation dragged on so long without the identity verification step that I finally caved and used Claimyr to get a live agent at Virginia VEC on the phone. The whole thing resolved in one call — the agent said my account showed a 'registration incomplete' flag on their end that I had no way to see from the portal. They cleared it and I had full access to verify within a couple hours. Worth it after weeks of getting nowhere on my own.

0 coins

A 'registration incomplete' flag that's invisible to the claimant is infuriating. That's exactly the kind of thing you'd never know to look for without talking to an agent.

0 coins

Exactly. And the agent said it's apparently fairly common, especially for accounts created during high-traffic periods when the system is under load. The system takes the registration info but doesn't complete the backend process.

0 coins

High-traffic periods would explain why I saw this same issue when I filed — that was during a week where there'd been a bunch of local layoffs and presumably a lot of people filing at once.

0 coins

Virginia VEC's identity verification requirement exists because of the fraud wave that hit unemployment systems a few years ago, but the way they implemented it created this exact problem — a step that's mandatory but that the system itself can break and leave you locked out with no visible fix. It's genuinely one of the worst-designed parts of the whole claims process.

0 coins

The fraud prevention logic is understandable but building a system where a backend glitch silently blocks a claimant with no error code and no self-service fix is a real oversight.

0 coins

And if you can't reach anyone by phone you're just stuck. There's no secondary contact method that gets a fast response — the message center takes days, there's no chat option, no way to flag urgent cases.

0 coins

This is why people end up missing benefit weeks they were entitled to. The friction in the process isn't random — it hits hardest when you can't take time off work to spend all day on the phone.

0 coins

My verification issue ended up being tied to my Social Security number not matching exactly what was in a federal database — not because I entered it wrong but because there was an older discrepancy in the federal records themselves. The Virginia VEC agent was the one who identified it and told me how to get it corrected. Would never have figured that out on my own through the portal.

0 coins

That sounds like a nightmare to untangle. How long did it take to resolve once the agent identified the discrepancy?

0 coins

About two weeks total because part of the fix required documentation submitted to a separate federal agency, but Virginia VEC was able to put a note on my claim so the weeks I was waiting didn't count against my eligibility.

0 coins

The SSA database mismatch is a less common cause but it does happen and it's completely invisible to the claimant. Only an agent with access to the backend verification logs can spot it.

0 coins

My account showed a completed registration and I even got all the confirmation emails but still had no verification path. What finally unlocked it was my weekly certification date passing — the system apparently tried to send me my first weekly claim notice, failed because I wasn't verified, and that failure somehow triggered an alert on the backend that got my case looked at. Pure accident that it resolved at all.

0 coins

That is an incredibly roundabout way for the system to self-correct. I'd rather not wait for a random internal error to accidentally fix my account.

0 coins

Totally understandable. I don't recommend waiting for it — I just lucked out. If I'd known about other ways to escalate I would have done that from day one.

0 coins

The fact that a failed weekly claim notice can accidentally trigger a resolution tells you a lot about how reactive rather than proactive the system is built.

0 coins

The core problem here is documented enough that there are really only three paths that reliably work: phone with an agent, in-person at Virginia Works, or the message center as a slow fallback. The portal has no self-service fix for a broken verification path. Whichever route you can access fastest is the one to pursue — but don't sit and wait for it to fix itself.

0 coins

This thread has made it really clear that waiting and hoping isn't an option. I'm going to pursue the phone route as the most direct fix and use the message center as a backup in parallel.

0 coins

Parallel is smart — send the message center inquiry today while you're also working on reaching an agent by phone. That way if one takes days the other might come through faster.

0 coins

Agreed that parallel tracking is the right move. The worst outcome is waiting to try option 2 until option 1 has fully failed — by then you've lost more of that 30-day window.

0 coins

Had this issue and want to add one specific detail that helped me when I finally reached a VEC agent: I had the exact timestamp of when I created my account ready to tell them. They were able to pull up server logs from that time window and immediately see that my registration had errored out silently. Having that timestamp made the call much shorter.

0 coins

I actually do have that timestamp — I saved the registration confirmation email which has the exact time. Good to know that's useful data to have ready for the call.

0 coins

Perfect. Also note which browser and operating system you used if you remember. Some of the backend logs track that and it helps them confirm which registration session was yours if there were multiple at the same time.

0 coins

There's a lot of focus on the phone in this thread and rightfully so, but I want to mention that Virginia VEC also has a formal online help request form separate from the message center in CSS — it's linked from the main vec.virginia.gov site under 'Contact Us.' Submitting through that form sometimes routes to a different team than the general message center and I've seen faster responses reported from people who used it.

0 coins

I hadn't found that separate form. Looking at vec.virginia.gov now and I think I see what you're describing. I'll submit through that today as well.

0 coins

Yes, it's not super prominent on the page but it's there. Include your account username and registration date in the submission so they can pull up your record without having to ask follow-up questions.

0 coins

I tried that form once and got a response in about 4 business days. Not fast but faster than the message center in my case.

0 coins

My filing experience with the verification issue made me realize there's basically no fallback designed into the system for claimants when the portal breaks. The assumption seems to be that everyone can reach a phone agent quickly, which obviously isn't true. The message center and help form exist but they're built for routine questions, not for account emergencies where the clock is running.

0 coins

The underlying design problem is that identity verification was added as a mandatory gate with no manual bypass for the claimant, and the error handling if that gate fails to initialize is essentially nonexistent.

0 coins

Exactly. A good system would detect that verification initialization failed during registration and send an automatic recovery email or at minimum show the claimant a clear error with next steps. Instead it just silently doesn't generate the verification path.

0 coins

From a software design perspective this is a textbook example of building a critical dependency without proper error state handling. Common in legacy systems that have new requirements bolted on.

0 coins

Popping in here because my wife hit the exact same wall — no option to verify identity after creating account — and what finally cracked it for her was logging in and immediately clicking 'Complete Registration' from the welcome banner that appears the first time you sign in. That banner disappears after the first login session and apparently it's the only place that link lives. If you've already logged in once and dismissed it the link is gone from the UI.

0 coins

That banner is completely gone on my account — I clicked around without reading it closely on my first login. That might genuinely be what happened, the initial registration completion link was dismissed before I used it.

0 coins

If that's the case you're not getting it back through the portal. The link doesn't regenerate. This is exactly why you need an agent to manually reset the registration status so it can re-send that link or flag your account as verified on the backend.

0 coins

The disappearing welcome banner as the only hook for verification is honestly terrible UX. There's no indication it's time-sensitive or that dismissing it removes your only self-service path.

0 coins

After spending about four hours total across multiple days trying to reach Virginia VEC by phone with no luck, I finally got through on a Thursday morning around 8:05 — literally right when lines opened. The hold was still about 45 minutes but I got an agent. If you can call right at opening time on a Thursday or Friday those seem to be slightly lower volume than Monday through Wednesday in my experience.

0 coins

Thursday morning right at 8 AM is noted. I've been trying mid-morning on weekdays which is apparently the worst possible time.

0 coins

Mid-morning is brutal. Everyone who tried to call when they first woke up and got blocked has redialed by then and everyone on their lunch break is starting to try. Early open is your best shot.

0 coins

The first 10-15 minutes after the lines open are genuinely your best window. After that the queue fills fast and hold times climb quickly for the rest of the day.

0 coins

Virginia Unemployment AI

Expert Assistant
Secure