Fluent Forms plugin review and common issues

Fluent Forms sends notifications through WordPress’s mail system. If notifications are not arriving, the underlying cause is almost always PHP mail deliverability rather than a Fluent Forms bug. The Fluent team specifically recommends their FluentSMTP plugin (free) for this reason — it routes WordPress email through a proper transactional mail provider. Install FluentSMTP, configure it with Mailgun, SendGrid, Gmail SMTP, or another provider, and test using FluentSMTP’s built-in email test tool.

Conditional logic failures are typically JavaScript-related. Check the browser console for errors when interacting with the conditional field. A common cause is an optimization plugin deferring or combining Fluent Forms scripts in a way that breaks the logic engine initialization. Add fluent-form-public JS to your optimization plugin’s exclusion list. Also confirm that you are comparing field values correctly — “contains” and “equals” behave differently, and option labels must match exactly including case.

Conversational forms in Fluent Forms use a fullscreen overlay mode with specific CSS requirements. Conflicts with theme CSS that affects z-index, overflow, or full-height layouts can break the display. Test with a default theme to confirm whether it is a theme conflict. Also check whether your optimization plugin is loading Fluent Forms CSS asynchronously — conversational forms require synchronous CSS loading to display the initial state correctly.

Fluent Forms has a Design & Styles tab in the form editor where you can set primary color, background, font size, and label position without writing CSS. For deeper customization, Fluent Forms outputs forms with predictable CSS classes — the form wrapper, individual fields, labels, and submit button all have classes you can target in your theme stylesheet. The form ID is also available for per-form CSS targeting.

Yes. Fluent Forms has a hook system for custom processing. The fluentform_submission_inserted action fires after a new entry is saved to the database, giving you access to the form ID, entry ID, and submitted data. Use this hook in a child theme or site-specific plugin to trigger external API calls, update custom database tables, or perform any custom post-submission logic.

Yes. These are free features in the core Fluent Forms plugin at WordPress.org. Conditional logic, multi-step forms with progress bar, multi-column layouts, and the survey module are all included at no cost.

Fluent Forms has a more generous free tier — conditional logic and multi-step forms are free in Fluent Forms but require paid plans in WPForms. WPForms has more templates and a slightly more polished visual interface for beginners. For technically capable users and teams already using the Fluent ecosystem, Fluent Forms offers more value. For absolute beginners who want templates and a guided experience, WPForms is slightly easier to get started with.

Yes, natively. Form submissions can automatically create or update contacts in FluentCRM, add them to lists, apply tags, and trigger CRM automation workflows. This integration requires no third-party connector like Zapier.

No. Fluent Forms only loads its CSS and JavaScript on pages where a form shortcode or block is present. On pages without a form, no Fluent Forms assets are loaded. This is a deliberate performance design decision that makes it a better choice than plugins that load globally.