|
|
|
Normally the TDR contacts you to ask if it has been resolved or not. So if it hasn’t they will need to investigate it. They can’t just rely on the telcos word for it. It is definitely an interesting situation and guessing it is fairly rare.
Linux:
Goosey:
When did they send you that communication…like weeks ago, or only within the last 5 working days?
have you had a new bill since? When you log into your account, can you see any adjustments?
@Goosey @Tomahawk66 tested today and the charges are still happening
Correct! The charges are still happening.
mattwnz:
Normally the TDR contacts you to ask if it has been resolved or not. So if it hasn’t they will need to investigate it. They can’t just rely on the telcos word for it. It is definitely an interesting situation and guessing it is fairly rare.
That happened this morning. I replied back to the TDR saying NO it has not been resolved. And now I have contacted them (the TDR) again saying I want it escalated as I got 'stung' again this morning while testing to see if Spark had actually fixed it. Spoiler alert.... they haven't.
Just a update to this thread @Tomahawk66 is 110% correct and is getting billed for mobile calls calling a 03 number and selecting option 1 or 2 but if I call the 03 number from my parents 2degrees landline and select options 1 or 2 no charges occur
Spark is billing the customer on the forwarded number when selecting option 1 or 2 and not the dialed number 03
Linux:
Just a update to this thread @Tomahawk66 is 110% correct and is getting billed for mobile calls calling a 03 number and selecting option 1 or 2 but if I call the 03 number from my parents 2degrees landline and select options 1 or 2 no charges occur
Spark is billing the customer on the forwarded number when selecting option 1 or 2 and not the dialed number 03
Absolute farcical response from Spark. Issue is still not fixed.
@Tomahawk66 the fix might take time but Spark should acknowledge that it is a billing fault
Linux:
@Tomahawk66 the fix might take time but Spark should acknowledge that it is a billing fault
Have emailed you with lots of details. Was told it would absolutely be fixed last Friday. It's not. Spark have done this 3 separate times now, categorically stated it would be fixed on X date, and it's not.
They should say, we are working on it and are not sure when it will be fixed.
|
|
|