V2 Rubric Detail — 163a126a-7647-11f1-8…

Generated 2026-07-18 01:05 UTC

← Back to comparison table
✓ Feedback submitted — thank you!
Call Start
2026-07-02 18:51
Duration
35m 11s
Contact
Jeff Rouleau
Issue Type
Hardware Fault
V2 Outcome
Partial Resolution
V2 Band
Needs Improvement

Agent & Case Context

Agent
Kharla Mae Proel
HappyFox Case
#LTS00115206
Support Country
United States
Product Family
MESH SYSTEMS
CSAT
Sentiment Trajectory
Ticket subject: LN1400_received a UK power adapter

V1 Rubric Scores

Resolution2.00/5
Accuracy4.00/5
Communication3.00/5
Protocol2.00/5
Efficiency1.00/5
Overall2.5/5

V2 Rubric Scores

Resolution1.56/5
Technical3.44/5
Communication3.75/5
Ownership4.29/5
Escalation2.50/5
Customer Exp2.50/5
Overall57.2% (+7.2)

V2 Grader Summary

The agent demonstrated ownership and technical accuracy, guiding the customer through a valid diagnostic step (ping test) while referencing prior history. However, no resolution was achieved, and deeper troubleshooting or escalation was warranted given the persistent, intermittent nature of the issue on a primary node. The outcome is Partial Resolution due to meaningful progress but incomplete closure.

V1 Case Analysis

Intermittent wired and Wi‑Fi connectivity on LN1400 node in mixed MBE7000/LN1400 mesh; firmware up‑to‑date; advised continuous ping test to router (192.168.1.1) and external (8.8.8.8) with LED monitoring; follow‑up required.

Troubleshooting Steps
  • Confirmed model and serial number.
  • Verified that firmware is up‑to‑date (customer checked).
  • Asked about network topology and confirmed the problem persists when laptop is directly connected to LN1400.
  • Advised continuous ping test to router and internet host, with LED monitoring.
Key Observations
  • Excessive hold time (~11 minutes total) without actionable progress or explanation.
  • Agent did not verify whether LN1400 is the primary router or a child node in the mesh.
  • No verification of WAN type (PPPoE, DHCP, etc.) or ISP details that could affect troubleshooting.
  • Technical advice (continuous ping test) was correct and aligned with KB.
  • Agent maintained a polite tone but provided limited guidance beyond the ping test.
  • No escalation path or hardware replacement discussion initiated despite clear hardware fault indicators.
Positive Highlights
  • Accurately collected serial number (64A10M25E00088) and identified LN1400 model.
  • Confirmed customer's firmware is up-to-date — correct step per KB.
  • Suggested a valid diagnostic (continuous ping test) that aligns with KB guidance for intermittent connectivity.
  • Documented intent to update existing ticket (S00115206) with test results.
  • Maintained polite and professional tone throughout the call.
Agent Errors / Gaps
  • Excessive hold time (15 minutes total) without clear explanation or progress updates.
  • Did not verify the role of the LN1400 in the mesh (primary vs child node) — critical for topology understanding.
  • Failed to confirm WAN connection type (PPPoE, DHCP, etc.) or ISP details that could influence troubleshooting.
  • Did not initiate escalation or hardware replacement path despite persistent hardware fault symptoms.
  • Did not set a concrete callback time or escalation path — left customer with open-ended follow-up.
  • Misstated router IP in transcript (1.1.1 instead of 192.168.1.1) — though corrected in context by customer.

V2 Indicator Ratings

Resolution
R1 Not Met Issue actually resolved conf 98%
Agent did not resolve the issue or achieve any outcome (RMA, escalation, confirmed fix); only requested customer to run a ping test and call back.
R2 Partially Met Diagnostic thoroughness conf 90%
Agent confirmed symptoms, asked about connection path, and suggested a continuous ping test — a valid diagnostic step — but did not perform full troubleshooting (e.g., factory reset, firmware re-verification, node replacement).
R3 Partially Met Correct resolution path conf 85%
Agent did not explicitly confirm warranty status, but continued support for a registered device with a prior ticket; pursued best-effort troubleshooting path appropriate for in-warranty device, though deeper action was warranted.
Technical Accuracy
T1 Partially Met Technically accurate info conf 90%
Agent identified intermittent drops and asked whether the laptop was connected directly to the LN1400, showing targeted questioning, but did not establish a full diagnostic sequence or root cause.
T2 Partially Met Appropriate tools / resources used conf 88%
Agent appropriately recommended a continuous ping test to gather data, a valid tool for intermittent issues; however, did not attempt to verify firmware version in real time or suggest log retrieval, which are relevant for this failure mode.
T3 Met No misinformation conf 95%
All technical guidance (e.g., ping test procedure, LED behavior expectations) was factually correct and consistent with KB documentation.
Communication
C1 Partially Met Clear & professional language conf 90%
Agent placed customer on hold and provided updates, but failed to set initial expectations or frame the interaction; call control was maintained but not proactively guided.
C2 Met Confirmed understanding conf 93%
Agent used accessible language, confirmed understanding with verbal cues, and adapted to customer’s technical level without overloading with jargon.
Customer Ownership
O1 Met Ownership & empathy conf 95%
Agent retrieved prior ticket (S0011 5206), referenced customer history, and committed to updating the same case — demonstrating ownership without transfer or avoidance.
O2 Partially Met Proactive follow-through conf 90%
Next step was clear (run ping test and call back), but no specific timeline or agent callback commitment was provided; customer left responsible for follow-up.
O3 Met Closure confirmation conf 98%
Agent successfully retrieved and referenced prior case details including customer name, device, and ticket number, avoiding unnecessary repetition.
Escalation Judgment
E1 Partially Met Correct escalation decision conf 87%
Intermittent wired/wireless drops on a primary node with up-to-date firmware suggest possible hardware defect — a valid escalation trigger — but agent attempted further diagnostics first, which is reasonable L1 triage.
E2 Not Applicable Escalation prep & handoff conf 90%
No escalation occurred, but one was borderline warranted; since decision was to continue L1 troubleshooting, E2 is N.A. as no escalation was executed.
Customer Experience
X1 Partially Met Customer effort minimised conf 85%
Agent apologized for hold time but did not acknowledge customer’s repeated effort, work impact, or frustration; empathy was minimal but not absent.
X2 Partially Met Tone & rapport conf 85%
Agent maintained a neutral tone and followed the conversation, but did not adjust pace or emotional engagement to match customer’s detailed, stressed delivery.
X3 Partially Met Overall experience conf 90%
Agent avoided re-asking known information and used existing ticket, but placed full diagnostic burden (continuous ping, LED monitoring) on customer instead of offering remote tools or logs.
Call Transcript46 turns · 50 lines
Speaker 1
Good afternoon. I'm calling regarding an L-M 1-4-0-0. It's a Velop Pro Ruger node. The reason for my call is I've had
00:00
Speaker 2
Welcome to Linksys Support. To ensure quality service, your call may be monitored. For in warranty products, our support team is available to help with performance and hardware issues. Register your product by visiting register.linksys.com. [silence] Please have your device serial number ready. For assistance, [silence] Press 1 now. For out of warranty products, please have your devices serial number and contact information ready. If unavailable, kindly call back later. For out of warranty product, paid support option may be available depending on the issue. [silence] Thank you for calling Linksys. This is Guy Lumalecca, help you? [silence] Okay, sir. [music]
00:00
Speaker 1
Southern connectivity, both wired and wireless, recently, and I can go through the list of things that I've done and what the symptoms are, what the network configuration is when you're ready. But you'll probably need my name and serial number and other details before we get into that. Sure. Let me pull up a photo because I just took a picture of it a short while ago. I do have a one previous request on this router, a technical support call. If it's easier to tie it to that, I could give you that number. I sure do. It is S0011 5206.
01:00
Speaker 2
okay so you better ensure that you support your client and make sure they get exactly what they need. Um, [silence] Yes sir may I have the serial number of this router? Okay. Can you have the ticket number? Okay. Okay, [silence] Okay, let me just check if I can pull up your record.
01:00
Speaker 1
That may populate name and serial number and everything automatically for you. Right though? Yes. That's correct. Also correct? Yes. That is correct. I only have one and that is it.
02:00
Speaker 2
[silence] Okay. All right, I was able to pull up a record here under Mr. Jeff R-O-U-L-E-A-U and your last name, okay? And then zero at gmail.com. and your phone number is 573 350-2501. Okay, and this LN1400 is the serial number is 64A10M25E00088.
02:00
Speaker 1
I have four nodes total. I have three that are MBE-7000. Those are working just fine, but I've got strange behavior from the single node that is LN-1400, which is the serial number you just provided. Very different, yes, matter all the same. Sure. The way the, the house network is configured is I have Frontier Fiver [silence]
03:00
Speaker 2
okay, you only have one node. Mm-hmm mm-hmm. Okay. Okay. Um your concern right now sir is different from your previous call, right? Mm-hmm. Okay, so what's the issues that you've been encountering right now sir with this LN 1400?
03:00
Speaker 1
From there, I have a Ethernet cable that runs directly to the Velop Pro, the LN1400.
04:00
Speaker 2
Okay. I'm -- uh-huh. Uh-huh.
04:00
Speaker 1
addition to the strange blue lights, I'm having wired connections that are interrupted and that's on multiple computers. My work laptop, my wife's work laptop. We've tried different switches. We've also tried different Ethernet cables, so we've debugged the connectivity piece. I've also had intermittent Wi-Fi problems, so Apple devices will not connect to the Wi-Fi network, Spotify Connect and Airplay intermittently fail. I have to forget and then rejoin the network and then sometimes that will have it work for a short while and then it'll drop again. So all of those are consistent issues across multiple different manufacturers, multiple different rooms. So the one consistent theme is it all goes back to the LAN 1400. I have uh also checked the firmware and all of the firmware is up to date. on all of the child nodes, as well as the parent LN 1400. The ONT has been rebooted. The LN 1400's been rebooted. All the child nodes have been rebooted. Obviously, the laptops, desktops, other things that are connected. Those have been rebooted as well. So I'm kind of running out of options to uh to to debug further and therefore, my call. No blinking, a solid blue. Yes, don't blinking, a solid blue. Like I say, these failures are not constant. It's very intermittent. Both wired and Wi-fi will both drop. I did set up one of my desktop computers to ping three different addresses.
05:00
Speaker 2
okay so right now the light is blue correct on your l n 1400. and as of now is the internet connection working well?
06:00
Speaker 1
[KEEP_UNCERTAIN] The address for the L N 1400 one is 1.1.1 and then another is a separate LAN device in my home. All of those pings have continued now for, I think I'm approaching a week that I've been constantly pinging. Those do not get interrupted when another computer loses wired connection. So the symptoms I'll be on a work call on my work laptop. My team's meeting is going just fine. I've got audio and video. All of a sudden, I lose connection. The icon that shows the computer screen with the Ethernet cable next to it disappears, and then it searches for Wi-Fi. If it can find a Wi-Fi network, then I'll reconnect to the video call and rejoin it. So sometimes I'm back on it a matter of a few seconds, which tells you that I haven't lost my internet. It's not a frontier problem because I went from wired to wireless and that's okay. Other times, once the wired connection drops, it can't
07:00
Speaker 2
Mhm. That's it. Mhm. Mhm. Mhm. Mhm. obvious turn up from uh, bravely and a lot of.
07:00
Speaker 1
I can't find the Wi-Fi and I can't reconnect to the meeting. And obviously since it's a work device, I need it to work and needs to function. So I've got to get a fix in place. [silence] The configuration after the [silence] LM1400, [silence] because that's a 10 gigabit device, it provides a feed directly into a tr geeignate 2 and 1/2 gigabit switch, [silence] and that 2 and 1/2 gigabit switch sends to all of the rooms in the house. [silence] So, when I refer to my work laptop, that room in the house is my office. [silence] There are multiple computers in that office. [silence] That's where I am right now, and just looking around, I'm looking at five different computers [silence] and I have two that I'm currently working on, so one of the only one was connected to the Wi-Fi, that's just kind of funny. I don't know if that's also important information. There's one hard wire in my office that's hard not hard wired into that switch that gets Fed out there, but that's bad and that's what I'm currently connected into. So, I don't know if that all sounds crazy, like, should it work or should it not work?
08:00
Speaker 2
All right, but um the computer that you're using, sir, is it connected directly to the LN1400, or is it connected to one of the Mbe or is it connected to the switch? Mm-hmm. I don't like the way. Uh, hang on.
08:00
Speaker 1
[silence] [music] [silence] a then wired. So the one wall jack in the office goes to a business switch. It's a cisco CB110. and from that each of the computers and servers have a direct ethernet connection. So there is another switch that's in line. However, I've taken one of the laptops. I've taken it from my office to where the ln1400 is, plugged it in directly and the problem persists. so it's not the switch. I've taken the switch out of the equation and the problem still is there. I haven't because then I lose my speed. I only have one node that has faster than one gigabit for at least two ports and that's the ln1400.
09:00
Speaker 2
Oh, yeah, sure. Uh, why not really, uh, find out one full one times, uh, two sets. Um, have you tried switching node, sir? Like make the one of the MBI as the, um, like, for a node. Uh huh. Huh?
09:00
Speaker 1
yeah, correct. The MV the MVE 7000s all have one two and a half gigabit port and four one gigabit ports. So two and a half for your WAN and then one giga bit for your LAN. So I will be slowing my network down to one gigabit. [silence]
10:00
Speaker 2
Yeah, because the, um, ALN 1400 is, um, like, it has, uh, up to 10 Mgbps of speed on the internet, um, port. Just tell me what's going on with Ranchia.
10:00
Speaker 1
Yes. Correct. Just about a half an hour ago, I tried to turn on a Yamaha receiver using the AV controller app in my phone. I have three- Amazon, or not Amazon, three Yamaha receivers that show up on the app. In this case, I only had two. So, I went over, I unplugged the receiver, I restarted the receiver, so it should find it a network connection again. Still didn't show up. My phone is on Wi-Fi. So, I disconnected from Wi-Fi, I forgot the network, I rejoined the network, and again, the receiver didn't show up. I then went to the LinSys app, and I scanned the network. And of the attached network devices, the
11:00
Speaker 2
So, it's like random. Like the dropping, uh, the intermittent, um, connection is like random, right? Like no specific, um, sorry. [silence] From. Um, I, uh, Mm-hmm. No, I'm, I'm,
11:00
Speaker 1
[silence] armahaw receiver was present. At that point, I went back to my app on my phone and it was there. So that's that's not appropriate behavior. It should show up all the time and consistently. That was just a half hour ago. And that receiver is connected with a wired connection. That is not using Wi-Fi. Yes. So that's just one more internet connected device that isn't functioning consistently. It's not just limited to computers. In other words. Yes, I took my work laptop into my computer closet where that LN 1400 exists, connected it directly with a fresh cat six Ethernet cable.
12:00
Speaker 2
your Yamaha receiver and you already observed sir the connection arm directly to the LAN 1400 right
12:00
Speaker 1
that then I was able to get a drop on my work laptop as well. So that's why I think I've got it narrowed down to the LN1400. It's not any of the switches. It's not a bad cable somewhere. If I can connect direct from a laptop to the the LN1400 and still reproduce the problems, then that narrows it down pretty well. I have rebooted it at least three times and I've checked the light color probably five times and it's consistently been blue. But when I've had a drop on either wired or wireless, I haven't immediately gone into the room to check the color. So the quick answer is I don't know, but all the times I have checked, it's been blue. Whereas previously it was solid white after it was set up and configured
13:00
Speaker 2
And by the way sir, with the LN-1400 that you're using, when it the connection drops, the light in it, changes color or it stays blue? [silence]
13:00
Speaker 1
All of the child notes are solid white. It is pretty rare that I go through an entire work day and I don't experience a drop in one meeting. So, several times a day. Does it happen when I sleep? I would have to assume so, but total number of drops, I couldn't say, probably five or six a day. So, every four hours. Correct.
14:00
Speaker 2
How often is a drop off of the connection? Sir. Like, uh, every 30 minutes, or... [silence] Five to six times a day, right? [silence]
14:00
Speaker 1
The total duration for symptoms has been about 10 days. And about a week of that has been intense diagnostics on my side. It was only yesterday that I took my work laptop and plugged it in directly. That was toward the end of the diagnosis. When that occurs, yes. When it dropped, then that's the exactly the symptom. But like I say, it's not all the time, it's intermittent.
15:00
Speaker 2
ut... um how long have you been observing it sir um directly connected to the um to the ln 1400. Uh-huh. uh-huh. um when it's plugged into your um ln 1400, the light's still blue but no internet, correct? [ Silence]
15:00
Speaker 1
Based on all of the information I've collected so far, it appears to be some sort of an intermittent discovery or forwarding issue rather than truly a pure disconnect. Which would point to firmware. when of course I went to firmware immediately and confirmed it was it was up to date. Yes. Okay.
16:00
Speaker 2
Okay. What is it? Uh huh. UhUh huh. What is it? Okay, so can I place you on hold for three to five minutes? Okay. Um just going to um check this um uh issue. Okay stand in line. I'll be back. hello sir thank you for patiently waiting i'm so sorry for that hold uh sir um can you give me another three to five minutes um i need lady to double check this okay thank you [silence] Hello, sir, thank you for patiently waiting. I do apologize for that hold. Okay, so for this time, um, with these, um, issues that you've encountered, we're not, as of now, we're not going to do anything as I double check this. We've, um, like recommended, sir, if we can like observe like how the, um, the disconnection or the intermittent connection, if we could observe it, sir by directly connecting a computer to the LN4000 and then we'll do a like a ping, continuous ping like [silence]
16:00
Speaker 1
So what I'm hearing is that you would like me to permanently configure a laptop to be connected directly to one of the ports on the eln 1400 and monitor a ping to the router itself as well as oneent one one one one, which is google. Report the color of the light and report anytime I have a a ping drop. [silence]
28:00
Speaker 2
are going to continuously ping the IP address of the uh router and then also we have need to have another uh internet we need to ping the internet like google.com then observe if there is like also a disconnection sir hmm want hmm uh-huh yes sir yes sir uh-huh mm-hmm yes sir yes sir okay we'll just do the um continuous ping and then uh if you will
28:00
Speaker 1
OK. OK. And who- Yes. And what information are you speaking? Because my impression based on the user manual is it's a persistent solid blue LED.
29:00
Speaker 2
Well, during the continuous being sir. If you want to test the, um, like the statistics, you can press control and then, pause break on your keyboard to like give you the statistics without, um, stopping the, um, ping, okay? Because if you're going to click on the control C, it will stop the ping. But if you just want to check the statistics, just control, um, pause break. And then, if you want to turn ping on, again, ping the IP address and then as well as the internet, okay? Mhm.
29:00
Speaker 1
if the LN 1400 is operating as a primary router would not be considered normal, and that would indicate either a hardware or firmware fault. So that's not being addressed by this test. Okay. And I should call you as soon as I have a dropout either wi-fi or this test would be wired. So I would do the wired test first. Yes.
30:00
Speaker 2
Mm-HMM. This is suggested. Okay, So, we don't need to do anything yet on the router. We'll do the ping test first and then after that, we'll go then continue what will be the next trouble shooting. Okay. Um based on the result of our ping test. Mm-HMM. Mm-HMM. Um oh yes. So, we'll do the wired, okay? which is better if we do the wired. Okay. So,
30:00
Speaker 1
Okay, that's fine for me. Yes. Okay. I was logged in on one of the computers next to me. Let me see if I can log back in and find that. It's probably also in the link to this app, which I should be able to get to from my phone. But since I was logged in here, let me uh see if I can get it directly from the the uh the browser.
31:00
Speaker 2
Okay. And then I've already I like take note what be the things that needed to be done and then I'll update the the same um ticket number, sir, the one that you provided. Since you've got the same um, your code on the same device, so I'll just update your record. Okay. Um, do you happen to know what's the um, firmware version too? So that I can already take note of here on our um, on your record? Okay.
31:00
Speaker 1
OK. I am at linksys smart
32:00
Speaker 2
You go to troubleshooting. Troubleshooting, sir. And then under troubleshooting, there is status and then devices and report. Under report. Okay. And the modem that you're using from Frontier, sir, is this a plain modem or is it a gateway? Uh, what route are you on? Uh, on T, right? And then RT. Maximum. Try. Reduce. Lower. LCD. On. Sorry, sir. Okay. Okay. Sorry. Translated by CCC Feedback. Translated by CCC Feedback.
32:00
Speaker 1
Okay. is your office open tomorrow or closed for the The Independence Day holiday. Okay. Do you are open Friday, July 3rd? Okay. Then I can let the ping run overnight. Okay. Okay, thank you, . Got it. Thank you.
33:00
Speaker 2
I know, sir. We're open on Monday through Friday. Yes, sir. We're open until July 3. That's around 8 a.m. to 11 p.m. Eastern time. Even though it's holiday there. Yes, sir. You can do that, sir. Okay. Even though it's holiday there, our Independence Day, we're still open. We're only closed during weekend sir. Okay. So I'll just update your record and use the same ticket. Okay? You're welcome, sir. So, thank you also for patiently cooperating with us, sir. And this is Carla again and you may check our website where that's support.linksys.com.
34:00
Speaker 1
Thank you for your help, Carla. We'll give you a call back after I have more. Have a good day. Bye.
35:00
Speaker 2
Have a great day. You're welcome, sir. Okay, sir. Thank you. You too.
35:00