Can't reach Social Security Administration? Claimyr connects you to a live SSA agent in minutes.
Claimyr is a pay-as-you-go service. We do not charge a recurring subscription.
Using Claimyr will:
- Connect you to a human agent at the SSA
- Skip the long phone menu
- Call the correct department
- Redial until on hold
- Forward a call to your phone with reduced hold time
- Give you free callbacks if the SSA drops your call
If I could give 10 stars I would
If I could give 10 stars I would If I could give 10 stars I would Such an amazing service so needed during the times when EDD almost never picks up Claimyr gets me on the phone with EDD every time without fail faster. A much needed service without Claimyr I would have never received the payment I needed to support me during my postpartum recovery. Thank you so much Claimyr!
Really made a difference
Really made a difference, save me time and energy from going to a local office for making the call.
Worth not wasting your time calling for hours.
Was a bit nervous or untrusting at first, but my calls went thru. First time the wait was a bit long but their customer chat line on their page was helpful and put me at ease that I would receive my call. Today my call dropped because of EDD and Claimyr heard my concern on the same chat and another call was made within the hour.
An incredibly helpful service
An incredibly helpful service! Got me connected to a CA EDD agent without major hassle (outside of EDD's agents dropping calls – which Claimyr has free protection for). If you need to file a new claim and can't do it online, pay the $ to Claimyr to get the process started. Absolutely worth it!
Consistent,frustration free, quality Service.
Used this service a couple times now. Before I'd call 200 times in less than a weak frustrated as can be. But using claimyr with a couple hours of waiting i was on the line with an representative or on hold. Dropped a couple times but each reconnected not long after and was mission accomplished, thanks to Claimyr.
IT WORKS!! Not a scam!
I tried for weeks to get thru to EDD PFL program with no luck. I gave this a try thinking it may be a scam. OMG! It worked and They got thru within an hour and my claim is going to finally get paid!! I upgraded to the $60 call. Best $60 spent!
Ask the community...
- DO post questions about your issues.
- DO answer questions and support each other.
- DO post tips & tricks to help folks.
- DO NOT post call problems here - there is a support tab at the top for that :)
Join the conversation
Join the conversation
As a newcomer to this community, I have to say this thread has been absolutely eye-opening! I'm 64 and starting to think seriously about my Social Security timing, and like so many others here, I've been hearing that "January is best" mantra from friends and family without anyone being able to explain the actual reasoning. What's been most valuable about this discussion is seeing how context-dependent this advice really is. The breakdown of specific scenarios where January timing might actually benefit someone (earnings test considerations for people still working, complex family benefit coordination, tax planning preferences) versus situations where it's just unnecessary delay has been incredibly clarifying. I'm particularly struck by the real experiences shared here - @Natasha Romanova missing out on 4 months of benefits by following generic January advice, @Paolo Moretti's sister getting caught off guard by the payment delay, and @Darcy Moore's success with filing in June when it was convenient. These stories really drive home how individualized these decisions need to be. The technical explanations from members like @Keisha Jackson and @Paloma Clark have also been fantastic for understanding the actual mechanics behind the myths. It's clear that for someone planning to be fully retired at FRA with straightforward benefits (which describes my situation), the month I choose to file won't significantly impact my benefit amount - it's really about personal convenience and avoiding unnecessary delays in receiving payments I'm already entitled to. This community is such a great resource for cutting through retirement planning myths with real facts and experiences. Thanks to everyone who took the time to share their knowledge and stories!
As a newcomer to this community, I want to add my voice to thank everyone for this incredibly comprehensive discussion! I'm 65 and approaching my FRA next year, and like so many others here, I've been getting that persistent "January is best" advice from well-meaning relatives who couldn't provide any concrete reasoning behind it. This thread has been absolutely invaluable in dismantling what appears to be a widespread myth. What strikes me most is how this advice gets repeated with such confidence, yet when you dig into the actual mechanics (as everyone has done so thoroughly here), it only applies to very specific circumstances - mainly people still working who might hit earnings test limits, or those dealing with complex family benefit situations. The real-world experiences shared here have been particularly enlightening. @Paolo Moretti's story about his sister being blindsided by the payment delay, @Natasha Romanova's regret about missing 4 months of benefits, and @Darcy Moore's successful experience filing in June all demonstrate that there's no magic to January timing for most people at FRA who aren't working. I especially appreciate @Paloma Clark's insight about how this advice often comes from financial advisors thinking about portfolio management rather than actual Social Security optimization. That explains why I keep hearing it even though it doesn't seem to fit my situation! As someone planning to be fully retired with straightforward benefits, I now feel confident about filing when it makes sense for my personal timeline rather than waiting for some mythical "perfect" month. This community has been exactly what I needed to separate fact from fiction in retirement planning. Thanks to everyone for sharing such detailed knowledge and real experiences!
Join the conversation
I just experienced this same issue yesterday evening! Got the notification email around 6 PM saying I had new messages, but when I logged into my account there was absolutely nothing there. I was really starting to worry that maybe I was missing something important about my upcoming benefit verification or that there was a glitch preventing me from seeing critical messages. Reading through all these comments has been such a huge relief - especially the official confirmation from the IT specialist that this is just a known system bug affecting many people. It's so reassuring to know this isn't a security issue and that we don't need to report it. I was actually planning to drive to my local SSA office tomorrow to ask about it in person, but now I know I can just ignore these phantom emails until the fix comes through at the end of the month. Thanks to everyone for sharing their experiences - this community has been incredibly helpful for a newcomer like me trying to understand what's actually concerning versus what's just technical difficulties with government systems!
Welcome to the community! I'm also pretty new here and had this exact same experience just this morning - got the notification email around 11 AM and immediately panicked thinking I'd missed something critical about my disability benefits. When I logged in and found nothing there, I was convinced something was seriously wrong with my account. This thread has been such a blessing! The official explanation from the IT specialist really helped me understand that this is just a temporary technical glitch affecting lots of us, not a security issue or something we need to stress about. It's so frustrating when these government systems malfunction, but at least we have this amazing community to help us figure out what's actually worth worrying about. Thanks for sharing your story - it definitely helps knowing we're all dealing with these same phantom notifications together!
I just got one of these phantom notification emails this morning too! As someone new to navigating the SSA system, I was really concerned when I logged in and found nothing in my message center. This thread has been incredibly helpful - especially the official confirmation from the IT specialist that it's just a widespread system glitch. I was actually getting ready to call the SSA helpline and deal with those notorious wait times, but now I know I can just ignore these emails until the fix is deployed at the end of the month. It's so reassuring to have a community like this where we can share experiences and help each other understand what's normal versus what actually needs our attention. Thanks to everyone for posting their stories - it really helps newcomers like me feel less anxious about these confusing government system issues!
Join the conversation
I work at a local SSA field office and see this confusion literally every day in January! What most people don't realize is that the COLA notice you receive in December is generated by one system that only knows about your Social Security benefit amount, while Medicare premiums are handled by a completely different system. When your actual payment gets processed, that's when all the deductions finally get applied together. It's definitely confusing and I wish the notices were clearer. If you want to avoid this surprise next year, you can request a COLA notice that shows estimated net amounts, but you have to specifically ask for it. Most people just get the standard gross amount notice. The good news is your online account should update with the detailed breakdown by the end of this month showing exactly what was deducted and why.
@f9baafdacf87 This is so valuable to hear from someone who works at SSA! I'm the original poster and this whole thread has been such a learning experience. I really wish I had known about the option to request a net amount COLA notice - that would have prevented all this confusion. When you say people need to "specifically ask for it," do you mean during a phone call to the 1-800 number, or is there a way to request it online? And is this something I should do right after I get my annual COLA notice, or should I request it earlier in the year? I want to make sure I'm prepared for next year's COLA so I don't go through this stress again. Thank you for taking the time to help educate us about how the system actually works behind the scenes!
@f9baafdacf87 Thank you so much for this insider perspective! As someone new to Social Security (just started receiving benefits last year), this explanation is incredibly helpful. I had the same panic as the original poster when my January deposit didn't match my COLA letter. Could you clarify how far in advance we can request that net amount COLA notice? I'd love to be proactive about this for next year. Also, is there any way to get a mid-year estimate if our Medicare premiums change during the year, or do we just have to wait and see what happens to our deposit? I'm trying to understand the system better so I can budget more accurately. Really appreciate you taking the time to educate us!
I'm so glad I found this thread! I'm relatively new to receiving Social Security benefits (started about 6 months ago) and this whole COLA/deduction process is really confusing for newcomers like me. Reading through everyone's experiences has been incredibly educational. It sounds like the key takeaway is that the COLA letter shows your gross benefit increase, but your actual deposit will be different due to various deductions like Medicare premiums, possible IRMAA surcharges, and tax withholding. What I'm still unclear about is the timing of when these deductions start or change. For instance, if my Medicare Advantage plan premium changes mid-year, does that immediately affect my Social Security deposit the following month, or do these changes only happen in January? Also, is there a way to get advance notice of ALL potential deductions in one place, rather than having to piece together information from multiple letters from different agencies? Thanks to everyone who's shared their knowledge - it's really helping those of us who are still learning to navigate this system!
@3a48add83475 Welcome to the Social Security world! Your questions are really good ones that I wish I had asked when I first started receiving benefits. From what I've learned through this thread and my own experience, Medicare changes typically take effect at the beginning of the plan year (January), but there can be exceptions for special enrollment periods or certain life changes. For advance notice of all deductions, unfortunately there isn't one consolidated letter - you'll get separate notices from SSA for your COLA, from Medicare for premium changes, and potentially from your Medicare Advantage or Part D plan. The key is to save all these letters and do the math yourself like @8125b180eaca suggested with the spreadsheet method. I'm still learning too, but this community has been incredibly helpful! @f9baafdacf87 might be able to give you more specific details about timing since they work at SSA.
Join the conversation
I went through this exact situation with MetLife about 8 months ago - $63k overpayment after my SSDI approval. Here's what worked for me: 1. **Get the itemized statement FIRST** - This saved me about $8k because they had incorrectly included two months where my LTD was suspended due to a return-to-work attempt. 2. **Call the "Recovery Solutions" or "Overpayment Recovery" department directly** - Don't waste time with general customer service. Ask to be transferred to whoever handles "SSDI offset settlements" specifically. 3. **Have your settlement offer ready** - I offered 60% of the corrected amount ($33k instead of $55k after corrections) and emphasized immediate wire transfer capability. They countered at 75%, we settled at 68%. 4. **Timing matters** - I initiated contact about 3 weeks after getting my overpayment notice. Sweet spot where they know you have the SSDI funds but haven't assumed you've spent them yet. The rep told me they actually prefer lump sum settlements because it eliminates collection costs and risk of non-payment. The whole process took about 5 weeks from first call to final wire transfer. One critical detail: Make sure the settlement letter explicitly states this resolves the overpayment completely and doesn't affect future eligibility for different claims. Mine tried to sneak in broader language that could have impacted future coverage. Happy to answer any specific questions about the process!
This is extremely helpful - thank you for the detailed breakdown! Your point about calling the "Recovery Solutions" department specifically is something I hadn't thought of. I've been dreading making that first call, but knowing they actually prefer lump sum settlements makes me feel much more confident about approaching this as a normal business transaction rather than begging for mercy. The 3-week timing you mentioned also makes sense - gives them time to process everything but doesn't let too much time pass. I'm definitely going to use your approach as a template. Did they ask for any documentation of financial hardship, or was the offer of immediate payment sufficient justification for the discount?
I'm new to this situation but reading through everyone's experiences has been incredibly reassuring - thank you all for sharing such detailed advice! I just received notice of a $41k LTD overpayment following my SSDI approval two weeks ago. Before finding this thread, I was feeling completely overwhelmed and thought I had no choice but to accept their payment plan. Based on what I've learned here, my plan is to: 1. Request the itemized statement first to verify their calculations 2. Wait about another week (to hit that 3-week sweet spot mentioned) 3. Contact their Recovery Solutions department directly with a lump sum settlement offer One question I haven't seen addressed: Should I mention that I'm considering legal consultation during the negotiation, or would that potentially backfire and make them less willing to work with me? I want to convey that I'm serious about resolving this properly, but I don't want to come across as threatening if that might hurt my chances of getting a reasonable settlement. Also, for those who successfully negotiated - did you find it helpful to have specific talking points written down before making the call, or did you keep it more conversational?
Great plan! I'd avoid mentioning legal consultation during the initial negotiation - it can make them more defensive and formal when you want to keep things collaborative. The representatives dealing with settlements do this regularly and know it's standard business practice. If you hit roadblocks later, you can always escalate, but starting with a cooperative tone tends to work better. Definitely have talking points written down! I made notes covering: 1) immediate payment capability, 2) why lump sum benefits them (no collection costs/risks), 3) any ongoing financial constraints from your disability, and 4) your specific settlement offer with justification. Having it written helped me stay focused and confident during the call. The key is presenting it as a mutually beneficial business arrangement rather than a request for charity. You've got this!
Isaiah Thompson
Just joined this community after stumbling across this thread while desperately searching for help with my own SSA/Login.gov authentication disaster! I've been stuck in the same endless loop for about 10 days now and was starting to think there was something seriously wrong with my computer or internet connection. Reading through everyone's detailed solutions here has been such a relief - it's clear this is a widespread system integration problem affecting tons of people, not just me going crazy! The email consistency issue that @Anna Xian discovered is absolutely brilliant - I just had an "aha!" moment realizing I probably used slight variations of my email address when setting up my accounts (maybe with/without dots in my Gmail, or different capitalization). I'm definitely going to try the complete sign-out + clear all browsing data + Firefox browser method this evening, making sure my email formatting is absolutely identical across both platforms. It's honestly ridiculous that we need this level of community detective work just to check our own Social Security information, but I'm incredibly grateful everyone here has shared their troubleshooting victories and failures so openly. This thread has become the unofficial tech support guide that SSA should have provided from day one. Thank you all for creating such an invaluable resource - will definitely report back with my results and hopefully add another success story to help future community members dealing with this authentication nightmare!
0 coins
Melody Miles
•Welcome to the community, Isaiah! I just joined recently too and this thread has been absolutely incredible for understanding this widespread SSA/Login.gov mess. It's so reassuring to know we're not alone in dealing with these authentication nightmares - clearly shows this is a major system integration failure rather than user error on our part. That email consistency discovery by @Anna Xian really is pure genius - I bet that small formatting issue catches way more people than anyone realizes. I m'also planning to try the complete browser clearing + Firefox method based on all the success stories shared here. The collaborative troubleshooting in this community has honestly been more helpful than anything I could find through official channels. It s'frustrating that we basically need computer science degrees just to access our own benefits, but at least we re'all figuring it out together! Good luck with your attempts tonight - definitely keep us updated on what works. This shared knowledge base keeps getting stronger with each person s'experience!
0 coins
Jackson Carter
Just joined this community after being stuck in this exact same SSA/Login.gov authentication loop for over two weeks! This thread has been like finding a treasure chest of solutions - I can't believe how many people are dealing with this same nightmare. The email consistency breakthrough that @Anna Xian discovered is absolutely mind-blowing. I just realized I definitely used different variations of my email when setting up my accounts (probably my.name@gmail vs myname@gmail). It's insane that such tiny differences can completely break the integration between two government systems that are supposed to work seamlessly together. I'm going to try the complete sign-out + clear all browser data + Firefox method tonight, making sure my email addresses match perfectly on both platforms. If that doesn't work, I'll definitely check out the Claimyr service that @Ev Luca mentioned since I've had zero luck with the phone lines. It's honestly both frustrating and comforting to see this is such a widespread issue - clearly shows this is a systemic problem with their integration, not us users doing something wrong. Thank you all for sharing your experiences and creating this incredible troubleshooting resource. This community support is infinitely better than the useless official help documentation!
0 coins
Liv Park
•Hey Jackson! Welcome to the community - I just joined recently myself after dealing with similar government website frustrations. This thread really has become an amazing resource for solving this widespread SSA/Login.gov integration disaster! That email consistency tip from @Anna Xian is such a brilliant discovery - I never would have thought those tiny formatting variations could cause such major authentication failures. The Gmail with/without periods issue is probably tripping up thousands of people who have no idea that s'the source of their login nightmare. I m'also planning to try the complete browser clearing + Firefox method based on everyone s'success stories here. It s'really encouraging to see how this community has basically created the troubleshooting guide that SSA should have provided from the start. Good luck with your attempts tonight - definitely keep us posted on your results! The collaborative problem-solving here has been so much more effective than any official support channels I ve'tried.
0 coins