Transcript
Bradley Eral (00:00) hey, Brittany?
Brittani Luyen (00:01) Hello again.
Bradley Eral (00:04) And then they will have on this call a dev manager, a lead dev and systems architect. Okay, cool. Alongside Sean. Hey, Ben. Hey, Nico, how are you doing?
Ben Newton (00:20) Hey, folks. Doing well. Good afternoon. Hey?
Bradley Eral (00:23) Good afternoon. Appreciate you guys making the time on short notice here.
Nikhil Oza (00:28) Short notice.
Bradley Eral (00:30) Hey, Ross.
Bradley Eral (00:42) And then Ben and Akhil, obviously we were chatting on yesterday’s call, but I know we didn’t have time for like formal introductions. Remind me kind of roles and responsibilities for you folks, what you oversee?
Ben Newton (00:57) Sure, Nick, do you want to go first? Mike, you go first?
Nikhil Oza (01:00) Yeah, I can go first. Yeah, it’s fine. Yeah. So I’m one of the dev manager at therapynotes, my team handles integrations with third party vendors like dr first and others and my team, one of my team may handle medallion as well. So, yeah.
Bradley Eral (01:19) Amazing. Appreciate that. Yeah.
Ben Newton (01:22) And I am the, I guess I’m the lead developer for our exchange team. So we, you know, we do some of those integrations and I’d be the maybe the technical lead on this. I guess it depends on which of the integration teams this winds up with. But yeah, that’s what I’m here to kind of absorb it all and learn about medallion and how things work.
Bradley Eral (01:48) Perfect. Well, appreciate you both joining. And then Sean, I’ll take your lead when we have quorum and, we can jump in. I know everyone’s time is valuable.
Sean Behan (01:59) I think we’ve got everyone from our side. Perfect. Might be able to join in a minute, but otherwise, you know, as long as Ben and Nick are here, I think we’re good to go.
Bradley Eral (02:10) Awesome. Well, appreciate it guys. You can see two new faces from our side. We have Brittany from our product organization, then Ross from the engineering team. And really the goal of today is want to further understand the iframe requirement, what’s his ideal state look like, what are you guys looking to drive? And then ultimately, the output of this will be our team’s going to huddle up internally, discuss what we learned today and come back to you with, hey, here’s. Kind of your options, right? From what this will look like within medallion. But does that sound like a good use of everyone’s time? Perfect. Well with that said, Brittany, I’ll pass it to you and we can jump right in. Cool.
Brittani Luyen (02:47) Thanks, Brad, like Brad bundgen. I’m a product manager here. I work with Ross on some of our integrations. And yeah, we just wanted to learn a little bit more about maybe some of let’s start out with, just like the workflow that you all are looking to build. And, you know, when you integrate with medallion, what you want that experience to look like, I want to make sure that I have a good understanding of that. So as we explore different ways that we go about this integration that we are solving for those primary needs that you all have.
Brittani Luyen (03:22) I don’t know if that’s a question for maybe Sean or, yeah. So the question is essentially like what is the experience that you’re hoping users will have once you complete an integration with medallion? Yeah, I’m doing.
Sean Behan (03:34) My best to pull up our subproud environment right now. I was lucky enough to get a brand new laptop yesterday and so nothing is saved or stored or anywhere. And so that’ll kind of do it. If you mind to share a screen, I can walk you through essentially what we would do with pretty much any vendor or something close to it.
Bradley Eral (03:59) Love it. Appreciate that.
Sean Behan (04:00) John, just share. I think this one should do it. So therapynotes app pretty straightforward. There’s a sharing because I’m in a different tab.
Brittani Luyen (04:15) We see it. I think, yeah, we see like my to do summary my upcoming appointments aside. Yep. Cool. So.
Sean Behan (04:21) Here’s the main thing. So if I pop into our settings page, this is where it would more or less look like if I have the right kind of permissions… I have our eprescribe as an example. So this is another integration that we do. So this is where I would enable this one’s already enabled just for us. Basically, this is where we would start the configuration, right? So we talked yesterday about having to send up that excel file and identify different users roles, all of those kind of things. So a settings page would be where they would enable it. We’d gather any additional data that way they would need, you know, choose which of the staff members are going to be the administrator, choose which of the roles are going to apply for different people if necessary, give them a place to drop in caqh numbers. Those kind of things for clinicians. So we’ll gather all of the necessary practice setup stuff here… save and enable that’ll, generate probably the excel file. We sftp that over to, you generate that. And then you’ll send the emails of, hey, here it goes. We’re likely going to have it live… that’s fun. Try it again. No staff endpoint’s not working right now. So it’ll live in one of the settings pages for staff members. Are we doing a deploy because it’s 12 30? Yeah. Let’s see. Is there another page that might work well for this to show what environment are you in? Sean? I’m in master? I mean… you shouldn’t be getting errors like this during deploys, but.
Sean Behan (06:16) Any time I’m trying to go somewhere other than settings for the moment. Let’s see if I can shortcut my way to a patient nope.
Sean Behan (06:29) So… nope… going anywhere in master for me, isn’t working right now?
Ben Newton (06:39) Yeah. I see the errors coming through. I think this is one of the teams is aware that there’s an issue with one of the tables. I can follow up with them right now, right?
Sean Behan (06:51) Well, then stop the share and switch your screen to prod. It’s not going to be quite the same here.
Sean Behan (07:08) No. So we had a bad merge. Is that what you’re saying Ben?
Ben Newton (07:17) You know, I’m not too sure. I know that it was in, it was mentioned yesterday. I thought this was fixed by now. I don’t know why it’s not in master. I think it was like service was changed but the database was lagging or something like that.
Sean Behan (07:35) Am I sharing at least the staff members table now? Yeah, yeah, cool. Great. Staff members will throw a new button up here, manage enrollments that’ll take you to a page that would iframe essentially the… dashboard from medallion would be the goal, right? So, there’d be a settings page to enable it kind of configure which users are using it. Put it here. You know, if I pop to something like this, it would just be in this content. That would be the long and the short of that one.
Brittani Luyen (08:14) Got it. Okay. This is super helpful. And I know that you mentioned iframe, I’m curious like are there specific outcomes that you’re looking for from a user perspective? Like is the intent of the iframe to say, for example, like create a more a quicker onboarding experience? Is it about maintain people in therapy notes platform? Like what are the specific goals that you all have with this experience?
Sean Behan (08:39) Yeah. So it’s maintaining the platform, right? Like you don’t have to leave the therapy notes ecosystem to get to where you need to go. Do you, yes on an iframe, you’re technically somewhere else like that. Most of our users are not sufficiently savvy to understand that, right? What I was hoping to do with our subprod environment is I can get to our E prescribing solution. Can’t do that in a production environment because I can’t really prescribe, right? But we have the test accounts. And so that would show pretty clearly what it looks like there. Does it look exactly like therapynotes? No, we don’t need that level of white labeling that it’s you know, an exact match for our UI, similar colors, logo somewhere close to similar styling would be ideal, right? But we know it’s never going to be the exact match. But if I’m working with my staff members, I don’t have to leave therapynotes, go somewhere else entirely and then remember to come back. So now I have timeout problems, it’s an ehr, you only get five minutes of being outside the system before your system locks, right? So as long as you’re staying in there, we can use a keep alive, right? So now, you’re not, you know, constantly logging back in, having to remember what tab has, what open. Oh, I need extra information about a staff member. Well, I have their profile one click away and I can grab what I need from them. Do I need to send a message to them to remind them that they need to update documents, that they need to do whatever. We have an internal secure messaging tool that’s one click away, right? So all of that unified user experience lives in our platform and we really don’t want people having to leave and go somewhere else because it just makes it harder to use. And we really think we’re going to lose a ton of customers along the way if we’re trying to push people outside, yeah.
Brittani Luyen (10:26) That totally all makes sense. The reason why I’m asking is because I’m trying to understand like, you know, so there are three core workflows that one of your users would have to complete when it comes to these enrollments, it’s figuring out what service requests they want to submit, right? Like what pay or what stay, what line of business, and then giving us all of the information we need to submit the application to the payer. And then if our team has questions following up on those questions and, you know, maybe there’s like a driver’s license that they need to re upload because it was blurry or whatever reason. And there’s a lot that we can do to actually pass that information to our platform from your platform without the user needing to do anything at all, which is, I think the ideal experience for them. You said the users aren’t savvy the least amount and they’re clinicians. So ideally they don’t want to be doing a lot of admin work. So if you already have the information in your platform or they can give it to us via caqh, we can populate a lot of the information that we need on the application without them needing to do any additional work. So this is an option that I think we’ll take into consideration when we’re evaluating all the potential solutions for you. But there’s a world in which we could do some type of integration where they can tell us within your platform, there’s a small API integration. They can hit an endpoint. Say here are the payers we want to enroll with. We can collect all that information from the provider without them needing to do a lot of additional work or even really needing to interact with our platform just all within your platform. And then maybe there’s some experience we build for follow up, which we can kind of discuss with that build that looks like. But yeah, I just want to make sure that as we explore solutions, we understand the experience you’re trying to build because that solution may not look like an iframe, but it may still accomplish your goals. Of user stays inside the platform, does as little admin work as possible and gets enrolled quickly.
Sean Behan (12:14) If you don’t mind, I’ll share one more because we’re going to go down that road. I can show you that was kind of more of our, you know, end state request where we’re hoping to get to. But we have a couple options here. Our list of, you know, the payers that we’re supporting. So we’ll have some that you might, right? Hopefully you guys enroll for Aetna. So within Aetna this tab, I can see where I am, users can actually configure this as part of their rate schedule and say that who’s out of network, if the practice is in network, right? I’m onboarding a new clinician they’re not in. So we actually update our entire billing workflow then to say that these people are going to bill in network. We’re going to have, you know, expected contracted rates and write off amounts and all of that here. We’re going to collect up front for the patient, that kind of stuff. But if somebody is out of network as a clinician, there’s going to be a button here that says, enroll, right? So if you’re out of network, it’s literally just going to be add them to your network. There’s going to be an option here on the billing page where you’re submitting claims, right? This one is going to set to bill as out of network. Let’s say there’ll be a little advertisement on here that says, hey, this person’s out of network. Would you like to get them in network? Do it there? So there’s a lot of opportunity for places that we can make it simple where it’s a one button click. We’re going to pass through all the practice information, all the clinician information, the payer information in one spot as our long term full integration. We’re definitely planning through that, but for right now, it’s that follow up. It’s the status pieces. It’s all of that stuff that we’re going to need to pull from you to try and get. And then right now, you’re telling us we’re going to have to build a whole UI to display all of that. And that’s going to take forever. Yeah.
Brittani Luyen (13:59) I don’t think that’s what we’re asking for at this point. I think we can about different solutions. I am sort of curious. So totally agree with you this like one click, you know, request enrollments experience is probably ideal and where we want to get, I guess, are there specific prerequisites that you all would like to meet before you get there? Is it from like a engineering resourcing at this point? A constraint or sort of like what’s the difference for you all between implementing that like at launch versus implementing down the line?
Sean Behan (14:28) I think, you know, our CEO wants to go to market as fast as possible, right? He thinks there’s a lot of value here. He thinks there’s a lot of opportunity. And so the simplest fastest integration is what he wanted to start with. And that was kind of what we talked about during our discussions was kind of a staged rollout, right? What’s our fastest go to market? How can we get this in front of people quickly simply? And then kind of over time include that level of all, right? One click here’s my request enrollment, right? And then I think the biggest piece was again the status, the follow up, how do I upload a document, right? I need to put in credentials for verification, all of that kind of stuff. So how do we pass all of that through to you? Effectively? Yeah. Okay.
Brittani Luyen (15:15) Quick question. Do you already collect caqh id as part of your workflows? Or would that be something new? We?
Sean Behan (15:21) Don’t now, it would either be on that enrollment page where we’re going to say sign this person up. Since we do have the annual fee for the platform, right? So we need to know who we’re going to be doing that for, or we do have staff profiles that we collect, license, npi, all of that kind of stuff. It’s just add a new field onto there.
Brittani Luyen (15:38) Got it. And at launch, as you mentioned, we wouldn’t be building this one click enroll experience right off the bat, what would be sort of the entrance into the enrollment process? So, how would customers express interest in that?
Sean Behan (15:54) So, we’d have that settings page, say that I wish to engage in enrollments, gather whatever information that we need to send that we don’t already have if it’s there, assign the user roles at that point, so that we can configure who’s the admin, who’s providers, what levels they need. And then from my understanding at that point, you’re going to send them an email inviting them into the medallion platform anyway?
Brittani Luyen (16:18) Got it. Okay. So there would be a place in the platform for them to like sign up for the enrollment basically, but we wouldn’t necessarily be collecting at that point or at least not in the version that you just described like which payers et cetera, that they’re interested in. It’s. More like user signup flow, role selection configuration.
Sean Behan (16:38) Okay. Right. For the very first approach, right? We said let them do as much as they can in medallion. It looks like a great platform. It looks like it’s relatively easy to use, just show it within there. But over time shift more towards that whole one click. You know, we do the single sign on to the iframe that has the URL parameters or whatever you need of this is the payr, this is the clinician id, all of those kind of things. When somebody onboards a new clinician, do you want to add them to your enrollments? That kind of stuff? Just part of the whole like sign up process and therapynotes. You start a new user in our account. You want them to be able to manage their enrollments with us as well. So there’s a lot of different places to make small adjustments. Okay? This.
Brittani Luyen (17:23) Is really helpful and it really gives us a better picture of how to achieve the outcomes that you want. Ross, Brad, do either of you have any additional questions or does your team have any additional questions for us? Oh, Sammy and Cameron, I think you’re on the call too. So feel free to chime in with any questions?
Ross Martin (17:41) Yeah. I think one thing that would be helpful for me is when we go back and kind of huddle on some different things we can propose is what is your like short and long term overall like engineering budget for this? And you can give that in terms of time or however you want to phrase that, but it is helpful because like there is no option is going to be obviously zero engineering. So I’m curious like what the realistic options are for this?
Sean Behan (18:08) Unlimited unlimited, right? Like our CEO said, this is our next thing he wants. We are a single member LLC. There’s no VC. There’s no, nothing, right? He says it goes. So, you know, if we say that tomorrow, it’s the highest priority for three dev teams and our entire infrastructure that’s what it is. Okay?
Ross Martin (18:32) Well, I think I’m obviously, we can’t promise anything. Hopefully we won’t destroy your whole roadmap. I think we can do a lot better than that, but that’s really helpful. Thanks Sean.
Nikhil Oza (18:42) Yeah. And from the technical standpoint, you know, based on the workflow that Sean described, what we would like to have is, you know, all the information that you need additional information or what’s the status things of that nature, right? You provide that information back through webhook calls, right? So that we can proactively let our user know, hey, there is an activity happen, right? We can notify them in the to do list, right? Like, hey, if they need to take any actions or if the status update happened, if they approved denied pending, whatever, right? You constantly feed that information back to us from the technical standpoint, that would be a huge value so that we can constantly keep our user in the loop and if there is anything needed from them, they know it’s right on their face when they come next time, right? And say, hey, this is, I need to do, right? To continue the enrollment process, right? And then from the security standpoint, Sean already mentioned, right? Single sign on is huge, right? We don’t want our users to leave and enter credentials on something else. And also so that’s from the API to API communication standpoint, but also scope right to that practice to that user, right? So that they don’t see other information that they are not supposed to see, right? So, it’s a higher level hierarchy as well that, you know, from the technical and security standpoint that we wanna make sure we implement it and consider that for the implementation.
Brittani Luyen (20:08) Yeah, that’s really helpful. We have some of those like you mentioned statuses so users understand what’s happening in the medallion platform or just, you know, where their application is, some of that’s already available via our public apis. We are making those more robust like statuses, follow ups, et cetera. In the next couple of months as well. That is on the roadmap. So that’s already available as if that’s something you guys are interested in giving your users an insight into in multiple parts of the platform. So that’s good to know. And.
Nikhil Oza (20:36) Josh, from our perspective, from the single sign on, like our preferred approach would be the entry id or there would be something else.
Joshua K (20:51) Yeah. I mean, I would hope we could do saml through entry. If we could do group based like rbac assignment, that would be great. I know not every vendor supports that, but at a minimum, we need to be able to do like a saml type sso.
Ross Martin (21:14) Wait for your users for.
Joshua K (21:17) Us, like for me, Ben, Sean, whoever needs to admin, the platform.
Ross Martin (21:22) Oh, okay. Got it.
Sean Behan (21:27) I mean, if worse comes to worse, we can probably run it through like a site admin thing, josh, right? We would just have a super user permission.
Nikhil Oza (21:35) Because I.
Sean Behan (21:36) remember looking at the permission sets available on their website and there’s like a corporate user style permission if I remember, right? As opposed to just practice admin. So we might be able to just make that a site admin permission for us.
Joshua K (21:52) Yeah. I mean, we still need to do like portal setup and issue API keys and like all that kind of stuff, right? So, those are the accounts that I’d be talking about.
Ross Martin (22:02) Yeah, I mean, would you be, but you would be able to like go to our platform directly rather than using the embed, right?
Joshua K (22:09) For that kind of stuff, I would assume that’s true. Is that right? Nick, like we wouldn’t want to build vendor admin stuff into the site admin site, like who would be doing that? That would just be?
Nikhil Oza (22:23) Yeah, that would be something from.
Joshua K (22:25) Developers and it, right?
Nikhil Oza (22:27) Right. Yeah. Okay.
Ross Martin (22:28) Yeah. Sorry, I understand the landscape. None of this stuff is a blocker yet. So, we internally have like an enterprise account structure to suit exactly this purpose where you have your super users doing this kind of account configuration and each of your clients will have like a tenant that’s connected to that enterprise essentially. And for your like login, yeah, we can do, I mean, any kind of standard, we can do oauth, with different vendors. We can do saml, anything that you want to be able to log in. Yeah. So that’s not a blocker in any way. I think it’s more about the client experience that we need. Okay?
Joshua K (23:03) Yeah, we don’t have a client saml implementation so that I don’t think we could do that anyway.
Sean Behan (23:12) Dr, first we hit an endpoint, get an authorization token, store that and use that for the session for the user. I’m pretty sure, right? Ben knows far more about that than I do. Yeah.
Ross Martin (23:23) Yeah, that’s exactly what we do. We retrieve a token and it uses, yeah, a flow from that.
Nikhil Oza (23:42) So, there are two types, right? Like one is the master token, right? From our platform to your platform, right? And then there will be underneath, you know, the user level configuration. I don’t think we need to have a separate token for that. I think it’s a master token just to initiate the API conversation, right? Communication and then scope it to the user based on who logged in. I.
Ross Martin (24:06) Believe. Yeah, that’s how we’ve designed our enterprise apis. So if you look at our public API documentation, have you been able to look at our public API documentation?
Nikhil Oza (24:16) Yeah, we have.
Ross Martin (24:17) Yeah. So, yeah, like most organizations don’t have this enterprise structure, they will issue one or more API keys that they can use. They can hit all of those endpoints. Enterprises have their own set of keys and then they just specify the user they’re acting on behalf of. So if you ever worked with like stripe’s API, it’s very similar in design to that. Okay. Yeah. And I don’t want to go like too far down the technical solutioning rabbit hole here. I think again, the goal is just to understand exactly what your goals were and what your constraints were. Sammy, did you have any questions like on the technical or product side before?
Sean Behan (24:53) No, I think I’ve covered everything we need to between.
Bradley Eral (24:55) Rossi.
Sean Behan (24:56) and Brittany, and then,
Bradley Eral (24:57) the therapynotes team. Yeah. And I guess quick question for my time. Obviously, you guys have rolled out many of these integrated partners in the past across the platform in the interim, in the past, like before this fully integrated experience, regardless of the mechanism to get there, were there any workarounds that you’ve had success with in the past as you’re building out like the ideal state?
Sean Behan (25:24) I’m not going to call it a success. We do have a partnership with the mphr. It is like one of the quality care platforms for CMS, right? So you’re going to do mips through that, you’re going to do value based care kind of stuff. And so that one involves somebody calling our customer success team, a customer success person, getting on a screen share with a customer enrolling separately in that platform and then coming back to our site admin page and manually entering ids that they’re pulling out as URL parameters from the vendor because they’re not… fun to work with. But once we have at least those ids, then we’re able to do API calls and whatnot, to push data over to that vendor. And then the customer has to work within the vendor platform to manipulate additional data. Right there’s. Stuff that we won’t capture that’s just part of a session that’s not possible to do. So they have to go to the vendor platform to say that they did something or didn’t do something? A session applies to a measure, that kind of stuff. And then they can submit through the vendor at the end of the year.
Bradley Eral (26:42) Gotcha.
Sean Behan (26:43) That way we have about 20… to 30 people per year in a good year because it’s so hard to do.
Joshua K (26:53) Yeah, that one’s tricky because it’s run by states and the states choose the vendor and we don’t really get to choose like if we want to integrate with North Carolina, we have to use the vendor that North Carolina picked.
Sean Behan (27:08) That’s the hie integrations we have. I was talking about mips with healthlogix which is even worse, but, yeah.
Joshua K (27:16) I thought they were the same thing. I guess they were equally bad. So, I assumed, yeah.
Sean Behan (27:21) We use the same platform with rhapsody to do those, but to manage the actual licenses and integration, you know, state hies, it’s pretty similar. They have to get ids from the state, come back to the platform, enter those in and then we have a single pipeline to sftp data over to the states.
Bradley Eral (27:39) Gotcha. Okay. So that makes sense. Obviously not an ideal workflow, but leveraging your customer success team to make it a cohesive experience with therapynotes. Just a different contact within therapynotes, whether it’s in platform or via customer success is the model essentially. The biggest.
Sean Behan (27:58) Difference is really our successful platforms don’t require the separate login, right? So the hie kind of stuff you’re staying within therapynotes, you put in the ids that you need, and we can manage that through therapynotes. Yeah, the healthmodics platform where they have to have a separate account and they’re logging in, there hasn’t been a whole lot of great success for people.
Bradley Eral (28:20) Makes sense. No, I appreciate the context there.
Sean Behan (28:25) I think that if we decide to dedicate a CS team, it would just have to be larger than what we’re planning, right? We’re already planning like there’s one team that’s going to be dedicated to this, that’s probably going to be seven to 10 people. Okay? And their goal training is going to be managing enrollments, right? Credentialing, that kind of whatever we want to call it for our customers because they have no idea what they’re doing for 90 percent of it, but it’s basically going to be there’s a dedicated phone line. It’s a 24 seven phone line for us screen share available that’s already kind of built into the plan. We’re hiring and prepared to train people. At that point. We would just have to blow it out to like 15, probably double the team size.
Bradley Eral (29:10) Yeah, no, yeah. Seven’s certainly a healthy number that’s awesome to hear.
Bradley Eral (29:20) Let’s see any other questions from the medallion side? I want to make sure that we fully understand exactly what we’re working towards ideal state for therapynotes. And, you know, as I mentioned, we’ll huddle up Sean and come back with, hey, here’s, some options of what this will look like.
Sean Behan (29:34) Okay. Yeah, if you need anything, if you have questions, I’ll do my best to get back to you too. Yeah.
Bradley Eral (29:39) Absolutely. But yeah, Brittany, anything else from your side? No?
Brittani Luyen (29:45) I think we’re set for now. Yeah, let’s definitely get time on the calendar for us to do an internal regroup?
Bradley Eral (29:49) Perfect. And then Sean, as long as I got you, do you mind hitting on, we can find some time for Monday to find some time for a debrief, where we come back with our proposed solutions if that works.
Sean Behan (30:01) Sure. I’ve got between one and two 30 on Monday right now.
Bradley Eral (30:06) One and three, bear with me.
Bradley Eral (30:19) Brittany, in your opinion, how long do we need for that? You think an hour or 30 minutes should do the trick?
Brittani Luyen (30:24) For the internal debrief?
Bradley Eral (30:25) No, for us to follow up with, hey here’s, what’s possible?
Brittani Luyen (30:29) Like half an hour, although I think we may need until maybe like the middle or late next week. I think Monday might be too soon. I think we’re already too close to the end of the week. So if we could do this call like Wednesday or Thursday, I think that’d be ideal. I just want to make sure we can get back with like a thoroughly scoped answer. Yeah, makes sense. Let me.
Bradley Eral (30:46) Ask you this. I know Brad’s getting back from pto, Tuesday. I want to make sure we’re putting you in a good spot internally from your side, what are your thoughts we could do later in the week or we can prioritize and get you in a spot where before Brad comes back, you have essentially the options, what would be best for you personally?
Sean Behan (31:11) I’d rather have the right option than a bunch of potentials. So, if you guys need some extra time to do it, it’s a lot better to just give him here’s. Some solid options than spaghetti. Perfect.
Bradley Eral (31:24) With that in mind, how does Thursday or Wednesday look for you?
Sean Behan (31:30) Thursday, I have either one o clock or after three?
Bradley Eral (31:35) One o clock or after three.
Bradley Eral (31:41) There it was. And that was Thursday, you said?
Sean Behan (31:46) Yep. On the 20 sixth.
Bradley Eral (31:51) Bear with me. I’m just coordinating calendars here. Yeah, we could do four 30 eastern if that works. Sure. Perfect. I’ll send over the calendar invite. We appreciate everyone’s time, the additional context. And yeah, excited to come back with some options here for you guys. Good.
Nikhil Oza (32:11) Question. I know, I think Brittany if I hear you correctly, there are some additional webhook events coming down the pike in the next couple months. I believe… yep, would that like, would you be able to provide that high level? Yeah.
Brittani Luyen (32:28) I can send it over an email today. Like so you’re looking for like what’s coming down the roadmap today, that could potentially make this integration a little bit easier and improve the overall experience? Yep, I can send that over today or I’ll send it to Brad. Absolutely. Yeah.
Nikhil Oza (32:38) Okay. Sounds good. Yeah, because I looked at the API, there are some things that I was hoping that it would be there as a webhook. I didn’t find it. So if there’s something coming down the pike, you know, what do you?
Brittani Luyen (32:49) Hope is there? Because the world is your oyster, we’re building this now. So tell us what you want and we can definitely evaluate it as we’re scoping this, yeah.
Nikhil Oza (32:56) Definitely. I think when I was evaluating, I didn’t see a lot of statuses or the document request and things like that, like need attention, but like what need attention? That detail, I didn’t see it, but I may have missed it. So things like that, anything that we need to let our user know the statuses, the action items they need to take, or the approval or denials, and the reasons, things like that, anything that’s available that’s great. But if coming down the pike, I would love to know that.
Brittani Luyen (33:21) Yep. I will send that over that’s exactly what we’re focused on in the next coming weeks is implementing webhooks for lifecycle tracking of the application. So I think that’ll be exactly what you need.
Nikhil Oza (33:30) Perfect. Thank you. And then.
Bradley Eral (33:33) I guess as long as we got the broader group, was there anything else missing that you identified in those API docs? I want to make sure we capture this now as we take things back internally… I think.
Nikhil Oza (33:45) At a high level, that’s what I noticed, right? Those webhooks, you know, the iframe was not that like single sign on support that kind of thing. So, once we have a little bit more understanding, you know, from the proposal, we may have additional questions, but that’s what I gather from my cursory look at the API, doc, Ben, do you have any questions? No, no, I don’t have anything.
Brittani Luyen (34:05) Additional.
Bradley Eral (34:06) at this time, gotcha. Well, we’ll give you some time back today again. Thanks for the time and looking forward to next week.
Sean Behan (34:14) Thanks.
Bradley Eral (34:16) Thanks, guys. Thanks all.