V2 Rubric Detail — d184c11e-792b-11f1-9…

Generated 2026-07-18 01:05 UTC

← Back to comparison table
✓ Feedback submitted — thank you!
Call Start
2026-07-06 11:14
Duration
42m 23s
Contact
+31612059637
Issue Type
Hardware Fault
V2 Outcome
Partial Resolution
V2 Band
Needs Improvement

Agent & Case Context

Agent
—
HappyFox Case
—
Support Country
Other / Unmapped
Product Family
MESH SYSTEMS
CSAT
—
Sentiment Trajectory
—
⚠ Transcript quality flagged: the ASR/quality-validation pipeline detected and excluded unreliable transcript segments from grading (1 hallucinated segment). 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.3/5

V2 Rubric Scores

Resolution2.19/5
Technical4.06/5
Communication2.50/5
Ownership3.57/5
EscalationN/A
Customer Exp2.50/5
Overall58.4% (+12.4)

V2 Grader Summary

The agent demonstrated ownership and used remote tools effectively to observe the router interface, correctly identifying a likely cabling issue. However, foundational troubleshooting steps were skipped, and the issue was not resolved during the call, resulting in a partial resolution. The recommended path was appropriate, but execution lacked completeness and customer effort reduction.

V1 Case Analysis

Customer reports wired child node shows wireless in app and has no internet; agent advised checking Ethernet cable and ports, suggested trying a different cable and follow‑up via email.

Troubleshooting Steps
  • Requested access to a computer and attempted to view router settings.
  • Asked which LAN port the Ethernet cable was connected to and suggested moving to another port.
  • Advised testing with a different Ethernet cable and checking the connection directly.
Key Observations
  • Agent did not verify parent node WAN/internet status or LED colors before troubleshooting.
  • No model, serial number, or warranty information was collected.
  • Guidance was vague, with many repeated questions and no clear validation of each step.
  • Call concluded with a follow‑up email/callback suggestion without confirming that the issue was resolved.
Positive Highlights
  • Agent remained polite and patient throughout the call.
  • Attempted to guide the customer to check Ethernet ports and cables.
  • Offered to follow up via email and provided a path for the customer to get further assistance.
Agent Errors / Gaps
  • Failed to collect essential device information (model number, serial number).
  • Did not follow the standard troubleshooting flow (modem test, node LED check, isolation of wired vs wireless).
  • Provided unclear, unstructured instructions and did not confirm outcomes after each step.
  • Did not achieve a technical resolution; left the issue unresolved.

V2 Indicator Ratings

Resolution
R1 Not Met Issue actually resolved conf 98%
Agent concludes with 'we really need to check that cable' and defers resolution to customer follow-up via email or callback; no confirmation of fix or outcome achieved during interaction.
R2 Partially Met Diagnostic thoroughness conf 92%
Agent uses remote access to view router interface and tests cable connection indirectly, but skips foundational steps like verifying modem connectivity, checking node LED status, or testing WAN link — relying on app display rather than isolating physical layers.
R3 Met Correct resolution path conf 95%
Agent correctly identifies cable or cabling infrastructure as the likely fault point and recommends rerunning or replacing the cable — appropriate path for suspected physical layer failure in wired backhaul.
Technical Accuracy
T1 Partially Met Technically accurate info conf 90%
Agent identifies symptom (wired node showing wireless in app) and explores cable and port variables, but fails to verify basic physical indicators (LED status, modem link) or perform a direct modem test to isolate upstream issues.
T2 Met Appropriate tools / resources used conf 97%
Agent initiates a remote-view session using 'join.zoho.com' and session ID 204, successfully accesses the customer's screen to observe router settings and port status — appropriate tool use for visual diagnostics.
T3 Met No misinformation conf 96%
Agent correctly interprets solid red LED as 'no internet connection' and explains that absence of 'X mark' on LAN port indicates no link detection — consistent with KB documentation.
Communication
C1 Partially Met Clear & professional language conf 90%
Agent maintains basic control but exhibits multiple long silences, repetitive phrasing ('uh', 'so'), and minor disorientation (e.g., 'I'm sorry to interrupt you') — indicating lapses in smooth call flow.
C2 Partially Met Confirmed understanding conf 88%
Agent uses consistent terminology but does not adapt explanations for customer’s technical references (e.g., 'Linux computer', 'Keystone jack'); assumes understanding of networking terms without confirmation.
Customer Ownership
O1 Met Ownership & empathy conf 95%
Agent owns the case end-to-end, does not transfer, and offers continued support via email or callback — demonstrating accountability despite unresolved outcome.
O2 Partially Met Proactive follow-through conf 90%
Agent tells customer to 'give us a call back or email' but provides no timeline, ownership, or specific next action — leaving follow-up undefined.
O3 Partially Met Closure confirmation conf 85%
Agent references prior contact with customer’s mother but does not leverage any documented history or avoid re-asking known details (e.g., number of nodes, setup configuration).
Escalation Judgment
E1 Not Applicable Correct escalation decision conf 100%
No escalation occurred and none was warranted — issue was a suspected physical layer fault within L1 scope and resolvable with customer-side testing.
E2 Not Applicable Escalation prep & handoff conf 100%
No escalation occurred, so execution cannot be assessed.
Customer Experience
X1 Partially Met Customer effort minimised conf 87%
Agent expresses politeness ('thank you', 'I'm sorry') but does not acknowledge customer’s repeated effort, technical investment, or frustration with complex cabling setup.
X2 Partially Met Tone & rapport conf 85%
Agent maintains neutral tone but does not adjust pace or simplify language despite customer’s complex explanations involving multiple cable runs and network topologies.
X3 Partially Met Overall experience conf 90%
Customer is asked to move hardware, swap cables, and reboot devices multiple times; agent could have accelerated diagnosis by suggesting a direct LAN-to-computer test at child node location earlier.
Call Transcript74 turns · 80 lines
Speaker 1
this is LinkSys technical support calling. This call is recorded for quality assurance. Please hold as we connect you to a LinkSys specialist. Hello? Um, hi, good afternoon. This is Clark from LinkSys. Um, I'm calling regarding your ticket. It was actually escalated to the department in order for us to further assist you. So, um, I actually talked to your mother, um, earlier and then, uh, she mentioned that she's not at your house, but you are available in order for us to do the troubleshooting. okay? All right. Thank you so much. So, um right now, um, I'm calling regarding with your LinkSys router, um, because, uh, the issue was actually on the child node that is, um, the connection of this one is wired child node. However, on the link, it is
00:00
Speaker 2
Hello, good afternoon. No. That's true. That's correct. Yeah.
00:00
Speaker 1
App it shows wireless and it's connected via wireless, right? And it should not be like that since again the child node is connected via an ethernet, correct? Okay, so right now, only one child node is wired, is that correct? Uh-huh. Oh, okay, so only one child node that is connected. Uh-huh. Mm-hmm. Okay, got it. So technically.
01:00
Speaker 2
It's true. Yeah. it's correct. Right now ah, I have one child node slugged in, the other one is in use but on a different network. So I have one parent, nodes, which is connected yeah ethernet cable to a child nodes. Yeah, Right now it's only more but uh well, yeah right, it's connected wirelessly right now which doesn't improve speed because there is a for full gift here.
01:00
Speaker 1
Right now, sir, so you have a total of three nodes, right? However, the other, the, the, one of the nodes is being configured in a different network. However, on the child node that we are talking right now, it's the one that is connected directly to the Pare node, is that right? Okay. Okay, got it. Uh, but again, um, since it's wired directly to the Pare node, in terms of connection, it should be wired, however, on the data side, um, especially on the Linux app, it's connected wirelessly, right? Okay, so in order for me to further assist you and do some troubleshooting right now, um, is that, do we have, like, a computer or laptop right now that we can use? Okay. All right. So, um, the computer or the laptop that you are using right now, is it like a Windows computer or a [silence]
02:00
Speaker 2
Yeah. Yeah, connected, correct. posted straight to the partner. That's correct. Yeah, I have tried the cable, multiple times at least 10 or 20 times. [silence] Yeah.
02:00
Speaker 1
okay.
03:00
Speaker 2
I have an Apple computer right in front of me. I'd rather not, but if that's the only possibility, it is possible. Okay.
03:00
Speaker 1
With your persona? Johan. Is that correct? Johan. Okay. All right. Got it. Thank you so much for that welcome, Johann. So, yeah. can we open now a browser? Okay. Just let me know when it's ready, okay? Mm-hmm. Yes, sure. Okay, yeah, sure.
04:00
Speaker 2
My first name is Johan. Yeah, Joan. It's a Dutch name. So it, the pronunciation will be hard. Um, sorry. [silence] I am logging into my computer. Well, for least I'm trying. Yeah. [silence] I don't [silence] I'm going to reboot it real quick. It doesn't [silence] I have a connection to a different server via VPN which it doesn't stop. So, I'm going to restart it.
04:00
Speaker 1
Alright, yeah, sure. Just let me know then. [silence] Alright, got it. So, can we type in this one? So, can you please type in the word join? So, J for Juliet. Uh-huh. Join. J-O-I-N dot or period. And then Zoho. So, that's Z for zebra, O for octopus, H for hotel, O for octopus.com. Okay, so, um, can you input the session ID, it's 204.
05:00
Speaker 2
I have a browser and a fonction. Joigne. Yeah, I have a session ID in the name. Do you? Yes. Zero. One. Three. Zero. One, zero. One. Three. Yeah. Silence.
06:00
Speaker 1
All right. Can you tell me what we're seeing right now? Okay. All right. okay got it and okay alright so uh I'm sorry what is that? yep I can see now your computer screen on my screen yep thank you so much um so yeah uh let me open now a browser so um so you're using the browser sir not Safari is that correct? okay but do you have the Safari browser? okay alright got it thank you so um let me now um so let's go ahead and access
08:00
Speaker 2
I'm trying to move my mouse, but it doesn't really... I think it is... I think it's in. I think you can... I would open... I, yeah. I also have Safari. It's this is Xero, but Safari is... This is a Chromium-based browser. [silence]
09:00
Speaker 1
yep, so, so, so let me now let's go ahead and accessed your outer settings. All right. Do you know what is there? The router password on this one? OK. OK, got it. Thank you so much for that. So, let me go ahead and uncheck. So this is the wired child node right now. Is that correct? OK. All right. Yep. Yeah, it's fine. Um, OK. And this is wired directly, right?
10:00
Speaker 2
oh I can yeah oh yeah You're welcome. That's the child node. It's in it's Wired directly. yeah it's [silence]
10:00
Speaker 1
Uh-huh. For the By cable. Okay. Uh-huh. Oh, okay. Got it. So currently, right now, it's uh these child node is wired to the pierce. Is that all right? [silence] Okay, cause apparently right now, sir, it seems that there there's no cable connected to any of the land ports of the pair node, because as you can see,
11:00
Speaker 2
Yeah, if your um parent mode... excuse me, when I put the child node in parent mode, it works directly, it gives the full speed. Yeah? [silence] is, [silence] to the one now gigabit ports [silence] to the child node and the parent mode is [silence] [silence] to a 2.5 gigabyte land port.
11:00
Speaker 1
see this portion the internet this is the connection directly to the modem running through the parent node but in terms of this this one the port one two three and four it seems that there's no cable connected to it but you mentioned that it is connected right now right? yeah I see can you try to um use it uh which port it's connected right now sir is it port number one two or three which port it's connected? yep all right on the parent node okay? on the parent node
12:00
Speaker 2
but, yeah. but we don't have it is connected but we also don't have gigabit ports. it's 2.5 gigabits. So it should be connected somewhere here which is strange. if I recall correctly, it's port one but I would check. Yeah.
12:00
Speaker 1
Port number four. Okay. Uh just give me a moment. Port number four. Okay. Um. Mhm. Mhm. Mhm. Okay, got it. Um, would it be possible sir if we were gonna transfer the cable to the port number two. Can you try it to port number two?
13:00
Speaker 2
Oh it's connected to four. Yeah. And when I changed the 12 node apparent font I switched them up because we have three. We, we I tried to uh to know some diagnostics and switch up the parent and child nodes and all of them had the same issue.
13:00
Speaker 1
It's connected to port number two. okay. it's not. uh, how long is this cable to the rec sector to the... child note? 10 meters. okay. um, these cable is it connected, uh, running through the wall and then, uh, the child node where is the?
14:00
Speaker 2
Ten meters, the end is select to port number two, the.
14:00
Speaker 1
A location where the child supposed to be connected to the wall patch, is that correct? Like the cable, so the cable running from the parent node or the one that is connected right now to the parent node down to the child node. Is it cable running directly or is it connected to a "Oh!" Okay. Okay. So it's connected via a wall patch, it's running on a wall patch, is that correct?
15:00
Speaker 2
It is What do you mean? I'm sorry, your mic isn't I'm trying to distinguish from words. No, it's not running directly. It's in a Keystone and then to the um to the child nodes with a RS232 cable, which I also tested that I tested I used multiple different cables. Yeah.
15:00
Speaker 1
OK. Um, on the location where the child node is connected, do you have like a a device that can be connected wire directly? cuz cuz we we need to, yeah, we need to check if that cable is really running um, like an internet connection for us to make sure that it's working when it's connected directly to the parent node. Yep, yep.
16:00
Speaker 2
I do, but it's not installed. I may have an adapter for it. Oh, I do. I need to get some. [silence] I'm going to use a Nintendo Switch, if that's all right. But I will have to take it before,
16:00
Speaker 1
So, you need to disconnect. the cable that's connected to the child node and connect a device so that we can check if that cable is really providing a connection or not. Okay?
17:00
Speaker 2
Oh I don't I need need you to someone yeah yeah Well I hope
17:00
Speaker 1
Yeah. Yeah, that's fine. As long as it can be connected via an ethernet cable for just for checking if it's getting connection via that cable.
18:00
Speaker 2
There is enough power. For me. [silence] Is it okay if I use a Linux computer? It's just that's easier, just. Yeah.
18:00
Speaker 1
I'm sorry, sir Johan. I'm sorry to interrupt you. But, um, if you can go back to your computer screen. The, s, uh, the, uh, it's now connected via, transcription. [silence]
19:00
Speaker 2
[silence] I hope this works. I oh, yeah. I am.
19:00
Speaker 1
a cable wired connection. Um, sorry. oh, it's not ok. Oh, you disconnected it. You disconnected it. Ok, alright. Alright, got it. Thank you. probably it's just a glitch. Okay. Can you please try to check on that computer if it's getting a connection or not?
20:00
Speaker 2
which is impossible because there is no table in the parent node. There is one... oh, there is no... oh, there's no... there is no cable in the child node. It's completely... there are no cables. Yeah. And I do have one in the Linux... Linux computer. I will.
20:00
Speaker 1
Yep like wired connection so yeah it seems that this is yeah that's right since again that's the main source how about this one can we bring this um child node close to the parent node can we do that all right yes next to the parent node and then do you have like a shorter cable that is available right now
21:00
Speaker 2
There is a wired connection, but it is... it isn't, it isn't, it does not work. There is no connection. Yeah, there is a Wi-Fi connection, but not a wired connection. But if I now put the cable in the modem, it is going to get connection. Yeah, I can bring it closer. Where would you like me to next to the... [silence]
21:00
Speaker 1
Okay. So, uh, yeah, okay. All right. So, uh, what you need to do, Sir Johan, is once the child node is close to the parent node, uh, let's connect directly a cable to it, from the parent to the child, while it's close together. Okay? Thank you so much. [silence]
22:00
Speaker 2
Yeah, I do. I have to search it. Oh, I have one. Yep. It is connected to child node or parent node, both are connected in transcribe, this audio from the right channel.
22:00
Speaker 1
Okay. Uh, but the child node is now rebooting. Is that correct? Okay. So let's just wait. Okay. Okay. Let's wait until the child node is uh, fully boot up. Okay. Um, and then right now, um, Sir Johann, okay, as you can check on the computer screen, so, earlier when the child node is on its location together with the cable running to its location, there's no x mark on the other ports, right? But the moment the child node is closer or close to the parent node with a shorter cable next to it, there is already an x mark on port number one. So this explain that this is not uh,
23:00
Speaker 2
Include this cable. [silence] It is rebooting. [silence] or starting up. It's not really rebooting. [silence] Yep. [silence] Yep. [silence] Yep. [silence] There is an.
23:00
Speaker 1
So this this explained that the, I believe there's a, um, uh, off on the cable that it's connected from the parent node to the location running on the child node, uh, because it's not recognizing the connection between the child node and the parent. So, um, [silence] mean to her is, um, the cable, the cable that is running, um, from the parent node, uh, to the child nodes locations, uh, probably that's the issue and then [silence]
24:00
Speaker 2
Yeah, that's Yeah, but that's strange because I right now I have a wired connection from my Linux computer. and it's using the same cable. [silence]
24:00
Speaker 1
Like the, probably the Ethernet port of that cable, or like the wall path, something like that is the issue here. Because earlier, also when I asked you to connect like a computer, since we used the Linux, right? The Linux computer is not getting any connection at all. So it seems that um, that that type of connection is really not working. Um, reason for the child node not getting any connection, or it's not getting a wired connection, but when using [eh] Um, using a shared Wi-Fi, it's able to connect to internet. But that's not the case with the Ethernet, even when we switched to a different variant of Linux, nothing gets through. [chuckles] But yeah, like we are probably going to check
25:00
Speaker 2
Yeah, but it's this isn't the only cable that has experienced this problem. We have multiple cable runs and they're all failing on the limbs. Everything's okay. It works when I use it. And it uses and it also works the cable also works when it's one length of cable or when it's one length.
25:00
Speaker 1
[silence] yeah, because that really [silence] foreign minister, as your [silence] uh
26:00
Speaker 2
So, it's only when two nodes are connected that this problem occurs. And that's the issue. I know the cable is okay, because it works, uh, it, it gets the full speed, it works correctly, except when there is one lynx, uh, when there are two lynx nodes connected. And it's not only this cable, it's in every cable that is at least like 10 meters long, it doesn't need to be the same. I have lots of different cables but then they all fail when there are two lynx nodes connected. And I also have outside cables with lynx nodes connected which now works perfectly, but when I put them in the lynx parent node, they fail. They fail, yeah, I think it's fail.
26:00
Speaker 1
As a Linux technician, the 10 meter cable is still actually okay. However, I can really... I'm sorry, just give me a moment. So, yeah, I'm sorry for that. So, yeah. This really explains, sir, that right now, I can really I can really as your Linux technician, I can't really say that there is really something wrong with that cable that is running to the location where this child node is located cuz the the parent node is not really detecting it. We we can actually see that one on this page on the links to setting. Once the cable is detected, there should be an X mark. Earlier, there's it's not showing. And then the moment that we transfer the cable, the moment that we transfer the child node and used like a shorter cable to it, the parent node able to detect that there is a wire connected to it. So this really explain that the child node or the node is really working. It's just that the cable is the problem or issue here. I totally understand that there are cables that are are working perfectly however it seems that the cable uh that the child node is using is having an issue and it's not detecting especially the parent node and that's explaining um this issue right now um why the child node um instead of wired connection it switches to um wireless uh connection so we we might we might really need to uh it's it's not incompatible sir it seems that we need to make sure that that cable is really working um because early uh
27:00
Speaker 2
So the cable is incompatible, if I understand, the cable is incompatible with the Linksys devices. Oh, I have another cable run on the other sides here.
29:00
Speaker 1
Yeah, let's try let's try to use that. this one, you can, you can work on that and then probably we can exchange some email. Um, once they're able to set up that one, then just reply to me by an email. Uh-huh. Okay. Uh-huh. Okay.
30:00
Speaker 2
Yeah. I can try that one. It's the same text. I have two cable arms to this room. But it isn't, I don't, it isn't set up right now, so I have to do a lot of work to put in the Keystone jack on it. Um, I do have another cable arm set up. I do have one setup, which is an outside cable. Um, which also doesn't, I can try and go there right now to set up the chassis, because it doesn't cable set up. [silence]
30:00
Speaker 1
[KEEP_UNCERTAIN] okay. okay. Okay. That table, where is it connected? okay. this we- The switch puts it to the parent- The switch must be connected to a parent node. If that, setup, um, we need to do that. So, um, the switch needs to be connected on the parent node, so that we can use that cable. Oh, okay. Okay.
31:00
Speaker 2
Well, I cannot do that because that of the internet and my other parents working and I don't think he'd appreciate that.
31:00
Speaker 1
Uh-huh. Uh-huh. Uh-huh. Uh-huh. Uh-huh. Uh-huh. Yeah, that's right. Sure. Uh-huh. Yap. Uh-huh. Alright. Mm-hmm. Okay. Um, would you, do you mind if you gonna, like, take a picture, sir? on the the device or, like, the the the, what you call this? the cable where it's connected on the, the disc?
32:00
Speaker 2
Okay, now put in a cable, so then I will connect the guy disconnect and I will shut off the shell now, and we'll use it. Yeah, every mode for, uh, set, uh, there. because if that's what I tried, if that works, that means the cable's also working. otherwise you cannot have anything. that's right now it doesn't. you probably do not have the internet, so I will fix it in a moment. [silence]
33:00
Speaker 1
child nodes location something like that for me to check if it's running directly to a wall or something like that. Oh, no, no. I'm going to send you via an email instead. Okay.
34:00
Speaker 2
Yeah, I, I can. Um, but I don't know how I I might be able to show it on my computer. It's a bit of a mess. I will, I will connect my computer to the internet so you can see, uh, get first the router set up. [silence]
34:00
Speaker 1
What is that again Shuriwan? to each other? You mean to each other? is that right? Mm-hmm
35:00
Speaker 2
It's still flashing blue light. And. I do have a quick question. Is it true that. Is it true that you can't wire three notes. Uh, links is nodes after each other. Because I also tried that. And it also didn't. Is it true that you cannot wire three links as notes wired. Uh, I wired up one parent nodes to one child now and then one child as notes to another child.
35:00
Speaker 1
that should work that should work uh because they're connected as one not unless if they're not connected uh like if they're um probably set up on a different network or something like that they it won't um detect on a one network so they should be in the same network so that um the parent node will be able to detect it [silence] Is it flashing red right now? Or solid red? Okay. So you are now connecting the cable [silence] or [silence] [silence] what
36:00
Speaker 2
nodes and that also did not work. Okay, uh if it's flashing red but it's on like, so I have to- Yeah, it's flashing red, but I put the wrong cable in, so that doesn't help.
36:00
Speaker 1
Is it on the child node location is right Right okay erg There is is at still flashing red or solid red OK so let's just wait for that bye.
37:00
Speaker 2
Yeah, I'm connecting the cable to the shell notes location and then connecting the equal to the modem. The modem does show a link cable or a link that's being a link that is active. Or at least it should. Oh, it shows, yeah. I'm going and now it is flashing blue. So it's booting up.
37:00
Speaker 1
It's solid red. Okay. So that means there, it's not detecting any connection at all, if it's solid red. No internet connection running through the cable. Um, yeah, there, there's uh, there's a indication that there is like a, a connection, a connection, like a cable connected. uh, so it will detect there's a link. However, in terms of connection, it's not, [silence]
38:00
Speaker 2
and now it's flashing or no it's solid red yeah it's solid red so that means there are something it does show a link the modem is linking it and yeah
38:00
Speaker 1
flowing or it's not getting any connection at all. the modem will detect that there's a cable connected because the port is being occupied. um however, in terms of connection, it's not getting or the connection is not flowing to that cable and that's what I'm uh I'm telling you about earlier that it- it is not really providing any wired connection at all. uh yeah, that's also that's actually correct. So, um that's the reason why like the T1 nodes on that location is switching to a wireless connection because the wired connection is not working at all. That's that's actually correct. [silence]
39:00
Speaker 2
there is a connection but it's not providing internet. And it also explains why the app switches to wired because it tries to connect wired and then it doesn't give any connection, so it switches back to Wi-Fi.
39:00
Speaker 1
I see. So yeah, that, we really, we really need to check that cable, Sir. We need to probably um probably rerun a different long cable, um, running to the location of the child node from the parent node so that we can really check and compare the connection. mm-hmm. mm-hmm. All right. Okay.
40:00
Speaker 2
Okay. But that also does not explain why the Linux driver does the same on every cable, even different cables when it's status on. For example, outside wrong, it does not work. Okay. I will be trying to fix that or at least another cable in the upcoming weeks.
40:00
Speaker 1
Okay, all right. So yeah, just okay, just give us a call back or probably I sent over an email to your mom's email. So if you have an update or something like that, you can just give us a call back and request like a call back if you need my help or just email us instead, okay? Okay, all right, Sir Johan, thank you so much for your cooperation. All right, thank you so much. Have a good one. Take care. Buh-Bye. Yeah, it's actually it's actually 9:00 right now here in the Philippines.
41:00
Speaker 2
It's gonna be a long. I need to order some stuff, uh, before I can, I run out. one more thing. I will email uh, what we have, okay. Thank you. It was helpful. I'm gonna, I'll try my best. Have a good uh, day. I hope I don't know what your time is. I hope. yeah, well, I've, I'm, it's my almost, it's almost uh, 1:00 p.m. right now so uh, this call is about...Yeah.
41:00
Speaker 1
All right. Are you too too have a good one. Bye-bye for now. Bye-bye.
42:00
Speaker 2
The day hasn't even started really. It's two o'clock right now, so I have a long evening then. Goodbye.
42:00