Automate More, Onboard Faster: Unlock the Full Potential of Merchant Central

My name is Jen McDonald. I am a customer success manager here at NMI Merchant Central, and joined with me is our product manager extraordinaire, Jaren Ruckman.

Excited to have you all here with us today. We got some great things to cover. Kind of the topic of today's webinar series is automate more and onboard faster. So what features and enhancements have we released recently that help you achieve those two things? So excited to go over those with you. And without further ado, we can start going through, going through the webinar.

Alright. So the agenda for today is that with respect to automate more and onboard faster, we're gonna cover some core features that we've had and, like, how that relates to these features. And those are web forms, custom properties, help desk automation, and then status triggers.

After we've gone through the deck, we are gonna hop over to the demo where you can actually see these items in real time. And then finally, we're gonna open it up to some q and a.

Now before getting into it, just wanna introduce you to our customer success team. As mentioned, my name is John McDonald. I'm a senior customer success manager and would like to introduce to you my colleagues, Anne Marie as well as Sivu. If you haven't spoke to any of us yet and would love to be in touch, we would love to hear from you. You can contact us at customer success at n m I dot com. That email will also be included in the video recording that we send you, early next week.

Alright. Okay. So web forms. What exactly is a web form? Well, it's essentially a digital form to collect data. And to help you visualize that a little further, I'm gonna show you a couple of examples of web forms.

So example number one, if you go into a website, in this example, this is our nmi dot com website.

If you select, let's say, to get in touch, you see this form to collect information on the right. That's effectively a web form. It's it's you can embed a web form on your website to collect lead information.

Another example of a web form is to take it a step further is, let's say, an MPA, which is what you're seeing here. It's a more detailed web form that collects that information from the merchant to allow you to board that merchant to a particular processor, for example. Not necessarily limited to processor, but any application that you need them to fill out. Finally, another example of a web form is sorry. I don't mean to say finally.

Last but not least, is account update. So you can update, let's say, a lead. Maybe a merchant has updated their bank account information, for example. You can update a lead using a web form.

So jumping back over to the presentation, some of the automation features that we've released with respect to web forms has to deal with the creating and updating lease, conditional logic, so you can embed if then statements on a web form. So if this is completed, maybe make this information required.

So that would be some conditional logic example. And then also, we have linking esign. So if you complete a web form and you wanna link an esignature form, you have that capability as well. And then we're also gonna share with you some overall workflow automation tips. Included in that is some additional reporting and visibility that we've made with respect to web forms and their status.

Next up is custom properties. So exactly what is a custom property? It's a basically, a tool that you can use to segment your portfolio based off of certain attributes, I e custom property.

To help you visualize what custom properties are, I'm gonna show you what we've built on our demo site.

So if we go over onto our demo site, you can see the different custom properties that we've created.

I e and then these, like you can think of it as attributes. So we have processor, and then under processor, we have pricing type.

That's the great thing about custom properties is that you can create different hierarchies as well, referral partner and then account closure reason.

So Jaren's gonna dive a little bit deeper into the different enhancements and automations that we built around custom properties, but kinda on a high level, what we've built is custom properties and how that can drive user assignment, how that can drive, updating different lead fields, how custom properties can hide lead fields or tabs. So depending on, let's say, what processor you're working that merchant is assigned to, you can hide different fields or lead tabs that don't necessarily pertain to that another processor, for example.

And then last but not least, custom properties is the one thing that stays with the merchant throughout the life cycle of the portal. So for example, whether it's leads, whether it's merchants, whether it's help desk, whether it's residuals, you'll always have access to filter and define by the custom property in that particular area of the portal itself.

Jumping into help desk automation. So help desk is our proprietary ticketing system. If you've worked with ticketing systems in the past, this is essentially same thing, but it's already embedded within the CRM.

And with respect to automation, we've driven some work flows and some preconditions depending on the ticket type, and those are all listed here, and we're gonna go through those in detail. Finally finally, another big, enhancement that we've made with respect to help desk is ticket outcome. So depending on a ticket outcome, you can change the lead status. Previously, you'd have to manually go in and change a lead status depending on a ticket outcome. But with this automation enhancement, you're able to automatically change the status depending on a lead out or sorry, on a ticket outcome.

And then last but not least, status triggers. So when you bring on a new merchant for the very first time or maybe you're just updating a merchant, there's certain stages that that merchant must go through. And status triggers are what we use to move those that merchant through the different stages.

And we built a lot of new enhancements and automation with respect to how to automate that journey and that movement of that merchant through the different stages. And we're gonna go through these items listed here in further detail during the demo.

Alright. Okay. So without further ado, I am gonna let Jaren introduce himself as well as he's gonna jump into the demo and go through all of the items that we've just discussed.

Alright. Hey, everyone. I'm Jaren Ruckman. I'm the product manager for Merchant Central CRM. And I'm gonna take the items that Jen just showed us and and walk through actually seeing those in the system, see how they're set up and can be used. And, as we go, of course, we have this open to questions. So we'll be addressing those a, a little bit after the the demo concludes.

So with with that in mind, I'm gonna open up my screen here, and we'll get started.

Okay. So I'm in an example lead here. We're gonna work through the same order that that Jen had looked at when we were checking out the, the slides earlier. So we're gonna start from the lead here looking at it, though, because the lead is really the hub of everything. Everything connects to the lead. Everything is tied to it in some way. That's, of course, the first thing that people work with when you're starting to sell an account and get them boarded and live and processing.

So we, of course, know that the lead has a lot going on. There's a lot of information in it.

Sometimes it can feel like there's there's too much, and we wanna make things faster. We wanna automate. We wanna take out manual steps. We wanna decrease the chance for errors. All of those human element things, the time, the effort, the attention.

So when we look at the lead, I'm actually gonna go down to our our web forms tab. So I actually have a a pretty pretty filled in lead here at this point with a lot of information, but the web form allows a couple things. One could be a static web form link that you have that could be public through a website. It could be in an email signature.

It could be just sent out. But on this lead, I'm actually going to use a link that is tied to this lead. So we can prefill the existing information and then collect more information, hopefully, to get me further along in the application completion process or just to get more information along the way. So I'm gonna go to my web forms tab and pick a specific one here, and I'm gonna generate and open this.

Now there are a few different options here. You can also preview it if as the agent or ISO, you just wanna see what the web form looks like. Or if you wanna send it by email or SMS, you can pick those. I believe it's just gonna remember what you last selected, which is convenient.

So I'm gonna pick generate and open.

Okay. It's gonna give me a little warning, just making sure that it knows that I'm opening this, and it's gonna be marked as opened.

But in this case, we're gonna see the form on page, and all that information I already had in my lead is collected. So if we imagine that I open this or maybe I emailed it to a merchant, it's up here on the screen. We're gonna see certain required fields. We're gonna see different pages that I can go through. And at the end after the summary is the submission.

So a couple interesting things that the form can do here. One is, of course, filling in the lead or updating it. You have different settings you can apply for if you have an existing lead, if you want that to overwrite certain information or just leave it as is. In certain cases, maybe the lead already came in. You don't and it and it's progressed through your workflow. You don't want the status to change when a new web form submission comes in. You wanted to keep that as is.

Also, we've got the ability to display and hide fields and set requirements with what we call conditional logic. So I'll show you an example of that. With the entity type, we see that that's required here. So I'm gonna pick entity type, and I've got LLC as a selection.

The federal tax ID is required. If I switch this over to sole proprietor, all of a sudden, federal tax ID is not required. I know I'm gonna get the SSN from the owner that's coming on a later screen, and so this requirement has changed.

Another example, I'll look at the monthly volume. This is a required field. I'm gonna type in fifty thousand dollars for monthly volume.

There's no change. Now if I go over fifty thousand dollars in my example, even, I think, by a penny let's see. Well, there we go. That's a much bigger number.

So five million. All of a sudden, I've got a bank statement field, this section that's shown up. I've got some instructions, and I have a document that can be uploaded here, and it's required. So I can dynamically change what's displayed in the application on the screen and what's required.

So I had previously set this to be hidden by default and to only show if this number goes over fifty thousand dollars.

And you'll see it's still true at fifty thousand and one. If I go to exactly fifty thousand, it goes away. Those settings are, of course, completely up to to you. I'll show you a quick look at how that's done in the manage web form screen.

So we're gonna go to my example form, and we're gonna go to edit the form. And when I'm in that screen, I've got, of course, all the fields and sections that I'm working with. Those are going to display here. But at the top, I've got a conditional logic button.

And when I open that, it's gonna show me the two things that I've already built here. If the monthly volume goes over fifty thousand, show the section called bank statement.

And if the drop down called entity type is not equal to sole proprietor, require the field called federal tax ID. It's very simple to add these things. You can make them pretty dynamic. They're just if bins, and you can add conditions and actions. So multiple things, will need to be there. And you can do and and or. So it's a pretty simple logic builder.

But you'll just go through and select these things.

So if I say, oh, the, the ZIP code is a certain one. I could do something. Very easy to build through there. It's also nice that when you look at the conditional logic table, it's gonna show you everything that's built. But also in the in the form here, it actually tells me with this icon that there's conditional logic affecting this field. So I can click that, and it takes me right to it here. It's pretty handy, pretty convenient, so you don't lose track of that, and it shows you exactly what's going on.

Now the back in my web form settings, I've also got this form that's tied to esign. So one of the big time savers is I've got a form. I've collected it. I love the web form experience.

I send that to my merchants. But how do I get the esignature done? You can tie the document to the web form. So as soon as the merchant or other party completes the web form, they hit submit.

They're gonna be taken straight to the esign screen. Everything from the form and from your lead would be populated into the esign document where it needs, and any requirements that remain on that form would be shown. Ideally, you've got no other requirements other than signature, and it's an extremely fast process for the merchant to complete.

Now other things that we recommend here in the settings with the web forms, you'll see right here for settings, there's a lot to it. So there's all these different settings. A lot of them have tool tips to help explain, but you'll see the confirmation page that you can set dynamically. You can also set automated reminders. So you send out a web form, and you want it to go back to that recipient and make sure that it gets followed up on, doesn't get lost. We see the esign selection here.

And then the other automation that I mentioned earlier, filling in the leads, setting different settings on the lead. That includes custom properties, which which we have a few examples of here. And then, of course, you have auto importing new leads. That's generally gonna be on unless you're doing testing. And then you've got the option to update the lead further. If it already exists and you send out the lead link from it or a public form, maybe you don't want it to update the status, so you leave that unchecked, but you wanna make sure it updates the custom properties. This is the setup I would use for that.

Now that's the a lot of the the web form automation that we wanna focus on. Now that we've just talked about custom properties, let's pivot over to those. So let's go to the configure screen for the custom properties.

We're gonna take a quick look at that. Jen highlighted it a little bit earlier. These examples that I've set up are, completely usable by anyone else, but also, we know a lot of our clients have come up with new ways to use custom properties to describe and track information for their accounts. So we see that I've got a few here. This one's nested under here. I can set permissions for the group and the user class for who sees those or can edit them or if they're required.

I can also go into the given custom property and give it reference fields, which we'll see in a bit, and I can set the actual values for that drop down. So for the processor of list here, we've got, I think, four or five entries. Let's see. Yeah.

Four entries. So I can make that selection on a lead. And that custom reference info that I have, I can populate that here. That means if I pick Fiserv North on the lead and I wanna see the relevant information about that, I can put in things like contact numbers, emails, anything other details that I want about that to show to people when they make that selection so it can be used as a reference.

And, of course, the main automations that we have here are with the let's see. Edit here. You can choose, which which fields are gonna be populated and the auto assign for the users. So if I pick a certain custom property, this is very similar to what we see on the help desk settings for tickets.

You can auto assign users every time or round robin or do it by user class. Those settings are right here. And lead tab field visibility. So if we go back to our lead, we see a lot of things here.

And right now, I've got TSYS pricing. I've got ScanX for underwriting, other underwriting related tabs.

And that's because on this processor drop down, I've picked TSYS FSP. This is my portfolio where those things are relevant.

If I switch this to Fiserv North, Page reloads. Now no more TSYS pricing. We have Fiserv pricing. The other underwriting tabs are removed that I said weren't relevant. Now my page is a bit more focused. Now you can do also do that specifically by fields.

So it doesn't have to be at the tab level. There could be certain pricing fields or other account information that you wanna gather that applies to one processor you work with or maybe another ISO, and it's not relevant for the others. So So why have it on screen? Why have it displayed? There's already so much information that you have to collect. You can get those things out of the way so yourself and the agents can focus on just clicking the information that you really need.

Now with the custom properties, it's important to mention that custom properties is is unique in that the information carries throughout the system. So on a lead where I've gathered this information during the sales process, I've got this information selected. I don't wanna lose sight of that. So when I actually go to my linked merchant record, I'm gonna see that same information, of course, in the profile tab because that shows my linked lead. It's gonna look like a very similar display.

I'm gonna go to the details, and, that information is populated here.

Now what's also important is my my merchants page. I go to my merchants.

Now we're getting outside of what shows on the lead. We're actually looking at merchant records. So not on that exact example, but on others, we can see processor was filled in, pricing type. I can select what I wanna show on the my merchants page, and I can also interact with it on the filters.

So the automation of selecting that information has carried out through the other parts of the system. And finally, if we go to the residuals page, we'll see that once again. So it perpetuates throughout. It also shows on help desk tickets, so you can use that reference info whenever needed.

So let's see. I'll go to one of the examples here.

Alright. So pricing type for this account was set here to flat rate. So this is all information that was set on the lead. It can always be changed on the lead. This is not based on the the merchant's information or whatever is coming through your processor feed, but it's information that has automatically propagated out to these other reports so you can keep the information handy and use it as needed.

Now moving on from the custom properties, we're gonna go on to the help desk. So there's a lot of information here. And what used to be called our help desk ticket types page is now called the help desk ticket settings. We've added a lot of lot more capabilities and some automation in this area.

So you'll see different tabs here. If you haven't been in here in a while, there's there's a lot more that can be done with it. And what we're gonna focus on is the main driver for help desk tickets, their ticket type. And we'll see in a given ticket type, when we go to edit it, we, of course, have the name.

And if it's active, you can default the priority, so preselecting it based on the ticket type. You can place it under a category, which helps you to group ticket types. You can give some help information that shows when a person selects that type.

We can also automatically calculate the due date based on the ticket type. So you don't need to manually select it. Of course, you can make edits like that, but I can say all gateway setups should be within two days, and I specify business days here.

And here's some new features. You can default the subject and the description for the tickets, and you can also have it dynamically fill information. In this case, it's gonna pull from the merchant because I'll have a merchant account by the time I'm doing the gateway setup, but you can have it pull from lead information as well. And as you're filling in the subject and description, all you have to do is type the at symbol, and so you can start to look through the list. But I can also type in DBA, and it's gonna give me all the fields that match, whether it's from the lead fields or from the merchant to fill that in. And that would look just like this. So if there's fields you already have that are relevant to this ticket and you don't want the person who's working the ticket to have to go over to the lead or look them up somewhere else, you can get that information prepopulated here so that it's there at the time of creating the ticket.

And, of course, we have our checklist. This is an automatic workflow for building out what you need to do with the ticket, what has to be done to get it completed, resolved, and moving on to the next item. We have a ton of options for how to set the requirements for it, but you've got files you can attach in the step. You require a file attachment like we have set here, and all the steps have to be done before you complete a ticket.

So you're automating the instructions, the workflow for a ticket. This helps, of course, new staff get familiar with processes or existing staff, making sure that they're not cutting a corner. You get all these things that are here. Each time you complete an item, it's marked in the notes of the ticket to show that it's been done.

And that helps you make sure that everything is done the way it's expected.

Now down below, we've got auto assign. We we saw that it's just like on the custom properties, you can auto assign users to a ticket. And we have a new feature here too, auto attach files by label. So just like with the subject and description, you wanna pull information from the lead.

This also allows you to pull files from the lead. So if you're doing a gateway setup and maybe you already have a gateway form attached to the lead, you can have it automatically look for that file based on the label and bring it to the ticket so you don't have to go download it from the lead or select it to be pulled over. It would grab it automatically for you. So that's that's a really important piece to save time.

You wanna make sure people get the right file. This is gonna do it by the label so you know it's the right one.

Now one other piece to show you in the help desk tickets is we mentioned categories. This is a way to group specific ticket types, but also categories are where you can link link outcomes.

So with outcomes, that allows you to set when you resolve a ticket, what actually happened for that ticket. Of course, any ticket can be resolved, marked as closed, but what truly was the outcome.

And with that, you have different linkings you can do, and it shows you conveniently here or if you go to the outcomes what's available.

But if I go into an outcome here, I can say, alright. Merchant canceled.

What's that outcome? The new option that you have here is to set the linked lead to the new status.

So when the ticket is closed and this outcome is selected, I could automatically pick and say, well, we need to move that lead over to a status, and I'm gonna pick something generic because it's just a a generic option there. But I'll I'll just say merchant canceled, unsatisfying with fees. So that will specifically update the linked lead when that ticket is resolved and that outcome is picked.

So that makes it so that you don't need to go over to the ticket, remember to update something. This can be very important in the boarding and deployment and account service state states. Probably not so much when you're first selling the lead because you probably won't have help desk to get involved at that point. But, certainly, once your operations team gets involved, you start to set up and deploy the account. This will be a good option to keep that lead in sync with the other work that you're doing for it.

Now finally, we're gonna go to Oh, Jaren, before you, hop on to the next topic, I just wanted to point out for those of you that are unaware because of the ticket type that Jaren had just demoed here was the gateway setup.

So you have the ability to open NMI gateway accounts through two different methods in Merchant Central. One of them is through tickets like Jaren just displayed. You can just go into a merchant or a lead and hit create ticket and create that gateway type ticket. The beauty of that is that it takes all of the lead data and sends it over to our gateway so that you don't have to rekey data. So there's that method through the help desk, but there's also through the Turbo app as well. You can configure Turbo app so that you can submit an account to the gateway within that Turbo app experience, again, not having to rekey data. So any opportunity, again, to automate and not have to do any manual work is a win and just helps you automate faster and onboard faster.

Alright. Good. Thanks, Jen.

Alright. We're gonna go on to lead lead status triggers. So this is the original automation point with with moving information and taking on tasks. We've got our new lead status management page here. We have the ability to expand out the statuses, within it and, of course, configure by group or applying those changes to all other groups, which can be a great time savings. And you'll see the little lightning bolt over on the side. For each given status, you can set status triggers and, automated actions.

So let's say I'm gonna go into one of the statuses here. This this will be sent sent agreement. So it already tells me how many are in that status. I'm gonna click the lightning bolt, go into configure the the status triggers.

Now the first thing to learn about status triggers is there's there's two ways to do them. There's instant, what we call status change, and there's delayed status age. So if a ticket or if a lead remains in that status for the set amount of time, then it will do the actions versus doing them immediately upon moving to that status. So let's look at some some the most important examples here that we wanna see. Very top ones to look at, sending emails. You can send an email to the contact on the lead.

So I move a lead to a status. I wanted to look in a specific field for an email address. Maybe this one needs to go to the owner, or I wanna send it just to the generic contact address. I'm gonna pick a template.

So that email template will prepopulate, and I can do follow ups, automatically send another message after a set number of days if we don't have a response and we stay in that status.

And I can do the same kind of thing for sending an SMS. So I can pick the field where the number is, use a template, use my sender information here, and then, of course, I can send an email to my own user. Now users are go typically going to be notified when a a lead status changes. But if you wanna do something specific, let's say it's gone to a status that was moved maybe by someone doing outreach, and you wanna make sure that besides the normal notification, you get an email that goes to the assigned user. So I want it to go to the sales rep, the sales manager.

I want it to maybe be like a an email template, like, urgent, you know, go go check this lead, something important like that to make sure that it becomes on the radar of the person who's needing to work that lead. And I can specify the set sender from email. So I've got an option here. Do I want it to go from the group, from the acting user? Like, who who did the status change, a specific user, or even a custom sender? Just fill in some other information.

So I've got that selection there. And what's what's really neat here with the with the emails when I can send those externally is I can use the custom property information for the sender, and I can check the custom property from an alternate template. So imagine back on our lead here, we've got the processor drop down, Fiserv North, Fiserv Omaha, Paysafe TSYS. Let's say whenever I board that account, I want an email to go and get sent out to the contact for that merchant, and I want it to include certain information in the email.

Now based on which processor I've boarded it to, that information might need to be a little bit different. Maybe I need to give them certain contact numbers or processes to follow. So when I go into that trigger, I can say, alright. If the processor is PaySafe, then I need to use a different email template than this one.

And that template would be built however I've specified to include the information that I need. But that's one example of how you can dynamically change the automation based on the custom properties. So the custom property really does carry out to a number of places and is very versatile in how it can help you automate and dynamically act on information.

Now the other things to show you with the status triggers, we already saw how when you change a ticket to a a resolved status and set the outcome, you can change the lead status. You can also have a lead status create a help desk ticket.

So besides on the resolution, on a ticket status change, you can have it create a ticket. And that can be either automatically, it just does it behind the scenes, or it can prompt the user on screen, and you can set the requirement that they have to create the ticket for that status to change. So you would set the default ticket type for it to use. And just like we saw on that ticket type automation, you can set the the subject and description. You can use the app character to fill in information. It's all about taking the time that you would spend to do those things that might be kind of monotonous or tedious or just tough to get to and making them happen automatically.

Another important thing to see here in the automations is the ability to set a date and time in a lead field. So when that status changes, you wanna record that specifically into a field. Maybe what was the boarding time? What was the time it was deployed? When did it go live? You can specifically update a field when that information passes in. You can also set the name of the user into a field that goes with that, and you can put that into reports like your advanced reports tab on your home page, get all of that information in a table, even export it if you wanted to do some math to look at different, differences on dates and times.

And that allows you to just prefill that information from those status changes.

And last two things we wanna look at is send to external CRM. This means you can share a lead automatically with another Merchant Central CRM site. Maybe it's a ISO, sub ISO, or agent and referral program that you have. They're going to board it to TSYS. You send the lead over to them, and you set all the information to be sent over when you set up that lead sharing profile. And they'll map that into a status and collect that information into their fields, and they can later then send the merchant back to you once it's got processing data coming through. So this is an inter site feature between the CRMs, which is very helpful to make sure you don't have to download information or email it over, saving you lots of time, making sure the information is accurate when it gets pushed over.

And the final thing to show you here is auto boarding to TSYS FSP via Turbo app. So we accomplish this with boarding profiles and equipment templates. So some things that you preselect and then set on the lead so that with the change of the status, the information can be submitted to TSYS FSP through the express and PPM APIs. And if there is an issue, maybe some information wasn't present or there was some kind of validation error, you can set it to an exception status.

That means it's got a a failure. It's gonna move it to that status, and it will also post a note into the lead with the information about why it failed. So besides having what we'd call manual boarding onto TSYS FSP, you also have one click boarding, and now we have this automated boarding. So for those on that platform, this can be extremely helpful.

If you get the information in, whether it's daytime, nighttime, or weekend, the auto boarding can make that process happen for you. And even if it's not successful and it goes to the failure status, we'll let you know what has been the problem, and you can remedy that and then be able to board it very quickly.

Now that concludes the demonstrations here. So, Jen, I will pass it back to you. I'll keep the screen on in case there's any specific questions we need to ask answer.

Thank you, Jaren.

Yeah. So, hopefully, you're starting to see kind of the big picture with respect to not only our core features and functionality with respect to onboarding merchants, but the the automated steps and enhancements that we've implemented with respect to those core features with the overall goal of helping you onboard your merchants faster.

Especially with status triggers, you can really lean in on that and just kinda move the lead along automatically as long as they meet, like, certain criteria. So from, let's say, when that lead converts and that NPA is signed, they can essentially board potentially automatically if it's through TSYS, for example. And if you have gateway Turbo app set up, a gateway account gets created. So from conversion to gateway created, that means that merchant can begin processing payments.

That can happen within minutes if you have that all all of these steps configured and set up. Now, obviously, it depends on the risk, your risk profile, and whether you take on risk or not, but the options are there for you, to, like I said, to onboard faster.

And just like one thing to also note, one thing that we're also working on is one x or merchant portal. So the ability to bring in all of our gateway functionalities into Merchant Central. So it's gonna be a one stop shop to not only manage your merchants, but also for your merchants to log in as well and not have access to, like, their statements, their transaction data, but also virtual terminal if they need to be able to process payments. So more on that to come. We'll likely host a webinar in early q sorry, in early twenty twenty six that will go over our, one x merchant command center merchant portal.

Alright.

So without further ado, I think we can hop into some q and a.

I'm gonna just take over Karen.

Here we go.

Alright.

So first question we have is, can we also set up the help desk to create a new ticket when a ticket is resolved?

Jaren, do you wanna take this one?

Yeah. This is one thing that can be, accomplished indirectly, and it's usually the ticket outcomes automation. So if you set that outcome to update the lead status and then you have a status trigger to create a ticket based on that lead status, you have indirectly taken the resolution of a ticket to create another ticket. It's going to happen within seconds or moments at the most and does require the lead status to be updated, but you can accomplish it that way. And I expect if it's something during the, boarding or deployment stage or even account closure that you're probably updating statuses at that time anyway. So, hopefully, it should fit right in with the workflow.

Perfect. Thank you, Jaren.

Next question is, this is on the web form. When prompting for SSN for the sole prop instead of the Inc or LLC corporation type, can you still determine where to map the field within the CRM?

Yes. The the mapping and the list of the options within that drop down field, are specific to to your site. So you have control over what shows there, which field it is in the lead, and what that logic would be with it.

Perfect. K. I see the option for Tisa's FSB auto board, which we did cover. Is that available now?

Yes. So we have that listed in our knowledge base. It's listed as a, kind of a bay beta or a pilot option. So if you don't have it now, you can contact support. They can enable it, and you'll just need to set up the equipment templates and boarding profiles to be able to use that. I always recommend when you first use it, try the one click boarding first because that will reveal any issues with, the data validation and requirements not being met, and then you can build up to using the auto board functionality. So it's kind of a, crawl, walk, run scenario where you go from manual boarding to one click to automated?

We do in addition to once we enable that feature for you, there are some help desk articles as well as a video on our help center that describes that. But, feel free to reach out to us at support, and you can cc customer success at n m I dot com as well.

Alright. Why do we not see all of the options on our instance of Mersen Central as compared to the demo being shared?

Ah, yes. So there's there's some things that we have just built where, this this call, I should have mentioned earlier, is the reveal of those. So we'll have those available very soon. I was just fairly excited to get them in front of people. So, one option that, was new is, like, the default subject and description in the ticket types, and also one that we didn't go into, but the ability to send a web form link via a status trigger. So those will be out, very soon. I'm expecting within within a few weeks, but wanted to show them here so we could make sure that people were aware of them.

And in addition, a lot of the, manage kinda site options or site setups that you saw, under the manage drop down, a lot of that information is only available to admins only. So depending on your user class, you might not see all of the options that we did display.

So two I think it's twofold. Some of them are new features, not even available in production yet, and then the other is depending on your user class, you might not have access to those.

Alright. Is TSYS auto or sorry. Is Autobore to TSYS the only gateway processor available? I'm working with Elavon.

Is that gonna be available in the future?

It's not planned for Elavon at this point. We are exploring other processors based on, which are used the most across the client base. But for now, it's it's only the TSYS FSP option.

When will Merchant Central include conditional logic on the lead field tabs? It exists for the web form, but not internally. Why is that?

Yes. So the we built it in the the conditional logic into the web forms because we knew that, you know, adjusting that experience, had the most value or impact in that merchant experience, typically, which is done in in the web form. So that was the focus first. We're not ruling it out for the lead field side, but, we may have some some other logic that plays in with that, that we're looking at for the leads. So it it may be part of something else, but it's certainly something that we're considering.

K.

If we have other processing banks that we work with, are we able to include them in the CRM? I'm assuming this is for potential processor boarding consideration.

It I guess I guess we would have to know exactly who you're considering because we do have a couple of processor integrations right now that are in in beta. One of them being Clearant, for example.

We're just wrapping up Elavon as well.

So, it depends on the processor, but generally speaking, it all goes on demand, our client demand. So if we have a lot of customers that are asking for a particular processor boarding integration, we will definitely consider it. So send an email to customer success, and we'll make sure that we get that, on our end of our product board for consideration.

K.

So for web form conditional logic, will there be more logical conditions that will be added from it, like getting three fields added to one hundred percent? And if it gets over one hundred, will there be a pop up note? I I guess I'm reading that as, like, more complex logic for conditional.

Yeah. That that one, I I always call that one field math. So we think of it in the in the lead or in the web form. Maybe you're totaling the percentage how, card acceptance method. Is it moto, card present, card not present, thing things like that. So the ability to total those and then see if that number has exceeded one hundred percent or it's less than one hundred percent, that's that's also another consideration that we have, around field math, and that could be any basic kind of math operation, summing, subtracting, multiplying, and dividing, and that's another item that's under consideration.

Somebody okay. So

if you are interested in, Merchant Central, formerly known as IRS CRM, we'll send out some details to you on Monday with how to how to be in touch and glad to see what you saw here today is resonating.

We've only touched a surface of what this CRM can do. It has a lot of capabilities and functionalities.

And, yeah, we'll be in touch, and we can definitely do a more in-depth demo of, like, what what what we can do and and what processors we're connected to, so on and so forth.

Alright. So there are no other questions. Thank you all so much for your time today and joining and having and being engaged with with all of your questions. We do hope you found this useful.

We are constantly re releasing new features and enhancements as you can see. We do make all of our new features available on our help center. So if you go on to the help center, you'll see new features and enhancements where we list everything that we've released from the previous month. You'll also see a pop up in the portal itself.

We aim to have these webinars quarterly wherein we do a deep dive on all of our new features and enhancements so that you are aware and then you are empowered to implement them yourself.

At NMI, we do have a lot of products that we offer. I don't know if you saw or you've noticed when Jaren was doing his demo, you saw the ScanX or the underwriting tabs. We do offer automated underwriting as well.

In addition, we have our gateway. So we are connected to the NMI gateway. We have all the gateway functionalities along with NMI payments. So depending on what solutions you need with respect to your merchants and managing your merchants and being able to offer payments and processing payments, so on and so forth, or getting a mid, we do have solutions for you. So please feel free to be in touch if you want to learn more.

And, if there's nothing else, thank you so much to Jaren. Thank you so much to everybody behind the scenes. Thank you so much to our partners. Without you, we wouldn't be able to do this and offer this. So we appreciate you, and we appreciate you joining. And if you have any suggestions for future webinars, we are all ears. Thank you so much, and have a great rest of your day.