


Ask the community...
This thread has been so helpful! I'm dealing with a similar intercept situation right now and was panicking thinking I'd done something wrong. Reading through everyone's experiences and the detailed explanations about what can cause intercepts has really calmed my nerves. It's frustrating that the system doesn't provide clearer upfront communication about these deductions, but at least now I know it's probably some forgotten debt rather than a mistake on my part. I'm going to try the secure messaging approach through eServices first, and if that doesn't work quickly enough, I might look into that Claimyr service someone mentioned. Thanks to everyone who shared their experiences and advice - this community is a lifesaver for navigating the ESD maze!
I'm so glad this thread helped ease your worries! I was in the exact same boat when I first saw that intercept on my payment - immediately thought I'd messed up somehow or that ESD had made an error. It's really reassuring to know that these intercepts are usually just old forgotten debts rather than anything serious. The secure messaging through eServices is definitely worth trying first since it leaves a paper trail of your inquiry. And don't feel bad about potentially using Claimyr if you need faster answers - sometimes you just need to talk to a real person to get things sorted out quickly. Hope you get your intercept mystery solved soon! Keep us updated on what you find out.
I'm new to unemployment benefits and just got my first payment, but I'm seeing a small "intercept" deduction too. Reading through this thread has been incredibly helpful - I had no idea there were so many different types of old debts that could cause this! I'm definitely going to check the Department of Revenue website first since it sounds like vehicle registration fees and tax issues are pretty common causes. It's kind of scary how easy it is to forget about these small government fees over the years, especially if you've moved around. Thanks to everyone who shared their experiences and the specific resources to check - this community is amazing for helping navigate these confusing situations!
Bottom line - file your claim, be honest about the circumstances, provide documentation of your illnesses if you have it, and don't let your former employer intimidate you into thinking you don't deserve benefits. Being sick isn't misconduct.
I went through something very similar about 6 months ago. Got fired for "excessive absences" when I had to miss work for a kidney stone, stomach flu, and my kid's emergency surgery. I was terrified I wouldn't qualify for unemployment, but Washington ESD approved my claim after about 2 weeks of review. The key things that helped my case were: 1) I had called in properly each time, 2) I kept text messages showing I notified my supervisor, and 3) I had some medical documentation. Even though I didn't have doctor's notes for everything, the fact that my absences were legitimate medical issues and I followed company protocol made all the difference. File your claim right away and don't worry - genuine illness absences are NOT considered misconduct in Washington state.
This is really helpful to hear from someone who went through the exact same situation! Your case sounds even more complicated than mine with multiple different types of absences, so if you got approved then I'm feeling much more confident about my chances. The part about keeping text messages is smart - I definitely have those conversations with my manager saved. Thanks for sharing your experience, it's exactly what I needed to hear right now.
UPDATE: I used Claimyr to get through to ESD this morning, and they fixed my account! The agent said my old account was in a 'dormant' status that was causing the login loop. They had to manually reactivate it on their end. For anyone else facing this issue - definitely try to speak with someone directly rather than just keep resetting your password. Thanks everyone for your help!
Great to hear! Make sure you file your initial claim right away since benefits are calculated from when you file, not from your last day of work. And don't forget to do your job search activities starting week one!
So glad you got it sorted out! I've been dealing with a similar issue for the past week and was getting really frustrated. Your post actually convinced me to try Claimyr - I just signed up and hopefully will get through to someone tomorrow. It's ridiculous that we have to use a third-party service just to talk to our own state unemployment office, but at this point I'll take whatever works. Thanks for sharing your solution and glad you can finally get your claim filed!
I went through this exact situation last summer when I visited family in Oregon for 10 days. Here's what worked for me: I continued filing my weekly claims but marked myself as unavailable for the specific dates I was gone. The key is being very precise - I wrote in the comments section exactly which dates I was traveling and unavailable for work. I didn't receive benefits for those weeks, but my claim stayed active and I had zero issues when I returned. One tip that really helped: I actually did some online job applications from my phone during the trip for the days I was marked as "available" (like the travel days before/after). This way I could honestly say I was job searching even while away. Just make sure you're not claiming you're available for work on days when you clearly couldn't accept a job if offered. The system is pretty forgiving if you're honest, but they come down hard on any perceived fraud.
This is really helpful to hear from someone who's been through the exact same situation! I like your approach of being very specific in the comments section about travel dates - that seems like it would help avoid any confusion later. The tip about doing some job applications during travel days when you're still marked as available is smart too. I'm definitely going to follow your example and be super precise about which days I'm unavailable versus which days I could theoretically accept work. Thanks for sharing your experience!
Just want to echo what others have said about being completely honest - I made the mistake of marking myself as "available" during a weekend trip to Portland last year thinking it would be fine since it was just 3 days. Big mistake! ESD caught it during a routine audit (they can see when your phone pings different cell towers) and I had to go through a whole fraud investigation process. Nothing came of it since it was clearly just a misunderstanding, but it was super stressful and delayed my benefits for weeks while they sorted it out. For your Arizona trip, definitely file your claims but mark yourself unavailable for the exact dates you'll be gone. Keep all your travel receipts and boarding passes just in case. The temporary loss of benefits is way better than dealing with potential fraud issues later. Have a great trip!
Wow, that's really scary that they can track cell tower pings! I had no idea ESD was that thorough with their audits. Thank you for sharing this - it really drives home how important it is to be completely honest about availability. I'm definitely going to mark myself as unavailable for the exact dates I'm in Arizona, and I'll make sure to save all my travel documentation. The last thing I want is to deal with a fraud investigation over a vacation. I really appreciate you taking the time to warn others about this!
Laura Lopez
I filed late by about 6 hours last month (submitted Monday morning instead of Sunday night) and my payment came through on Thursday instead of the usual Tuesday. It was definitely stressful waiting those extra days, but Washington ESD processed it normally. The key thing that helped me was logging into SecureAccess Washington the next day to check my claim status - it showed "processed" so I knew it went through okay. One thing I learned is to file your claim as early as possible during the week (like Saturday) rather than waiting until the last minute on Sunday. That way if something comes up you still have buffer time.
0 coins
Isabella Martin
•That's really helpful advice about filing earlier in the week! I never thought about doing it Saturday instead of waiting until Sunday. The buffer time makes total sense - life happens and it's better to be safe than sorry. I'm definitely going to start filing my weekly claims on Saturday mornings from now on. Thanks for the tip about checking SecureAccess Washington too - I didn't realize you could see the processing status there. That would have saved me a lot of anxiety if I had known to check that right away.
0 coins
Sean Flanagan
I was in almost the exact same situation a few weeks ago - filed about 20 hours late because I completely forgot over the weekend. I was panicking thinking I'd lose my benefits, but it turned out fine. My payment was delayed by about 3 days (normally get it Tuesday, came Friday that week) but the full amount came through. The Washington ESD system accepted my late filing without any issues. Just make sure you keep up with your job search activities for that week since they can audit those anytime. Set some phone reminders for Saturday/Sunday going forward so you don't have to go through this stress again! You should be okay, just prepare for a few extra days of waiting for your payment.
0 coins