V2 Rubric Detail — c54ba29a-73be-11f1-a…

Generated 2026-07-18 01:05 UTC

← Back to comparison table
✓ Feedback submitted — thank you!
Call Start
2026-06-29 13:31
Duration
7m 20s
Contact
+447791685886
Issue Type
WiFi Connectivity
V2 Outcome
Partial Resolution
V2 Band
Developing

Agent & Case Context

Agent
HappyFox Case
Support Country
United Kingdom
Product Family
OTHERS
CSAT
Sentiment Trajectory

V1 Rubric Scores

Resolution2.00/5
Accuracy4.00/5
Communication3.00/5
Protocol2.00/5
Efficiency2.00/5
Overall2.8/5

V2 Rubric Scores

Resolution2.19/5
Technical3.44/5
Communication5.00/5
Ownership5.00/5
EscalationN/A
Customer Exp3.93/5
Overall71.9% (+15.9)

V2 Grader Summary

The agent correctly prescribed the KB-backed fix for SPNM60 mesh topology issues (sequential child node resets) and communicated it clearly with ownership and structure. However, no diagnostic depth was applied (e.g., signal check, dashboard review), and the secondary speed issue was not investigated. Resolution was not confirmed, resulting in a partial resolution outcome.

V1 Case Analysis

Customer reports child node connecting directly to main router and low speeds; advised to factory‑reset child nodes one‑by‑one and reboot modem/router.

Troubleshooting Steps
  • Confirmed device model (SPNM60).
  • Advised factory reset of child nodes sequentially (nearest then furthest).
  • Suggested reboot of modem and Linksys router for speed concerns.
Key Observations
  • Agent did not verify WAN/internet status or backhaul signal before recommending resets.
  • Instruction about resetting both child nodes simultaneously was contradictory and could confuse the customer.
  • No warranty, serial number, or case number was collected; support eligibility was not discussed.
  • Agent failed to check signal strength or node placement despite customer mentioning topology issues.
  • No mention of checking Ethernet backhaul or wired connection options despite customer uncertainty about cable availability.
Positive Highlights
  • Polite and patient tone throughout the call.
  • Correctly identified the product model.
  • Offered a clear, KB‑based factory‑reset procedure for mesh nodes.
  • Suggested modem/router reboot for the speed issue.
  • Recommended correct order of node reset (nearest first, then furthest) which aligns with SPNM mesh best practices.
Agent Errors / Gaps
  • Failed to confirm internet connectivity or backhaul signal quality before troubleshooting.
  • Provided confusing guidance about resetting both nodes at the same time versus one‑by‑one.
  • Did not summarize next steps or set a clear follow‑up expectation.
  • Did not ask customer to verify signal strength between nodes using admin interface or app.
  • Missed opportunity to recommend wired backhaul as a more stable alternative for long-distance node placement.

V2 Indicator Ratings

Resolution
R1 Not Met Issue actually resolved conf 95%
Agent did not verify resolution of topology or speed issue before ending call; customer stated they would try steps and call back if unresolved.
R2 Partially Met Diagnostic thoroughness conf 90%
Agent suggested factory resets and modem/router reboot but skipped diagnostic steps like checking LED status, signal strength, or reviewing network map details.
R3 Met Correct resolution path conf 96%
Factory-resetting child nodes one-by-one is correct remediation for SPNM60 mesh topology problem per KB.
Technical Accuracy
T1 Partially Met Technically accurate info conf 92%
Agent acknowledged symptom (topology leapfrogging) and offered fix but did not probe root cause (e.g., backhaul signal, interference, firmware) or ask about LED states/placement history.
T2 Partially Met Appropriate tools / resources used conf 90%
Agent did not use or direct customer to check admin dashboard (http://myrouter.info) for backhaul signal strength or node connections, which is available and relevant for SPNM60.
T3 Met No misinformation conf 98%
Instructions to factory reset child nodes one at a time and reboot modem/router are technically accurate per KB guides for SPNM mesh topology recovery.
Communication
C1 Met Clear & professional language conf 93%
Agent framed interaction, set clear action plan (reset nearest then furthest node), and kept conversation on track.
C2 Met Confirmed understanding conf 95%
Agent used plain language, confirmed model number, and adapted to customer’s non-technical description of mesh tree.
Customer Ownership
O1 Met Ownership & empathy conf 96%
Agent owned case, did not transfer, and invited follow-up if steps failed, showing accountability.
O2 Met Proactive follow-through conf 95%
Clear next steps given: reset nearest child node first, then furthest; reboot modem/router; call back if unresolved.
O3 Not Applicable Closure confirmation conf 100%
First contact; no prior case history or handoff occurred.
Escalation Judgment
E1 Not Applicable Correct escalation decision conf 100%
No escalation performed and none warranted — issue was within L1 scope and valid resolution path provided.
E2 Not Applicable Escalation prep & handoff conf 100%
No escalation occurred; execution cannot be assessed.
Customer Experience
X1 Partially Met Customer effort minimised conf 87%
Agent was polite but offered limited empathy for customer’s frustration with recurring topology and speed problems.
X2 Met Tone & rapport conf 94%
Agent matched customer’s pace, used accessible language, and confirmed understanding during reset sequence explanation.
X3 Met Overall experience conf 95%
Agent avoided unnecessary repetition, used known model info, and provided direct action plan without extra steps.
Call Transcript14 turns · 15 lines
Speaker 1
Hi. I have a bit of a problem with my mesh network. Um, and I was hoping somebody might be able to help me with that, uh, just troubleshoot it, see if I can get it up and running again. Um, so I have a mesh network of three, uh, nodes, uh, main router and two child nodes. But, um, one, one child node is further away at the bottom of the garden. That seems to be leapfrogging the middle node and going straight to the main router. Um, rather than, um, connecting to the sort of intermediate child node. uh, this has only happened since this morning when I reset it, because I was trying to solve another problem.
00:00
Speaker 2
Welcome to Linksys Support. To assure quality service, your call may be monitored. Please remain on the line for assistance. Hi, thank you for calling Linksys. My name is Van, and I'll help you today. What seems to be the problem?
00:00
Speaker 1
But now it's just showing me in my little um sort of mesh tree on the Linksys now portal. It's just showing the main node and then the two child nodes branching off of that. Does that make sense? I have tried moving them around, moving the third, sort of the furthest node closer to the middle node, um based on sort of the AI chat recommendation. Um and um that doesn't seem to have done it. It still seems to be trying to connect directly to the main router, even when the middle node is uh much closer in proximity, which it always is to be clear, it's always uh much closer. So I've only tried those. Um it's also recommended sort of linking them with ethernet cables, but um I don't I don't believe I have any unless they're a boxed in.
01:00
Speaker 2
[silence] And have you done some changes in regards to the node or any kind of troubleshooting? good. All right.
01:00
Speaker 1
uh with the units when I got them but I don't believe so. Um and even so I don't I don't know if that would solve it or not or if that was just uh sort of over eyes. Uh uh yes, well I'm through the browser version. Um which uh I've been using um the app doesn't seem to let me log in, so the browser one's got got everything I need on it. Um I believe it was um I can remember it off the top of my head. I'll just read it off the unit. SP NM 60. Uh, I believe so. They they certainly look um um the same, but I'd have to check. They they all came together as part of a community.
02:00
Speaker 2
All right. Lastly, are you using the Linksys app to monitor your network? What's the model of your mesh to confirm? Thank you so much. Are they all the same model? Mm-hmm. All right. I see. Thank you. Thank you so much for that one. So after you've done those changes, as you mentioned, you've tried moving them around just to see if there's any kind of changes in how they interact, unfortunately, it's still doing the same thing, is that correct? All right. Thank you so much for that one. If that is the case, I do have to set expectations that your last thing that you need to perform for your child nodes only is to consider doing a factory reset on those child nodes. But instead of doing it on both of them at the same time, you need to do it one at a time. In order for the topology to correct itself, you need to set up the nearest child node back first, then the furthest child node, so that once you relocate them one at a time, the furthest child node should reconnect to its original child node and it will all be correct afterwards.
02:00
Speaker 1
I see. So, just to, just to clarify that again, sorry, that the middle note needs to be factory reset first and then switched on and all reconnected and then factory reset the furthest one.
04:00
Speaker 2
to the nearest child note then you can factory reset both of them at the same time. However, in setting them back up, it needs to be done one at a time, from nearest to furthest. There's no need. The main note works as it is, only the child node needs to be uh done some changes. You can reboot the parent node however, since rebooting will not affect it and it will do some balancing after the reboot.
04:00
Speaker 1
Okay. Okay, fine. That's that's what I'll do then. I'll try and do that and then if it doesn't it doesn't work, I'll get back in touch. I did uh since I've got you. And the reason I tried resetting it this morning is because actually I had another problem, which is that when they were all linked correctly in the right order and I was getting a really good full signal on all three nodes, on the dashboard here showing the topology. They were all showing full green, full good signal. But I was still finding the child node was only giving me downloads of about between say 1 and 10 megabits per second, whereas in the house off the main router I was getting around 200. [silence]
05:00
Speaker 2
no since you're just doing the resets on the child node if you factory reset them the parent node will retain those information so once they're successfully reconnected they will also use those credentials back
05:00
Speaker 1
there's obviously some sort of loss somewhere along there. and it was regularly uh disconnecting itself from its devices. um and so I don't know if if there's anything else I need to be doing to ensure despite the fact it was saying the signal between them all was very good. whether there's anything else I need to do. Okay. understood. Um fine, I'll I'll take a look at that separately, then once I've um once I've got this situation back up and running, I'll I'll consider that as an option.
06:00
Speaker 2
If the main concern in regards to that one is the signal strength and as well as the speed, the best way to do it is to do a reboot on both the modem which is from Community Fiber and your Linksys device. If there's no modem which only connects it directly to the outpost or through the internet directly just by a wire, that's the time you will need to relay this kind of concern to Community Fiber.
06:00
Speaker 1
No, I think that's everything for now. Hopefully, I'll get somewhere with this. I appreciate your help. You too. Thank you very much.
07:00
Speaker 2
No worries. All right, so is there anything else? All right. Thank you so much for calling, Lexus. Take care and have a great day. If you have any more concerns, feel free to call us back.
07:00