- Duration: 27 min
- Platform: zoom
- Source: Read.ai 01JDJ5T30J2WVSGS46GBJM36D9 (https://app.read.ai/analytics/meetings/01JDJ5T30J2WVSGS46GBJM36D9)
Transcript
[Michael Houck]: Hey, something’s wrong with my Slack. Oh, there it is. Okay. [Michael Houck]: What’s up, everybody? UNKNOWN_SPEAKER: Hey, guys. [Sid]: Hello, guys. [Michael Houck]: How’s everybody’s weekend? Good stuff? [Sid]: It was good. UNKNOWN_SPEAKER: Cool. Same here. [Michael Houck]: So let’s take a look at last sprint. We completed 56 points of stuff. We missed on some things. I’d already removed some stuff from the sprint on like last Wednesday. We still missed a bunch. Some of which I think we thought we were going to complete some other stuff. There was things that came up that pushed it into this one. But we’re behind as a result. I think our likelihood of launching the referrals page and groups this week is minimal at best. I hope I’m wrong about that, but I think our new goal should be to get everything out this sprint. So if you guys feel like we can get it out this week, great, let’s do it, 100%, full steam ahead. But I think at this point, trying to hold us to that won’t be successful necessarily. So I’d say as long as we get it out this sprint, well, we’ll have fame for that. I mean, is that accurate? Do you guys agree with that? [Rafael Bruno]: About the referrals, I was testing some stuff with Merlot. We just need to test the entire flow, but everything seems to be good right now. Okay. We could launch that. Since it’s referrals can run independently from groups, we can launch it separately. [Michael Houck]: Yeah, I think groups is blocked by referrals, but referrals is not blocked by groups. So if we’re, we have referrals ready to go, we should just launch it whenever, basically after we test it. And Rafael, you and I, I think for this feature should probably do what you’ve wanted to do for past features, which is we get on a call and we walk through it together. Um, so yeah, I think let’s, um, if we can get that out this week. Great. Sid, what about on the group side? Where are we at? UNKNOWN_SPEAKER: What’s blocking launch? [Sid]: Yeah, we are also going pretty good on groups. So I was testing what has been implemented. And I think we are on track so far. We just need to address the new tickets. I mean, the tickets in this sprint. And that way, and by the end of this sprint, I think we will be in a good place to test the flow thoroughly on a dev environment. That were QA. UNKNOWN_SPEAKER: Got it. OK. [Michael Houck]: I think if we want to get it launched this sprint, so I think, Rafael, if you have some bandwidth after we’re done with referrals, if you want to move over and help sit out with the final few things on group so we can accelerate that, let’s do that. And anything else, aside from urgent bugs, right? Anything else we can push beyond? OK. So. Ben, do you want to start by giving us just a heads up on what you’ve been seeing over the past week? [Ben Ornstein]: Yeah, so number of tickets went down last week was 12 this week or two weeks ago was 12. Last week was 8, which is better and a lot of them were one off little things. So really a lot better when I’m more, you know, one wanted to close the account. So really like not create the biggest bug that still remains. And I think everyone, most are aware of the, it’s just the dashboards. And other than that, like I think things are looking really good. So yeah. Cool. Yeah. [Michael Houck]: I would expect we might see more people reach out about that. Although over the weekend slash this morning, we did identify the root cause. And so it’s not fixed yet, We’d hoped it would be fixed by now, but it’s not. But regardless, we know what the root cause is. And so Rafael and Rizwan are addressing that. So I think that should be fixed sooner rather than later. I know next week, obviously, we have Thanksgiving second half of this week. So it won’t make sense for you to do this this week. But next week, it would be good if you could do like a look back over the past few months and just show like, hey, Google Sheet, like each week, how many issues do we have total, and also how many of like different categories and types so we can see like where the consistent, consistent trends. UNKNOWN_SPEAKER: But cool. Yeah, sounds good. [Ben Ornstein]: Oh, and one other thing I would say is that we have not had one user other than this guy Yassin, who’s had just so many issues. Sid, I think I tagged you on, there was one guy that, yeah, his latest thing, I think he canceled an active subscription and then restarted another one where he has his LinkedIn and his Twitter. That’s what it looked like, And he’s having trouble logging in. I don’t know exactly if that’s what happened, but that’s what it looks like from Stripe. Yeah, if you could check that out, because this guy is probably very close to churning with how many issues he’s had and how long the wait time between each has been. [Sid]: So Ben, I and Rafael were discussing about this. And his status is updated properly now, although it was earlier there as well. But because after he cancelled the subscription, our system was not letting him in. So we have updated it again after the subscription got cancelled. Now you can ask him to log in again. He should be able to log in. Awesome. Thank you. [Ben Ornstein]: Appreciate it. [Michael Houck]: And Ben, when you reach out to him, you should give him a free month because of all the issues that he’s had. So do you know how to add the promo code onto his subscription? [Ben Ornstein]: I don’t believe so. I don’t think I’ve done that yet. [Michael Houck]: Okay, just shoot me a message in Slack so I have a reminder to add that later today, but tell him we’ll add that to his account so he won’t have to pay for the subscription next month. Got it. I’ll message you now. Thanks, everyone. Okay, so let’s start with the urgent issue. So, Rafael, you want to get us started to kind of explain where we’re at and timeline the next steps? [Rafael Bruno]: Okay. So, as Hauk said, we finally figured out what was the root cause of all of those missing engagement issues. Regarding the backend, I already wrote the fix. It’s already in production and I’m waiting on Rizwan to finish his part so we can make sure that everything is OK. Besides that, today I will see this other issue regarding messages being sent to creators. And I’ll try to finish the remaining tasks of the APIs of the referrers project. And besides that, I think everything is going well. Probably on Wednesday, Mehul and I will do like an entire test of the referrals flow. And if everything is okay, we can test together, Hauke. UNKNOWN_SPEAKER: Cool. [Michael Houck]: Okay. That sounds good. Let’s try to do that test, I guess, on, I guess it can be Thursday. If we do Thursday morning, I can do it. If we do Thursday afternoon, I can’t. It’s a big holiday here in the US, so we’ll be traveling. It’s in the morning on Thursday, I can do it. As far as the issue that we were fixing, we also need to do the data cleanup for that, right, with Reena? [Rafael Bruno]: Yeah, I already created the table, the spreadsheet, and Reena is working on that. [Michael Houck]: Okay, well, what if there’s a new broadcast that comes in like right now before the fix is shipped on RISC-One side? [Rafael Bruno]: Will we need to add that? After I add what Reyna is identifying, I will look again for missed broadcasts and I’ll pass that to her. It will be like a smaller list. [Michael Houck]: Okay, cool, sounds good. Ben, FYI, that will result in a few probably cases of overspending on broadcasts as well. So people reach out and be like, why is this over 100%? Same thing as before, the same process we’ve run. If they are bushy or really upset about it, we can offer to cover, but obviously we prefer to just acknowledge it as a bug that happened. Yeah, yeah, let them know it won’t happen in the future. UNKNOWN_SPEAKER: Got it, thanks. [Michael Houck]: So Rafael, after that stuff with the referrals page like post Wednesday, there’s a lot of stuff in here. I would say that most of it is like medium to low priority. Actually, all of it is being below priority. So you should check in with Sid at that point and see if. Others any group stuff that you, that’ll make sense for you to jump in on to help get that across the finish line of the sprint too. If not, if since you’re in a good place and we feel like we’re making progress and or just take too long to sort of get you up to speed on that part of the code base or whatever, then, excuse me, then you can start working on this kind of group of tasks here, updating the pricing feature. And we can talk about that when the time comes. Some of these will go to Mehul, but then others are either you or Sid. So we can talk about that when the time comes. UNKNOWN_SPEAKER: Sure. Cool. [Michael Houck]: Sid, let’s talk about groups. [Sid]: Yeah, about the groups, I’m working on this email thing, which is completed with the logic thing. I’m just waiting for the email. And while that it’s all also completed. I’m looking at the 1067 thing. So just looking at the design, what are the things I need to return from the API? What are the things I need to implement? And yeah, I think this is what the groups detail. Apart from that, then there will be group emails that also I’ve created a list where I mean, which are the triggers where we need to set up the emails regarding the groups. So I think those two, those three tickets are the high highlight of this group thing. And side by side, I’m also checking, I’m also testing the groups flow to make sure that it’s working as expected. UNKNOWN_SPEAKER: Cool. Yeah. [Michael Houck]: If there’s other emails, I’m trying to think if there’s other emails that we need here. I would imagine the invite to join a group maybe, or no, I think we already did that one. Maybe we want an email that says like if somebody, let me make a note here. Oh yeah, there’s a few I wrote in here. Okay, so I’ll go through this list. I’ll write any of these and then I’ll send them to you because that’s blocking 476. UNKNOWN_SPEAKER: Okay, fine. Cool. Okay, great. [Michael Houck]: And then once you’re done with that, we can move on to the other, the payments structure stuff, pricing structure stuff as well. Um, and then there’s a few other tests in here, um, this sprint for you, uh, too. Um, so we’ll see if we get to those. [Sid]: Hopefully we do. UNKNOWN_SPEAKER: Um, yeah. [Michael Houck]: Okay. Cool. Um, Rizwan, how about your side of the, um, the missed engagements issue here? Yeah, sure. [Rizwan Hameed]: So basically all with the week or with, uh, with the last like Friday I was working on the de-use cause thing but then started the investigations for this engagement share the findings and then I was testing the engagement URL as well today in my earlier day so found some issues like the LinkedIn classes updated so I was working on those changes as well but then I asked Phil to log this task as well so now I’ve started working on this thing and hopefully I’ll try try my best to complete it today. Otherwise, hopefully tomorrow I will make sure like, you know, the things are, uh, this should be completed at least by tomorrow because I know the agency of this ticket. So, uh, actively working on it. And then I’ll be resuming the changes for the engagement. You are a lot to this thing. So I know engagement while, and they would use costing on pending right now. [Michael Houck]: Great. So this one, this one, this one. Should all be completed this sprint. Do you think we’ll get to the replacement logic? [Rizwan Hameed]: The reduced costs won’t be completed because it’s a longer thing. Like, you know, I have to implement the, like, you know, I have to implement a lot of changes for using, like, you know, switching between the two accounts instead of using a dedicated account, right, for each port. And then the second port, will be like I have mentioned the details in the comment as well. So once that is done, then the next part will be like, you know, doing the R&D on using your like executing two bots for two different platforms in the same VM. So in this way, we can reduce the number of machines as well. So these will be based on the R&D as well. [Michael Houck]: So this is going to take time. Can you do me a favor and break this up into sub-issues by clicking this and creating some sub-tests in here? Both the parts you’ve already completed and also the parts that are in progress or remaining. Just break them up into individual parts and give a size for each one, just so I have visibility into where we’re at. Sure thing. UNKNOWN_SPEAKER: Okay. [Rizwan Hameed]: Sure. Definitely. [Michael Houck]: And I would imagine that some will keep in this sprint and others will move to next sprint. Yeah, yeah, yeah. That totally makes sense. UNKNOWN_SPEAKER: Cool. [Michael Houck]: Okay. So I’m going to move the replacement logic to next sprint then, since we’re not going to get that this one, correct? [Rizwan Hameed]: What was this one? Like I had account replacement logic. [Michael Houck]: This was where, um, I was saying that in order to avoid you want to basically switch to a new account, if one of our LinkedIn accounts or Twitter accounts gets banned for some reason. [Rizwan Hameed]: Right. Yeah, this is going to be moved to the next part. [Michael Houck]: Okay, I’ll move that to next sprint. That’s fine. [Rizwan Hameed]: And then I’ll move this because because this is Yeah, so this is going to take time as well because we need to figure out the ways where the account we need to check like the account is not logged in or there’s some issues with the account logging things. UNKNOWN_SPEAKER: So yeah. [Michael Houck]: Okay, it would you say this one is a the missing agents one as a small or medium. [Rizwan Hameed]: This is a medium one. But I will try to make it small as much as possible. [Michael Houck]: Sounds good. All right. Just keep it. Yeah, just add those subtests in there. Let me know when I can go in and just take a look. [Rizwan Hameed]: Sure thing. Sure thing. But I’ll do that after once the decision issue is fixed, then I will make it on the task for their court. [Michael Houck]: Yep, same page. Thank you. Okay, well, there’s, I brought the new account shelf back into this Hopefully we can get to it. But again, it’s not the highest priority thing. So the higher priority things are referrals and groups and probably the payment structure stuff too. So if we don’t get to new account shelf this sprint, it’s okay. We can do it next sprint, but I added it here just in case. [Mehul Jariwala]: Yeah. So for my side, the referral page will be all ready. I just had a call with Rafael and we were discussing like the flow of it. So probably it’s mostly ready, but I have one question. Like in the file page, we have a referral page, we have the invite flow, right? So the user type email, and then they send the invite to the user, right? So does it like consider as a inner circle invite, or it will consider as a normal invite? So that’s what I was discussing with Rafael. [Michael Houck]: Yeah, yeah, I think we went back and forth on this a little bit. I think the default should be that if you receive the invite, then you should get invited to someone’s inner circle. But remember that if somebody is on the free tier, which again, I don’t know if we technically have live yet, but that might be the pricing structure project here. But if someone’s on the free tier, they only get six people in their inner circle. If they’re paying for either starter or pro, they get unlimited people. So yes, the answer is yes, by default. Let’s add them. Um, but if they’re on the, if they’re on the free tier and the inner circle is already full, then they should see some sort of modal that says like, let this person know to add you to their inner circle because it’s full or something like that. UNKNOWN_SPEAKER: No. Okay. Sure. [Mehul Jariwala]: So which means like it is considering as a inner circle, right? By default. Yeah, I think so. [Michael Houck]: I think that’s the best way to do it. Cause then basically whenever you’re inviting someone to join mega they’re getting added to your personal megaphone, you know, which is your inner circle. Okay. So it makes sense. [Mehul Jariwala]: Then I’ll check with Sid because we need to have the inner circle flow also to be set up. Currently, it was inner circle flow was not set up. It’s just a referral flow set up. So I’ll check with Sid. Yeah, because we need to pass the group ID as well as a part of the sign in flow. So that’s something I’ll check with Sid, like if we can merge with it. The rest of them is already done. Only that was pending. So I’ll finish that as well, and then we could run that. Yeah, because I mean, I guess think about the flow, right? [Michael Houck]: If you’re only going to have one link, so if you send that link to somebody, you’re basically inviting them to join. So by default, they should be in your inner circle. You can always remove them later in your- your group details settings or whatever. But for now, it should be default. Okay, cool. Thank you. [Mehul Jariwala]: That’s the question which I have. And that is the one thing, that is the thing which is pending on referral page. And apart from groups, I haven’t like integrated actually whatever the API that has seeded is created. I just need to integrate it in case if need any suggestion, I’ll reach out to seed on that. Cool. [Michael Houck]: And this is what we were just talking about. I forgot. I knew I put this in a test somewhere. I didn’t know which one it was. It’s 1060. Basically, we need an experience for someone if they get invited to join, but there’s no spots in their inner circle. So you can read more about the conversation at the link here. UNKNOWN_SPEAKER: Okay, cool. [Michael Houck]: And then the other stuff, there’s some low priority stuff down here as well. We should try to get to that after the new account shelf. Again, I’m not sure if you’re going to be able to get to all this this sprint. Most of this stuff, I think, is pretty small. Individually but there’s a lot of it so and I know there’s other stuff going on too so um let’s see where we can get to um hopefully we can get through this stuff but if not just flag it to UNKNOWN_SPEAKER: me as early as possible. [Mehul Jariwala]: Good I’ll let you know I’ll first focus on the refer page and then I’ll let you know. [Michael Houck]: Cool and then yeah I have to do some writing I already did the FAQ so I’m gonna move that to done did that for you over the weekend um On the feather stuff, I want to try to get that live. Remove strapping a feather live. I want to try to get that live. I have to do some DNS work first. So I’m going to do that. UNKNOWN_SPEAKER: Yeah. [Michael Houck]: But then we’ll, then we’ll, we’ll make the switch. Um, oh, and yeah, I meant to ask about this one too. The, um, is this, is this done? [Mehul Jariwala]: Yeah, I’ll, I’ll finish this, uh, today because I was involving into, uh, there’s some changes which Rafael suggested, so I was doing on that in referral pages. [Michael Houck]: I’ll pick up that after that.