G2

Verified User in Banking

Small-Business (50 or fewer emp.)

10/30/2026

"Easy, Secure Onboarding Forms with Smart Logic and Branding"

4/5

What do you like best about forms.app?

Honestly, what I like best about forms.app is how easy it makes building secure onboarding and document request forms for our small community bank, Maple Creek Community Bank. I’m Eunice Richey, Banking Operations Specialist, and our team is only 11–50 people. We don’t have a dedicated IT developer on staff, so any tool we pick has to be something I can set up and adjust all on my own. We’ve tried a few other form builders before, and a lot of them feel bloated or make basic banking-related forms way more complicated than they need to be.

A couple months back, we needed a new customer information request form for our new account onboarding process. We had to collect basic contact details, ask for copies of IDs, proof of address, and let the applicant note which account type they were interested in. I put the whole form together in forms.app in less than an hour using the drag-and-drop builder. I added required fields for all the pieces we can’t skip, turned on file uploads, and set up conditional logic so if someone selected a business account, extra fields for business registration info would show up automatically. If they were opening a personal account, those extra sections stayed hidden. That keeps the form clean for the user and prevents people from getting overwhelmed or abandoning it halfway through. Before this, we were sending static PDF forms back and forth over email, and we’d constantly get packets missing one document or signature page. It ate up so much of my time following up with applicants.

I also really appreciate the built-in notification controls. I can set it so every new submission sends an alert straight to our shared operations inbox, and I can add separate alerts for our lead banker when a business account request comes in. That way high-priority requests don’t get mixed in with routine personal account inquiries. It’s simple to toggle those rules on and off without digging through confusing menus.

Branding is another big plus for us. I can upload our bank logo, match our brand colors, and tweak the intro message so the form feels official and consistent with our other customer communications. When people see our branding right on the form, they feel more comfortable submitting sensitive supporting documents. That trust factor matters a lot in our line of work.

The submission dashboard is straightforward too. I can quickly pull up all entries, sort them by submission date or account type, and export clean CSV files when I need to cross-reference data for our internal records. I don’t have to fight messy exports or misaligned columns like I did with some other tools we tested.

We don’t rely on it for every single workflow, and we still use some of our established checklists internally. But forms.app is perfect for our day-to-day ad-hoc requests: missing document follow-ups, simple service request forms, and pre-onboarding questionnaires. It gives our small banking team a lot of flexibility without needing engineering support. It cuts down our back-and-forth emails, reduces incomplete submissions, and keeps our onboarding flow moving steadily even when we’re busy. Review collected by and hosted on G2.com.

What do you dislike about forms.app?

Honestly, forms.app works really well for our customer onboarding and document request forms here at Maple Creek Community Bank, but there are some consistent pain points that slow me down as a Banking Operations Specialist. Our team is small, only 11–50 people, and we handle a lot of sensitive customer information, so those limitations hit a little harder for us than they might for other teams.

The biggest frustration is around the file upload feature. Our applicants regularly send in government-issued ID copies, proof of residency documents, and business paperwork. While forms.app lets people attach files, there’s not a great way to organize or label those uploads inside each submission. A customer might drop three or four PDFs and photos into the same upload box, and there’s no built-in prompt to tag what each file is for. More than once, I’ve gotten a submission with unmarked attachments and had to send a follow-up email just to confirm which document was their ID versus their proof of address. It adds extra back-and-forth that I was hoping the tool would help cut down on. Also, the individual file size caps are pretty tight, so every now and then an applicant tries to upload a multi-page scanned packet and the upload fails entirely. I end up walking them through splitting the files up, which isn’t a great experience for our customers.

I also wish the audit logging was more robust. Since we’re in banking, we need to keep clear records of who accessed submissions, when they downloaded customer documents, and any changes made to form entries. Right now, forms.app only logs the basic submission timestamp and the submitter’s info. It doesn’t track internal team activity like who opened a record or downloaded attachments. That means I have to keep a separate manual spreadsheet to log our team’s access for our internal reviews. It’s not a dealbreaker, but it’s an extra administrative step I shouldn’t have to maintain on the side. Review collected by and hosted on G2.com.

What problems is forms.app solving and how is that benefiting you?

Honestly, the main problem forms.app solves for our small Maple Creek Community Bank team is that we don’t have dedicated developers to build custom intake pages every time we need to collect information from customers. I’m Eunice Richey, Banking Operations Specialist, and we’re only an 11–50 person shop. Before we started using forms.app, our go-to method for new account pre-screening and document requests was sending static PDF forms over email. That workflow was messy. Customers would fill them out, attach supporting files, and reply back, but those emails would get buried in our shared inbox. We’d constantly receive incomplete packets, missing signatures or proof documents, and I’d spend hours each week chasing people down over phone and email to get what we needed. It slowed down our whole onboarding timeline and created scattered records that were hard to track.

forms.app lets me build these intake forms independently with the drag-and-drop builder, no coding or IT ticket required. That combined personal and business account form I mentioned earlier is a great example. I added required fields for contact information, built conditional logic so business applicants see extra sections for formation paperwork and authorized signers, and turned on file uploads for IDs and proof of address. This directly cuts down on incomplete submissions. Customers can’t skip the mandatory fields we need, and they only see questions relevant to the type of account they want to open. That keeps the form from feeling overwhelming and lowers abandonment. Fewer half-finished submissions means way less of my time spent sending follow-up emails to customers. That’s the biggest benefit for me.

It also fixes the issue of scattered customer data. All submissions land in one central dashboard inside forms.app instead of floating around dozens of separate email threads. I can sort entries by submission date, account type, or status at a glance. When I need to compile records for our internal review, I can export a CSV and pull the data over to our shared spreadsheets. Even with the quirks around file links in exports, this is still far more organized than digging through old email chains to locate a customer’s paperwork.

Branding is another piece of the puzzle it solves. When we send out a PDF attachment, it can feel informal to customers. With forms.app, I can add our bank logo and match our brand colors. The form looks official, so customers feel more comfortable sharing their personal details and sensitive supporting documents. We’ve noticed applicants are more thorough with their responses compared to when we just send a PDF back and forth. That builds a little extra trust, which goes a long way for a small local community bank like ours.

The notification setup helps us avoid bottlenecks too. Once a customer submits the form, our operations team gets alerted right away. We don’t have to wait until I manually forward an email over to the banker assigned to that applicant. We can start reviewing the request sooner, which shortens our turnaround time for new accounts. Review collected by and hosted on G2.com.