Back to Arizona Unemployment

Royal_GM_Mark

Arizona DES verify phone line disconnects after long hold - anyone else?

So I've been trying to get my identity verified through the Arizona DES phone line for going on two weeks now and every single time I finally get to what feels like the front of the queue, the line just cuts out. Dead silence, then dial tone. I'm not talking about getting hung up on early - I mean sitting there for sometimes 45, 50 minutes only for the call to drop right when it seems like someone might actually pick up. My claim has been sitting in adjudication the entire time because I can't complete the verification step. The CACTUS portal shows my identity verification is still pending and there's literally no way to resolve it without speaking to someone. I work part-time mornings so I've been calling on my lunch breaks and after shifts, tried early mornings too - same result every single time. The disconnect happens around the same point in the hold music cycle which makes me think it's some kind of automated timeout. Anyone else dealing with this? Is there a specific time of day that's actually worked for getting through? My weekly claims are still going through but I know eventually the adjudication hold is going to catch up and freeze everything if I can't get this identity piece sorted.

Two weeks of dropped calls on the DES verify line is brutal - I went through the exact same thing trying to get my identity confirmed back in March. After about the fifth time getting disconnected at the 40-minute mark I finally tried Claimyr. It's a service that essentially holds your place in the Arizona DES phone queue and calls you back when an agent is actually ready to pick up - so you're not sitting there waiting for the line to drop. Used it at claimyr.com and there's a video demo showing how it works at https://youtu.be/vwA1GGuV83Y. Got connected to a DES agent within a couple hours and had my identity verification sorted same day. The adjudication hold cleared about 3 days later.

0 coins

The 40-minute drop thing is real, I've read about it in a few places. The DES phone system has some kind of session timeout built into the hold queue. Good to know there's a workaround - been considering trying that service myself.

0 coins

Claimyr is something I hadn't heard of before. Does it work specifically for the identity verification line or is it for the general DES number? Because I've seen people say the verify line is a different queue than regular claims.

0 coins

The number I used was the main Arizona DES claims line and I told the agent I needed identity verification - they were able to handle it directly. Didn't need a separate line. The key was just actually getting a human on the phone which the callback system made possible.

0 coins

The timeout you're describing sounds like it kicks in somewhere between 35 and 55 minutes depending on call volume that day. What helped a friend of mine was using Claimyr - she'd been getting disconnected repeatedly trying to resolve her adjudication status and the callback feature meant she stopped burning through hold time just to get dropped. She said the agent she reached was able to pull up her verification status immediately once she explained the situation. Worth checking out claimyr.com if the direct line keeps failing you.

0 coins

35 to 55 minutes tracks with what I experienced. I started setting a timer after my third dropped call and mine consistently cut out somewhere in that window. The timeout theory makes a lot of sense.

0 coins

Does Arizona DES have any way to verify online instead? I feel like making people call a line that just disconnects them is insane for something as important as identity verification blocking a whole claim.

0 coins

Online verification through ID.me exists but a lot of people run into issues with it not matching their records correctly, which is exactly what forces them onto the phone line in the first place. It's kind of a catch-22 situation with the verify process.

0 coins

My identity verification got stuck for almost a month and during that time I found out about Claimyr through a different forum thread. Used it to reach a DES agent who confirmed my ID.me submission had actually gone through but wasn't syncing to my CACTUS account correctly - a backend issue they fixed manually while I was on the call. The direct line had dropped me four times before that. If you're at the point where your weekly claims are still going but adjudication is looming, getting that verification call completed sooner is way better than waiting until the freeze actually hits.

0 coins

A backend sync issue is something I hadn't even considered - I assumed if ID.me verified me it would automatically update CACTUS. So those two systems don't always talk to each other properly?

0 coins

From what the agent told me, they're supposed to sync but there's a manual review step that can get stuck, especially during high-volume periods. The only way to catch it is by speaking to someone who can actually see both systems.

0 coins

This happened to my brother too. His ID.me showed verified but DES still had him in pending for verification. Took an actual phone call to get it resolved. The systems are just not well integrated.

0 coins

First thing I'd try is calling right when the phone lines open at 7:30am. The hold times are shortest in that first 20-minute window and you're less likely to hit the timeout before an agent picks up. The DES verify line gets absolutely slammed after 9am and that's when the queue backs up long enough for the timeout to trigger. I've gotten through in under 15 minutes calling at 7:31 versus never getting through calling after 10.

0 coins

7:31am is exactly the approach my coworker used after weeks of failed attempts. She said the same thing - before 8am the wait was manageable, after that it became a gamble.

0 coins

Mornings are tough for me because of my part-time shift but maybe I can call the moment my shift ends, which would put me around 8am depending on the day. That's earlier than I've been trying.

0 coins

8am might still work depending on that day's volume. Mondays and Tuesdays after holidays are the worst. Mid-week at opening is probably your best shot with a morning shift constraint.

0 coins

Something nobody's mentioned yet is that the DES verify line and the main UI claims line actually merge at a certain point in the phone tree. If you go through the main claims number and select the identity verification option from the menu, you sometimes get routed to a shorter queue than calling the dedicated verify number directly. Sounds counterintuitive but I've heard multiple people say the main number got them through faster.

0 coins

The phone tree merging is real. I stumbled onto this accidentally when I misdialed and ended up getting to an agent faster than I ever had calling the specific verify line. Might just be luck but it's worth trying both.

0 coins

Speaking of different routing options - I had luck with Claimyr specifically because it navigates the phone tree automatically and routes to the right queue without you having to sit through the menu options. The whole callback system means you skip the timeout risk entirely since you're not actually holding. Ended up being the fastest resolution I found after trying every other approach including the main line trick.

0 coins

That callback approach makes sense for avoiding the timeout issue specifically. The phone tree trick I mentioned is more about queue length than timeout risk - two different problems with the same call attempt.

0 coins

BEEN DEALING WITH THIS FOR THREE WEEKS AND NOBODY AT DES SEEMS TO CARE. My claim is completely frozen because of the identity verification hold and I cannot get through no matter what I try. Called 11 times. ELEVEN. Every single one dropped or I got a busy signal before even entering the queue. My bills are not going to pause while DES figures out their phone system.

0 coins

11 calls is exhausting and I completely understand the frustration. The phone system really does fail people at the worst possible times. Have you been continuing to file your weekly claims while the adjudication hold is in place? It's important to keep filing even if payments aren't releasing so you don't lose those weeks.

0 coins

Yes I've been filing every week because I read that you lose the weeks permanently if you don't file even during a hold. So those are piling up unfunded while I sit here unable to get through the verify line.

0 coins

Filing consistently is the right call. When the verification finally clears, all those held weeks should release together. It's a painful wait but keeping that filing history intact means you don't lose out on the backpay.

0 coins

My coworker told me the timeout issue is intentional and DES does it to manage their system load - like they'd rather drop calls than have an overloaded queue crash entirely. I have no idea if that's actually true but it would explain why it happens at such a consistent point in the hold cycle. Either way it's a terrible design for people trying to do something as critical as identity verification.

0 coins

Whether it's intentional or accidental the effect is the same - people needing to verify their identity for their unemployment claims can't get through. The reason behind it doesn't really change the problem.

0 coins

The consistent timing does suggest something systematic rather than random. Random system failures would drop calls at unpredictable points but OP said theirs always cuts out at roughly the same place in the hold music. That's a parameter set somewhere in the system.

0 coins

Exactly what I thought. Random failures are random. When everyone reports the same 40-50 minute drop window, that's a threshold someone programmed.

0 coins

For the CACTUS portal showing identity verification pending - there's actually a way to check whether your ID.me submission was received on the DES end specifically. Log into your CACTUS account and look under the correspondence section, not just the main dashboard. Sometimes a notice gets generated there that tells you exactly what the hold is for and occasionally gives an alternative resolution path. It's not always present but worth checking before your next call attempt.

0 coins

Correspondence section is somewhere I hadn't checked - I've only been looking at the main status screen. Going to look right now. If there's a notice there that explains the specific hold type it might at least tell me whether this is an ID.me sync issue or something else.

0 coins

The notice, if it's there, usually says something like 'identity verification required - additional documentation may be needed' and sometimes lists a document upload option as an alternative to the phone call. Not guaranteed but it's shown up for people in similar situations.

0 coins

Didn't know about the correspondence section having different info than the dashboard. That's actually useful. My sister had a pending verification notice for weeks and I wonder now if there was something in her correspondence section we never checked.

0 coins

just had this happen today actually. 48 minutes on hold then dead line. called back and got a busy signal three times in a row before i could even get back into queue. its like the whole system is designed to wear you down until you give up on your claim

0 coins

48 minutes then dead line - that's the exact pattern OP described. The getting a busy signal immediately after a drop is its own special frustration because you can't even get back in queue while the call is fresh.

0 coins

yeah by the time i could get back into queue it was like starting over completely with no memory of having been there before. 48 minutes of waiting just completely erased.

0 coins

The queue having no memory of previous attempts is a real flaw. Other states have callback systems built into their actual UI phone lines so you don't lose your place. Arizona DES doesn't have that natively which is why third party solutions end up filling the gap.

0 coins

Something that sometimes helps with the timeout issue is calling from a landline if you have access to one. Mobile connections can drop or weaken during long holds in a way that contributes to disconnects that might look like the DES line cutting you off. I know most people don't have landlines anymore but if a family member or workplace has one it's worth trying once just to rule out whether your connection is part of the problem.

0 coins

Landline access is actually something I could potentially arrange through my workplace. I hadn't considered that my mobile signal might be a variable. Though other people in this thread seem to have the same experience so it might not be the whole story.

0 coins

Mobile signal being a variable doesn't mean that's the only cause - plenty of people drop on what should be solid connections. But ruling it out is easy if you can get access to a landline so worth one test at least.

0 coins

Tried calling from my home wifi calling and still got dropped at the same point. So for me at least it wasn't a signal strength issue since wifi calling is essentially internet-routed.

0 coins

The identity verification process through DES has gotten way more complicated since they updated their system last year. Before the update, a lot of verifications were handled automatically without needing a call. Now more of them get flagged for manual review which floods the verify line with people who would have been auto-approved previously. The phone line was never designed for this volume which is why the timeout problem exists now when it wasn't as bad before.

0 coins

That context explains a lot. If the manual review threshold changed and suddenly three times as many people need to call, a system that worked fine before would immediately become overwhelmed. The timeout is probably the same as it always was but now the queues are long enough that people actually hit it.

0 coins

Knowing why it's broken doesn't fix the fact that my claim is frozen. But at least it's not like I'm doing something wrong - the system is just overwhelmed and dropping everyone.

0 coins

Definitely not anything you're doing wrong. The DES verify line is genuinely overloaded and the experience you're describing - multiple drops after long holds - is happening to a large number of claimants right now.

0 coins

For what it's worth, when I finally did get through to a DES agent about my identity verification hold, the call itself only took about 8 minutes to resolve. They pulled up my record, confirmed my ID.me data matched, did something on their end, and told me the adjudication hold would clear within 72 hours. It actually did clear in about 48 hours. So the call you need is not a long complicated one - the whole problem is just surviving the hold to get a human on the line.

0 coins

8 minutes to resolve after two weeks of trying to get through - that's both reassuring and infuriating at the same time. At least once I do reach someone it shouldn't be a lengthy complicated conversation.

0 coins

Exactly. When you finally get through, have your Social Security number, your CACTUS account number, and your ID.me confirmation email handy. The agent will ask for those and having them ready speeds things up even more.

0 coins

CACTUS account number and ID.me confirmation email - good call flagging those specifically. Having everything ready when you finally reach an agent means you don't waste any of that hard-won phone time hunting through emails.

0 coins

The weekly claim filing question is important here - even with an identity verification hold in place on your adjudication, you absolutely need to keep filing your weekly certifications on time. If you miss a week assuming you can't file because of the hold, those weeks don't come back. The hold affects payment release, not your ability to certify. File every week no matter what your claim status shows.

0 coins

Filing through the hold period is something I wish someone had told me earlier in my own adjudication situation. I missed two weeks thinking I couldn't certify while pending and lost those weeks entirely. Don't make that mistake.

0 coins

Losing weeks because you thought you couldn't certify during a hold is unfortunately common. The CACTUS portal lets you certify regardless of adjudication status - the hold only blocks payment, not filing.

0 coins

This is worth repeating clearly: identity verification hold does not prevent you from filing weekly certifications. File every week. Payment releases retroactively when the hold clears.

0 coins

Has anyone tried submitting a written inquiry through the CACTUS portal messaging system while also working on the phone approach? I'm wondering if getting something documented in writing speeds up the resolution at all or if agents can even see those messages when they pull up your account.

0 coins

Agents can see the portal messages when they pull your account - I confirmed this when speaking to one. Whether it speeds things up is less clear. What I'd say is that having a paper trail of your attempts documented in writing can't hurt, especially if you later need to appeal anything or explain a delay in your verification timeline.

0 coins

Having attempts documented is a good reason even if it doesn't speed things up. I'll start sending messages through the portal just to create that record alongside my call attempts.

0 coins

Portal messages are visible but agents tend to work from the queue in front of them rather than proactively resolving written inquiries. Good for documentation, less reliable as a primary resolution path for something time-sensitive like identity verification.

0 coins

One thing that caught my attention in this thread - several people are assuming the CACTUS dashboard and what an agent sees are identical. They're not. Agents have access to backend notes, verification flags, and system status indicators that never appear in the claimant-facing portal. So your dashboard showing 'identity verification pending' tells you there's a hold but doesn't tell you WHY it's held or what specifically needs to happen to clear it. That information only comes from actually speaking to an agent.

0 coins

Backend notes not visible to me through CACTUS is exactly the kind of thing that would explain why my dashboard shows the same generic status no matter what. There could be a specific flag or note on my account that would tell me exactly what's needed and I'd have no way to see it.

0 coins

Exactly the situation. Generic portal status is designed for the most common case. When your situation involves a flag or note beyond the standard workflow, the portal just shows the holding status without any of the detail that an agent can actually see and act on.

0 coins

This is why the 8-minute resolution call I described was possible - the agent could see immediately what the specific issue was and what needed to happen. Without that backend view, you're just waiting for something you can't diagnose.

0 coins

My approach after getting dropped twice was to try calling immediately when I hit a lull in what I was doing rather than scheduling specific call times. The DES phone volume fluctuates throughout the day and sometimes a mid-afternoon window opens up that isn't predictable. I ended up getting through on a random Tuesday around 2:15pm after failing every morning attempt. No scientific basis for it but anecdotally the mid-afternoon slot worked when structured timing didn't.

0 coins

Random Tuesday at 2:15pm is not the kind of advice you can really act on consistently but it does illustrate that volume fluctuates more than people think. I've read that after lunch breaks when agents return from lunch there can be a brief window too.

0 coins

After-lunch window around 1pm to 1:30pm is another one people mention. Neither is guaranteed but trying multiple different time slots across different days covers more chances than calling at the same time every day.

0 coins

To summarize what this thread has covered for anyone finding it in a search: the DES verify line timeout appears to cut calls at around 35-55 minutes in the hold queue; calling at 7:30am opening is the best direct-dial approach; checking your CACTUS correspondence section may reveal a document upload alternative; keeping weekly certifications filed during any hold is essential; and the actual verification call takes under 10 minutes once you reach an agent - the problem is entirely about surviving the hold. Hope this helps whoever is reading this later.

0 coins

Summarizing everything into one place is genuinely useful - this thread wandered productively but having a clean summary helps. My plan based on all of this: check correspondence section tonight, try to arrange a landline or early morning call this week, and keep filing my weekly certifications without interruption.

0 coins

That plan covers all the bases. Good luck - the resolution itself really is straightforward once you reach someone. The fight is getting there.

0 coins

Bookmarking this thread. The timeout range and the 7:30am tip especially are things I'll remember for my own situation if I ever hit a verify hold again.

0 coins

Arizona Unemployment AI

Expert Assistant
Secure