V2 Rubric Detail — 8794da12-5eeb-11f1-a…

Generated 2026-07-18 01:05 UTC

← Back to comparison table
✓ Feedback submitted — thank you!
Call Start
2026-06-03 01:28
Duration
29m 42s
Contact
Sylvan Cordier
Issue Type
WiFi Connectivity
V2 Outcome
Unresolved
V2 Band
Needs Improvement

Agent & Case Context

Agent
Nathan Amores
HappyFox Case
#LTS00131968
Support Country
United States
Product Family
MESH SYSTEMS
CSAT
Sentiment Trajectory
Ticket subject: MX4200 - tech inquiry on disconnection
Transcript quality flagged: the ASR/quality-validation pipeline detected and excluded unreliable transcript segments from grading (4 hallucinated segments). Excluded from aggregate KPIs — treat remaining scores and transcript with caution.

V1 Rubric Scores

Resolution2.00/5
Accuracy3.00/5
Communication2.00/5
Protocol2.00/5
Efficiency2.00/5
Overall2.2/5

V2 Rubric Scores

Resolution0.94/5
Technical1.88/5
Communication2.50/5
Ownership1.50/5
Escalation0.00/5
Customer Exp0.00/5
Overall25.1% (-18.9)

V2 Grader Summary

The agent collected basic device details but failed to resolve the customer’s mesh network issues, offering only generic placement advice without systematic troubleshooting, escalation, or empathy. No concrete next steps were provided, and diagnostic tools were not used, resulting in an unresolved case with poor customer experience.

V1 Case Analysis

Customer with MX4200 mesh system reports missing nodes in the app and inaccessible router admin page. Agent misidentified model, provided generic placement advice, and did not resolve the issue.

Troubleshooting Steps
  • Asked for model and serial numbers (incorrectly recorded model as MX6200).
  • Requested signal strength from the app (reported -53 dBm).
  • Provided generic advice on node placement and signal propagation.
  • Discussed environmental factors affecting signal (brick walls, mirrors, metal).
Key Observations
  • Agent misidentified the router model (MX4200 as MX6200).
  • No structured mesh rebuild steps (reset router, reset nodes, pair) were performed.
  • Admin-page access troubleshooting was never addressed.
  • Warranty or support eligibility was never discussed.
  • Call ended without a clear next-step or escalation.
Positive Highlights
  • Agent asked for signal strength from the app.
  • Attempted to explain the impact of placement on mesh performance.
  • Correctly identified blue light on primary node as indicating internet connectivity.
Agent Errors / Gaps
  • Incorrect model identification (MX4200 reported as MX6200).
  • Failed to collect or confirm serial numbers accurately.
  • Did not follow the universal mesh full rebuild KB.
  • Provided inaccurate signal strength thresholds (-70 dBm as the disconnection threshold).
  • No verification of internet connectivity or router LED status beyond initial color check.
  • No case number, warranty check, or escalation path established.
  • Failed to troubleshoot admin-page access (e.g., ping, browser cache, URL).

V2 Indicator Ratings

Resolution
R1 Not Met Issue actually resolved conf 95%
Agent provided only general placement advice and did not resolve the core issues of missing nodes or red LEDs; no confirmation of resolution.
R2 Partially Met Diagnostic thoroughness conf 90%
Agent asked for model, serials, ISP, and LED status, but skipped key mesh troubleshooting steps like power cycling, firmware check, or 5-press method.
R3 Not Met Correct resolution path conf 90%
No warranty status verification, no offer of paid support despite potential OOW device, and no escalation path offered despite unresolved hardware-like symptoms.
Technical Accuracy
T1 Partially Met Technically accurate info conf 85%
Identified symptoms (nodes not showing, red LEDs) and asked relevant questions, but failed to isolate root cause beyond environmental factors.
T2 Not Met Appropriate tools / resources used conf 90%
Did not use any diagnostic tools (e.g., app signal strength verification, remote access, firmware check) despite customer having app access issues.
T3 Partially Met No misinformation conf 85%
Correctly cited RSSI thresholds (~-69 dBm), but gave technically inaccurate advice about 'horizontal-only' signal propagation and material effects.
Communication
C1 Partially Met Clear & professional language conf 85%
Maintained basic call flow but had multiple long silences, abrupt transitions, and failed to set clear expectations or agenda.
C2 Partially Met Confirmed understanding conf 85%
Used understandable language but did not adapt technical explanations (e.g., load balancing, signal reflection) to customer’s level or confirm understanding.
Customer Ownership
O1 Partially Met Ownership & empathy conf 85%
Created a case ticket and stayed on the call, but did not take ownership of unresolved issues or commit to follow-up.
O2 Not Met Proactive follow-through conf 95%
No specific next steps, timeline, or follow-up plan; advice was vague ('trial and error', 'reposition nodes').
O3 Not Applicable Closure confirmation conf 100%
First contact; no prior case history to reference or handoff required.
Escalation Judgment
E1 Not Met Correct escalation decision conf 90%
Failed to escalate despite persistent node disconnections, app display issues, and customer frustration—valid triggers per escalation guide.
E2 Not Applicable Escalation prep & handoff conf 100%
No escalation was performed, so execution cannot be assessed.
Customer Experience
X1 Not Met Customer effort minimised conf 95%
No acknowledgment of customer frustration or repeated outages; no empathetic statements or validation of effort.
X2 Not Met Tone & rapport conf 90%
Maintained a single technical tone throughout; did not adjust pace or simplify explanations despite customer confusion.
X3 Not Met Overall experience conf 95%
Customer repeated serial numbers and signal values multiple times; agent did not record or reference prior inputs efficiently.
Call Transcript41 turns · 48 lines
Speaker 2
Welcome to Ingenus 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.ingenus.com. Please have your device serial number ready. For assistance, press one now. For out-of-warranty products, paid support may be available depending on your issue. To hear more about your service options, press two. Please select from the following options. For in-warranty products, our support team is available to help with performance and hardware issues. Please have your device serial number ready. For assistance, press one now. For out-of-warranty products, paid support may be available depending on your issue. To hear more about your service options, press two. To hear these options again, Press 8. Please select from the following options. For in-warranty products, our support team is available to help with performance and hardware issues. Please have your device serial number ready. For assistance, press '1' now. For out of warranty products, please have your device's serial number and contact information ready. If unavailable, kindly call back later. [silence] For out of warranty products, paid support option may be available depending on the issue. [silence]
00:00
Speaker 1
Yeah hi. UM so I have an issue. I uh I have a mesh uh Wi-Fi uh setup. So I have one router and uh several nodes. Uh but I'm having a hard time uh I'm setting them up. I I mean they have been set up uh for a while but uh I'm having outages uh here and there sometimes with some of them. So can you uh with me with that please? Yeah I am Vankese. Yeah. um my name. I'm I'm Devan Ross [silence]. [silence].
04:00
Speaker 2
Thank you for calling links. My name is Nathan. With whom am I speaking? OK. Let me verify first is may I have your name please. No, no what is your name. Yes.
04:00
Speaker 1
COR D I E R. So OR D I E R. Yeah, uh so that was my last name and my first name is Sylvain, S Y L V A I N, yeah. Yeah, uh so I I don't know uh I can't remember if it's set up on my name or my or my wife's name actually.
05:00
Speaker 2
Kalem. Kalem A. Dordier. And then what's your last name? Sylvaun. Sylvan. All right. All right, uh, let me create a case ticket for you. Sylvan, I don't have, uh, information about you in our system. Do you have an email address that I can work with? That's okay. Any email that you can receive. I'm good with that. One. All right. Thank you. I got it. Now, let's talk about your router. Do you have is it area number so that I can verify how it looks like?
05:00
Speaker 1
All right, so, are you there? So 3, 8, U 1, 0, M, 3, 3. I think it's an 8 or it's a B. So small. I think it's a 8 0 8 7 8 8. Yeah, the link is uh MX uh 4200 C. For each one. Yeah.
07:00
Speaker 2
Are you here? Do you see the model of the router? Can you see it? 4200. All right. Uh, the one, the one that you gave me, is this the mother node or the
07:00
Speaker 1
Hey, sorry. This is the mm-hmm, this is the this is the motor node. Yeah. [silence] Yes. Yeah. Um I'm going to have one here. Okay, so just so, 38.
08:00
Speaker 2
or the child. is this the mother node or the child node? the main. all right. can you give me another serial number coming from the child? take a picture. take a picture so that you can expand it.
08:00
Speaker 1
BMW three zero zerou I'm M six nine eight one.
09:00
Speaker 2
Okay. Let's take a look. I got it. All right. I found it. So if this is an MX-6200. uh you have since October or 2022.
09:00
Speaker 1
okay no it's it's uh which one the the trial or the main well it's I cannot tell you for all of them because I have like uh 11 nodes connected uh to each other and uh because they're connected to several apartments and for some for some apartments it's not bad
10:00
Speaker 2
from five years ago. Now you have three of this one, right? Do you know what your internet service provider is? Is it Spectrum or Xfinity? Alta fiber. Now, tell me, what is the color of the light on top of the two devices of your MX 4200? Is it blue, red, pink, purple, all of them? Tell me all right, all right, okay, okay, just the mother node, the primary, the primary node, what is the color of the
10:00
Speaker 1
uh the the primary was blue yeah and and I I have I have I have issues with um um uh uh uh uh and and in um and I have other issues for example on the app I and when I go to the Linksys app uh it it doesn't show all the nodes it it shows like seven or eight when I have 11 total so it says 11 nodes but when I go to the G terms it it only shows like eight or nine
11:00
Speaker 2
light on the mother or the parent no blue good is internet and then
11:00
Speaker 1
eight of them. And so that's one issue. The second issue I'm facing is uh, I used to get access to my network uh, directly from my computer by typing the IT address. But it it sounds like it it looks like it it's not working anymore, so I don't know how you can help me with that. Yeah, correct.
12:00
Speaker 2
All right. All right. Number one, the first question is the Linksys is not showing all the nodes are correctly done. Now, that will happen normally, because this is A mesh network it will always connect, disconnect, Inters of power outages, power surge, power panoramic, t will disconnect a route. This is a low voltage and low power. So it will be affected, it just blank station. Sometimes,
12:00
Speaker 1
and the problem here is... like I said, I have the main node is in my apartment, and I have also in my apartment I have ...
13:00
Speaker 2
the child node will not automatically reconnect because it can be far or the nearest child node is also off. So the solution for you on that one is you go to the physical router itself. If the router is white, sorry, blue or bluish green, teal, that's okay. It will just take some time, it will reconnect. Now, if the connection is red or blinking red, all you need to do, bring the child node near the mother node, and it will reconnect itself, and then send it back. The same thing with the rest of the devices. Mhm.
13:00
Speaker 1
um, I have few child nodes, child nodes. I have other child nodes, uh, nodes that are connected to the main, uh, router, in aa, nearby apartments, uh, because we, we own two buildings, and that are next to each other. And I have been trying to build a mesh, a big mesh system, with this, uh, internet, uh, so they should connect, uh, to the node and to each other in a cascade, uh, ideally. But I cannot even set, set up the the cascade as I would like to, so is there a way to do that?
14:00
Speaker 2
MN. Mm-hm. You need to verify where the allocation of the child. [silence]
14:00
Speaker 1
Well, yeah, I opened the listening. Sub, yeah. Uh, uh, I, I think, uh, actually, it's showing. So on the own page.
15:00
Speaker 2
is good or not. If it's bad location, that will always disconnect. If it's good location, regardless of the fluctuation, even if you turn it off, it will automatically reconnect or the mother will automatically detect or find this lost child node. Now, question is, how do you know whether the location is good or not? Using the link systems app, you will be able to see what is the signal strength of the child node. Go. I will teach you how to do it. Do you have a Linksys app? Can you open it for me? All right. Go to the nodes. Go to the nodes. Select one of the child nodes. And tell me, what is the signal strength? Any of the one that has working
15:00
Speaker 1
Yeah, so on the home page It shows 11 nodes and when I click on the on those to see the the D tern I have one, two, three, four, five, six only showing and the the the strength is for all of them is strong. Yeah. Yeah. Yeah. Yeah. Yeah. I I'm in. it. Yeah. Yeah. Yeah. So this one is negative 53.
16:00
Speaker 2
Okay. [silence] Okay, open one of the nodes. [silence] Click one of the nodes. [silence] It will tell you what [silence] Click one of the nodes. [silence] or the child nodes. [silence] Open. [silence] Now, tell me it will tell you [silence] the child node will connect to the router [silence] or will it connect to another child node? [silence] And there is a signal strength in terms of negative dbm. [silence] What is the value? [silence] negative 53. [silence] That's good. [silence] If you reach more than 69, that location is bad. [silence] That will disconnect. .
16:00
Speaker 1
So, I have one that is at minus 59.
17:00
Speaker 2
69 is good, but 70, not good. OK. Then, maximum, should be negative 69. That's the threshold. If you go more than that, 70, 71, 80, that location will disconnect frequently. OK. Zero is that the first one that you see, the one with the period? You may need to turn on and turn off the child. That is a trial and error. You may need to reposit the router, the nodes. Three things that you need to understand. First: the signal on routers is "horizontal", not vertical. If you say "vertical", it is very minimum, weak. The signal is magnified on the horizontal: forward, backward, and sideways. Now, it can go up to 50 to 100 feet with good signal. And since it is horizontal, you have to place the router minimum 3 feet above the ground. 4 or 5 feet would be ideal so that it will spread wide. And the third thing you need to do: avoid placing furniture, books, or any objects near the router because it will create hindrance or obstruction.
17:00
Speaker 1
So, so can you can you can you say again uh what would reduce the signal?
19:00
Speaker 2
If it's a mirror, it will create a reflection. If it's a metal, it will also create diffraction. Over. Yeah. Yep, it will create. Yep. Avoid, move it away around 3 or 4 feet away from the router because if it's beside the router, it will significantly reduce the signal. Child node or mother node. Number one, it should be above 3 feet from the ground. If you place it ground, the signal is weak because signal propagation is horizontal, not vertical. Number two, it avoid placing books, yeah, metals and anything that can reflect the signal to other things.
19:00
Speaker 1
So our our homes are old homes and they are brick. So you are that brick is not good.
20:00
Speaker 2
or objects on the router, okay, near the router. Number four, avoid placing it near the wall. It will create reflection or vibration. Near the mirror. These are waves. It cannot penetrate mirror. It cannot penetrate metal. Breakst it will absorb it, but it cannot penetrate it. Drywall, regular drywall and timber, it can penetrate. That's good. Yes, yep, there's nothing we can do about it. So, let's say, you have a room with bricks wall, it cannot penetrate it. So, you may need to position the router away from the brick and then trial and error. Put it in the hallway or near it, but away, not touching, and then either, okay, not good, not good enough, let's move it back or whatever. And sometimes you can see the signal strength, but it is not good enough. OK. But anyway, those are some of the things that you need to consider. All right.
20:00
Speaker 1
[silence] But the two buildings the two buildings that I'm connecting are bricks. So I is so you are saying that the signal cannot really I mean can can can can go through the bricks, but uh it was going to be weak. Yeah, it's it's close to a window. It's like from a window.
21:00
Speaker 2
[silence] [silence] Open the door of the room so that it can get a good connection or signal. [silence] Weak. [silence] Yes. [silence] Now, what are you going to do if you see, you have two buildings made of bricks. [silence] Position them near the window. [silence] That would be a better one. [silence] Okay. [silence] That's good. [silence] If it's closer to the window. [silence] Okay. [silence] Right now, you have a -54, -51. [silence] That's a good number. [silence] Very good number. [silence] If you have a above 65, 69, still acceptable, still manageable, and it's still good. [silence] But if you have more than that. Then 70 or 70. No, that's not good numbers. You can... Ah, I understand what you wanted. You cannot do that then. You will defeat the purpose of the mesh. The mesh will recalibrate itself based on load, based on connection. If a computer, for example, there is a child node away from the router, and I am near the router, I am supposed to be connected.
21:00
Speaker 1
Yeah, yeah.
23:00
Speaker 2
directed to the router, right? By logic. But then the router is carrying everybody, all traffic goes to the router, so the router is busy. It's heavy. So instead of me connecting, the router said that instead of the devices connecting to the router, instead of the device connect it to the router, it said, connect to the child node. That child is lazy. It has no load at all. It's free. So it will pass you there so that you can get a connection flow. It is memory, processing power and the number of data packets passing through it. So that is the reason why you cannot uh position yourself as, okay, I need to be connected this one. Now, that is for the devices, okay? Your router will automatically recalculate which is the optimum or the best connection for you. It is not necessarily the distance, But it's more on the load on the router. Second question that you may not ask, but I will answer anyway. Nick, your question is mine, you have eight child nodes. Some will connect to the child, some will connect to the router, and you want them to connect to specific child because this child is too far away from the router and then it's still connecting to the I will not connect it. What you're going to do is, turn off all the routes that a child knows. Turn on first the newest, okay? Alright, give around 5 to 10 minutes. It router will calculate, okay? This is the best option. After 10 minutes, maybe turn on the second farthest and then it will recalculate again and then after 10 minutes, another 10 minutes, 30 minutes, maybe.
23:00
Speaker 1
but but should I do that only one or should I do that yeah yeah but this is not for me yeah practical in real life because like I said you know are those two those nodes are installed in different locations rent an apartment, I don't want to bother every or the two. as easy as I would think. Hmm. The problem is it's happening more often. So, like, every week the signal is, I mean, some nodes are blinking red. So, they're not getting the signal. Uh,
25:00
Speaker 2
It is a mess. Oh, you should have seen how complicated it is. For example, shopping mall, where they have multiple mess network, shopping mall, retail stores. Uh, believe me, the technician or the IT guys will always be around. They just… we just don't know them. They would reset the router, uh they had to do things like that every day because of the traffic. Good thing for us we do it every quarter once every six months or maybe once a year, it would be good. At least do it at some maintenance park. Have Have
27:00
Speaker 1
wired I mean, I can connect the... I mean the main is connected is wired the main world is wired, but the other one, you know, they are it's not possible to connect them with wire and Wi-Fi.
28:00
Speaker 2
It's possible, is a two uh-huh, You connected like to another I really don't need another wire coming from the child going to the mother. You can connect from child to another child let's say three mother node connect to a child node, which is 50 ft. And then farther away another 50 ft that's 100 ft already. The third one is like a 200 that's already too slow. So why don't you connect the internet from the third to the fourth child one? So that whatever the third one can get will.
28:00
Speaker 1
Yeah. Well, you know, they are located is tricky to run wires. So, and, yeah. Okay. Okay. All right. Thank you.
29:00
Speaker 2
(Despairingly.) will be taken by the fourth one.
29:00