Fluent Forms Pro sells itself on breadth, and the breadth is real. The feature list on the pricing page runs to more than sixty items across form building, styling, validation, entry management and integrations, and almost all of them are included in every paid tier rather than parcelled out by price. That makes the licence decision simple and the evaluation decision harder, because a list that long does not tell you which parts you will actually use.
The features worth paying attention to are the ones that touch what happens after submit. Building a form is a one-off task. Reading, sorting, chasing and answering responses is the work that repeats every week, and that is where a form plugin either earns its place or quietly hands the job to your inbox.
What the licence costs and what it does not gate
Fluent Forms is published on the WordPress plugin directory with 700,000 or more active installations and a free build that is itself substantial. The Pro licence is priced by the number of domains it runs on.
| Licence | Domains | Annual | Lifetime |
|---|---|---|---|
| Single Site | 1 | $79 per year | $349 |
| Agency | 5 | $159 per year | $599 |
| Unlimited | Unlimited | $299 per year | $899 |
Every tier carries the line "All Features Included", and the vendor states a 14-day refund window. Annual licences include one year of plugin updates and priority support. Lifetime licences carry updates and support with no renewal.
The point to take from that table is the axis. The bill grows with the number of websites, not with submissions or with people. A single site running fifty forms and receiving two thousand responses a month, read by eight members of staff, pays $79 a year. That is an unusually good deal, and it is the strongest argument for the plugin. It also means the pricing page tells you nothing about whether the tool fits a team, because team size never appears on it.
The four gates that usually force the upgrade
Before the feature list is worth reading, it helps to know what the free plugin already does, because the free build here is wider than most. It ships the drag and drop builder, conditional logic, conversational forms, an AI form builder, more than 25 input fields, Stripe payments, email notification, form scheduling, role management, entry export to CSV, Excel, ODS and JSON, entry filtering, form analytics, custom CSS and JS, and migration from WPForms, Contact Form 7, Gravity Forms, Ninja Forms and Caldera Forms.
Given that, the honest question is which specific gate pushes a site onto a licence. In practice it is one of four.
File uploads are the first and most common. Both the File Upload and Image Upload fields are Pro only. Any intake that needs a document attached, which covers most job applications, claims, grant submissions and support cases with a screenshot, is a paid site from the start regardless of how many other free features go unused.
Multi-step forms are the second. The Form Step field is Pro, so a long application that needs to be broken into pages rather than presented as one wall of fields requires the licence. Save and resume sits on the same side, which matters because the two usually get wanted together.
The third is repeatable input. Repeat Field and Container Repeater are Pro, so collecting an unknown number of attendees, previous employers or line items means a licence. Rich Text Input, Ratings, Net Promoter Score, Chained Select and Range Slider are all Pro as well, which covers most survey work.
The fourth is routing and lifecycle: conditional email routing, admin approval, conditional confirmation messages, double opt-in and auto-delete entries are all on the paid side. That group is the one this article is really about.
Entry management: what the screen gives you
This is the section of the feature list that matters most and gets read least. Under Entry Management, Fluent Forms Pro lists export and import of entries, advanced filtering, editing entries, a front-end entry view, printing entries, a maximum entry limit per form, automatic deletion of entries, partial entries, save and resume, visual data reporting, form analytics, and admin approval.
Several of those are genuinely load-bearing. Partial entries capture what a respondent typed before they abandoned the form, which is the only way to learn where a long application is losing people. Save and resume lets someone come back to a half-finished submission, which matters for anything longer than a contact form. Admin approval holds a submission in a pending state until a person releases it, which is the closest thing in the list to a workflow step.
Automatic deletion of entries deserves a specific mention, because it is a data retention control and those are rare in form plugins. A form that collects identity documents or health information should not keep them indefinitely, and having the expiry enforced by the plugin rather than by somebody's calendar reminder is the difference between a policy and an intention.
Visual data reporting and form analytics cover the aggregate view: how many submissions, which fields get skipped, conversion on the form itself. That is a different question from the operational one, and it is worth keeping the two apart when evaluating.
Where the entry list stops being enough
Everything above treats a submission as a record. The operational question treats it as a piece of work, and the two need different things.
A record needs to be findable, filterable and exportable. Fluent Forms Pro does that well. A piece of work needs an owner, a state, and a history of what was said to the person who submitted it. The entry screen has none of those three as first-class fields. Admin approval gives a binary pending or approved, which is one step and not a pipeline, and it says nothing about who is handling the case.
The consequence shows up on any team past two people. Two staff open the entry list, both see the same twelve unanswered submissions, and the only thing preventing duplicate replies is a message in a chat channel. Nothing in the record carries the fact that one of them took it. When somebody is away, the question "what is outstanding, and whose is it" cannot be answered from the screen at all.
The reply is the other half. Fluent Forms Pro has email notification, conditional email routing, email summaries and double opt-in confirmation, which between them cover the templated messages well: the acknowledgement on submit, the routed alert to the right team, the digest. A message written individually to one applicant about one detail is composed in a mail client. Once it leaves from there, the entry in WordPress has no record that it was sent, and the sent folder that does have it belongs to one person.
Conditional routing is not case ownership
Conditional email routing is the feature most often pointed at when this comes up, so it is worth being precise about what it solves.
Routing decides where the notification goes. If the respondent picked "billing", the billing address gets the alert. That removes a triage step at the moment of arrival, and on a site with several departments it removes a lot of forwarding.
What it does not do is track the case from there. After the notification lands, the state of that submission lives in whatever the receiving team does with email, and the WordPress entry list is no longer the source of truth about it. Teams handle this with a shared mailbox, and shared mailboxes work until two people open the same message, or until the person who answered it is not available to say what they said.
Activity logs and API logs in the Pro feature list are sometimes mistaken for a solution here. They are diagnostic records of what the plugin did, which is valuable when an integration silently stops firing. They are not a history of the conversation with the person who filled the form in.
Comparing on the axis that decides it
Three pricing models are common in this category, and they behave very differently as a team grows.
| Priced by | Cheap when | Expensive when |
|---|---|---|
| Domains | Many people, few sites | Many client sites, one coordinator |
| Submission volume | Low steady intake | A seasonal spike |
| Seats | One or two handlers | Everyone needs access |
Fluent Forms Pro is the first row, and for a single busy site it is close to the best case available. If the honest description of the situation is "one website, a lot of forms, several people reading them, and the replies are templated", the licence is good value and the entry screen is adequate.
If the description is "several people each own a subset of responses, and most submissions end in a message somebody writes by hand", the constraint is not the plugin's feature list. It is that an entries table is the wrong shape for a queue. Some teams bridge it with a workflow plugin on top of WordPress. Others keep WordPress for the pages and move the handling to a tool where the owner, the status and the reply sit on the response itself, which is easier to judge by watching it work than by reading a comparison, and worth a look at the demo of anything under consideration.
Self-hosted means the update work is yours
One line in the Pro feature list is easy to skim past: Version History. Along with the free plugin's position on the WordPress directory, it is a reminder that this is software you host.
That has a real upside. Submission data, including uploads, stays on your own server, under whatever access rules and backup regime you already run. For anything handling sensitive intake, that is often the deciding factor and no hosted service can match it.
It also carries a standing obligation. Every plugin release has to be applied, promptly, on every site that holds submissions, because form plugins handle uploads and payment fields and are therefore worth attacking. The annual licence covers one year of updates; whether they get installed is on you. Add SMTP to the same list. Notification and acknowledgement mail sent from a WordPress server without an authenticated sending path lands in spam often enough to matter, and a missing acknowledgement is indistinguishable, from the respondent's side, from a form that failed.
What to change first
Count last month's submissions, then count how many produced a reply that a person wrote by hand rather than a template. If the second number is a large fraction of the first, the form is not the problem and the handling path is, and no entry in the Pro feature list closes that gap. Decide where a response should be worked on, keep the owner and the status on the response rather than in a chat message, and weigh candidates on how they charge for access against the number of people who genuinely need it, which is the axis Halict is priced on.
Q1. How much is Fluent Forms Pro, and is the licence per site?
The listed annual prices are $79 for a single domain, $159 for five domains and $299 for unlimited domains, with lifetime options at $349, $599 and $899. Every tier includes all features, so the only variable is how many websites run the plugin. The vendor states a 14-day refund window.
Q2. Which Fluent Forms Pro features actually change daily work?
Partial entries, save and resume, admin approval and automatic entry deletion are the four that alter what happens after submit rather than during it. Partial entries show where a long form loses people, save and resume keeps a half-finished application alive, approval holds a submission pending, and automatic deletion turns a retention policy into something the plugin enforces.
Q3. Can a team of several people work the entry list without duplicating replies?
There is no owner field and no multi-step status on an entry, so nothing in the record says who took a submission. Admin approval provides a pending state but not a pipeline or an assignee. Teams generally coordinate in a chat channel, which holds at low volume and breaks when submissions arrive faster than someone is watching.
Q4. Does Fluent Forms Pro keep a record of replies sent to respondents?
Email notifications, conditional routing and email summaries are all logged as plugin activity, which covers templated and automated messages. A reply typed individually to one person goes out from a mail client, so the entry has no record of it and the only copy sits in one person's sent folder.
Q5. Is conditional email routing enough to sort submissions between teams?
It is enough to deliver the right notification to the right team at the moment of arrival, which removes most forwarding. It does not track what happens next, because after the notification lands the state of that submission lives in the receiving mailbox rather than in the entry list.