- Duration: 27 min
- Platform: zoom
- Source: Read.ai 01JF8BFKX0Y1WAKG7FQA0YR6T0 (https://app.read.ai/analytics/meetings/01JF8BFKX0Y1WAKG7FQA0YR6T0)
Transcript
[Ben Ornstein]: Hey, what’s up? UNKNOWN_SPEAKER: How’s everyone doing? [Rafael Bruno]: Pretty good. [Ben Ornstein]: Yeah, same, doing good. [sid]: Oh, there we are, Rafael. Michael Houck: I see you. Cool. Okay. Anyone got any interesting weekend stories or should we just jump into it? What do you guys think? UNKNOWN_SPEAKER: No, no interesting stories. [Rafael Bruno]: No, just normal weekend. Michael Houck: I spent my weekend booking a bunch of travel for the next couple of months. So I’m going to be in Brazil, Rafael, the country, I think Argentina and Chile and then Texas when I get back. [Ben Ornstein]: That’s awesome. [sid]: Are you visiting for work or just some other reason? No, just to travel for a bit. Michael Houck: It gets cold here in New York and I don’t want to stay here through the winter. UNKNOWN_SPEAKER: Okay, nice. [Rafael Bruno]: Same behavior as birds migrating to the south. Michael Houck: Yeah, I’m just a bird. I guess. Yeah, so you guys will see different backgrounds in like, I guess two weeks, starting for two weeks for a while. But okay, let’s jump into it. So let me share my screen. Okay, so we’re doing pretty well. This sprint, we’re a little bit behind where we wanted to track, but we also added some stuff So we’re actually on like a pretty, pretty good pace. Um, obviously we want to hit everything, but pretty good pace right now. Let’s keep it up this week and have another, another good week. Um, so let me first go to, uh, Rafael, since we were talking this morning about a couple of different things. Um, can you give us an update on where everything’s at? Um, most importantly, the engagement tracking, but also everything else. [Rafael Bruno]: Okay, so the first thing here, fix the issue with max budget per amplifier. I just need to check something with Mehul and then I can mark that to done. About other tasks that I have in progress, same thing. I need to either check with Mehul or check with Rizwan to mark as done. And regarding the task of checking the engagements, I’m working on that. I’m checking some logs that BreezeOne shared with me. And today I will probably have some results to share with BreezeOne or you to update the situation. Okay, cool. Michael Houck: Keep me in the loop with how that goes. Other stuff, I think my hypothesis is that most of them are pretty small except for maybe the one we were talking about with the scraper. So if that’s the case, just let me know. Maybe we can add some more stuff into the second half of the week depending on how quick this stuff actually is once you get into it. Okay. Okay, cool. Rizwan, you wanna go next? [Rizwan Hameed]: Yeah, sure. So basically, you know, It was a tough week, the last one. And yeah, so we missed a lot of engagements and Rafael shared the details with me as well. So I investigated it into a deep details. And then I shared like, you know, most of these situations, Scrapper is passing information to the API. So I shared all the details like the events that I’m receiving and the API payloads that I’m logging on the Scrapper site. So I have shared that with Rafael. I’m just waiting for the feedback from his site. And other than that, I’ve already working on the, the running two bots in the same machine. So other than that, like, you know, three accounts, two accounts are down from the accountify site. And I’m still like, you know, constantly in touch with them, like, you know, pushing them like, you know, either they should fix the accounts issue or they should give us some alternate accounts as well. But what I did is like, you know, I, as we left with the three accounts of the LinkedIn, so I know, like, you know, using one account in two machines so far, and it’s working fine so far, like for the post engagement specifically. So like, you know, one LinkedIn account is running on two machines with same IP, same credentials and stuff. So if that until they come back, if they thing is working fine, then we can reduce the accounts as well. Michael Houck: Yeah. I mean, we’re paying for the full five right now. How long have they been down for? UNKNOWN_SPEAKER: Yeah. [Rizwan Hameed]: So like, you know, it’s been like a while, like it’s been like more than a week. If you check the Slack, I’m constantly like, you know, pushing them, like, you know, when this will be updated. So they are also like in the waiting situation right now about the accounts, verification stuff. Michael Houck: So aren’t they supposed to, isn’t, I remember when we signed up with them, they said that for each account that we buy, they give us an account and they also have a backup account ready to switch in for it. [Rizwan Hameed]: Have they not done that? No, basically, uh, for one they did, but for other tools, uh, that those are still in, uh, like in the pending situation, if you check the channel on the Slack, you will see like, you know, my messages I’m on daily basis, I’m pinging them, like, you know, either give me the alternate accounts or fix these things. Yeah. Okay. I’ll jump, I’ll jump in there after we have this call. Sure thing, because it was taking too much time. So I just started like, you know, using an existing account for the same machine with another machine. And luckily it’s going good so far. And if this goes longer, then we will not be needing any more accounts from them. Like, you know, we can keep using existing ones. And even though we can reduce the accounts as well, if this goes works very well. Cool. Okay. Michael Houck: Um, obviously you have a ton of stuff in here that’s, you know, some of it’s quite large. So I imagine we’re not going to get to all this, this sprint. [Rizwan Hameed]: So the first one, if you see I messaged her or feel like, you know, is there anything for the fixed engagement thing? So is there anything to do? Otherwise I don’t have anything to do on that part for the first for the first ticket, which is 1069, mega 1069. If you see like, you know, I tagged a field today. And other than this, if you go to this, like, you know, the second ticket, which is 1100, yeah, this thing. And so I’ve done two parts, like, you know, remove the extra delays and reduce the random delays as well. And then I updated the whole logic of of the engagement URL, like getting the engagement URL. That was taking a lot of time as well. So I improved it and implemented it as well. So it’s working fine and it’s quicker as compared to the previous implementation. Michael Houck: You’re making me wonder if there’s things that we can do later, right? So if things are taking more time in the moment, can we go back to that engagement and look later rather than trying to do it all at once so that we can save time. Like the engagement URL, like we don’t need that right away. We can have it check like, you know, 12 hours later, 24 hours later, whenever it doesn’t really matter. [Rizwan Hameed]: So. Well, if, if in that situation, like, you know, what we can do, like, you know, I’ll need some input on the firmware fail as well. Like, you know, we can just request the engagement URL in the late events, not in the super fast or in the time events. What do you think about it? Michael Houck: Yeah, yeah, yeah. I guess that’s, I guess that’s a good way to do it. That way we don’t have to add like extra stuff. Okay. Let me put some thought into that. Maybe there’s other data too. I’ll send you a message about that later. [Rizwan Hameed]: We can take that offline. Sure thing. And these, these were the two updates that, which I have done to improve the speed. And yeah, so right now I’m working on the other third one, which is like, you know, like running the two bots in the same machine. So it was, it took a lot of time because there was a lot of going with the post-engagement stuff. So that’s why like, you know, that has a much higher priority. So I announced back to the sticker. It makes sense. I’m just asking about these other ones though. Michael Houck: Like, are we going to get to these this week? It’s not a big deal if we don’t, cause we had the issue come up as higher priority, but if we should move these to the next sprint, just let me know so that they’re not just sitting here. [Rizwan Hameed]: Yeah, I think so. We should move these out because again, still, you know the running two accounts in the same machine will still need a lot of testing like you know what I’ll do I’ll be implementing this gradually like you know initially running this on the two machines for the profile photo then moving it towards the followers update and then gradually I’ll be using this thing and yeah so we can move those in the todos out of the cycle and once the above one I finish and then I can move it back to the in progress, I got it. Michael Houck: Great, yeah, if you finish these, feel free to move one of those back to the cycle. Sure thing. Okay, sounds good. And then just, I guess you and Rafael just stay in close contact with the engagement tracking fix, because right now we’re reverting to a manual process, which, you know, is not what we’re trying to set up, so. [Rizwan Hameed]: Yeah, yeah, definitely that makes sense. UNKNOWN_SPEAKER: Okay. Michael Houck: Sid, what about on the inner circle group side of things? Yes. [sid]: So about inner circle, I think we are pretty much done. We are just like, we have already like more state on the dev environment. So I and Mehul, we are testing it. I think there are some fixes that, I mean, suggestions that you give on the front end side, which Mehul is doing right now. And once those are done, and once you also review it, then we can and take a decision to launch it further on production. So that was the final circle. Yeah, that’s it. Michael Houck: I’ll review, I’m gonna move this then to in review. I’ll review today. I imagine there will be some changes. Rafael, it’d be good if you take a look too. If we both do that today or tomorrow at the latest so that we can unblock launch. And then. So then I guess until we’re while launch is pending, you’re taking care of this one said and then moving on to content queue. Yeah, that’s right. [sid]: So I’ve created few tickets for content queue, but as you said last time could not add them in the sprint and not added added them yet. So these are more. These are four tickets and I’ll also also be getting one more ticket that I I just like splitting the task of that ticket. So once that is done, I’ll create it. And yeah, and then I’ll start with the content, content queue project on the backend side. Great. Okay. Can you make sure to add the size to each of these? Michael Houck: Cause I’m going to go through it later and pull some of these into the sprint. So can you just make sure that the, their size correctly? UNKNOWN_SPEAKER: Okay, sure. [sid]: I’ll update them as well. Cool. Just a few minutes. [Rafael Bruno]: My only concern regarding inner circle would be how that would interfere. Michael Houck: I know what you’re going to say about the number of engagement requests and how it’s going to impact the scraper and all that. Yeah, let’s solve that problem later this week. I want you guys to focus on solving the first problem with the scraper and engagement first. We’ll handle that secondary. So we’re not going to launch inner circle week, that’s okay, but we still should test it and get it ready to go. UNKNOWN_SPEAKER: Okay. Michael Houck: Um, okay. Cool. On the front end side, where are we, where are we at? I know you’re working on campaign stuff. Yeah, correct. [Mehul Jariwala]: So I haven’t started working on campaign stuff, but in middle of our file needs some help on the, uh, subscription flow. So that’s something which I was working on it. So currently what’s happening is when user tried to log in, it will redirect them back to the dashboard and then they’ll redirect back to the login page again. So, which means like most of the user complain that that’s not working correctly, but it actually, the subscription was expired. So what I was doing is I’m just trying to redirect them to the pricing flow so that they can re renew their subscription. Okay. Um, something which I’m working on it. And I mean, barely, I will also creating the view for the, uh, amplifier and also I’m testing the inner circle, uh, flow end to end. Michael Houck: For that, for that first thing, can you send me a video of it just so I can see it? [Mehul Jariwala]: Yeah, I almost done, but I just need to take the few couple of scenario, uh, you know, the code, which I haven’t written. So just wanted to make sure it worked well. Uh, and then once I feel everything is good, then I’ll send you the recording of it so that you can cross. Michael Houck: If anything’s not here, just feel free to add a task for it. But that all sounds good. And then will we get to all this campaign stuff this week or should we move one of these to next sprint? I’m not sure what your bandwidth is like for the rest of the week. [Mehul Jariwala]: Yeah, I’ll just try to take a look at and then I’ll move the few of them to the next sprint because I was juggling between the inner circle and the referral flow and this subscription one too. Yeah, makes sense. Michael Houck: I’ll move that one. And then this one’s probably really small. So this should probably even just be an extra small. So yeah, if we can get to this campaign stuff this week, that’d be great so that we can be unblocked soon for you to work on content queue as well. So. [Mehul Jariwala]: Yeah, sure. Okay. The feather one, so I can just switch back to the live, back to the blog. Michael Houck: Yes, I have an action item for myself to update the feather page this week. So I’ll flag that to you. Cool. Ben, so actually let me quickly give heads up to everybody. So Marina is going to start helping out with the intercom messages. She’s going to be sort of like flagging these to Ben, Ben will be kind of letting her know what to do. And if there’s one that is like a new situation or something like that, or that requires support from you guys, then Rena will flag it in the channel, the same channel. So Ben will still be sort of overseeing support, but Rena will be executing more of it. So Ben, can you give some context on where we’re at and how last week went? [Ben Ornstein]: Yeah, so we didn’t start The, oh, well, in terms of the Reena stuff, we started today. So it’s going to be very, very close contact. I’m going to be helping her write the messages, ask her how she would respond, and kind of like the process you did with me at the beginning. So we’ll hand that over time. So she started replying today. In terms of intercom, last week was 12 closed conversations versus two weeks ago, which was 11. I will say though, that the closed conversations from last week were people who had actually been former clients who were actually, who wanted to come back. Like two, I got two or three of those. So, which is great. So people are, you know, they’re coming back. I don’t know how or why they’re deciding to after like canceling, but which is great. So that was like three of the tickets. So many of them are creators following up as well about the ongoing dashboard issues, and then just, yeah, a couple other, no huge concerns, which is great. Michael Houck: Okay, if you see some people come through today asking about charges, that’s related to an email that Rafael and I sent out this morning, where we charged some people’s cards who had been undercharged for past broadcasts. This is related to fixing engagement dashboard, the engagement tracking issue. So just be aware, most people are just emailing me back directly if they have any questions, but in case someone comes in through intercom, you can just find it to me. [Ben Ornstein]: So this is the opposite or this is this is casters being charged correctly now? Well, it’s it’s a net net thing, right? Michael Houck: Like if the amplifiers aren’t being paid enough, then the casters aren’t being charged enough, right? So it’s the when we make a change, it impacts both sides. UNKNOWN_SPEAKER: Cool. [Ben Ornstein]: Okay. Michael Houck: I think that’s it for me. I think I’m optimistic. We can make it through most of this stuff. If not all of it, hopefully this week. If you guys feel like you’re tracking behind or I think in Rafael’s case and in particular, if you think you’re tracking ahead, let me know and I’ll update the sprint. I’ll toss it back to you guys and I’ll see you on Slack. [Rafael Bruno]: See you, Hawk. Guys, so one thing, Rizwan, can we meet after we end this meeting? Sure thing. UNKNOWN_SPEAKER: Okay. Sid, any questions? [sid]: No, no questions, but just as a suggestion, it would be great if you guys can just keep keep us in the loop about what about the issue of that account defined other things that we know, we are aware about the problem, problem about engagements and account defined all that stuff. I mean, I know, I know most of the stuff that the conversation is happening, but just for other people also. [Rafael Bruno]: Okay. Usually, we have actually about that problem, we have a separate channel that we’re handling that. But usually when we have those problems, we either reply that on the ANG channel or, yeah, usually it’s on the ANG channel. [Mehul Jariwala]: How about you, Mehul? No, I don’t have any questions. I’m just dealing with the subscription issue. [Rafael Bruno]: OK. After I finish my meeting with Brisbane, I’ll probably call you, OK? Yeah, OK, sure. UNKNOWN_SPEAKER: OK. [Rafael Bruno]: How about you, Ben? Anything to say? [Ben Ornstein]: Just, is there any update? I know Friday got insane. For that guy, Frederick, who’s, I think it had to do with the URL not being, it might have been that same thing that you and Mahu are working on with the, the URL. [Rafael Bruno]: In that case, I don’t think it’s the validation because of all of the issues on Friday and today I didn’t have time to continue on that task. [Ben Ornstein]: But after I finish this, I’ll follow up. UNKNOWN_SPEAKER: Sounds good. [Rafael Bruno]: That’s all for me. UNKNOWN_SPEAKER: Okay. [Rafael Bruno]: So let’s have a good week, this week, actually good week this week. But everyone have a good week. UNKNOWN_SPEAKER: See you guys.