Transcript
Brandon Chase (00:00) come in and see if this… is going to be an issue. Hey, Ryan. How you doing? Hey, good. Good morning. Did you have any issues getting into this?
Ryan Jones (00:13) I did not. Okay.
Scott Peterson (00:16) Good.
Brandon Chase (00:19) Typically we’ll schedule a Microsoft teams meeting. Okay? Everyone’s trickling in. So, I was a little concerned, I saw that Michael put the Google meet on and I’m like, no, we’re going to have no one showing up to this. But here we are. So that’s good. Hey, Scott. Hey, Bobby.
Scott Peterson (00:42) Hello? Hey, good morning. Good.
Brandon Chase (00:45) Good. And then I believe we’re just waiting for, is it Dina? Is that her name? Yeah, Dina? Yeah.
Bobby Pace (00:51) She won’t, she won’t be able to attend.
Brandon Chase (00:53) Okay. So it sounds like we have a quorum then.
Scott Peterson (00:57) We’re good.
Brandon Chase (00:58) Awesome. All right. Well, I appreciate y’all’s time and I figure I know you already talked with Michael for a little bit. He passed along his notes. I watched that recording and I figured for today’s call, what I propose for an agenda is just going over just some quick intros, who’s who in the zoo, I’ll confirm just kind of briefly what we’ve heard up to this point. And then really, it’s just like we’ll hop Scott and I will hop into questions and make sure… that we’re sort of kind of, you know, just understanding exactly what needs to be done and then telling you kind of, you know, how we can do that.
Scott Peterson (01:39) So, without.
Brandon Chase (01:41) further ado, my name is Brandon chase. I think Michael was probably referencing me by name on the call. I kept hearing him say like a payer specialist or something like that, but, you know, by title, I’m director of partnerships here at medallion. So I’d be owning the relationship between triwest and medallion. You can think of me as kind of your single point of contact for all things, you know, all things that are contained, you know, in this relationship. And I also brought Scott who I would consider the payer expert, Scott. You want to tell the group who you are? Yeah.
Scott Everline (02:18) Hi, all. So, Scott Everline, I’m the principal solution consultant here at medallion. So, I’ve been in this credentialing provider data space for quite some time. Bobby, your name rings a bell. I don’t know if I think we may have worked together. You were at caresource at some point in time. I was at caqh for about nine years. So worked closely with caresource teams, worked with triwest in the past. So just kind of here to support the conversation, make sure we’re lining everything up to meet y’all’s needs and, you know, hit expectations. So, nice meeting y’all, nice.
Scott Peterson (02:48) Meeting you. So we’ll do the same, Brandon, go over on our side. So, Scott Peterson CIO at triwest, Bobby, you want to go, yes.
Bobby Pace (02:57) Bobby, pace director of provider systems and quality triwest?
Scott Peterson (03:01) And Ryan, hey.
Ryan Jones (03:04) Everyone a consultant in the it area for provider tools and customer service?
Brandon Chase (03:11) Awesome.
Scott Peterson (03:13) All right. So, just.
Brandon Chase (03:14) Kind of jumping into what we heard. We’ll keep it simple. I have two bullet points here. One, the specific ask from Scott was that y’all, want to understand kind of what our model looks like in terms of how you would pass over the providers that you need credentialed.
Brandon Chase (03:32) And then what do we do with that? And then how do we pass it back to you to ingest into your current workflow? And then, you know, in terms of like volume, we’re looking at the immediate use case of about roughly 30,000 providers?
Scott Peterson (03:48) Yeah, I think that’s right. And I can give you a little context we’ve been, we’ve got a significant backlog of 30,000 plus and growing daily, I think, Bobby. And so, you know, we’ve been in the middle of a verifiable implementation for a while and we feel like we need to explore some other options and understand capabilities others have out there to attempt to quickly credential folks and then bring them back into our environment. Again. And so, it’s.
Brandon Chase (04:24) I believe.
Scott Peterson (04:25) You guys at times work in a hybrid model. I don’t know. I know nothing about you. Bobby probably knows much more than I do, but I’m just curious about, you know, if you operate in that way what it looks like and, you know, maybe if you could just talk us through some examples, and help us understand that. And Brian, Bobby, please feel free to add anything you want to that ramble.
Bobby Pace (04:50) Yeah. What Scott said sums it up. We were migrating from visual Symplr to Salesforce verifiable with verifiable doing the integrated within the Salesforce doing the credentialing… but we have a,
Brandon Chase (05:06) backlog about.
Bobby Pace (05:07) 30 31,000 might be a little less, might be some duplicates in there because of aging, and then they’ve been sent again the same providers so, but we’re just for quantitative purposes, we’ll just say, you know, around that 30,000.
Brandon Chase (05:23) Yeah, that… makes sense. Okay. And then just a question about the verifiable implementation. Are y’all, is that something that you’re pausing or is this something that you’re going to continue with? And then verifiable will be your ultimate solution. But you’re just looking for a stopgap right now?
Scott Peterson (05:42) Yeah, that’s the intent that it’s a long term solution. I’m not saying we don’t pivot away from that, but right now, that’s where we’re at got it.
Brandon Chase (05:51) I’m very, I came from the Salesforce ecosystem and, you know, I sold a verifiable implementation. I believe our sow, I was on the SI side on the implementation services side, and our sow was about 18 months. So, I know what y’all are going through. It’s not, it’s a big lift, right?
Scott Peterson (06:11) It is.
Brandon Chase (06:13) Okay. And so, so I guess how are you currently handling? I know that there was like a total network size talked about of 900,000 like outside of or inclusive of these 30,000, can you just kind of walk us through? Like just like a high level overview of how, your, what does your current workflow look like?
Brandon Chase (06:38) Like let’s say that, you know, magically we wave a wand and like we’re ready to go a month or two from now, right? What, what does that process look like? Understanding it probably won’t be verifiable, how are we plugging into that current process right now?
Scott Peterson (06:58) So, maybe be helpful to share the process flow and where we have some pain points just for you guys to visualize and see what we’re working through and where we think we need help. I think the biggest thing for us, Brandon is understanding how.
Scott Everline (07:16) Flexible.
Scott Peterson (07:17) you are, in terms of what you return back to us and how we can ingest that back into our environment so we can continue to have control, right? Or, you know, be able to continue the workflow and still tick and tie everything on the back end. Bobby and Ryan, you know, feel free to correct anything it’s more about, you know, can we understand medallion’s capabilities in this? Or how you just operate in general? And maybe that’s the jumping off point for us to say, hey, we think this will work or hey, we’re not sure and ask you additional questions if that makes sense. Yeah.
Scott Everline (07:54) I mean, I’m happy to do like the 30,000 foot all the way down to digging in the weeds conversation if we want to. Can we?
Scott Peterson (08:02) Go to like 15,000 feet?
Scott Everline (08:04) Yeah, we’ll meet in the middle. Okay. Yeah. So essentially the way medallion operates is, you mentioned Scott a hybrid model that’s how we integrate with a lot of payers today. Whether that’s feeding data into a Symplr system, whether it’s feeding it directly into Salesforce. We built out a custom Salesforce integration with optum behavioral health. So if you’d imagine from a volume and size perspective pretty similar, we did that as well with a company called spring health which is a telehealth behavioral health system. Same thing built directly. Our cvo service is kind of bolted on to their Salesforce instance. We also have an end to end platform. So if somebody wants to leverage a medallion platform, we have a credentialing workflow management tooling. So depending on how you guys want this to feed into your system pretty flexible, we have a bi directional API. So essentially what you could do is you could kind of kick off those initial requests. The 30,000 or some odd providers submit that through an API call. We can also just receive that as a flat file. We leverage caqh for our application intake process. So we would essentially, and I’m pretty sure triwest has a caqh instance. So we would basically call your caqh instance roster, those providers extract the data into medallions or that application and the metadata. We process all the psvs, put it into a nice pretty little packet, flag that packet as basically clean or issue. And then we can either store that on the platform and you can manage that through committee in the platform or what a lot of our customers are doing are taking that finished file, calling back from the API, the data as well as the packet, storing that in their system of record, then making those decisions. And in this particular use case, I don’t think we would need to know what your decision was, right? Because we’re not scheduling those providers to re cred, we’re just giving you the file, right? So that’s almost where we would part ways as far as a deliverable goes if you wanted to or considered medallion as a future partner. We would want those re cred decisions or those credentialing decisions. So that we would reschedule those providers for 36 months down the road and then rinse and repeat. But that’s kind of, I mean, it’s I hate to say it, but credentialing is pretty straightforward, right? And I think to maybe what you’re getting to is it’s the hardest part is connecting everything, right? Making sure you’re getting things in a way that you can. Efficiently consume it and manage it within whatever ecosystem you have. And that’s how we work with most of our payers today? What?
Scott Peterson (10:31) Does a typical integration timeframe with you guys look like? And I know that, you know, everyone’s different, but like, and I’m not going to hold you to a number you tell me yep.
Scott Everline (10:41) Yep. I mean, I would want from a Salesforce perspective, if that’s what we’re talking about. And the modeling looks very similar to what we did for optum behavioral health. I would imagine it would, I think it took us about eight weeks with optum to really have the full plugin, but that was also because we were doing it for the first time and it was a pretty unique use case. I would say we’ve definitely after doing three or four of these Salesforce type integrations, I would bet we’re probably within four weeks depending on like how prepared we are for those four weeks, right? So, like do we have? Because I think the biggest challenge with integrations is more like data translation, right? So like you guys will call a provider, one thing or a specialty might be able to do something else if we’re feeding off a standard taxonomy and an nucc table, probably going to be a whole heck of a lot cleaner if you’re using caqh’s data standards, a lot cleaner because we’re matching like to like… so I’d say like probably around that four to six week mark is my guess. If you’re talking about full like embedded integration depending on how fast you guys are looking to move, it might be something that you’re literally, I mean, processing files in medallion to get the files processed, and then pulling the metadata in after the fact and loading it, right? Because if it is really like we have this backlog, we need to know these providers down the road to process for re, cred, through the variable system and in Salesforce. But like right now, you could potentially manage that process end to end from a credentialing perspective within medallion and just feed those output so that it can be stored for the longer term that’s going to be a much faster track because we’re not building that integration per SE. You’re just doing file feeds, right? And.
Scott Peterson (12:17) How flexible on the file feed? Are you, like, I mean… within reason, but, you know, to make it easier to ingest on our side, what’s the, I… mean you mentioned a couple, yeah. So.
Scott Everline (12:31) What we do today on Salesforce is just a Json file that comes back and it’s a multitude of endpoints. So API endpoints that we would connect to feed into the Salesforce instance… we for like caresource as an example, we actually create, we replicate a CDT file that’s delivered from their incumbent cvo and that’s like us mapping our cvo file directly into an excel file. And then we deliver that excel file to them. And that takes a fair amount of mapping and data translation because we’re not looking at things the same way. So, I think there’s some flexible. I mean, I think it depends on what you’re looking for, right? Is it like a flat CSV file? Is it a Json file where you’re pulling back individual providers? Are you pulling back bulk of providers? I think there’s some nuance, and we have some translation tooling that we kind of layer in between because no two systems and no two integrations are the same. So there’s kind of a translation module that we have baked into that process. So the data will come out of medallion, go into this configuration tool, that then configures it back into whatever the outbound apis are, and then translates that data into the system. Yeah.
Scott Peterson (13:42) And so the way I mean, you articulated, well, kind of the way we’ve been thinking about it is one of the models we walk through in terms of, hey, we send you bulk data, you credential, you send us back a flat file, we send you a flat file, you send us back a flat file, we re ingest and we kind of move on.
Scott Everline (13:57) Yeah. For short term, that might be the lowest lift, right? Because an integration is a pretty big investment both from like a resourcing perspective. And also you’re like theoretically, this is less than a six month engagement. Yeah. Right. And so like invest all of that integration into a six month engagement, might feel heavy handed and it might slow the whole process down.
Scott Peterson (14:17) Right. Yeah, we can’t afford that.
Scott Everline (14:21) Scott, how.
Bobby Pace (14:23) quickly.
Brandon Chase (14:25) Are you looking to get this done? I mean, is it like typically like yesterday kind of a thing? Yeah.
Scott Peterson (14:30) It’s literally yesterday and I mean, I think we will likely have an RFP on the street really quickly, likely early next week and we’re so we’re just trying to understand capabilities and you, your guys’s name have come up in a variety, of venues. And, you know, I just kind of wanted to understand from you guys what you thought you’d like, you know, if this was something that’s even in your warehouse, it sounds like it is obviously the devil’s in the details when you get into it, but yeah, we’re looking to move really quickly, to do something.
Scott Everline (15:05) Bobby.
Scott Peterson (15:06) Anything you want to add to that or Ryan?
Bobby Pace (15:09) Let me just ask, if we sent files, do you have a, just a team that could… credential those? And how would you get them back to us? If, if we just need to send you that, what we have and get it credentialed and get it back to us? What would that look like?
Scott Everline (15:27) When you say files, what do you mean by that? Like you have… got we?
Bobby Pace (15:33) Got the, we got the rosters and, you know, those type things. If y’all, pull up the caqh and all of that, we just sent you that and you get the package, you know, credential them and send it back to us in.
Scott Peterson (15:46) A file. Yeah.
Scott Everline (15:47) I mean, like our intake, I can even show you guys, sorry, Bobby, go ahead, no.
Bobby Pace (15:52) Just asking, do you have a model for that? If, yeah.
Scott Everline (15:56) So literally, just like a quick run and gun, what picture are you guys? Are you guys seeing anything on my screen? Yeah.
Scott Peterson (16:04) We can see it. Yeah.
Scott Everline (16:06) Yeah. So you’re saying just like a quick run and gun basically like cvo option. Yeah. So what we would do is like we have a standard import template which is literally like cqh id, mpi, first and last name, and then that fires off an API call to caqh to extract that provider data. And then what happens from there is we get to… delivering these files, right? So what you would get back is essentially this credentialing file. So this is the platform workflow. But let’s envision you not interacting with this. You would call the API. You would essentially get this summary checklist along with all the verification metadata that goes along with it. So images of licenses, a credentialing packet, right? I don’t need to exhaust that unless you want me to. And then you could store the PDF of that packet if you so desired. So you could actually store the PDF of the credentialing packet. We could deliver all that through the API that’s kind of like a like we get that inbound file, start the processing call caqh. If there’s missing data, we’ll follow up with the providers for missing data. If their caqh is out of date, we’ll ping the provider about getting caqh current. We actually call caqh daily through the credentialing process. So if they’re making any updates, we’re pulling back that data in real time via caqh. And then we literally just deliver that file to you. And then it would be in the API. I think turnaround time. We’d want to talk to our engineering and our operations teams just from a bandwidth perspective because there are people that are in this process, 30,000 files as you can imagine are a lot to process in one fell swoop especially have a credit analyst do a final QA and sign off. So, a lot of this is automated like our typical turnaround time for a CPO file is a day, our contractual SLA is five days. But I think with that volume, we might just want to try to pace that out and understand like overall what that timing looks like because we’re not going to be able to honestly, we’re not going to be able to deliver you 30,000 PSV packets completed like that’s. It’s I wish we could, I don’t think there’s anything. I don’t think there’s anybody that could, and if somebody tells you they can, they’re probably lying and God bless them if they can. So. But I think we would just figure out what that timing looks like and just stage that in a meaningful way, that kind of gets us all to the same place as far as delivery goes. But Bobby, hopefully that answers your question, right? Like we could take that inbound flat file we’ll manage doing the caqh calls. And when those files are ready, we make them available on the API. There’s a webhook on the API. So you’re basically just going to get the webhook and say who’s done, right? Like every day, every couple hours, I’ll call the webhook, who’s completed, go pull those packets back into your system or if we want to deliver them like as a sftp deliverable, we could do that as well. That’s what we do with care source. The less custom configuration we do, the faster everything will be able to get done, right? Because all that’s going to take time for us to configure versus like we’re shooting off a packet in the metadata. And you guys have a CSV file with the data you want and it has the packet with it and you run with it. Then that’s going to be, the path of least resistance for you all. And.
Bobby Pace (19:10) Then in a file exchange, what, how flexible you’re like on the format of the file? Like?
Scott Everline (19:18) You’re talking about like file format as far as like whether it’s a CSV file or a piped limited text file, or a Json file or something like that, right?
Ryan Jones (19:25) Or a.
Bobby Pace (19:27) File that we are already like sending a like aperture file or something like that?
Scott Everline (19:33) Like a CDT file, right? We could do a CDT file. They’re paying the butt to make, but we can make them and we do one for care source today, so we could replicate it. I think the problem we’re running into a problem. The challenging care source is like, the data mapping, right? Bobby, you probably even know this personally, right? Like care source has like other provider boards, it’s like we like, how can we map to other provider boards that’s like very hard to map into a CDT file? So again, like, if we’re mapping raw, what’s coming out of medallion, which is essentially what’s coming directly out of caqh into that CDT and it’s just us moving data into that file. It’s going to be much less of a lift. But if we have to change like a provider board specialty to whatever your internal board specialty is and do all that mapping on the front end that’s going to slow things down because it becomes like a data mapping exercise. Okay?
Bobby Pace (20:24) Does.
Scott Everline (20:25) that make sense there?
Ryan Jones (20:26) Will certainly. Yeah. And I think we need to factor that in because taxonomies have been much more complex as we’ve moved through it. So, which, I mean, not surprising to either of you. Any of, you all know, that, I would probably recommend in avoiding any kind of direct to Salesforce movement, of the data. I think, you know, we bring it in, we do the mapping. We use some middleware to load it, right? That, that way, you know? So we’re in a gov cloud instance of Salesforce. And that just every single time it takes, what we assume will be simple much it makes it much more complex. Yeah, we, you know, if we take in the files, we can figure it out from there congress. Yeah. Exactly. So I think Bobby started to touch on this and would like to hear a little bit more about your staff, your effort, your people that can take on the credentialing. I mean, you have the easy ones that are boom, Bam, they’re done, but that’s not always all of them. It’s rarely all of them, right? So what kind of stuff do you bring to the table there? Whether it’s I don’t know augmenting your own staff to pump through it or manage service capabilities. Do you want to dive into that more? Yeah.
Scott Everline (21:52) So, we have a pretty large bpo. I shouldn’t even call them bpo because they’re medallion staff, but we have a pretty large credentialing team. A chunk of them significant chunk are in India again badge medallion employees, but they are in India. We have onshore resources that we leverage as well. And then we use a fair amount of AI for like the outreach. It’s actually pretty cool. I’ve had my kids play around with their AI tools because you can ask your questions, right? So like it’ll call out and say like, hey, I’m calling from medallion on behalf of triwest, it looks like you need to update your caqh profile and you’ll be like what’s caqh. It’s like caqh is a council for affordable healthcare. It’s a blah, blah, blah. And so we use AI tooling for a lot of that, what we do with customers as far as like what I think you’re getting to an extent Ryan is like completion rate, like how many files are actually going to get completed versus how many are just going to fall flat because providers aren’t responsive or we’re not putting the effort, we will configure that based on your needs. So like claresource as an example is pretty aggressive. They’re like anybody who’s not responsive for two weeks. We want them out of the system like close that file. We will not put them in our network. Some organizations would be like, we need 60 days, right? We’re a green smaller organization. We need 60 days to kind of massage some of this. So we’ll continue to do that outreach primarily via email. We will do a follow up on phone calls. We’ll use the AI phone agents to do the outreach. And then ultimately, depending on what timeline you guys are looking at, we would then archive those files as incomplete. You’ll still get those archived files. So you’ll get what we processed. And if you need to internally, maybe finish it off, right? Because you guys are the plan. So you guys are the ones writing checks. If you follow up, maybe they’re more responsive and you already have what we started. And then you could take it from there. But again, like I think the volume, the staffing augmentation is less of an issue as long as we just know the volume is coming. And then we can set ourselves up and we do a lot of like payer enrollment and licensing work that we can pull some staff over from as well.
Scott Peterson (23:56) Would it be a challenge, Scott, if we need 100 percent onshore model?
Scott Everline (24:02) Potentially, I mean, I would just need to let the staff team know, right? So, do you think you guys are going to be, we?
Scott Peterson (24:10) Absolutely. I think even.
Scott Everline (24:12) though it’s not member data, it’s provider data. You guys are okay? Because I know that’s a tricky wicket, right? Like sometimes provider stuff can go offshore depending on what it is and what the offshore teams are doing, but.
Ryan Jones (24:26) Yeah, socialize.
Scott Everline (24:27) That internally, if it needs to be 100 percent onshore?
Scott Peterson (24:30) Bobby, did we, I know we talked about exception on kind of the security requirement from an individual perspective, but I don’t know that.
Scott Everline (24:40) We at… least?
Scott Peterson (24:43) I haven’t been in the conversations about onshore offshore that we could actually take this offshore. Can we, do, you know, if you don’t know that’s fine. I’ll find out. I,
Bobby Pace (24:51) don’t I don’t know, I think we… can, because it’s not going to be dealing with any phi. Yeah, I think that would.
Ryan Jones (25:03) Yeah, we need, yeah, we should verify it because I would almost lean the other way from, you know, the last couple years. I’ve been surprised at the things that aren’t allowed to go offshore that are even less secure than this. So, I mean, Scott, I would take that internally, and prepare that, you know, if we were to move forward, this is highly likely to be all onshore and it’s a bonus if it’s not.
Scott Everline (25:29) Okay. Yeah. I mean, I would think there’s going to be very few of any vendors in the cvo space that could support that volume with 100 percent onshore for sure. Yeah. And our data is stored onshore so that’s like data storage is onshore and secure. And again, it’s at least medallion staff. So we’re not even outsourcing to a third party bpo, I.
Ryan Jones (25:49) Think it’s a spend. It’s a spend. It says dollars where the dollars are going kind of?
Scott Everline (25:54) Thing. Yeah, yeah… we’ll.
Brandon Chase (25:58) we’ll definitely take that internally, but, would, I don’t know if Scott or Ryan would either one of you be able to kind of own that and just kind of track that down just to confirm for?
Scott Peterson (26:07) Us. Yeah, we’ll find out. And obviously, as we create the RFP there’ll be specifics in there about what would be required? So I, I’m that’s probably in flight already outside of these conversations, but.
Ryan Jones (26:17) Okay.
Brandon Chase (26:20) We’ll we’ll do what we need to do internally to kind of prep our team, but.
Scott Peterson (26:23) Okay. Just,
Brandon Chase (26:24) understanding it’s most likely going to be needed.
Scott Peterson (26:28) Yeah, I think that’s fair.
Bobby Pace (26:31) Okay. What?
Scott Peterson (26:34) Other questions, Bobby, do we have, I think you guys have you’ve answered my questions? I understand the capabilities you have now, so.
Brandon Chase (26:41) Yeah, I don’t know. I don’t think I have.
Scott Peterson (26:44) Any more. Okay. So.
Scott Everline (26:46) Done yesterday, but like what is your real realistic time frame for actually getting all these files processed as far as like, is that something that you have three months to complete? Is that something you need done in?
Scott Peterson (26:58) Three days. We’d really seriously like to have done yesterday. I mean, I think a month for us is probably tenable. It’s too long, but it’s probably tenable if we can get somebody that we can work with quickly to get a month, you know, and beyond that, I think it, and there’s going to be stragglers, right? I mean, you’re not going to, and we recognize that, but we’re trying to get, we’re just trying to burn through this backlog, and be able to come out the other side in a different place than being in the hole because frankly we got, we have to do, you know, keep doing the same thing over and over again. I expect a different result. It’s probably not going to happen. So that’s why we’re having this conversation.
Brandon Chase (27:42) Just to double click on that too. Scott, when you say if we’re talking about a month, you mean having all 30,000 files completed in the month, or are you talking more of like kicking the process off? And then, yeah.
Scott Peterson (27:56) I mean, we’d like to have them done in a month. I like I said, we know that we’re not going to get all 30,000 like there’s going to be lag and some of that. But as many as we can get processed, we’d like, you know, to make sure that we’re on track, you know, in 30 days to be at least out of this, the, how buried we are now.
Scott Peterson (28:20) Yeah. Okay. I think Bobby, you guys are getting 300 a day or something like that. I heard one like that. So like it’s just the, you know, what the team is doing is not keeping up with even the intake. So, so.
Scott Everline (28:36) Probably a Brandon question, but contract wise, right? Are you guys just looking for like a letter of intent kind of type contracting? Are you all able to do that through triwest, given kind of all the government components of it? Yeah.
Scott Peterson (28:50) I mean, I think we do have to release an RP, right? But we can turn them quickly and obviously, you know, having conversations like this is what gets us further down the path, right? And I think that, you know, as long as you guys can turn quickly, we can move really fast internally on that. But to your point to get started, a letter of intent would work as well. Okay? So.
Brandon Chase (29:15) Has there been a budget dedicated to this? Was there a budget set aside for this or like, does that still need to be approved as well?
Scott Peterson (29:22) I’ll just say, this is the organization’s number one priority. So, and nobody’s talking, you know, just get it done, get it done. Yeah, Bobby, Scott and Ryan, go get it done.
Brandon Chase (29:34) Yeah, figure.
Scott Peterson (29:36) It out yesterday. So, like I said, we really appreciate the conversation, the candor, frankly, good conversation, and we will definitely be in touch.
Brandon Chase (29:49) That sounds great. Thank you very much. We appreciate it guys. And we’ll be prepping the team for the incoming RFP.
Scott Peterson (29:58) Sounds good. Thanks a lot. Thank.
Brandon Chase (29:59) You. Thank.
Scott Everline (30:00) You. Bye guys.