Leave a legacy.

Remove O2 coding from the service checker

By: scrappydez | 03-03-2016 17:20

Due to this problem

giffgaff should seriously consider using there own coding for the service checker. Having the O2 coding misleads giffgaff users into thinking that they can use the TUgo service for O2 contract customers.

Comments

by: iqbal92307
on: 01-10-2019 13:38

Yes supported

by: emmalouisep93
on: 08-04-2019 13:13

supported.

by: adamtheant
on: 01-09-2018 10:50

yes supported

by: adamtheant
on: 16-03-2019 14:03

1

by: dantheman12326
on: 09-11-2016 20:43

Yeah that could mistake thousands of people

 

by: dan_the_man
on: 19-05-2016 19:35

??My apologies for posting without checking the second page! 

 

Nice to to see this has been resolved with the new giffgaff service.

by: dan_the_man
on: 19-05-2016 19:32

Supported as all the above have said - need to avoid any possible misleading output. If we can't then we should not offer the service, but simply link / refer to it with caveats about only the signal data being applicable to giffgaff users.

by: timo_t
on: 17-05-2016 13:03

We now have our very own service checker, visible right here: https://www.giffgaff.com/coverage-and-service

Thanks for the suggestion and congrats on the implemented idea!

by: jeff_elephant
on: 13-05-2016 16:17

Supported

by: talisker35
on: 01-05-2016 08:58

Supported.

by: simonoloughlin
on: 27-04-2016 20:02

Agreed, new to GiffGaff and though I could use TUGo as a result of the service checker post. :(