Hey Sumo-lings 👋

Yesterday, we shipped Conditional Confirmation in FormGent v1.8.

With this release, we’ve completed a major development sprint just before our AppSumo campaign ends.

When we launched FormGent on AppSumo, we had a few clear goals. One of them was to learn directly from you. We wanted real feedback from real users, not assumptions. Then take that feedback seriously, build on it, and shape the product to fit different needs.

Over the past two months, that’s exactly what we’ve done.

We shipped fast, tested ideas, fixed gaps, and kept refining the product. Today, FormGent is far more feature-rich than when we started. It can now handle a wider range of use cases without needing extra tools.

That said, we’re not done.

There is still room to improve, and we will keep working on it. Our roadmap is open and clear, and we are committed to building this with you.

But one thing I’m particularly proud of is the pace of development over the last two months. That didn’t happen in isolation. The AppSumo community pushed us to move faster, think better, and build something more practical.

So this progress belongs to you as much as it does to us.

Do check out the latest release.

Everything is included in both tiers of the AppSumo plans.

And if FormGent has been helpful for your work, a quick review on AppSumo would mean a lot. It helps us reach more users and continue improving the product with confidence.

Thanks again for being part of this journey

Masud Rana

Founder & CEO, FormGent

I want to be straightforward with you: the AppSumo deal closes in 11 days, and I think it's worth your time to understand what you'd actually be getting before that window closes.

Not a pitch. Just context.

What the Last Two Months Looked Like

Since February, we've shipped three substantial releases. Here's what they added to the product.

v1.4 gave FormGent a proper entries system. Before this, reviewing submissions meant opening each form individually. Now there's a dedicated Entries menu in the WordPress sidebar - a single table showing every submission across all your forms, with read/unread status, a notification badge, and a single-entry view that shows you the full response alongside submission metadata (browser, IP, OS). More usefully: you can edit an entry directly, without asking a user to resubmit. That last piece sounds minor until the first time you actually need it.

v1.5 was the biggest release since launch. Six separate payment blocks were consolidated into one unified Payment block that handles Stripe and PayPal, one-time and recurring, from a single place. Subscription support arrived - memberships, retainers, monthly donations - without needing WooCommerce or a separate plugin. A Save & Resume feature was added for long forms: auto-save captures partial entries even if a user closes the tab, and a personal resume link lets them continue later. Forms can now switch between Classic and Conversational mode from within the editor, without rebuilding. An Entry Log tracks every edit made to a submission, giving teams a full audit trail.

v1.6 added SMS OTP verification. Now you can verify an email or a phone number at the point of submission - via OTP sent via email or SMS using Twilio, Firebase, or any custom SMS gateway. For lead capture forms where a real email or phone number is the whole point, this changes what the form is actually worth. Default country selection on the Phone field was also added, so international forms no longer default to the wrong place for most of your audience.

What's Shipping in the Next Few Days

One more feature is almost ready: Conditional Confirmation.

Right now, FormGent shows the same confirmation message to every person who submits a form. That works for a contact form. It doesn't work for a quiz where someone scoring 90% and someone scoring 40% both see identical feedback, or a survey where you want to route different responses to different next steps.

Conditional Confirmation lets you define multiple confirmation messages and set conditions for each - so what the user sees after submitting actually reflects what they submitted. It's shipping within the next couple of days.

If you're on the AppSumo deal when it goes live, you get it.

The Honest Case for Acting Now

FormGent free plan includes more than most plugins charge for, that's not changing. But if you're running forms that’s tied to payments, lead capture, qualification, or team workflows - the Pro features are where the real leverage is.

Payment and Subscriptions, Save & Resume, OTP verification, partial entry tracking, PDF exports with digital signatures, CPT submission, Webhooks - all are included in the plan. One subscription, lifetime access on AppSumo terms, while the campaign is active.

Sixteen releases in seven months. That's the pace we've set. The roadmap has more on it. See what's coming.

Grab the deal if you’re confident that this is what you need now or in the near future.

One Small Ask

If you've already redeemed FormGent and found it useful, an honest review on our AppSumo listing would be appreciated. Not because it helps our numbers - though it does - but because it's how other users decide whether to trust a plugin they've never heard of. An honest review from someone who actually uses it is worth more than anything we could write ourselves.

Thanks for following along.

• Masud Rana

Founder & CEO

Here's Why We Built It

Hey Sumo-lings,

People are using FormGent to collect quotes, payments, quiz scores, and job applications - and then walking away from their WordPress dashboard to open Word, copy-paste the submission data, format it, and email it manually.

The form was doing its job. The hour after the submission wasn't.

That gap between "data collected" and "document delivered" is where a lot of the friction lives for small businesses and freelancers. You finally have good form. You still have to do the paperwork.

We shipped PDF Generation to close that gap.

What it actually does

When someone submits your form, FormGent can now automatically generate a formatted PDF and deliver it - either as a download link on the thank-you screen, or as an attachment in the confirmation email or both. No manual steps. No copy-pasting.

The PDF pulls in the actual submission data through dynamic tags. So Full Name, Email, Paid Amount, Digital Signature - whatever your form collects - shows up in the right place in the document, personalised to that specific respondent.

You set the template up once. It runs on every submission after that.

Templates, or a blank canvas

We didn't want people to start from scratch every time, so we built a few starter layouts:

Business - a letterhead-style layout for quote confirmations, application summaries, or anything that needs to look like official correspondence. Pre-structured with address placeholders and a clean body area.

Invoice - a table-based layout pre-loaded with payment tags: billing name, transaction ID, payment method, amount, currency, items table. If you're running payment forms through FormGent, this one is ready to go almost immediately.

Certificate - a decorative layout built for quiz completions or graded forms. Pre-populated with respondent name, score, and user details. Pair it with FormGent's Quiz feature and you have a full completion-to-certificate flow without a separate tool.

Custom Template - a completely blank editor. If your use case doesn't fit any of the above, you have full HTML control and can build exactly what you need.

A few things worth knowing

PDF Generation is a Pro feature. If you're on an AppSumo tier that includes Pro, it's already available to you under Form Settings → PDF Generation.

The first time you enable it, FormGent will prompt you to download the PDF rendering library. This is a one-time install across your site - not per form, not per template.

We also included password protection per PDF and RTL language support (Arabic, Hebrew, Persian). 

What this changes, practically

If you're running a service business and collecting quote requests, your client now gets a formatted quote summary the moment they submit - not after you've had time to type one up.

If you're running a paid course or membership, quiz completions can generate and deliver a certificate automatically.

If you have a donation or payment form, every transaction produces an instant invoice without you touching it.

FormGent has always been about not charging for things that should just work. PDF generation is table stakes for any serious form builder. It took us longer than we'd have liked to do it properly - dynamic templates, multiple layouts, email delivery, confirmation delivery. But we'd rather ship it right than ship it fast and patch it for six months.

We'd love to hear what you're going to build with this. Drop your use case below - especially if it's something we haven't thought of. Those replies directly shape what we prioritise next.

Thanks for being on this with us.

Masud Rana

Founder & CEO, FormGent

New Feature: OTP Verification

Hi Sumo-lings,

The conversations we've been having with you have been the most valuable part of this launch. You've shared use cases, edge cases, and frustrations - and that feedback goes straight into what we build next.

Today I want to talk about something we just shipped that many of you have been asking about, and frankly, something the form builder space has been surprisingly slow to get right: OTP Verification.

TL/DR; OTP Verification is live now. You can find full setup docs here: https://formgent.com/docs/otp-verification/

Here's the problem we kept hearing:

You spend time building a lead generation form, a registration flow, or a booking form. Someone fills it out. You follow up - and the email bounces. Or the phone number is fake. Or it's a bot. Or it's just someone who typed fast and made a mistake.

Every fake or unverifiable submission is wasted time. Wasted effort. A lead that was never really a lead.

We looked at what's out there. Many form builders either skip OTP entirely, or they bury it behind expensive add-ons and third-party workarounds that require you to stitch together three tools to make it work. That's the exact kind of fragmented, overengineered experience we built FormGent to replace.

So we built OTP Verification natively into FormGent - and we made sure it's actually flexible enough to use across real-world scenarios.

How it works:

When a user hits submit, FormGent sends a one-time password to their email address or phone number - whichever your form collects. They enter the code, it checks out, the form goes through. No verification, no submission.

You get to control the full experience:

• Email or SMS - email works out of the box with your existing WordPress mail setup. SMS works through Twilio, Firebase, or a custom gateway via our SMS Gateway integration.

• OTP expiry - default is 5 minutes, fully adjustable.

• Max attempts - blocks brute-force guessing after a set number of wrong entries (default: 5).

• Resend cooldown - prevents repeated resend requests (default: 45 seconds).

• Custom messages - every prompt, error, and confirmation shown to the user can be edited to match your brand or language.

You can set this up per form, directly inside your single form settings. No global switches that break everything else.

Where this actually matters for your business:

• Lead gen forms - stop collecting leads you can't reach. Require phone or email verification before the submission counts.

• Contact & inquiry forms - reduce junk inquiries from people who typed the wrong address or just wanted to skip past the form.

• Registration & onboarding - confirm a real person owns the email or number before creating their account.

• Booking & appointment forms - make sure your confirmations and reminders actually land somewhere.

• Quote or proposal forms - high-intent forms deserve real contact. OTP adds that trust layer without adding friction that drives away genuine leads.

• Gated content forms - stop disposable emails from accessing your resources.

This is the kind of feature that quietly improves every downstream process — your CRM stays cleaner, your follow-up rate improves, and your team stops chasing dead ends.

We've been deliberate about which features to build first. We're not trying to ship everything at once. We're trying to make sure that every feature we ship is done properly - configurable, native to WordPress, and genuinely useful in real workflows.

If you run into anything or have feedback on how this works in your specific use case, drop it in the comments or reach out directly. This community is shaping what FormGent becomes - and we're not done listening.

More coming. Stay close.

It’s been a few weeks since we launched FormGent on AppSumo, and one thing became very clear from how people are using it.

Collecting responses is only the first step.

What actually matters is what you can do with that data after.

We saw users trying to export their form entries for reporting, sharing with clients, or simply reviewing submissions in a structured way. In many cases, this part becomes harder than building the form itself.

That’s something we’ve been focusing on improving.

With FormGent, you can export your data easily, whether it’s a single entry or a full dataset. The goal is to make it usable right away, without extra cleanup or formatting.

👉 You can see how it works here: https://formgent.com/docs/entries-dashboard/

Alongside that, we’re putting more focus on form analytics.

Not just numbers, but insights that help you understand what’s working and where users drop off. This becomes especially important when you’re using forms for lead generation or decision-making.

👉 If you’re curious about how analytics can support real use cases, this might help: https://formgent.com/docs/report-analytics/

Many tools help you collect data. Fewer help you actually use it.

That’s the direction we’re continuing to build towards.

If you’ve been using FormGent, I’d love to know how you’re handling your data right now. What works, what feels limiting, and what would make it more useful for you.