Gong Logo Thryv & Twilio - Zipwhip migration Will von Kaenel III with Thryv, Inc. Recorded on 8/17/23 via Zoom, 32 min. Participants Twilio Will von Kaenel III Associate Account Executive Dan Bartlett Solutions Architect Timothy Johnson Head of Strategic Accounts (Franchise) Steve Rehnborg Senior Account Executive Scott Simon Director, New Business Accounts Thryv, Inc. John Manalaoor AVP, Thryv Product Engineering Travis Schluter Software Engineer Natalie Sanchez Technical Support Specialist Michael Greenberg Director of Product Christie Hathcock Product Client Success Manager Other Angela Forsberg Topics Call Setup0:00 Small Talk0:34 Pricing5:39 Proxy Number6:03 Support10:25 Next Steps17:54 Authy18:30 Account Management27:31 Wrap-Up28:13 13 More Transcript ”This English transcript was generated using Gong's speech-to-text technology” Call Setup WILL 0:00 Hey, Tim. How? TIMOTHY 0:01 You doing? WILL 0:02 Can't complain… is some other calls? How about you? TIMOTHY 0:08 Just navigating away? WILL 0:12 Yeah, seems like we'll have to navigate lately. TIMOTHY 0:15 Yeah, no, I get some good windows pulled up. We'll get everybody aligned. WILL 0:19 Cool. Hey, Steve. TIMOTHY 0:25 Hello? Small Talk WILL 0:34 Hi Christie. CHRISTIE 0:36 Hello. How are you gentlemen? WILL 0:39 Doing well. How are you? CHRISTIE 0:40 I'm well, thank you. Good. TIMOTHY 0:44 Yeah, I can see. CHRISTIE 0:47 Pardon. Where? TIMOTHY 0:47 Are you at? CHRISTIE 0:49 I am located in Denton, Texas too *** outside. TIMOTHY 0:55 I'm going to do a pass or this weekend. CHRISTIE 0:59 My thoughts are with you? I hope you don't burn up over there. TIMOTHY 1:04 Yeah. Go pick up my daughter's car and drive it back. That should be fine. CHRISTIE 1:08 Well, be an interesting drive. TIMOTHY 1:11 Yeah, it's not that interesting. CHRISTIE 1:15 Hopefully you have some good podcast picked out or something? TIMOTHY 1:18 Yeah, exactly. We'll be all set. WILL 1:24 You know, hey, Dan. TIMOTHY 1:29 Hi, is that hello? WILL 1:30 It's being high? Call Setup CHRISTIE 1:35 Hey, Natalie. Hi Travis. TIMOTHY 1:40 Hello? WILL 1:45 Hey, John. Hey, there… looks like where… there he is? WILL 2:00 Hey, Mike. MICHAEL 2:03 How you there? WILL 2:07 Am I can we call you G, or is that something that's reserved more for the thrive employees? MICHAEL 2:12 No, it's just out there. WILL 2:15 Cool. MICHAEL 2:19 And Angela is actually the one that gave that to me what I think eight or nine years ago now? Small Talk WILL 2:23 Yeah. ANGELA 2:24 Sitting in the Denver office back when we had a Denver office. I had three is reporting to me this way too crazy. WILL 2:35 Is that everyone from your side… from the thrive side? I think we've got a full house from Twilio right now. Yeah, cool. Well, thanks so much for taking the call. Call Setup WILL 2:47 Really excited to chat. I know we have only 30 minutes and a pretty full house here. So I thought we try to get through the introductions relatively quickly from the Twilio side. My name's will I'm a Twilio enterprise ae? So you can view me as a main point of contact for any questions regarding this migration? I'll make sure you get all the resources you need to be successful. Joined here by my manager, Scott Simon, Steve rainberg. He's a senior enterprise as dropping in because he specializes in some of our largest retail accounts. Then we have Dan Bartlett, Twilio solutions architect, who can provide guidance, anything related to the Twilio technical side. And then Tim Johnson who, I know Mike, you've already spoken to, he oversees, the strategic customer migrations from ZipWhip to Twilio. So, Mike, in the interest of time, I thought maybe you could introduce yourself, your team, the roles and sort of what you're most curious to get out of this call. Call Setup ends WILL 3:42 Then I'll let him take the lead on kind of asking questions and helping you understand what a ZipWhip to Twilio migration might look like. MICHAEL 3:49 Yeah, that works. So, from my side, I am over product and then Kristi owns business center, which is, has the text line like pins. Call Setup MICHAEL 4:01 Angela is the director of our part operations here. And then she has Natali and Travis on her team that they handle all of our tech operations migrations, making sure that the functionality is working. And then John is our avp over engineering. MICHAEL 4:20 So just to at least kick this off, so after we found out about the migration actually via a partner, a different part of the was trying to take the business, we reached out to find out what was happening that's when I met up with Timothy or Tim and just to talk about what the migration would look like when it comes to actually moving over ZipWhip into Twilio, so I think what would be good for us is we're evaluating if we decide to keep everything, moving it over to Twilio as it is today or if we look at other avenues which I know Tim and I kinda talked about maybe we're not being told the full thing in that case, which is what exactly would that process be on our end? Is it just kind of switching out the ap? Is, I believe when we talked, we're going to have to do all new Loa for everyone or potentially at least resurface all the Loa that Travis and Natalie have been sending over the last few years. We just wanted to maybe rekick that off, kind of get the ball rolling there just to find out exactly what that process is. Call Setup ends TIMOTHY 5:25 Okay. So this call is for you. So feel free to interrupt, ask questions, whatever you need to do. First of all, congratulations, you know, we've been working together is back in 2018. And you guys, I was able to get a real list. It was associated with your last invoice. Pricing TIMOTHY 5:39 So that's about as real as it gets. And we're looking at right? About 42,000, 385 lines. So I've done what at 40,000? So, this is the, this, the real deal as it relates to a quick question there, do you own the lines or when the customers subscribe for your service? Are they owning the line themselves? Because I'm just thinking from scaling on the Loa piece, do you know? Proxy Number MICHAEL 6:03 Mixed bag. So we do both. Yeah. So if a client has their own landline number, then we let them register their own number. And so in that case, if you need an Loa, we actually reached out to that client say, hey, you need to fill up this Loa in the case that a client do not have a landline, say they just had a cell phone, we would actually provide them one, from our account then. And then we would actually sign the LO a as, because it's our number a thrive number. Pricing TIMOTHY 6:26 What do you think that makes is 50 50? MICHAEL 6:29 John? Do you have any idea? JOHN 6:32 I don't think it's 50 50. I think it's more landlines, than the ones that we provision. Like I would say, probably 25 percent of them are ours and I think probably north of 75 percent is probably real landlines for customers. Pricing ends TIMOTHY 6:55 Okay, perfect. Thank you. That's helpful. So the reason all this stuff is important is because I just, the number of lines I'm gonna go ahead and share my screen real quick if you guys don't care. And we'll kinda look at something. So this is the export. I would just so you can see it. We kinda talked briefly. Michael last time, what we do at Twilio, is obviously we're as compliant as anybody you're gonna meet into. And while that may seem like it's cumbersome, I can tell you that as these carriers start, you know, flexing their muscles, anybody who can get around what we're gonna talk about. It's gonna catch up with you. So I'm not here to, you know, talk negatively about anything, but I'm just letting you know, we really focus on the compliant piece because as soon as these texts all go out, your support just gets blown up, everybody gets blown up. So we're trying to avoid the blow ups. So anyway, the way that it kinda works, you know, we kick off with, you know, the, that line list. And the first thing we're gonna do is we're gonna go in and actually let me go over this one. First, this is called an eligibility report. Let me make it full size for you. So we're basically are gonna take all of the lines and ingest them into Twilio, right? And once we do that, then we can make this list. And what this list illustrates is what's the story here? What bucks they go into, a, I don't know if this is going to surface the ownership piece, that would be good to know. But basically what we've gotta do in the beginning is find out of the green, yellow or red. So green lines, we're just gonna move over hosting it's seamless. You know, nobody knows anything for the, you know, it's just a matter of KORE graphing. But as we get into some of these other ones, it does get more complex. It could be a broken out with a carrier. It's some carrier that, you know, is not in the system. We're equipped to dive into anything you see in yellow and red and work with you. And then once we go and we do that, then we start batching out the numbers. Call Setup TIMOTHY 8:49 We say, okay, what when's our launch date. So we don't just launch, right? We start with a pilot. So let's move a group over. So we move a group over, we see how it works together. Everything's copacetic and then we put together the schedule. So the schedule in your case is going to be pretty. Call Setup ends TIMOTHY 9:04 It's going to be pretty large, right? Because we got 40,000 to go. And that way that we know that from an infrastructure standpoint, what can we digest? What can you digest as this happens? Right? Knowing that any of the variables we can run into. So, this is kind of phase one of kicking this thing off is what are we dealing with? Right? Because it's really important that we know exactly what we're doing. And again, ideally it's you know, if nothing else, it surfaces what we need to know to set proper expectations. So then what we do with most customers that are certainly even close to your size, is we put together an internal run book and this run book is everything we could possibly run into. Okay? And there's two conversations we're always having one is migration, one is registration, right? And that's why I asked the ownership question. So they run in parallel but the migration ideally does not commence until we've gone through everything we can with registration. So, you know, depending on how this call goes, we share what we're gonna do we go do an eligibility report. The first thing we wanna do is start, the bulk upload process to get these things registered? So we'll have to determine exactly what that means based on this report. But then there's a team that now joins you, right? So now we're not alone because as much as I like to oversee these things, there's only so much I can do. Support TIMOTHY 10:25 As you can see, we've got some folks on the call that are all versed. But there's lots of internal folks that are going to run into as it relates to the personalized support. And again just with your size and this many lines, anybody who tells you that it's a walk in the park. Support ends TIMOTHY 10:38 You know, one thing that we should probably understand we're setting precedent here. Okay, messaging has not been around that long moving live messaging is a very dicey proposition because if it's down for 30 minutes, it's a train wreck, right? You just get lit up. We get it up. Everybody does. So we've got, we've literally built the infrastructure over the last year to be able to scale this migration and registration process. So the automation tools, the hosting is, it got to be ported. All of those things are what we uncover with that first report. So again, I just wanted today's call is really to understand at a high level some of the tools and the resources we have in place. And then let's see. There was one other thing I wanted to show you what the maybe that was. It. Yeah. So this is kind of what it's gonna come. What it's gonna look like. You know, this is more the back end. You don't see this stuff, but this is all the querying we've got to do by carrier. So it's whether it's Twilio or anybody else. It's a serious lift and it has to be done because otherwise you're gonna do a batch of numbers, you know, we're gonna load up 500 and say, let's go. And 38 of those things are gonna come out and say that's a no go. Call Setup TIMOTHY 11:44 And you must know that ahead of time. So the whole goal of all of these resources and all of, these, the reports that we run is to set proper expectation with you so you can set proper expectations with your customer first. Then we figure out timing when's the best time of the day to do it. Call Setup ends TIMOTHY 11:58 You know, how, you know, how big a batches do we wanna do? How do we want to break them up? You know, is going to be based on what they're actually using within your system? So, all of these things are variables that we want to eliminate before we commence the actual migration process. And once the migration kicks off, we've done hundreds of thousands of lines now coming off of zip web. So we're pretty versed at it and I can tell you that it's for the most part. It's it's a lot of work for a lot of people on the back end. But it can go pretty smooth. So just wanted to tell you that high level overview and then kind of field questions that you may have as it relates to, you know, the process itself. Any questions that will come up when you're investigating other partners and why they may be able to do something or claim something? We'd be more than happy to dive in on our end and come back, and give you both a bias and an unbias answer as to why we think, that is a feasible claim or not? MICHAEL 12:56 No, that'd be great. I think the first one's Travis and Natali in terms of the Loa that you've been submitting over to ZipWhip over the years. Have you kept those? Is there any sort of mapping or anything or as they just kinda sent over on a ticket basis to ZipWhip? TIMOTHY 13:12 Both. I should have record for any Loa that I've sent over there? MICHAEL 13:16 Okay. So that's good. ANGELA 13:17 And all of our new ones are on the Google sheet as well. So. TIMOTHY 13:20 Okay. So that's good news because again, this registration shut down is happening August 30 first. That into a Twilio is not do with anybody else you're talking to here. And it's real, right. Good news. You're sitting on ZipWhip, you're safe as long as you've gone through. And I think you guys are 90 percent plus as far as the registration process. But as of September one, if that wasn't the case or somebody was in, you know, kinda limbo, if you will going from one platform to another, it's a challenge and you do have to re, register when you leave ZipWhip. I don't care where you go. If somebody says we can bypass all that, it's gonna get you. Pricing MICHAEL 13:56 Yeah. Well, I think that's good that we had as Nate. I mean, I think we were back in the day you and I were just sending over those Loa. So I think we've been doing that at least since 2019, probably even 2018. So we should have a good chunk of anyone that is still actively using. We probably should have those Loa then. Pricing ends TIMOTHY 14:15 Right. And that'll be very helpful. So, as far as what the professional support does is it allows us to leverage what you've already done with ZipWhip. So obviously, if you send them to us in theory, we would have them somewhere. Is it readily available? Not necessarily because it was never planned to be repopulated, if you will anywhere else but, the team working directly and a lot of the ZipWhip people are now with Twilio. So, the people that originally did the registration and work with carriers, it's the same people? MICHAEL 14:46 Yeah. So. TIMOTHY 14:47 We do in cases like yours once we do know from an ownership standpoint, we get that data, then we can look to leverage what we have. Again that's not a common practice. But given the relationship and your size, that's something that we would pull out the stops to do to minimize a lift on your end because it can get as, you know, even going, you know, we did it over a long period of time. You try and do it in a short period of time. It's a lot of data and it's a lot of back and forth. So, the goal is to eliminate as much back and forth when you registered. I can tell you what is required now is a different set of data, right? You made it, you're right now. But as we go forward, there's additional things that have been added since we did that last year in Q3 and Q4 to where there's going to be fields where we're gonna see. Okay, you need to do this piece, you can do it in a uniform fashion. You can send over thousands of them for this group of customer. But this is a field that didn't exist before that needs to exist now. ANGELA 15:47 So I think for some of that G, are we thinking we would just put another Pendo screen in and direct them to kind of the user to do some of this or are we trying to proactively go out and try and find all of our old Loa, submit all of those loas, and then still potentially not have all the information. Proxy Number MICHAEL 16:09 I think that's what it comes down to is, I mean, ideally any Loa that we have, it'd be great if we could somehow submit that. I don't know if that's feasible by any means at this point with the number of as the number of time, if it's a live account, because I believe too, the way we have it at ZipWhip, is there's no mapping between number registered and then the business center account, which that's our biggest gap. I think we'd be trying to say this account is here and maybe Kristi, we could get, with our partner and see if they can actually map that out. If we give them the list of numbers, if they can say, hey, this one is with this thrive ID with this thrive ID. Proxy Number ends MICHAEL 16:50 And that could be, that could at least help us identify which businesses, each one. Because then Tim green, if I'm wrong, if you say, with your professional services, if you would have it on file, is there a type of query you could do to find that? Or what's, I guess the path is what's the easiest way to get those Loa resurface again? TIMOTHY 17:10 We were, we write scripts to go in and pull the stuff and then it's gonna be obviously, we have to line it as you would with any other partner with Twilio and the new registration roles. And that's where we identify, this is what we can pull and push. And once we do that, what's… MICHAEL 17:26 Yeah. TIMOTHY 17:26 Right. And that's where, you know, it's like Pendo was invented for 10. It's the most effective thing. I've ever seen it useful, but it's if you got to go in a hopefully, a lot of this stuff. I know the idea is we wanna make this seamless to a customer. But as it relates to registration, you know, we can work with you on languaging and things like that to make it as, hey, look, this, is it's to protect you? And at the end of the day that all of this stuff is to protect the phone lines. Because if we don't it's gonna end up like your e-mail… Next Steps MICHAEL 17:54 Right. TIMOTHY 17:55 Right. ANGELA 17:57 Yeah. So, we are doing, we just ran a big campaign last week or two weeks ago to get the remainder of our clients who have not registered yet to register. We're running another one hopefully this week as soon as we get the updated list might be early next week. And then we'll run another one kind of that last week in August because we're giving them the August 30 first deadline or else we're gonna shut off. So we do have a couple more iterations going. So we do have a big chunk of people who are in the registration process right now. Authy ANGELA 18:30 My question is does the registration process today replace the Loa of yesterday? Because when we first started doing this, our Loa were just here's, the number here's the business, there was no E ID required. There was no anything like that required. It was just Loa, just a signature basically versus today, they have to actually go through the full registration process. So do our Loa even make a difference at this point? Because they register? TIMOTHY 19:02 Right? You know, what? You're absolutely correct? So, the Loa process there's certain things we can do. So the good news if you go, if you go elsewhere and I would definitely confirm this if you're seeking to go elsewhere, there's a verification required. So because you're on zip web, we were able to eliminate that after lots of legal time, but that's really going to be the key. So the la is our second thing. But verification is something that you've never been exposed to where they've got to submit bills. I guess it all kinds of things and it's a log jam, right? Move them all over the Loa. We really want to get a snapshot of them for me to set expectation on what we can and can't do. Authy ends TIMOTHY 19:42 It would be premature. But I can tell you that we will pull out the stops to do whatever we can in a compliant fashion to make it scale because this is got a scale. We can't there's just too many lines too many. MICHAEL 19:55 So with that though, I guess the question is since we're so right now in our, what we're asking businesses to submit to us that we're sending over to ZipWhip because I don't think we're really doing the yellow anymore. We're just submitting business name Ein number address, what their campaign type is an example of it, is that, was that what the new? TIMOTHY 20:14 Yes, yeah. You're you're doing the new. Okay, but when you move again, regardless where you move, the Loa will come into play. And, to your point, Angela, it's not the same Loa that was signed before. So skirting the Loa is something that's why I was asking about number ownership. It's ideal. I mean, even if we can walk a chunk of them out by having you do it or if we can put together some groups because then we can build templates for it and we can put it in console and you can do it in mass with the new Loa. So again, when we need to identify, how many can you sign for and how many do we need to submit a new one for? So, I wouldn't spend a, invest a lot of time trying to find your as the new registration process you're putting them through is going to collect, the information to the best of my knowledge, not seeing it that we need today. Proxy Number ANGELA 21:05 Yeah. So Travis, we may just need to because, we already have the list pulled between whether or not it's a number provisioned by us or if it's the customer numbers. We already have that list. We already also know the accounts that have already verified are and are registered and what we're calling it. Proxy Number ends ANGELA 21:23 And so we would just need to see if there's anybody that's registered on a different like before some of this other stuff happens because that's really going to be our chunk of customers that we're gonna need more information. TIMOTHY 21:39 Right. Okay. And so the first thing I'll do and we didn't look at anything like that today is I'll look internally at what does exist from how you've historically registered. So that's engineers going in and looking around and seeing what they can pull. And again, this, the migration is simple compared to this process. Yeah, I mean, it's simple because we'll know exactly what's going to happen and we don't have to touch customers. This one may require some customer touching. So getting knowing that as soon as possible would be, very important. ANGELA 22:14 Yeah. And I think we can go like the good news, is they're going to be very used to us communicating with them about it? However if they've already been verified, we're not communicating with them today. So I think we'll just need to figure out like is it in a combination of marketing emails, Pendo? Messaging? MICHAEL 22:34 Yeah, yeah. We'll just have to. I mean, the nice thing is, we can blame it all in the carriers as usual, which they're at least starting to get used to if there's been so many carrier changes lately that they're probably starting to even ignore those at this point. So the next question would be then probably more for John's sake… for the integration we have today with the current. I think we're using the V1 ZipWhip apis… because I don't think we ever even moved over to the new, the newer one or maybe we're on the newer one and they were trying to get us over onto the Twilio ones a little bit ago, but then we just said let's just say where we're at? What is, what does that change like for the engineers, and maybe that's a separate call to really dive deep into that. But just for John's knowledge right now. TIMOTHY 23:17 Yeah, I think a separate call is the right answer. So the good news, is we worked it, you know, zip, we got a lot of ideosyncracies because it was kinda just hand built as it scaled. But those engineers that built that stuff there's a handful of them still at Twilio, so they would look into it. And I knew just finding the data when we started looking before I got okay, I can't go down the usual paths to pull this. So it was finance that actually helped out, with the line list. But well, as far as the apis and whatnot, I can get some clarity on that. And then we'll get somebody on the call, they can speak directly to both the apis you're on. And what does it mean to move them over to Twilio? MICHAEL 23:56 Okay. Yeah, that'd be great. Next Steps MICHAEL 23:59 And John, maybe we, as soon as we'll get back from… you know, our thing right now, maybe next Thursday, we can even just do away from today. If you guys are available to just get the engineering call as soon as we're we can just kinda see what that looks like as we start to scope out architects engineers, what we need for this yep. Next Steps ends MICHAEL 24:17 So just going back to what Andrew was talking about just because maybe I'm missing the piece. So for everyone we're right now that because we're still submitting to zip today. So for the new ones that we are submitting and we're getting the Ein and everything even with this migration and we move over to them to the Twilio API. Is that new… flow? We would still need to resubmit an Loa and that information again for the number. Is that correct? TIMOTHY 24:44 That's correct? So, the question is, do we have to involve the customer again so that's our goals to eliminate whatever percentage we can of those touches? Because every bit it's gonna matter. MICHAEL 24:57 Yeah. So is the way you figure that out just by running that query on that number list on? TIMOTHY 25:03 Well, actually the registration, is separate. I mean eligibility report is gonna feed into the, them looking at the registration. It's really going to be a matter of talking to engineers. I mean this is literally engineering engineers saying this is what we, this is what you collected. And again, the day one collection where somebody got the green light versus the green light today, two different green lights. So it's really going to be a roll up the sleeves type effort. And then they'll run queries on it and they'll come back and we'll get say we've got the eligibility report, then it's going to be this registration report. What scripts do we need to write on our end? What could you do on your end? But it's definitely going to be a joint effort. And that should be the case with, I can't fathom you being able to talk to somebody where that wasn't the case, right? So again, the value is that, the engineers that built it and did it whether it's registration or the API they still exist. MICHAEL 25:57 Yeah. And then what is the flow post migration? So once we get past all this, we say, okay, we got all these numbers migrated. Now, we start submitting new numbers. Is that all done via API at that point or is it a manual submission? Like Travis is doing today where he has to e-mail it in? I think he's doing a couple of times a week. TIMOTHY 26:16 Yeah. So it's first to speak to that. I think it's all done in console though. DAN 26:19 Yeah. Well, I'm happy to talk to that. And on the Twilio side, I mean, I think that's one of the huge advantages about doing this is that we have very large customers similar to you that need to do this at scale and continually. Support DAN 26:34 So, you know, Twilio has the infrastructure put in place to be able to scale and be able to do compliance at scale. I mean, this is a huge priority for us, but I think one thing that hopefully you come away from this call is that, yes, this is a pain, yes, you know, Tim as the experts and the professional services to make this happen. But also, yes, the end result is something that's gonna be able to handle your needs now and then going forward as well. I mean that's gotta be a huge part of this. ANGELA 27:02 Yeah, cause I think a huge part right now like our team gets Travis team and Ali specifically gets buried with these requests especially when we send out emails. Support ends ANGELA 27:13 And then we get hundreds if not thousands of them that come in because then we need to take the request, the ticket information and then submit it. So if we could build a process to automate that because the customer is already filling out their information. If it could just go straight to you and bypass us altogether, that would be the. Account Management DAN 27:31 So, yeah, I mean, and I apologize for cutting you off, but to be very specific, there's API is to do all these things. So, you're gonna create a sub account. You're going to create the container that needs, to handle, you know, the campaign, you're going to create the sub brands, the sub profiles, you know, and kind of do attach all of that programmatically and you're able to kind of receive responses back. Account Management ends DAN 27:57 So, when a state changes and one of these things, okay. Well, now, we know that one's been verified, we can move forward. So there's just a ton here because this, you know, the truth is this is the reality for all of us, and we've got to be able to solve this, and we've put a ton of resources into solving those. Yeah. Wrap-Up ANGELA 28:13 That's great, cool. Yes, please. MICHAEL 28:19 Yeah. Right. That's being… amazing. So, so Tim, what are the next steps that you, that we need, to do here in order for us to start looking at what numbers need more information, the information we're collecting today, just to kinda get an idea of what that migration would look like? Wrap-Up ends TIMOTHY 28:38 So, I think next steps is we need to have the engineering diligence call right? As far as diving in on the other side just because it's engineers and his time and is queries, eligibility. And there's obviously lots of customers we would want to get to where there's any objections or concerns you have with going forward with Twilio. We put him to bed. Yep because I can't pull resources and then go, it was a trial run. They're going to be like, yeah, you, you'll think trial run. So whatever we can do to help you address that is related to Twilio. You know, I think that's important. I don't have a problem having that, you know, let's move forward with the engineering call to understand the API component. The, the other one is it does take time. So before we unleash, the resources to pull it off, we want to be on the same page. Yeah, this looks good. Let's partner make it happen. MICHAEL 29:27 Yep. And, is the deadline for ZipWhip deprecating the December first? TIMOTHY 29:33 That's correct. And it's there's been many that tried to move it. Yeah, lawsuits every is like go nowhere. We've got time. We don't have a whole lot of time but we certainly have time. Yeah. Meanwhile for you guys, it should be business as usual. Again, get those unregistered lines registered in the meantime and we'll figure out how to solve that going forward. MICHAEL 29:55 Yeah. And then I think in terms of that, I think it just comes down to contract discussion is the, if, what if what's happening? Is it just continuing on the same zoo contract? Is it a brand new contract? So we, are we going through pricing? What's I think that's the piece that is also up in the air that hasn't been discussed with us? TIMOTHY 30:09 Yeah. Since it relates to commercials, we wanna look at everything you're doing. I think you are doing stuff with Twilio already today, leverage anything and everything you're doing and put together the right program that reflects today and tomorrow, right? Where are we going? And what are we doing? So? And that can happen in parallel if you want to have set up something to look at the commercial side of it. But yeah, it'll be all of the, all of the zip with papers are gonna be put to bed. So either move to another carrier or another provider or it's just on December one. It's just gone and literally a plug, we're going to unplug it. MICHAEL 30:45 Yeah. So if we could just get, the information on contract and whatnot on commercials? ANGELA 30:52 Would it help if Natalie sent over a couple of examples of like one of our number Loa, and a customer number Loa? TIMOTHY 31:00 Yeah. I don't mind doing some diligence, cancel right now that's fine. We just can't give them the whole shooting match, doing some discovery? ANGELA 31:08 I just curious because if you determine that it's not helpful at all then that gives us, you know? TIMOTHY 31:12 I don't want you doing it. So simply be off with your heads. ANGELA 31:16 Yeah. And then if you can find like one of each, right? Thrive one and a customer one, just shoot over just so they can see. Wrap-Up MICHAEL 31:27 That'll be awesome. TIMOTHY 31:27 To… wonderful. MICHAEL 31:31 Cool. All right. We are. TIMOTHY 31:34 All right. You'll send out some availability for reconvening next week with regard to engineering and commercials. MICHAEL 31:39 Yeah, John, I'll sync up with you just because I know as well. I assume we'll probably need some architect or an architect and an engineer or two. So. TIMOTHY 31:49 Cool. Perfect. All right. Well, thanks, everybody. We. MICHAEL 31:53 Thank you. TIMOTHY 31:54 Progress. Not perfect. DAN 31:55 Thank you. Bye. TIMOTHY 31:56 Take care. WILL 31:57 You. TIMOTHY 31:58 Bye bye. The End