Auto-email proof of sim/phone barring for insurance claims

[#1]

This was posted on FB waall this morning

"giffgaff, why don't you automatically send proof of handset/sim barring? I'm unable to claim on my insurance without this. "

Seems reasonable, and not too resource intensive.

Searched and no duplicates found

Cheers

Phil  (woohoo, first idea )

[#2]

Sounds fairly simple to implement and potentially useful. Would save the time an agent has to spend to create a report if the lost phone / lost sim report can be automatically generated.

R

[#3]

Can't see this being a problem re fraud - at the moment people could very easily manually get the message from an agent, claim on the insurance, and then cancel the bar a few days later. Making the system automated doesn't really change anything as far as fraud goes - and in any case it's not gg's fault if people choose to abuse the system in this way.

[#4]

Nice, simple idea. Kudos.

[#5]

Yup I like..... I also need to sort out insuring my phone!!!!!!

[#6]

GG should feedback

[#7]

I believe its a duplicate of http://community.giffgaff.com/t5/Submit-Great-giffgaff-Ideas/Automated-proof-of-usage-documents/idi-... an idea I submitted.

[#8]

Hi @kurtiss5561 - not really, your idea was for the information to be available to everyone. This one only calls for it to be sent to people who have reported a lost phone

[#9]

My idea was similar in the sense when you reported the device as stolen it would let you get a PDF file of the required papers for the insurance company.

[#10]

im having a problem with the email giffgaff sent to the claims department for my phone insurance, giffgaff recieved an automated response to say that their email had been recieved but the claims department claim that a day later they dont have the email saying its probably because the attachment was a word doc and not a pdf, this is now holding up my claim and i will be without a phone for even longer because it will take longer to process.

im not happy

[#11]

Hi guys, this is a great idea however we felt not for us. Part of the reason is technically difficultly in actually implementing it, and the other is that we feel these requests needed to be handled on a case-by-case basis. Thank you for the idea and the huge support, I look forward to your future contributions. Kind regards, Hazel.