We’re here 24/7. 365 days a year.
Ask questions. Find your answers. Connect.
Tuesday - last edited Tuesday
I 'ran a connection test' a couple of weeks ago.
The result was that it found something, but didn't know what the something was.
But it would record it as a fault with a REP number, and see what comes up in the days ahead.
Today, I checked to see whether it had found the something.
This was the result, at https://support.talktalk.co.uk/fault-tracker-case-status:
abc
This is where it hung for the next 15 minutes, after clicking 'Check your case status'.
In other words, it couldn't find its way to the case status.
TalkTalk has had problems with 'running the connection test' for at least the last 18 months, and giving logical results.
Bill
yesterday - last edited yesterday
No, @Chris-TalkTalk
I am testing TalkTalk's software. Not because there's a fault with my system
This same problem has persisted as I said above at least from 18 months ago
I, as a customer might be 99% sure that my system is OK
If TalkTalk's system also thinks there is no fault, then 'there is no fault' and my system is OK.
But if it can't give its own opinion, then TalkTalk's system is problematic. What is its purpose if it can't do that?
Please look at the first picture, where I asked TalkTalk's system if my query 2 weeks before, is now positive or negative.
Well, it could not answer even one word. It just sat there, whirling those little black balls, forever.
I can't see why you would find that acceptable.
You say that when a line test passes (and 'run a connection test' IS a line test) , that does not mean 'I don't have a fault'.
Well, that's OK. When I run a connection test (a line test), I am only looking for an answer to whether the line test passes, nothing more. If there is another test to be done, it will done much later. Anyway, I gave it 2 weeks to perform, including to do any other test, if it wanted to. But it didn't perform, even the basic line test.
And why those whirling little black balls, forever?
Bill
yesterday
But it's assuming that you have a fault because you have run the test, just because the test passes doesn't mean that you don't have a fault. We often arrange engineer visits for customers experiencing problems with there service but the line tests pass, no fault found.
Chris
Chris, Community Team
Our latest Blog l Share your Ideas l Service Status l Help with your Service l Community Stars l Set your preferences
yesterday - last edited yesterday
My point is, if it does not find a fault, it should drop the case, forget about the case, say so, and then keep quiet.
As I demonstrated above, the case was uselessly kept open for a couple of weeks.
Would it not be good, if it got out of its misery, and just kept quite after 2 minutes?
When I used the first procedure, to check what progress it had made in the last 2 weeks, it could not come out of its loop.
Only when I asked for a new 'Run a connection test' was it able to come out of its first loop and start a new loop.
Aren't you going to inform the programmers?
Thanks, @Chris-TalkTalk
Bill
yesterday
Hi Bill,
I think it is opening a case because it's assuming that you are experiencing a problem because you are running a test. Both you and the test have confirm that there is no problem so the case will just auto close in few days. If you do experience any problem with your service just let us know and we'll look into it for you
Chris
Chris, Community Team
Our latest Blog l Share your Ideas l Service Status l Help with your Service l Community Stars l Set your preferences
Tuesday - last edited Tuesday
(I've had to do 3 messages, because the editor does not display properly when including a picture or multiple pictures)
As the picture above says, 'We're unable to identify a fault'
And 'Our test has been unable to find a fault with fibre connection'
And yet, it says it 'We've opened a case' 2 minutes earlier
And after spending the 2 minutes, and 'being unable to identify a fault'
the system keeps the case open, instead of closing the case.
I.E. There is no case.
Please report this to the TalkTalk programmers.
My system is running at the right speed and there are no connection issues.
I was doing this test to see if TalkTalk had corrected itself.
(EDIT: If I repeat the the first procedure above, I will get the first result, running forever.
I won't waste any more time)
Bill
Tuesday - last edited Tuesday
I just 'ran a new connection test'
This the result:
de