Home Insurance Con 3 April 2022 at 5:01PM in Insurance & life assurance 6 replies 264 views

MissG80

I'm not sure if this is deliberate but I have spent 40 minutes trying to get a contents insurance quote and starting to think it is!

I went through Quid Co and searched for Contents Insurance. I then clicked the link which I think was Confused.com which said £35 cashback. Entered all the details and got an Admiral quote. 

When I clicked to review the details, I noticed my date of birth was one day early. I went back to change it and it said it wasn't a valid date of birth!

I registered for a new account on Top Cash Back and went through the same process - it still said my date of birth was not valid.

I even called Admiral and they said it's £19.50 to change the date of birth.  I wouldn't mind the hassle of changing it if there was no charge! 

Has anyone come across this before?

[Deleted User]

What is the con? And by whom?

TELLIT01

Why was the date of birth invalid?  Is the offer only open to people above/below a certain age?

user1977

And why would Admiral have an admin charge unless you had already bought the policy?

dunstonh

Home Insurance Con

As usual with these sort of threads, no con.

When I clicked to revivew the details, I noticed my date of birth was one day early. I went back to change it and it said it wasn't a valid date of birth!
<snip>
I even called Admiral and they said it's £19.50 to change the date of birth.  I wouldn't mind the hassle of changing it if there was no charge! 

Those two things do not correspond with each other. Admiral only charge an admin fee on policies that are in force.  Not on quotes.

frederick1950

Generally speaking to get cashback you have get a quote and buy there and then.
If you have to complete the purchase by ringing in or if you go back and use an existing quote you don't get the cashback.
As you also went though confused com the issue is probably a glitch  on the confused site  .

MissG80

I forgot to upate - I changed my date of birth by one day and it seemed to fix the glitch. It came up correctly on the policy despite me having typed it in one day out!