Notifications
Clear all

just saw a story about a guy in Kansas whose car got totaled by hail, and turns out his insurance didn't cover it.

1,055 Posts
900 Users
0 Reactions
26.3 K Views
dennis_fox2493
Posts: 19
(@dennis_fox2493)
Eminent Member
Joined:

Yeah, I’ve always thought “comprehensive” was a weird name for what it actually covers. Like you said, it’s not the catch-all people assume.

“He thought ‘full coverage’ meant everything. Spoiler: It didn’t.”
That’s the trap—insurance lingo is designed to confuse. I’m all for saving money, but skipping comprehensive if you park outside is just rolling the dice. I’d rather pay a bit more than get stuck with a totaled car and zero payout. The fine print is where they get you every time.


Reply
Posts: 15
(@nala_star)
Active Member
Joined:

That’s the trap—insurance lingo is designed to confuse.

Honestly, I’ve read through my policy a few times and still find parts of it confusing. “Comprehensive” sounds like it should cover everything, but then you realize it’s just for stuff like hail, theft, or vandalism—not collisions. I get wanting to save money, but if your car’s outside most of the time, skipping it feels risky. I had a neighbor lose his windshield to a falling branch and he was out of luck because he thought “full coverage” meant exactly that. The wording really does trip people up.


Reply
wafflesmartin504
Posts: 9
(@wafflesmartin504)
Active Member
Joined:

Yeah, the whole “full coverage” thing is super misleading. I’ve had to explain to friends that it doesn’t mean what they think. Ever had to file a claim for something weird, like a tree branch or hail? Curious how that process went for you.


Reply
john_wood
Posts: 2
(@john_wood)
New Member
Joined:

Yeah, the whole “full coverage” thing is super misleading. I’ve had to explain to friends that it doesn’t mean what they think.

That’s spot on—“full coverage” really just means whatever your policy says, not literally everything. I actually had a claim a few years back when a neighbor’s tree branch fell on my car during a storm. The process was smoother than I expected, but only because I had comprehensive coverage. Without that, I’d have been out of luck. It’s frustrating how easy it is to assume you’re protected from stuff like hail or falling branches when sometimes you’re not. Insurance language could be way clearer, honestly.


Reply
Posts: 15
(@blogger17)
Active Member
Joined:

Yeah, I hear this all the time—people think “full coverage” is some magic shield. Like you said, it’s just whatever mix of coverages you picked when you signed up. I can’t count how many times I’ve seen folks surprised after a hailstorm or a tree branch incident because they didn’t actually have comprehensive.

It’s frustrating how easy it is to assume you’re protected from stuff like hail or falling branches when sometimes you’re not.

Honestly, the term “full coverage” should probably be retired at this point. It just sets people up for disappointment. It’d be way clearer if policies just listed out what’s covered in plain language—like, “Hey, this covers hail, but not your engine blowing up.” But then again, insurance companies seem to love their jargon...

I do wonder if some agents are partly to blame for not explaining it better during sign-up? Or maybe people just tune out once they hear the price. Either way, it’s a mess when you only find out what isn’t covered after something bad happens.


Reply
Page 211 / 211
Share:
Scroll to Top