Convert More Leads, Onboard Merchants Faster: The Power of NMI’s Web Forms

Welcome, everyone, and thank you so much for joining our web forms webinar. So excited to have you all join us today.

My name is Jen. I am a customer success manager here at NMI Merchant Central and joined with me as one of our many product experts, Marco.

So for those of you that are brand new, welcome. Happy to have you here. And for those of you who are either web form experts or have attended our webinars in the past, welcome back. Glad to have you join us here.

So before we get started, just a couple of housekeeping rules. This webinar is being recorded, and we will send it out to everyone start of next week, likely Monday, but potentially Tuesday so that you'll have it for your records.

Next, we are gonna open it up for questions at the end of the webinar. So if you have any questions, feel free to drop them in the chat, and, we'll save some time at the end to go over those questions.

Alright. Let's get started.

So the agenda for today is that we're gonna cover what is a web form for those of you that don't know or are curious, and then common use cases for web forms.

Then finally or not finally. Sorry. Then we're gonna hand it over to Marco who is gonna demo building a basic web form, and Marco is gonna go over the latest enhancements that we've recently implemented for the web forms.

And lastly, we will open it up for any questions.

Alright. So the question is, what exactly is a web form? For those of you that don't know, it is an online form that your merchants or prospects can fill out and submit, and it will automatically update Merchant Central, the CRM system.

Essentially, it's like a digital version of your paper form but smarter.

And once a merchant submits the form, like I've mentioned, the lead gets created in the CRM system.

Any, supplement information that was included in the web form gets stored to the CRM under that lead. And you can set it up so that, the lead that gets created is automatically assigned to a sales agent to follow-up on.

Then in terms of common use cases for web form, number one would have to be lead generation.

Who does not want to generate more leads? Right? More business. Great.

With web forms, you can create a link and embed it directly in your website. So if you have a a merchant or a potential prospect that is searching your website, they can easily sign up using our web forms. And what that what happens is that when they sign up, the lead gets created into the CRM, and then you can set up the steps for proper follow-up.

Alternatively, maybe you have a sales agent that's working directly in the CRM, and they wanna be able to send out a form to collect more information from a potential prospect. They can do so, using web forms.

So lots of great use cases to, generate those leads and and get some excitement and get the information in those leads in the door.

Secondly, we have agent assisted sign up. So maybe you have your agents are out on the field. They're speaking with prospects directly in person, and they wanna enter information on their phone or enter information on an iPad, for example. They can do so using web forms. And what that does is that it automatically updates or creates the lead in in the CRM.

Excuse me. And then moving on to the merchant application, you can provide a digital guided experience with built in logic using web forms. And, basically, what it allows you to do is capture the right information the first time. As we know, merchant applications can be long and arduous process to fill out. But with our web forms, you can provide that guided experience and making sure you get that information right the first time.

Change forms. So your your clients, your merchants, they constantly change information. You can use a web form to update that information, which will in turn update the CRM.

And lastly, but not least, stay modern. So with web forms, you can send it out through SMS, and you could, again, provide that digital experience that people have come to expect in this day and age.

So those are some of our common use cases that you can use for web forms. Not limited to this by any means, but just wanted to call these out in particular.

And without further ado, we're gonna hop over to a demo, and Marco's gonna take you through how to build a basic web form.

Thanks, Jen.

Let me pull up my own screen.

Alright.

As Jen said, thanks everyone for being here. We are gonna start with just a very basic, lead form creation since there are some people here who I think, have not had experience building out a web form, and I just wanna show what that kind of simple straightforward experience is like with our drag and drop editor. And then for those of you who have been existing partners and are maybe already using web forms, go into the details of what we've been adding over the past six months to a year that have made them more advanced than they were when we first released them and get into the details of how you can really tailor the experience of them, to fit those use cases that Jen mentioned.

So when I'm in my Merchant Central site under manage web forms, and this is where you'll see all of the the web forms listed that you've created, I've got mine grouped here, so you can create different groups to organize them. So I have applications, obviously, some demo items. You could separate them by processor or however you see fit based on the forms that you are creating.

So I'm gonna create a new form. And if you've been with us for a little while, you've seen this, this window kind of grow in the number of features that we have here.

So there are more settings to add, but that's great because it allows you to do more with the web form. So there's different email templates that are used at different, parts of the flow. So if you're sending it from a lead, it will use this email.

So let's do merchant account application.

We'll select our submitted template.

You can decide if you wanna notify people. So whether you're assigning the lead once it's created automatically, those people will get notified. Or if you have managers or other operations folks that you want to know when this specific form is submitted, you can have them notified on their own.

We've also added confirmation pages, which I'll get into a little bit later. That's what is seen by the applicant once they complete the form. As Jen noted, we have added SMS support, different types of form. I always start with a blank one and then who this form is actually gonna come from if you send it out.

Choose a couple of default statuses here, and then you can choose your properties and your, custom settings here if you have any custom properties set up. So that's the behavior that the lead will have and the properties it'll be assigned once it's created.

I'll go into some of that more in detail in the enhancements portion, but for now, I just kinda wanna show what we're going to see when we, actually build this form.

So I chose a blank form. This is a blank slate. If you have, say, an MPA that you've already mapped in your system for your processor, you can actually select for that to be what generates this. So because all of the lead fields within Merchant Central tie together so that you only have to enter data once. You're not duplicating data entry. We leverage the mappings that you probably did during implementation or if you have our PDF expert Mario doing new mappings for you as you add new MPAs. Those mappings can then be used to kind of populate this, and then it's more of just a a user experience editing where you're moving things into new sections and cleaning it up a little bit so it better fits your desired merchant journey or whoever the applicant is gonna be on the form.

So, again, I'm just gonna do a basic lead form here with a couple like, a contact form that you might have on your public website.

So over on our left, these are our widgets. So we have layout widgets and section widgets. So you just drag those over to add them. So layout is gonna be kind of the layout of the page or pages, and then section widgets are gonna go within sections, on a page.

So you can structure data, collect documents. You can do copy, some validation, all of which we'll get into in a little bit. And then I'm gonna go over to my field. So this this mimics what our lead field, tabs and values look like over here.

And I'm just gonna click and drag it over to my section and start organizing the fields here.

As long as I click and drag correctly, you can have multiple fields on a row. You can have multiple sections kinda side to side, but we are going to keep it very simple, like I said, and just do a basic contact form.

Let's do phone number as well, and we'll do a contact full name. And then from there, I would just save the form. If I had any errors, such as missing a signing email, if I had a esign document linked to it, it would let me know, and any other data validation to make these are set up correctly.

You can rename the field. So if you want the user experience to kinda look different than what your internal usage is, so if you didn't like company name, you wanted business name, you could actually edit that and change the title. It doesn't change your lead field. It just change, changes what's presented on the form itself.

And then these are just other settings you can have here. So if you want it to be required or read only, maybe you're using the default values to populate something and you don't want the merchant or whoever's applying to change it. It's just informational, you would set it as read only. You could hide it by default and then use our conditional logic to show it if certain criteria are met and then min max symbols so that, you know, things like ZIP code if you only want it five digits, Social Security only nine.

You could set that as the max there. And then you can change the field type as well. So if you're collecting a phone number, making sure it's a number, things like that. And then placeholder would be, you know, showing a a an instruction maybe.

So fill in your business address or something of that nature.

So then one of the features that's new or enhancements, that we added within the last six months is our embedded functionality. So now that I've created this form, I want to actually embed it.

So if I go over to my lead form, I do share, and we have two types of sharing options. We have link, and we have embed. So what I created at first was a link. And then if I wanted to do an embed, I would select embedded, go through basically the same thing I did in my regular form setup. And then, again, another new feature that we'll go over in a little bit is kind of the custom styling per link, and then you can get fine grain detail of, like, updating the automation specifically on this form that overrides the overall form settings.

So what does this look like?

You basically get a simple embed code. So this is a little dev environment. I am not a developer. I am not technical, but I was able to pull our iframe that we copy pasted from the, share settings there, put it into my little dev environment. Thanks to chat JPT.

And then here's what that web form would look like embedded within my web page. So, again, I'm not a web developer.

If you have them, they could definitely make this much, much more appealing, but that form this is a different form, but this is the form that I created and embedded here, all by myself, to be filled out and then submitted straight from here. So that's great for a contact form on your public website. If you're an ISV or working with ISVs, you can generate an embed code of any of your forms. So you can do the full merchant application with esign and embed that directly in that software.

So that's a great use case there.

So couple questions are coming in. I'm gonna wait a little bit just because I wanna get through some of them, and maybe we will address, some of them in what I've covered.

So that's just a basic creation of a lead form.

Very simple contact us. But even if you're doing a full MPA, it's still just dragging and dropping those sections and really easy to work with and has the familiarity of the lead record that you work with, probably pretty frequently.

So our development process for web forms, like I said, in the past year, we've added a lot. The The web forms feature, I think, was released about a year and a half, two years ago at this point. And in the past year, we've invested a lot in it and are going to continue to. So I'm very excited about that. This is my baby. So, you know, only nice things to say about it if you have questions or comments.

I've seen it grow and evolve over time. So we kinda put our heads down, develop a bunch, and then kind of have these different release stages. So back in September of last year, we had some of our biggest features, come out for web forms to take them from, yeah, this feature exists. You can collect some lead info to, okay, this is a more dynamic web form that you can do more with and have these different use cases.

And then, in February, we had three different releases with all of these features that started to tailor it more to those different use cases, and I saw some names in in the attendee list. Aaron, I think you're here. A lot of this was feedback from partners. This isn't me just sitting at my desk thinking, what could make this better?

It's direct customer feedback, and their use cases being put into action and us trying to find ways to solve problems of how do we get March and supported, how do we reduce abandonment, how do we go through this flow more efficiently. So that's what we're continuing to work on and and try to solve every day with these releases.

So, I don't wanna speak about each of these without showing them. I'd rather demo. I think that's better.

One note I wanted to make for the custom branding per share link, This overrides branding by group, so you kinda saw the custom color settings when I was going through and creating a new share link. If you want that enabled, you do have to reach out to Merchant Central support just because we didn't want anyone who is using the group branding to have it overridden.

So you kinda make that choice of what level you want to do the branding, the colors, the logo, all of that on. So if you're using our custom properties, you most likely want to use the custom branding per ShareLink. This is really great if you have kind of a referral partner relationship.

Maybe you have banks that are referring to to you, and you want each of them to be set up as a custom property since we are enhancing those capabilities pretty quickly as well, but still have their branding like groups, has offered in the past, but maybe you're not relying on groups as much anymore.

So going back over to my web forms, let's go into a larger format form. So this is gonna be a full MPA with assigning doc at the end of it, and I'm gonna start by opening up the settings to show a few items.

So I went through this quickly before.

A lot of new things have been added. Like I said, this has expanded over over time. We'll hopefully make some adjustments to the UI to make it a little bit easier to digest. Just haven't gotten to that yet as we've been more focused on the features and delivering those.

So confirmation pages, this is what the merchant or applicant sees once they complete the web form. And we have two options. You can either do a confirmation page or redirect to a different Url. So if once they complete the web form, you want them to go to a specific landing page on your public website that you've built, you could choose to do that Or within Merchant Central, if I go into my confirmation pages so if you go into manage, search for confirmation pages, here's where you manage them.

And then this is kind of an example one, that's populated with some dynamic fields. And then let me bring up the editor.

It's a lot like our rich text editor. You can paste images in here. You can control what the wording is, the display, background image, if you want.

And then it can also be combined with the URL option as well. So up here, you can see I've got a redirect URL. So, again, that could be your public website. And after ten, thirty seconds, or a minute, you could redirect the applicant to that web page. So they see the confirmation page. You know, thanks for applying or thanks for filling out our form. You'll be taken to, you know, this web page, and then you can provide more information on that web page if you want more control over that.

So that's the confirmation pages.

We have also added save progress.

So you may have seen on, the web form here, it has a save progress. Not as useful for a quick lead form like that, but really great if you have a longer form MPA. If it's a merchant filling out, obviously, they are also trying to run a business, so they may get busy in the middle of filling out this form and need to come back to it. So they can save progress, and let me type something here, and they would just enter their email for this to be sent out after.

So they can resume. They'll get a link in their email, that they enter here that's unique and comes with all of the data they already entered prefilled within there. We've also seen this used interestingly for the agent assisted workflow that we were mentioning, where your agent could start filling out the form, be working with the partner on-site, and then save this and either send it themselves or send it to the merchant that they're working with so that the merchant can then finish filling it out and then be the one to execute the esign document at the end so that your agents aren't doing it on their behalf since that's not a great compliance practice.

So if I jump back to settings again, we're gonna do some bouncing around here. So, stay with me and, try to cover everything.

So with the save in progress that I just mentioned, we then have the in progress, like, notifications.

So you can send web form reminders if an applicant hasn't completed that web form. So whether or not they've saved progress or not manually, it doesn't matter. We're kinda saving that all on the back end, and then we'll send out a reminder, at different cadences, and you can set what that cadence is. So second reminder, I want, you know, one day after, probably trying to find that balance. So I don't want to annoy the merchant, but I would really like them to complete this application and get them onboarded and processing so that we can monetize their payments.

Alright.

I alluded to to the SMS sending. So, previously, you could only send these by providing the link or sending via email, kinda like our esign functionality, but we did recently add support for SMS. So just like emails, you create an SMS template with the application URL dynamic field and then select whichever template you created for it here. And when you trigger that, e or that SMS out to the partner, they'll have a link. They open it. And when it's sent from a lead record, it is also prefilled with any data that you have already collected.

Esign. Esign's been around. You can add multiple.

We added support for the custom properties. That's been in there for a little bit. And then one thing that was asked for for a long time and we finally were able to make an update to is updating the properties of the lead when you have an existing lead that the data is being submitted for. So public form means it's like a static link, kinda like what you saw here where it's just empty. It's blank. Nothing is prefilled.

Whereas, what we call sessions or the lead forms is when you're actually in the lead record and you generate it from here, it creates a specific link unique to that lead so we know where to put the data back to and that it's prefilled with whatever data is entered on the lead.

So going back to those settings, if I want an existing lead updated when a public form is filled out, this is basically the merge duplicates functionality. If it recognizes based on that email, hey. We already have a lead for them. Let's update this.

I can choose which settings are updated. And then if I send the lead or send the web form from a lead so that the data is prefilled, I can select which settings it updates. So what was happening before is only the lead data would be updated, but you wouldn't update the status, the assignment, the campaign source, custom properties. So this lets you control it so you can build out your funnel and use web forms to go from a brand new lead to, you know, maybe presigning to fully signing and filling out their final MPA web form.

And then once that's done, it hits all the hits all of the other automations so that they can be boarded, via turbo app or or if you're doing it outside of Merchant Central on your own. So that helps you really build your funnel using web forms since those are typically a little bit more user friendly, than filling out the the full PDF MPA in the Adobe signing document.

And then that way, once they get to the Adobe signing document, it's just clicking to sign. They've already filled in everything that you require them to fill out in the application.

So that's some of the settings options and then share forms. So this is an overall recommendation and advice I give to our partners about how to configure web forms.

If you are using the same form with the same fields, so, typically, if it's the same processor agreement, you wanna try to keep your forms down so it's less to manage. Use that form and then create unique links for your different maybe reps or use cases if you're sharing these with a referral partner. And that's where some of these updates came, and feedback from partners was if we're going to do that, we need to be able to have more granular settings on the share link level, that override the form settings so it's unique to that link, whether it's an assigned, assigned sales rep or a referral partner.

So if I go to add a new link, again, I can do link or embedded. I'm gonna do link in this case.

You can select default templates, and those are the default values that populate the web form.

And one thing we haven't quite released yet, but it's almost ready, is using custom property default values. So if, say, you're setting them based on referral partner or the processor, and having fields just defaulted in value, pricing is probably the prime example for this. You'll be able to use the custom property for that rather than the default template, and that will override the default template. So you don't have to set up all these defaults for different use cases and different pricing. So it should save you some time there. So keep your eyes open for an announcement about when that's actually available, on your sites.

Form sender is new. So, previously, this was a top level form setting, but now on that specific link so I had chosen Adam before. Now I could do Anna as the form sender, and this could be Anna's form. We auto assign Anna to this anytime this form is submitted.

This is her link. She's maybe a rep, and she's gonna use this specific link, so we can associate the leads with her, and she can share it out, to her leads to fill out. She can then also have her own confirmation page. So, again, in that specific, like, sales rep example and this link being unique to them, if I go back to my example confirmation page, my data is a little inconsistent since it's a a preview and doesn't have a property associated with it.

It's gonna populate populate who that sales rep is, their email, and using those dynamic field variables, like we have in our email templates and elsewhere within Merchant Central so that you don't have to have an email per rep, especially if you have hundreds of reps or hundreds of referral partners. You obviously don't wanna manage all of those.

Alright.

So the next item is the branding per link. So, again, alluded to this earlier. But, again, if this was a referral partner or even if it's an agent, maybe the agent has their own branding or preference on on the styling of the form, you can create your own styling here. So it's got our default Merchant Central, like the blue colors, but I could change this, you know, over to maybe the NMI colors and make this more purple.

Add a header logo that's different than what the site logo is. I'm actually gonna add that one.

And then I can preview any changes that show up, and that will be unique to this specific link. It won't change any of your logos and settings and your groups or your site overall. It'll be just for that link.

And then lead automation's still there. This just overrides the the form level.

Alright. Let me pause quick for just to review the questions.

There's a lot of info.

So, yeah, multiple if we have multiple agents, will we need their own web form to be tagged independently? So that's kinda what I just covered. Our recommendation, use a main web form. So whether that's process or MPA or a general lead collection, the fields are going to be the same. Use that same web form and create different share links for each. Do the auto assignment for who it should be assigned to, and use the share links and embed options to kinda share that out without having to manage the form. Because if you choose to make changes later, say, you wanna add conditional logic, you wanna add a required field, it's much easier to do that once on the form level than have to go through, you know, dozens of forms you've created for each of your reps.

What would be the best way to tag relevant agents if a lead is filling up the form and doesn't name the agent? This can easily get lost. That ties back to the auto assignment as well, but let me loop back to, something in regards to the saved progress that we will be releasing soon as well. So like I said, we're continuously saving the data that is kind of being entered on the form. So I think it's every, like, ten or fifteen seconds. We'll save it regardless of a manual save happening.

And then if you go to the web forms reporting tab on the home page, you'll see an in progress status.

So if I click on that, you can actually see where someone's at in their form.

And this also kinda tracks just opens in general. So if there's no data, it means that, you know, I was testing something. I opened it and then closed out of it. But that kind of gives you a sense of abandonment.

So you can see, is this form working? Is it getting in the right people's hands? Like, if I have five hundred opens, but only ten people have filled it in, is it not friendly? Is it not being shown to the right people?

You can use that data to go off that, but then we click the little grid to show the progress data.

This is the groups, the sections that you built into your web form. So I can see, okay. This company, like, they filled it out. Why didn't they submit it?

They're pretty much done. Now I can have a sales rep follow-up with them. You can look at it based on on the form name. So that's how you could get into it on a sales rep kind of basis and have them kind of more proactively following up with these leads who maybe you don't know our leads yet because they haven't finished filling this out.

That way, you know, you don't have as much abandonment. And then if you can see here, if the email and phone are entered, you can use our email and dialer functionality directly from here. So your agent can just, you know, call them. They can send an email, say, hey.

I saw you were, you know, filling out this form on this website. Can Can I answer any questions? What do you need to to finish this up, to get more leads through the door?

When should we use a new web form versus the post token URL through the API for our referral partners to import leads?

My advice regarding post tokens would be don't don't use them anymore going forward if you can avoid it. It's an older tool. When we first built web forms, we did leverage the post token, functionality. But I think, like, a year and a half ago, we intentionally moved away from using post tokens as the base tool for importing the lead data.

It gave us more flexibility to do a lot of these settings, the in progress stuff, the merge duplicates and updates, that are much better than the post tokens ever have been. So I would recommend setting up a form. You know, again, if it's if all of your referral partners are using the same form, do one form, create a different link for each of them, do the custom branding per link, brand it for them if they want, and then provide those links. That, I think, will be a much better experience for everyone.

We've worked with the post tokens internally as well, and it's just never as smooth of a process.

Okay. I'll jump back to questions more towards the end, but all of those were kind of relevant to where we were at and some of the stuff we had covered.

So let me go back into our web forms again, and I actually want to show one second here.

We're gonna go over some of the features that are specific to the form editing and form configuration, so more specific than the top level settings that we went on.

So one of the biggest things I think that we've added in since building web forms is the conditional logic. So, you know, if then statements based on what data is filled in. And the purpose of this is obviously to make it as streamlined as possible for whoever's filling out the app so that they're only seeing the the fields they need to actually fill in and are relevant to them. Otherwise, you have, you know, extra fields and, like, do I fill this in? It's optional, but maybe I need to provide it. So we can avoid that by using the conditional logic.

A common situation, for example, I think I have a moto questionnaire.

Okay. I don't have the full moto questionnaire, but, if we look at the sales profile, this might indicate certain things where I need more information.

So, for example, if the volume is over a certain amount, maybe I need to require a different field or a document upload. So we're gonna add this logic, and we're gonna start with kinda what triggers it. So in this case, we're gonna do a field, and that field is the monthly volume. And if that monthly volume is greater than, no, twenty five thousand, then what do we wanna do?

So we could show a section that was originally hidden. We could show some helper text. We could make a field required. So, see.

It's not really relevant, but let's say it's Moto, for example.

We could require that that field is then filled out. So you could also hide it by default and then show that field once it, matches this criteria.

Or in the case of volume, if it's, meeting high volume where you know you're gonna need bank statements, you could actually do, document upload. So we're gonna say we need, you know, the supporting document.

I don't think I've named those, but you would have it named as, you know, bank statements, and then you would require that. So that way, they have to upload the documents once they're filling out the application so that you already have them when your underwriting team goes to review.

So that is the conditional logic again, one of the things that I'm most excited about, that we've added.

Again, sales profile where kind of a lot of the conditions and criteria happen for determining what's next and how to handle the merchant. So we added some validation. So we had seen some errors happening when trying to board merchants where, you know, they said card swipe was seventy and keyed present was ten.

Where's that other twenty percent coming from? We need a hundred percent total. So if I close out of this, some validation is actually now a a little widget, so I can add that in here.

And then it has helper text to kind of show an error when a hundred percent is not met. And in the fields, I'm gonna select which, which fields I need to total up to that value.

Keyed and then one more.

So I want these three fields to total one hundred. The field must equal a hundred. I think a hundred is the most common use case. I don't see many there, like, must be fifty. Guess for owner, you could say the owner percentage must be greater than twenty five percent since for, you know, the compliance things, you only need to collect owner information for those twenty five percent and greater owners.

But, yeah, that's what you could do there. Hide by default so it only shows it up once they start entering that, and then you control the the messaging here, what it looks like, if you want it to be bright red to make sure they know. And then, you know, you must fill this out to equal this value, so they're not confused why they're they're getting errors.

Let's see. That was a big one.

Copy button, I think, is another, you know, subtle thing but important. So copy buttons in the past on web form specifically only did from one section to one other section. You can do fields within the same section. You can do fields from one section to multiple sections, sections, like an address that you expect. You know, it could be the same for DBA, legal, possibly owner.

So couple of updates here to make it more like our lead functionality. Copy button, if you're familiar with that.

What you can do is choose kind of the display of it. So if you wanted it smaller, maybe you're only doing one field to others, you could actually do this as just a copy icon and put it more embedded within the form rather than its own separate thing at the bottom.

But then we have other options, obviously. So icon and title puts both of them in there, title only, and then pull this down.

I am working with the team to find a little bit of improved UI for it since this is crammed, but this is where you choose the field mappings. And, again, this could go from one field within the same section or, you know, one field to many sections, wherever you need to copy them. But you select the field you want it to copy from and where you want it to copy to. So, again, mostly used for address, from business to legal, especially to do phone numbers, emails, things like that, if with small businesses who kind of expect them all to be registered and set up. Like, maybe it's all the owner information just to save them time so that they're not frustrating that they're entering this data over and over and over again.

Alright.

So that is, I think, the bulk of it. Let me just pop over to the enhancements option.

Yeah. I think those are the biggest ones that I wanted to go over.

So we're actually at the demo. And then a few other small ones just worth noting. If you're using the embeddable, we added support for local host as the domain. So if you're working in a dev environment, you can do that. We don't have to add the domain in. We did Google Maps address autocomplete, a lot like the lead field.

For that, that's actually worth noting.

When you're dealing with the address kind of auto populate, you select the related address fields. So I would do city, DBA, state, and ZIP so that when I fill in the address here, it populates these with their values based on the address I entered. In order for the fields to show up in this drop down to relate them, they need to be set on the lead field as those field types. So we know it's a state field. It's a city field. It's a zip field. Otherwise, it there's no way to tell what kind of field it is, and just showing everything isn't a great option either.

So Tool tips for pricing and fees table also coming.

So previously, each of the fields could have them, but on the on the pricing tables, there was no tooltips to maybe explain more in-depth what that fee is when it's charged. So you'll see all four of the items in the fee table. Enter your tooltip content there, and you can expand them to to show more if it's hard to read.

Alright. I have gone over a lot. I've talked a lot. Hopefully, it's good content.

Aaron Minmax is new, especially for, like, special characters.

Previously, if it was, like or special fields. Previously, it was just, like, you know, basic text fields and things like that that had min max. So, one bug with that that we're gonna be releasing a fix too soon is for the social example. Right?

A US Social Security number is always going to be nine digits. Currently, you can't set the min and max as nine. It wants them to be different values. So we're gonna make it so you can set those both as nines so they have to enter nine digits, since, obviously, eight would not be an acceptable one.

Jen, do you want me to just roll through the list here?

Sure.

Yeah. Just before we get to questions, thank you so much for taking us through that demo, Marco. Wow. Lots of information, and super exciting stuff that we've been working on. So regardless of your level, whether more basic, we got you covered. If you just wanna create a basic a basic web form to put embed on your website, it's quite straightforward.

Right straight through to advanced. If you like like those advanced features and you wanna be able to implement them and add that more robust guided experience, we have those tools for you as well. And we have a very detailed, well, help center available. So all of the features and functionalities that we've gone over today are available in bite sized chunks on our help center. So we do strongly encourage you to go to that, along with the video that we will make available.

But we just scratched the surface of all of the features and functionalities that we do support within the web form. So like I said, if you wanna learn more, we do have articles on our help center.

And all in the name of helping you grow your business, generate the leads, reduce abandonment, offer a world class digital experience for your prospects and your merchants.

So, thank you. Thank you, Marco.

Yeah.

Alright. So, yeah, let's let's get into some more questions. Yeah.

I think this is real quick.

Can I do the Oh, yeah? Forgot about the road map.

Just I teased some of the readings.

That's the most exciting part.

Yeah. I teased some items in the demo. And, again, a lot of this is customer generated feedback. We are listening. You know, I've talked to a few of you frequently.

The canny things, I do read them. I do see them when you submit feedback, and I'm thinking about, you know, what the value is and how we include those. So in progress reporting, we looked at using your custom properties to default the field values rather than the actual default templates. And then this is kind of it seems minor, but I think it'll make things easier and more consistent as we're merging how public links, so just that static link you share out, operates and is configured with how sessions, which are generated from the lead record, work so that they're one and the same.

They were previously separate. So the branding that you set on the, custom property or the individual share link, excuse me, wouldn't necessarily show up if you were sending it from a lead record. So we're gonna be merging that so the branding stays consistent no matter where you're configuring it, and that's just one experience. Any changes affect both workflows, both experiences.

So you're not like, why is this using my group settings, and this is using the the link settings?

And then kind of a longer term, we're starting to tease out, and will be more like end of q two into q three releases, open banking integration. So partnering with Mastercard. If you're using ScanX and doing the whole MRM solution in your underwriting, rather than just entering your routing and bank number and using our Gayak Bank integration.

This will be the user authorization where they log in to their, actual online banking, choose their accounts, and then that authorizes you to pull certain information, which will create scoring rules around, so that you can do a better and faster underwriting process, and have that option, both on in ScanX and Merchant Central. Conditional signing documents. Again, Aaron, I know you're on the call. I know you want these as well.

Basically saying, you know, if this criteria is met, we also want to add this document for signing beyond whatever the base document was that was selected. So if you're maybe offering additional product products, maybe it's cash discounting, maybe you're tracking device kinda sign up, and you need them to sign a lease agreement or agree to a product edition where there's a fee that can then be added and stacked into the signing doc at the end based on them checking that checkbox or saying yes to to that product or service in the application.

And then editable pricing permission. So dynamic pricing is another way we're calling this. So, basically, you could authorize and permission certain users to set the pricing and have an editable view of the form to change the pricing and then generate that form, that's unique now with that pricing to send out to to the merchant to complete.

That way you don't have to kind of start with the partner on the existing form. It's kinda like a two step process of, setup and then actually sending out to the merchant to complete.

Non esign doc generation isn't immediately part of the scope for conditional signing documents, but it is still on my radar, Aaron.

Hey. Let let's yeah. We have a couple other questions. So let's get to those. I know, really engaged group here today, so thank you so much.

What is the best way to avoid duplicates If an agent has created a lead to manage their pipeline then sends a web form to the lead to fill out, will it create a duplicate?

And I believe we covered this under the web form settings, Marco, but maybe you wanna just elaborate.

Yeah. I hope I understand this correctly because I'm maybe thinking you're trying to use, like, a pregenerated one specifically for that partner. They should use that base link if they have default values that make sense. Use the default templates or coming soon, the the custom properties. But the merge duplicates functionality, so the update public form or update existing lead will identify based on the email just like the rest of our merge duplicates functionality.

So you can choose whether it creates a separate or new lead.

So, yeah, I think that's the answer to that to avoid duplicates.

It gets a little tricky if you have, say, a merchant who serial entrepreneur. They have tons of locations. They're the primary contact with the same e email on everyone. If you know that, then maybe you wanna disable that setting in that link or create a separate link for it if you have, like, a really big deal where that's gonna happen. But you should be able to avoid it with just configuring that merge duplicates, setting or not.

Perfect.

Thank you, Marco.

Yeah.

If we want to use more than one form to get the full information of a lead as per the sales process, can each form fill in a specific each form fill in a specific part?

Yeah. So I think my recommendation here would be you more so have separate staged forms depending on what your workflow looks like in the sales process. If, I guess, if you just want kinda one of those forms, that stuff starts to show up as they fill in, you can either use multi page, which I didn't go over.

But you can add multiple pages as we saw with this MPA form.

If that's the experience where you want the full form and to break it down, whereas in the past, we only had the ability to do one long one. The other option is if it's different points of contact where you're incrementally getting more information from the applicant, then you could potentially do fewer or you could do, like, smaller broken down forms and use the, like, update existing lead data and send them from the lead record.

So, yeah, maybe reach out to support or myself or Jen, if you still have questions about that one because I I think we can answer it, but I don't know that I'm I understand the use case quite well enough.

So I think the next one is when you send SMS, which field does it pull the number from?

Let's grab a form. We're gonna generate and send the SMS. So, again, there's a few things I I didn't cover in detail already. This is a good opportunity.

We also made some updates to this generate portion of the web form tab in the lead. So generate versus preview or generate and open versus generate and preview. Preview will not let you submit it. Generate and open actually brings the actual form, which can be filled out and submitted.

So the use case there that we made the adjustment for was referral partners filling them out. This gives them an easier way to open the form directly from here. Previously, you had to go into, like, the email that was sent out, to the end applicant and, like, open the link from there, which wasn't convenient. So we made it available in here.

Obviously, you see SMS now. And then we also show the original web form that created this lead if it came in, through that channel. So you'll see all web forms filled out by this lead at any point. But going back to the SMS, so lead special phone, this is how SMS works in general.

So I click on that error. It's gonna take me to the field that needs to be filled in.

Save my lead.

And then that's where it's gonna generate the regular SMS pop up that you would see if you were sending a regular SMS, and then this is the unique link for them to open the form with.

Yes. Webinar will be available, afterwards, so you'll be getting an email with the recording. I think we have a a short survey, about the webinar, and you can submit any follow-up questions there if you think of things after as well.

Moving through this. Is there a way to tie a web form to a PDF that is not esign capable?

Kind of address that, from one of the other ones I saw in my other chat window.

Not yet. So, currently, it's only the application, the actual signature signing documents from esign that can be pulled in.

So, for example, if you're doing some sort of change form that didn't require a signature, you would use that to collect the new info, but then you would your team would have to manually update the lead or go through a help desk ticket, whichever kind of option you're using, to update it again depending on what that that process is. So that one is under consideration.

I believe it may be tied in depending on our capacity to some of those coming features that I saw. So I'll keep you all posted on that.

Multi page. Yeah. Oh, go ahead. Yeah.

Sorry. No. No. No. You you got it. Multipage. So we we we you just just cover it quickly, but then this follow on question is, can you omit an entire page based off of what was answered previously?

Don't think we can do an entire page. I believe it's a section. So let me see. If field what do I wanna do?

I don't know. This one's easy because it's a basic math operator. Let's do average ticket greater than a thousand.

Then yeah. We don't have a full page. It would be a section. So a good idea because I didn't I wasn't sure on that one. So if you have the time, that would be a good one to submit in the feedback platform, and we can take a look at, as we try to expand the conditional logic a little bit more as well.

K. I think we have one time for one more question, Marco.

So, the autosave feature do you want oh, what about the autosave feature? Does that add the data to the lead, or is it stored somewhere else?

Yeah. So currently, for the auto saving we're doing in the background, if the user and it applies to if the user is manually saving their progress.

The lead does not get created. The main kind of viewing place for that is this in progress reporting on the web forms tab, but it currently does not create a lead for, like, an in progress one. I believe one of the partners, I don't know if they're on, had kinda requested that because they it is a lead. Right? At that point, they started entering data, and maybe it's they've entered their contact info and just haven't finished the MPA. It would probably be worth creating a lead.

So definitely happy to consider that one, but it does not currently.

And, Jen, I'm gonna do one more just because there's, like, a couple questions related to field validation.

There is not custom field validation at this point, including, like, regex operators.

And then this also relates to, like, verifying fields, like, verify the Social Security number, make sure they match or email address matches.

That one has been coming up more lately, with the making sure two fields match. I don't have a timeline on it, but that one is definitely one we want to add as we improve the validation, the conditional logic, all of that. So I'm open to that idea as well.

Great. Thanks. Wow. We got an engaged group today. We didn't even get you all the questions.

Really appreciate all the feedback. And to Marco's point, we are listening to you, our partners. Therefore, if you have any recommendations, feel free to submit it in what we call Canny, which is the feedback tool that is available to you in Merchant Central. If you go under your name, under the settings, you'll see feedback.

We are listening to you, so strongly encourage you to enter any feedback there. There will be a survey submitted or offered when we send out the video. If you have any topics for future webinars, please submit it in the survey. We wanna hear your feedback.

So here at Merchant Central and Amai, we offer choice, flexibility, and modularity.

So regardless of what solution you're needing, whether it's the gateway, whether it's embedded payments, whether it's automated underwriting, processor boarding, reporting, residuals, you name it, anything that with regards to managing your merchants, we have a solution. So if you wanna learn more, we encourage you to reach out to us directly.

We'd be happy to to share more information on the solutions that we have.

On that point, Marco, if you wanna just roll forward, our next webinar is coming up on April the seventeenth, wherein we're gonna cover everything residuals.

All of the work you've seen that we put towards web forms in the last few quarters, we put equal amount of work into residuals, so lots of enhancements there that we're excited to show you. We'll we will be sending out an invite shortly, so encourage you to all to to register.

Thank you all so much. Thank you, Marco, for walking us through all of those enhancements, and thank you all to our partners. We value you. We appreciate your collaboration. We wouldn't be here without you. So thanks for attending today, and, look forward to seeing you all next time.

Thanks all.