Things are not working right. Um,
and you're gonna talk to Anthony,
but fix that, right? What is
this? Yeah, yeah, we, we had
a detailed discussion later on. Uh,
there was a little, uh, you
know, gap between us. So we
had a sync up. Uh, that,
that I think has been resolved.
OK. Uh, and,
and then there were a few, you know,
uh, PR raised by Anthony. So I was
just going through, um, so now, uh, I'm
focusing on, um. Getting the
latest front end and back end right or
whatever has been uh pushed to dev or
UAT. OK,
Yeah. Uh, and you're going to widen
that, that. OK, Karen. So over there,
so Malaysian, uh, we had a disconnect
in our understanding. So Malaysia
understanding was let's say it doesn't
matter how many leads you have. So
when the scheduler runs, right? So
there's two pieces to it. There's. Here,
runs right, It doesn't run every 60
seconds. There's a fixed delay, so
there's an iteration of the scheduler. So
Malaysia was thinking, so if I have, if
the scheduler picks up two leads, it
would go through the entire course of
those two leads, that is each and every
priority list, and then run the second
iteration after 60 seconds. The
new implementation, the way we've
implemented is that is scheduler runs, it
picks up, deletes, right and then it
sends it to the first available lead
and that's it. The reason for that
is because if we just, if we
wait for the first or second lead
to run its course, right?If I have
10 BPS, right, and it can take 10
minutes for that iteration of that
scheduler to run, right? So the new leads
are coming in. Those will have a day
first and 2nd that, uh, scenario that you
asked and she has also asked, let's say
I have a lead, I have a priority
list of. ABCD, right? I ring A is
active, A doesn't answer, then I ring B.
Right now, let's say A comes back,
ideally should again go back to A, right?
Because we know that A is available and
B hasn't answered. So the new
implementation is in Malaysia is aligned
relative, we all talked about it, right?
It will ring. Right. If A doesn't
answer, it will ring B. If A comes
back active, right in the next iteration
of the scheduler, it will again see A
is active, it will send to A, right?
So I think, uh, scenario wise, business
functionality wise, I think we are
covered. Malesh, you, myself and Anthony,
we can connect. Into the code and make
sure there's no edge cases, there's
nothing that we're missing. But for the
most part as far as the business logic
and the flow is concerned, we are
covered, yes, you know to malicious point
right now and.
So that I will have at least a listening
here and I will understand the thing. No,
that's that's 100% OK. We, we actually
want you to Yeah, OK, sure. That's I'm
I'm still have some Gray area which will
help me to understand clarity. Yeah. No,
no, I'm sorry. No, no,
no worries. So I got 2 points. 1
is the confirmation. So um.
So a lead comes in which
and there are five A/B ABCDE
or 12345 VPS. Every time it
switches from 1:00 to 2:00 because
somebody is inactive or somebody's not
picking the call. Regardless of that
every time it is switching between
1:00 to other. It is checking
who is available against the scoring. Is
that understanding correct? Yeah, yeah.
So current, uh, two things over there.
The model is outputting right, uh, that
hey, this lead should go to this
VPS, but what can happen is we
might get new VPS's as well. Right.
The model is not updated every day,
right? So maybe you know even is getting
a lot of business and we hire new VPS,
right? So in addition to the leads or the
VPS that model is assigning right from
the back end, we are then appending the
other VPS's that are not part of the
model, right? Because let's say if model.
Between 5 EPS and even has 10 VPS
right? So model only has data for those
five. We don't want to ignore the other
file that we have, but we will go
in the order 12345678910. Does that
answer your question? No, it answers
partially. Point here is why are we not
having updated model on the regular?Basis
what, what is the limitation there? Well,
I'll let you speak because obviously can
you know, uh, model is going to be
updated. We haven't decided that and are
you should know better. Maybe a frequency
of four times like each quarter. It just
depends how much data we have, right?
Because you would need to retrain the
model and all right. So if it comes to.
The cost or some maintenance I can
understand, but if it is just based on
some data, it is scoring something, it is
sending an input data. Why do we need
to wait to run once a month or
once at two weeks? Why don't they run
every day? I do you mind explaining that
limitation?So, uh, current the
limitation is basically regarding the
calls itself. That's not a cost and
partially, and the second part is how
much data that we are getting. So suppose
right now what I can see is we
have around 13,000 closed jobs and total
of 80,000 jobs in the data that I
have, correct. So now suppose. Every day
I'm just getting 100 or 200 jobs. So
it's not enough data to retrain the model
because model will probably give you the
same results. So once we have enough data
up at least 30% or 20% of the
data that we have currently have, there
is an increment of 20% or 30% data,
then usually we retrain the model
because. If we have less data, new data,
then in most of the cases you will get
the same results. So it will incur the
cost of retaining the model, but you will
get the same results you want. If you
want to train the model every day, we can
do that. That's not a problem. We can
just create a. If it comes with cost, why
don't we have a push?You've pushed the.
Design like every time new PS gets
onboarded right OK, I yeah yeah can can
can if you think about it let's say a
new PS is onboarded right there's just no
data for them anyways, right. So I mean
if I go and hire 5 new people right
now we just don't have any data for them
to even. But that's fine,
I they can't not get leads to
Karen's point right? Like because.
They'll be like in the last in the queue.
That's OK. Yeah, yeah, yeah, I need to be
considered. Yeah, yeah, they'll get the
chance. Correct, correct, correct. Yeah,
yeah, yeah, yeah. That's still there.
Model will only give you the VPS list
that model has data for in our back end
logic in addition to the VPS list that
model is giving. We are also checking
what are the other VPS that we have in
our database and also consider those. But
obviously the ones that model gives those
will be given priority over the over the
VPS that are not part of the model. But
yeah, we we're not saying that we will
ignore those VPSS. OK, maybe you can help
us here. My point is, tomorrow it
shouldn't happen that they have added two
VPS and our model is not even, uh,
triggering or directing anything to them.
Consider all of them even if there's no
data points because. Like it needs
to be able to handle that scenario. Like
there's any new text, there's going to be
a, you know, like that's going to happen
all the time. There's gonna be brand new
text. You have no data on them. How are
you analyzing them? There's going to be
no, like, if I'm brand new, there's gonna
be no pairing between Karen and I. You
can't just like, not consider my lead or
think I'm like, crap. Ohh, no, no, no,
we, we, we are obviously just that, uh,
we can decide, right? Like like Ayush
mentioned on the frequency of how often
we want to train the model. So if you've
trained the model on 10,000 records and
you get 100 more leads, right, the output
of the model would still be the same,
right? Correct. Are you saying we need
significant amount of data?So what
is trying to say that the I understand
the scenario that you are saying that if
a new VPS has been added into the company
and into the workforce, but still we
don't have the data for them, right? But
we don't want to ignore them, we want
them in that list. So we have already
included this case by creating a back
end. Budget. Anyways, if suppose Karen is
the new VPS, he has just recently joined
and tonight we retrain the model.
Anyways, the model is gonna put children
in the last because we don't have the
data all out of all the available
medications. Will be included. So rather
than in retraining the model without any
data. For the new VPS, we are anyways on
the back end. We are appending that list
with the new VPS as well, so we are
not getting ignored. If the new VPS is
joining the workforce, he's getting
included into the VPS list. Just like the
model will include them at the last, we
are also including them at the last once
we have sufficient data. All the BS, then
it makes sense to retain the model.
Again, if you want us to retrain the
model, we can put it on the frequency of
daily basis, but the end result which
will will be the same well. They
will be they will be added at the
last and it will cost you for the
retail loan model, we should we should
pick up a balanced approach and the
priority is there should be an alignment
between whenever VPS gets onboarded
before they start the job and when I
say job their work, they should be parked
their. Dr. employed should be part of
this model, OK. And we cannot have them
outside of the model and they they are
not getting any calls and not being
productive because of.
Yeah, they, they will get the calls if
the other VPS are busy, OK, right. We,
we're not saying like like I, so if you
add them as part of the model or you can
add them as part of the model like like
Ayush mentioned, there is no data for
that VPS, right. So as per the model
there would be last in the priority list.
So that's exactly what we are doing,
right. We give priority to the VPS's. The
model spits out ohh, right. We expect the
data to be generated if we don't add them
only when we add them, you'll get the
data for them right? So they'll they will
be added to our back end database. Now
let's say uh, I have 5 epses today right?
So I a lead comes in right You go
abcde right, it goes to. And today we
hire someone new, right? Uh, if right, a
lead comes in, model will say this should
first go to A, then B, then C, then D,
then E OK, that's what the model will
say, right? When our back end code will
run, it will call the model. Model will
say, hey, send this lead to A first, then
B, then C, then D, then E It will not say
send this to. B as well, because model
has no data for E, right? And even if
there was any data, if we were to add it
in the model like to use this point, it
would be last in the list. So what our
back end logic is doing, first it will
send to A, then B, then then then then
then F yeah. So no, no, they they are
part of the employee is part of the pool
then. That's fine OK, but point is they
shouldn't be outside just because they
just joined. They they can
care, right? They will eventually be
right if we decide, hey, we want to train
the model on a quarterly basis, right. So
each quarter you know any new apps that
are coming, those will become part of the
model, but they are part of our back end
database, right. We already have logic in
our back end. Hey, something that's not
part of the model still consider all the
other VPS that Evan. This and append them
to the list as well.
Right, yeah, so the the the logic is it
model gives me ABC DE, right? Our back
end code will check apart from ABCDE,
what other VPS is we have, right. If we
have FGHI, what our back end code will do
is it will append FGHI to the list as
well. So it will first go to a. If
it doesn't answer, then B, then C, then
D, then E, then F, then then G, then then
H. OK,
Yeah. So yeah, yeah, yeah, yeah, yeah.
It's all considered, right. It's not
that, hey, any new one that comes in that
we, uh, they're not gonna receive any
calls. No, we, they will receive calls.
But obviously if you remember what Luke
and Matt said, hey, we want the best VPS
working the most, right? If any best
state comes in, give him. Delete, Right.
So that's it. That's all those things
considered. That's why we have this
information. So you have to have
something. OK, yeah, yeah. So question.
Code right, Malaysian Anthony yeah, OK.
Uh, the, uh, the VTS is new.
He will be part of the call
routing algorithm. So yeah uh, only thing
is that, uh, to, to train the
model again, uh, there should be a
reasonable chunk of data for that BPS
to train. Then again, yeah, and Karen, I
can show you that test case as well
because I know she has a question. So if
you see over here. Yeah,
yeah. So Karen, if you see over here,
right, you see as per the model, model
gives me 4 priority list. 1234 model does
not give me Dale Chaotic, right? But what
happens is it first go to test 9,
then test 6, then test 3, then test
2, then it goes to dance.
So we already have this list. The model
is giving me 4 BPS, but in the database I
have 5 VPS, right? So it will go in and
order first. It will try to follow the
order that model gives you. If none of
those answered, then it will go to other
VPSS that are not part of the model.
Makes sense? So all those things are
considered and then let's say. Uh, each
quarter we retrain the model. Right now
we have data for Jane Sharrock, right?
And you know, Dane comes in new and he's
been killing it, right? So Dane might
trump increasing test 6 or, or, or
something like that, Yeah.
So Are you sure the question and uh, she
has also had a question, so.
Says Do you wanna go first?
Are you are you on mute? I think?
Yeah. So based on my limited knowledge,
definitely I understand that without
having the proper enough data, more
training the model won't be that much,
uh, outcome have. But then yes, uh, same
time the question from the Kieran, I
found that one as well. So, uh, uh, what
is the logic and how we are making?
Sure that only the register VPS are not
getting call. And definitely you
mentioned it's there, but then, uh, uh,
what if, let's say those, let's say one
of the area, we have the five or six
VPS and they are pretty attentive and
they are receiving the call. And there
are the new VPS who are willing to take
the call, but they are not getting
because. Register VSR addressing so the
the new apps won't get call. That
means they won't be able to generate
the data and then how? At what
stage? How much data bulk data we
need at what stage we will decide
there to pull them into the registered.
Uh, pool or maybe or create the data for,
create the OR train the model for them.
So if you can answer that part, uh,
that's, that's a very broad question,
right? We, it just depends how much, how
many leads we're getting once we go live,
how much data we, we have. And then we
can decide on the frequency. Maybe we're
getting a lot of leads and we can decide,
hey, maybe we need to retrain the model
every two weeks. Versus every four months
or three months yeah so that's a good
question but it just depends on how much
data we have and how much significance
actually watch race is asking so suppose
Assad, Kiran and Ayush the registered VPS
who already have the data in the back
end right model is trained for these
three people now suppose. Not just
one, but Malesh, Shreyas and Anthony,
these are the three new VPS, right?
There might be a case where you
and me are always active or always
free and they are Shreyas and Malaysia
and Anthony. The new apps are not
given getting the new. Jobs
are fine then how they are gonna generate
the data? Well, so that's why I raised
the hand as well because this this might
be the edge case. Exactly. It's an edge
case. And eventually that can happen. And
you know, if nobody's gonna take keep on
taking calls, they're gonna get so that
if you, if you guys remember, I think I
should have part of that call with Luke
and Matt. They made it clear we want the
best VPS working the most, right? If he
gets tired, he can. Himself as active,
right? That's why we have VPS, that's why
there's this whole thing of queue, right
and. And you know, if we think
hey, we have inner VPS, why would even go
and hire other VPS if we have 5 EPS and
we don't we're not getting that many
leads, why would even go and hire 100
more VPS's? Hey, but then that will be
that will be the latter stage after
adding and realizing that OK for a month
or 4 to month, these new added VPS are
not getting call. Of the existing VPS are
enough after some time we will get that
idea no, no no not not not not you you
would know that hey I have 10 reps right
now we would monitor hey how efficiently
are we handling the queue are we getting
more leads or or how much is the wait
time right they don't need businessmen
make that decision to go and hire new VPS
so if you think about it if. Only 10
leads can we just cannot handle the call
volume right now. Then only business will
go and hire more VPS, right? Like no one
has money falling from the sky. They say,
hey, I'm gonna go and hire him. This guy
first demand comes in then only you would
you would get a supply to support that
demand, right? You're not just going to
go and hire hundreds, right? OK, if that.
That is fine. Uh, other thing after how
many uh, calls the new VPS got in terms
of the data is generated for that
particular person and then when we will
start, OK, now this is the I I don't
think there is an answer for that. OK, if
you're just yeah, exactly if you want to
go that nobody can. OK, So that's
an open question. We need to come
to an answer. But one second question
I had, um Malaysian Anthony and if
the call gets disconnected, so certain
lead comes, maybe I'm the call goes
to Ali and during the conversation call
gets disconnected by some technical.
Reasons. What happens next?
Umm, we, we talked about it when you say.
So, uh, Kiran call, will you, we send
the notification to the VPS, right? So,
and then what happens is once you take
the call, right, your status is set to
busy, right? If let's say you're calling
from your iPhone or something like that,
your connection gets choppy. So it's. Up
to that VPS to make sure he calls
the customer back and his status will be
busy up until the job is completed or
cancelled. So what if he accidentally
closes the tab?Well,
if he closes the tab but he's not
connected, he's not calling from his
browser. No, no. But what if he
accidentally closes the tab? He needs to
get back to it. How does he do that? What
do you mean close the tab?
VPS closes the entire window of
delete. Log back in
and it would be the same status. It would
and it would still be there. Yeah, Yeah,
it would show that exact item. What if it
doesn't? I mean, is it a practical
scenario? I know it happens only 1% of
the chances. How are we going to
reestablish the connection with the field
guide? So that's the point here.
So when the notification goes to a
VPS, right? So yeah, uh.
I mean, when you say uh, he will
get disconnected like Ali mentioned,
probably he will accept it and then he
closes the browser, right. So in that
case that lead, uh. Will
be. You know that that VPS will
be shown as busy, right? Once again
he has to open up the tab
and proceed further. Say
that because now the the objective is to
serve the lead, right? Yeah. OK. Are you
saying that now gets dropped?
It will be in progress because he
accepted. I think I can answer Karen's
question. So Karen, you're saying that if
the call gets dropped, Yeah. So there's
no integration right now, so they would
simply just have to call them back on the
phone.
OK. We are not building
system for that. I'm just just no, we
don't have any way to build that right
now. Yeah. From this
perspective, yeah. Yeah, I think, I think
that lead, uh, is in progress.
But yeah, if you want to
handle this scenario.
Yeah, it connects people. Even if what we
can do is, is as far as the
admin portal, we can see, hey, if someone
is in a call, why are they in
a call for such a long time?
We have no way of knowing when they call
the person.
Yeah, yeah, right. If you see. Hey,
because we we, we, we, we know what time
the call was received. We know what time
he accepted the call or the notification.
And an hour later it still says that he's
in the call. So we can maybe ring that
technician. Hey, why are you still in the
call? Did you close your job? Did you
forget to close your job? Yeah, there's
all these things that we can do.
OK, I I think during the testing there
are many other scenarios which will
surface, or maybe you need to closely try
out different combinations. You need to
write extensive test cases for this in
all scenarios, not just the happy path
right now. OK, that's fine. So what is
the next step?Then you have
implemented the core implementation. Now
you are going to stick with the front
end code. Is that correct?
Yeah. So we need to get the latest,
uh, UI front end and back end, uh,
can get that, uh, uh, working in our
local and then whatever we have
implemented. Who who
can help here? So who can help
uh, point of contact wise? Yeah yeah,
I'm in touch with both the front
end and back end guys. Front end
Palani and Tarun back and Ayush and
Ramesh. I'm in touch with them. OK,
And what is the ETA to complete?
Side integration.
Um, or at least efforts. How many?
How much? How many days? How many
hours? Yeah, maybe by by Monday or
Tuesday it should be good.
OK, three days of work, they're saying
OK. Um, so for
the next three days, both, uh, you
and Anthony have sufficient work in this
regard or anything else you can pick
up?Uh.
I will be.
I know you are focused on
the integration.
Right. You are focusing
on the integration with the front end,
right? You are coordinating with the
front end developers on making sure the
API's and all that stuff, correct. Thank
you. Yeah. So Anthony I think
has bandwidth when it comes to, well,
he's working on automating those testing
and all, but I think Anthony has
bandwidth. He can maybe take up some new
tasks related to call outing. We can, I
know we talked about it. If it's too
early to talk about what other
enhancements we can do apart from core
Logic, No, hold on. Before you
go to announcements, um, Sundra or Sarah,
do you mind?
Sharing JIRA board, I want to see there
are 5 or 6 stories we had identified
a month ago, right? Sydney complete all
six.
Yeah.
The managing associate before, do you
have that handy?
I don't have that Andy, but I have, uh,
all those things that have, uh, are there
or on JIRA board, OK, Can you please
share that?
Yep, I'm sharing. Hope my screen is
visible.
So these are
123456.
OK. And seven OK, um listen that
I need your help. OK, so tar
is not receiving the call league both
leaves receive the calls and you have
seen the demo right other day from
Malaysia and you also heard the update
from both Anthony and Mallesh.
Looking at this, uh, tasks stories
here, do you think any of
these seven stories is pending or
you want to, uh, take a
status?
Yeah, as per the demo that
day where Malesh came according to
that here I think it is
working fine even the call routing
first one. Yeah, can you please
explain the the description of this?
Those that that both teams received the
calls and this is also taken care.
I guess yes, that's the wrong person.
You know it better, um, on the
torch app after torch needed accepted
Paul, what is the description here?
Could expand. So could you just scroll on
the description? Yeah, over on the
description.
The same person since appeared with the.
I think Monday should have taken care of
this of this, right?
It doesn't appear now. OK, OK. So
the only thing is we have seen
for two VPS we have, we need
to see for multiple. Maybe these are
something you need to help. OK,
invalidation. Right. Yeah, I,
I, I shared those scenarios with the
shares as well. OK, OK, good. Can you
please go back to the list, Um, Saurav?
Yes, Kiran. Uh,
production issue? Torch app system
glitched out? What was the the
description here?
The torch member accepted lead, but it
was blank for the torch lead. Later,
duplicated duplicate leads were created
on Service Titan for a single lead and
there was no data. I
don't think we have verified validated
this after the new implementation, have
we Malish?
Just reading this SO.
OK.
Was long for
sleep. I
think, uh, uh, this is during when
the service item, uh, goes offline or
service station goes down maybe, well,
we'll verify this. Yeah, I mean, as
part of the unit testing, please verify
it and says ultimately you're going to
look at acceptance data about all this.
And if you need more details, please
take help from Ali Assad just to
get more understanding against each of
these. And Rosandra. OK, next one. Again,
access have was provided so I can
be able to go through the description
and everything. OK, OK. Which is the
fifth one?
Um did not go e-mail
also. Outside, but
they generate a lead in service at all.
This kind of bypassed. Again, this needs
a validation right Malesh, this is
something I don't think you could
validate. Uh, need did
not go through talk chat. OK, need to
validate this. Ohh, yeah, this one was on
production only. And then Kieran like,
uh, we need to do uh, like testing
with multiple calls. So then only like we
can give you the functionality assurance.
So it's working as expected with one or
two. It's like.
We are going to have that project
yesterday. Prior to that it's really
just. You should do
one or two calls and you're just hoping
that will work on multiple projects, but
this time onwards that is the reason
because that's going to help us. We have
recorded languages to validate we don't
have or have the ability to.
Those are the things we are going to
validate more and whatever we need to
establish that record project for the
document that in that wizard or somewhere
in there so that we can do all of that
at once. And then really all we're doing
is copying the CDN. And
so I'll be able to, after refreshing the
page, the details became visible again.
Source. It's like itchy. This is also
something you can validate as part of the
testing. It's great to see it all night
and yesterday. So we'll just start with
you, Devin. OK, one thing then the
implementation as part of the unit
testing test test. For the the language,
yes, we still have the languages.
Sort of, but I think it's still in
the new UI Now we are doing that.
But um, OK, I'll set up yes, we
just have it for the rest of the
languages. The last one, yes, I'm still
working on the offline mode list. Right
now I'm working on restoring the Plaza
and reward store. Ask
for close jobs, delayed call
initiation, duplicate lead assignment,
and early dismissal of call
pop-ups. Move on to the
the other thing, like the
languages and the SO1. Healthier.
Maybe one or two are kind of
overlapping. Is it possible to capture
evidences for the unit testing whenever
possible?Yeah. I
don't want, yeah, I don't want it
directly goes to Q and they start doing
the testing. OK. If you could do that
at one first round foundational level of
testing, then serious then do the impact
testing, right, right, sure. OK. Yeah,
please capture that.
Yeah, I'll just do this with
the latest, uh, UI. The background
makes sense.
Yeah, Yeah, yeah. So you, you need time
to access that maybe being able to come
get to RC, what is that? Yeah, yeah, get
to Anthony and continue on the UI
implementation. And if you think that
some of the tasks which can delegate, I
mean given to Anthony, please let us know
if you can complete by Monday, that would
be great other. Yeah.
Yeah, we will let you know Anthony, the
next 1-2 hours, I'll, I'll figure out
something for you so that you will get,
uh, some tasks for you.
OK. Yeah. Thank you. The last one lead
calls are being received. This is did we
go through that?The
net. What it
says ready for QA lead calls for
jobs that are already marked as closed.
OK, let's see.
Comment for this text SO issue which
was according to the self mentioned
description job description job is closed
and service Titan. Those jobs will not
be routed to torch member. In our
current implementation we are routing
only lead jobs. Ohzora
by think this issue they have fixed it,
but we need to test it. So without the
NDC adding, does that mean we are unable
to test it? We should be able to get an
error code back to these API requests
anyway, so we'll be able to distinguish I
think in most cases between just like a
400 error code or so. You know, uh,
research down before I 500 error codes.
I'm back for Anthony.
Do you have anything in your mind which
from the, the so-called implementation,
yes. And the two things, yeah. Anthony,
I'd say continue going through malaise,
uh, review the code Malaysian Anthony,
please, please review the code. All these
scenarios that we just talked about, make
sure all these scenarios and edge cases
are covered. And as Karen mentioned. Make
sure that you automate or test your code
as well, right before we pass it on to
the QA, right? We want to make so
Anthony, as much as you can automate. I
know that some scenarios are difficult to
automate, like that one scene that we
talked about yesterday where you have one
lead, then a new lead comes in. So make
sure in the meantime, just go through the
code, make sure there's no bugs. Nothing
like that and have solid unit testing,
right. So Karen, I think we we
can still keep busy, right? We can
still continue refining the code. Malesh
had really good comments, right state for
implementation. That's exactly right.
Yeah. But my thinking is I think
we should as soon as we have
the new UI. Right, Uh, if Vasundhra
or Shias, you guys can prepare test cases
from the new UI. So Shreyas, you've seen
the PowerPoint, right, that Anthony
shared with the five test cases. Those
are from the back end only. If we
can create test cases, right, relating to
those ones, what happens when I have a
single lead?What happened when I have a
multiple lead? What happens when I have a
different priority map for all? What
happened when I have the same priority
map? We can have the test cases ready. So
we know, so Kieran knows how many IDs we
would need to to do those testing, right?
And so let's say if we want to do
multiple testing with multiple VPS and
all, it takes time, right? We solved for
Group One to set up those. I's all that
stuff. So Kieran, you can start that
process behind the scenes, smart way of
doing that as that I mean 1 is
very basic. OK, can we make use of
some tools? That's my question.
For these kind of scenarios, can we
make yourself some tools to trigger
multiple calls in a sequence and the
gap in between the some kind of
scheduler?Yeah.
So, so you are talking about having the
multiple leads, uh, that will get pop up
on the Torch app and then the multiple
user can respond that part correct,
Correct. Yeah. So, yeah,
so yeah, yeah, so, so the same script
with the different user, different thread
at the same time, we can generate the
multiple lead and then on the UI of the
torch lead, uh, we will log in with the
different user and then they will, we
will control the flow who will accept,
who will deny, who will sit idle and
something. And that definitely through
the parallel exhibition we can achieve
that part, OK? Uh, more technically wise,
if there is anything we can, I
can check that part and find the
solution. OK. And that's what's possible.
Yeah, that's what we are working on.
Uh, you know, we'll be having different
browsers. For a different session, right?
Like we'll have one Google Chrome
browser, one Incognito window for two
users, and then again Safari and then
Edge. So we'll have different browsers.
For different users. So that's
the real time, uh, scenario.
Yeah. So like last time.
Well, sorry.
Yeah, so like last time, as I mentioned,
I have completed the, uh, NDC form. Uh,
unfortunately green light form is still
not available, so I couldn't proceed
there. But that flow is done so I
can have the parallel execution from
different, different. Currently I'm
focusing on the iPad 16 Pro, I guess.
And we'll have the multiple lead
generation, OK. And then ultimately once
that is done, so it will get
notified parallely on the Torch app, on
the UI handling data, I will have
the multiple sessions open on the
browser, OK, So right there.
Users and they they will accept deny or
on hold anything. So that is the plan
as of now. And then the blueprint is
with me and we discussed with the
Malaysia. That's awesome. This one trying
on the move. Any any thoughts on this
round a little bit too to make it
right?You know what you're going
to do and then I can check it modeling,
right. So if if you automate your green
light, that's right. Anyway, if you use
the same green lights for let's say you
basically and it's the exact same
details, sometimes it's a possibility
that your model will give the same score
and save everything for that graph,
correct? And the we would not be able to.
Where I think it would be nice if we
can have multiple versions of your green
lights form, right? Maybe one with, let's
say that everything is yes, one bit so
that you get different forms so that we
can get different leads with different
scores and we make it as I know it's
a little tricky, right?We just pop
around, you have to have a function for
the way that I've been like formed with
this score, right? So that you also know
that this is the best lead that you're
generating, this is the second best 1, so
forth. So if we can look into that, I
know I'm not saying do it from the start,
but that's one key piece that we have,
right? The model piece, right? If
everything is the same. Then we will get
the same score. So it will almost become
a first in first out. We we we don't want
that. We want to sit. OK, OK, I
unfortunately I couldn't play around with
the green light form 8 because it's not
available. So you are you saying the
whatever the values and permutation
combination for the form fill up that
should be different, different that. With
the Unicode exactly when it does, we'll
try it out. That will be the real
scenario, real time scenario, correct
functionality. That's and then I right I
move based on the. Down so
you can scalable radio button until
you index yeah.
Right, we probably need to do that, Yes,
that can be parameterized instead of
sometime maybe the value, sometimes
select the value B and then different,
different Dropbox and then the thing that
can be done easily. If this
is done for you. I
want to ask the Kirana Vasundhara
specifically. So since this Vasundhara
unlocking manually from long time you
held the functionality. I'm sure there
must be the test cases written across
the bug or maybe the user stories
as well, because after some time if
we go back and find some. I
guess we should take we won't remember.
That's my experience. We won't remember
the edge cases. Some of those are pushed
off. I'm sure if we are having already
test cases associated with the video
story or the bug test, it will be
easy for us to pick a particular priority
based test cases. Do we have those
discusses available? OK, every user
stories or bug and did you so the Rockets
studies we have the crappy machine. Could
you check the chicken?
Umm, OK, because sometimes used one bugs
give us multiple thought processes and
based on that we can have the
different H cases and we can download
these cases return and that will be
useful in the future, which essentially
for the automation type, otherwise we
won't remember. Because I wasn't able to
find out those cases. So if we can do
that, please, that will be good.
Yeah. Like where the trainer was
duplicated, I think may have been
affecting, well, obviously those
scenarios. Everything seemed a
lot better. I was doing them, I think,
Matt.
Which also makes a big difference.
Cases also can be covered with
with modification in the existing.
And then I'll just go back and check them
all again. And there's just
like there's anything obvious before we
send them to Wayne, OK. Once that is
done with, uh, Pauline, yes, yeah. So we
will focus on five or six scenarios, but
as Kiran was mentioned, because this is
the finding option. What?
Matthew Sleeker.
I've just been poking around with your
DLP USB blocking setup what kind of been
digging through the docs.
But I've been investing all that. I still
need a little more time to look deeper
into a couple spots because some of it,
yeah, it's kind of hiding behind the
menus.
Yeah, yeah. It's hard to find all the
patterns like this.
Yeah, we, I think we should both sort of
take a look when you find things like
don't implement any policies, of course,
yeah. With these, but we
have to see exactly what's going on. You
know, what I thought we might do,
Matthew, is we have a representative at
like an Azure contact at Microsoft. Maybe
we should have a meeting to just sort of
talk over some of these things or have
them give us a little, you know, overview
of what we can do. Would that be helpful?
Uh, yeah, obviously, but just after
I I've got enough knowledge on
that.
That would be good. So you that you have
questions. OK, Yeah. OK. All
right, Well, I'll reach out to him today
and see if we can set up a meeting
for, you know, a week or two from now
after after Thanksgiving. We can do it.
All right. Yeah, that sounds good. OK.
Um. Yeah. And where
so we ohh, you did this obfuscate data,
so can I how about the the UI
stuff for the MFA? Is that on? Is
that up there now?
Think it's not pushed yet? A
perfect thing. I can get it
pushed today, sooner or later.
OK. All right. Well, I'll look at it all
once you get it up there.
OHK OK, Thank you. Thanks.
All right, great.
All right, Matt. Um,
so we're working on. RSR
single instance and style bracket make
sure that all the animations played
through. I did talking animations for the
2 directions.
It will have the machine resources
notification issues and it will give
the wrong impression that OK issues.
The IT based apps, some some GP and
you're you're gone somewhere you can spin
off. But yeah, I mean, I don't know what
time, but The thing is I may work on like
in the morning. My
daughter's car from the shop and
I'm waiting for this camera can
be done, but again through Jmeter
performance brand new red. That's simple
particular area performance testing will
fulfill that need and then the.
Anything. It's DJI.
Bump up, it's under the professional
cinematographer type, Practical amateur.
It's OK then users are coming
in, call getting tagged to write
ups or not. We go and
make the third scenario. Third replaces
inactive. Will it switch to 4th
1?Yeah, right. Yeah. So that's
what Malaysia and we were talking that
OK, we will have the maybe 4:00
to 5:00 to 6-7 different user, uh
available and interacting with the
different, different combination and that
will that's what someone will go through
the this browser Firefox. Sorry, ignore
Incognito and everything. So 10 user,
let's say 10 user, if we are launching,
doing the lead creation and on the torch
also we are creating the 10 user handling
those, uh, leads. We can check how, how
they are handling because some couple of
VPS should be sitting idle the third
wheel. Accept or decline. So that
combination for that combination we will
need 5 to 6 or maybe 4
to 5, uh, different user, different
browser, uh, sessions already. So that's
the way we are planning. Yeah, yeah.
So there is a, there is a,
there is one more option here.
This like in the the Chrome
using the same browser itself we
can have multiple sessions something here
OK yeah so so we can
achieve that probably same browser
multiple session or different browser
different session but given we will
not be worrying. One API load
testing, uh, so no, I'm I'm not
worried about this. Yeah. So those are
all different areas, yeah.
Logic is working or not. Yeah, yeah, that
is more important, right. So super
important, right, right. So we can start
for they're not giving it for Amazon or
Flipkart, right. Like they're exactly,
yeah, it's not like like Uber.
You did? Yeah. No, I'm gonna tell you
this. We we need to do a little
load testing as well. But we'll take it
that in the later stage. But for now,
we are more focusing on validation of the
logic that that's the total flow. Yeah.
But first tell me this Malaysian Kieran,
how many?ID's we have
in UAT for VPS and how many
ID's we have for technicians so we
can have up to how many we
had Sandra with the we had 6
or 8.
Uh, you mean whatever we are
using OK, yeah test accounts. I
think I think we we as
of now we only have for
technical uh technical uh sorry VPS
4 out of which one is
not working for sword, so we
only actually. Knowledge 2 are not
working, so, uh, to answer Assad's
question, so Assad totally for tech app
and torch app uh, for the tech
technicians and the VPS, I totally we
have around 9 alright. In that for
VPS, we have around 12344.
Accounts. So in that actually, Kiran, we
need UH-2 test accounts for which uh
yeah, we need more about this purpose
only. I mean, generally they are not so,
um, user accounts, but in this scenario
we can say that call routing needs more
test accounts for the validation. We need
more, otherwise we cannot validate. We
can. Just for that case, yeah. And
Kieran, one more thing for, uh, the
currently we're having 4 right for VPS.
So in that we need for two accounts, we
need uh, password reset to be done
because they're not working.
OK. Is it?
What is the yes, yes, in finishing we're
going to retire that sort of OK. We are
not going to renew that. I mean those
ID's will have a new accounts, new test
accounts, Yeah, there should be no
mention of anything, right, Because we
did all the hard work. Yeah. Can you tell
me this and I'm not even.
Yeah. How many VPS's do we have in prod
today, do you know? I'm just thinking the
worst case if I have 5 BPS.
30 FPS, OK, 30 people. I, I believe
that's what I have for some of the calls.
Yeah, yeah, yes, even in the meeting,
that's what I heard. Kieran 30 yeah, has
been for VP and AYUSH, from your data
profiling, how many lead jobs are
submitted, not including call routing,
because this does not include call
routing. Typically how many lead jobs are
submitted a day. I'm just thinking if we
want to simulate. Election like loads
like prediction like scenarios, if we can
maybe do some something similar to that.
If I have 30 VPSS and how many lead jobs
are coming like how often a queue forms
are you, do you know on top of your head
typically how many leads are submitted in
a given day?And no, I, I
have to look into the data for this one.
I don't have this handy. Yeah, it would
be nice to know so that we can also
simulate something like production. Like
if I have 30 VPS, I have these many leads
coming in during the day. How often
there's a queue form, right? Because we,
we would have to check our business
logic. We want to make sure that the
queue is not forming for too long, right?
If I'm getting. 530 VPS, I'm getting 100
leads. We're confident that we can easily
handle it without a queue forming. But if
I'm getting thousands of leads and I have
30 VPSS, right, with the new logic, we
can get some idea, hey, maybe the queue
might get too long. So it'll be just nice
to yeah, these are all things that we
will do close to the prod release, but we
just nice to know how many leads are
coming during a day. Sure,
I'll get back to you with the number.
Hey, I do have to drop by 10 question.
Question for you. Are you aligned on the
business logic and everything that is
implemented? Basically it will ring
right? We will check if a lead is less
than 10 minutes old, we will check the
score. We will check the priority list,
we will see. For other apps that are not
part of the priority list, append them
ring, find the first available
technician, ring it, and the loop will
close. 60 seconds later, the scheduler
will run again. We will see if that lead
has been answered and we will again
compare with what other leads we have,
right? So I just want to make sure that
you and Allie are aligned on the
business. On the yeah, on the happy
part is concerned, I have seen it and
it is a good progress, OK. And those
are the fundamental primary glitches
which had observed those have been fixed
based on the demo what I saw on
Tuesday. But do I know all the scenarios?
No. Ohh, yes, yes, yeah. And thus, does
anyone on this team know all the
scenarios? No. OK. Because only when we
start testing, there's a lot of
permutation combination here. Yeah, Yeah,
if you think about it, yeah. But so,
yeah, very good progress so far. So where
we were a month ago or six weeks
ago, but I feel job is only.
Ohh, yeah, yeah, Right now we've only
been testing, simulating and all, but
this is good progress. I know we were all
over the place at first. We were like,
what to do? So I think the team has done
a good job, but I think continued testing
and testing is the key, right? If they
can. I mentioned there's a lot of
permutation combinations. Like if you
think about it, so far we've been
creating. The call routing model as a
black box, right? So I don't know what
testing we can do for Ayesha's code,
right? I mean, I guess we just trust
Ayush will give on that. Yeah, I just
help. Yeah, yeah, yeah, sure.
Problem on that part. So basically you
know something like load testing, what
happens if we call your API 10 times,
right? We want to make sure that your app
does not go down. We wanna make sure that
it's giving the correct output each time.
We want to make sure. So if we can do
some load testing for the call routing
because that's a separate service. Again,
not right now, but these are all the more
we think of scenarios. Whenever we have
these things ready, we can start thinking
through it. And I think we actually asked
here, she has, hey, not everything we can
automate, but as much as we can automate,
the better.
Sure. This is going to be interesting now
because we will. I mean, everybody needs
to participate, everybody needs to ramp
with their own suggestions on scenarios.
Not being everything, right, There will
be some scenarios. Some suggestions need
to come for Sundara Vishwa. I mean,
I need your. Uh, yeah. Which was
very quiet these days, I've noticed.
Yeah, he's been busy in other black
background. Something is deployment. OK,
you've been in other tracks, but let's
get started. OK. To
summarize before we drop, you'll continue
on the UI implementation, UI integration
rather we're going to take, I mean
you and Anthony collectively will run
this and peer code review needs to
be done. Please go ahead and do
that all the 8. Police are tasks
which are written in. Take a deeper look
once again, see if everything is in
implemented, taken care as part of the
code A capture the unit testing evidences
wherever possible, record it somewhere.
Whether it's a Word document or Excel
document, anything is fine. Or in the G
writes you can do it. That is great.
So let's, let's make uh, March towards
completeness of the work. OK, once
everything is ready from the unit testing
almost says support, OK, we will, uh,
we'll see how the integration testing or
the logic testing will be achieved in.
Can you share the new Figma designs?
With me for the new torch app
and other access the asset.
And As for the new, uh, Torch VPS,
Kieran, I think uh, Ali has not yet
confirmed on the new UI desktop view for
the VPN. I think probably she'll do it
tomorrow. Asal, I'll keep you posted on
that. If not, if you, yeah, just keep me
posted. I wanna make sure that, you know,
everything is covered. It's not just a
copy and paste of the old. And if
anything new we can add, given, you know,
if we want to do what we call, uh, like
Karen mention, right, how long you've
been in the call, all these things. If I
can get the new Figma as well, I'll make
sure that it covers everything And we
have all the back end stories to cover
that as well. So there's, yeah, as soon
as you have it sorted or currently share
that with me, OK. And maybe we can go
through it in the next call. OK. Yeah.
Thank you. Hey, I'm only tomorrow. Please
stay back after this call for two
minutes. Yeah, I am off
tomorrow, but I will be available via
Teams if you need me. OK. Thank you all.
Thank you. Thank you. I have a drop a
message for you to provide the Word
document for the scenarios, if you can
share that one. Yeah, Yeah, yeah. Let me
drop it in the chat right now. Yeah. OK.
Before you drop off. Uh, can you stay
back for just two minutes? I need to
discuss something with you. I will, yeah.
Couldn't even meet.
Yeah, I will. Yeah. OK.
Yeah. Thank you. Thank you.
Thank you. Thanks. Bye. Bye.
Thanks.