# Fluent Support

Source: https://pluginsuggest.com/plugins/fluent-support/

## Plugin Health & Stats

- Checked 2 days ago

- Source: [WordPress.org](https://wordpress.org/plugins/fluent-support/)

Active installs

 **10,000+**  (Official WordPress.org tier)

WP.org rating

 **4.6/5**  (69 ratings)

Version

 **2.5.0**  (Current repository release)

Last updated

 **2 weeks ago**  (Nov 2, 2026)

Total downloads **348,141**

Tested with WP **7.1.4**

Requires WP **5.6+**

Requires PHP **7.4+**

Support resolved (2 mo.) **3 of 3 (100%)**

Plugin age **5 years**

Updates observed **3**

Tracking since **Sep 28, 2026**

## Historical overview

 364-day WordPress.org history

 **Download trend** Daily package downloads · last 90 days

  (7d) **3,151**   (30d) **20,034**   (90d) **45,137**   (Peak day) **3.2K** *Aug 20*

 **Active version adoption** Current usage share

-  **2.5**  44.1%

-  **other**  27.0%

-  **2.4**  20.0%

-  **2.3**  8.9%

## Quick take

Fluent Support is a self-hosted WordPress help desk for teams that want customer tickets, agent workflows, customer history, reporting, and support automation to stay close to the rest of their WordPress business. The free plugin already covers the foundation of a real support desk, while Pro adds the features that matter when support becomes a team operation rather than one shared inbox.

I would shortlist Fluent Support for SaaS products, WooCommerce stores, agencies, membership sites, course businesses, and other WordPress-centered companies that need an owned support system with unlimited agents and tickets. I would keep the setup simpler when one person can still manage a low volume of questions reliably from a normal mailbox.

 **Best for:**  WordPress businesses that want a self-hosted multi-agent help desk with customer portals, email support, reporting, integrations, and automation.

 **Free version:**  Yes. Core ticketing supports unlimited agents and tickets.

 **Paid pricing:**  Current first-year promotion starts at $103/year for 1 site, with a regular price of $129/year.

 **Current release reviewed:**  2.4.5, released October 9, 2026.

 **Hosting model:**  Ticket and customer data remain in your WordPress environment.

## Fluent Support features at a glance

| Area | What Fluent Support can do | Availability |
| --- | --- | --- |
| **Ticket management** | Run shared ticket queues with status, priority, products, agents, tags, filters, notes, bookmarks, merge tools, saved searches, and collision detection | Core capabilities in Free; some advanced operations in Pro |
| **Agents** | Add unlimited support agents and control what each agent can view or manage | Free core; advanced permissions and team workflows vary by feature |
| **Customer portal** | Let customers submit, search, filter, view, reopen, and reply to tickets from the frontend | Free core; Remote Portal is Pro |
| **Email support** | Send notifications and turn support email into ticket conversations through email piping and reply handling | Pro for business-email piping |
| **Workflows** | Automate assignment, tags, replies, priorities, conditions, follow-up, and other ticket actions | Advanced workflow automation in Pro |
| **Reports** | Track ticket volume, agent performance, response behavior, products, inboxes, activity, and time | Core reporting plus Pro Advanced Reports |
| **AI assistance** | Generate responses, summarize tickets, analyze sentiment, and audit conversations using OpenAI, Gemini, or Claude | Pro; provider API costs are separate |
| **MCP** | Connect compatible AI clients to read and manage supported help-desk data under WordPress permissions | Available in Free and Pro; requires FluentHub |
| **Integrations** | Connect customer context from ecommerce, LMS, CRM, booking, community, and messaging tools | Mix of Free and Pro integrations |
| **Migration** | Import tickets from systems such as Help Scout, Freshdesk, and Zendesk | Migration tooling available in Free |

## The main benefit is a shared support queue inside WordPress

![Fluent Support dashboard showing ticket statistics, suggested tickets, product activity, and agent performance](https://pluginsuggest.com/wp-content/uploads/2026/10/fluent-support-fluent-support-dasboard-scaled.webp)

A normal support mailbox becomes difficult once several people are answering customers. Two agents can reply to the same issue, important requests can disappear under newer messages, and the team has no reliable view of ownership, waiting time, or customer history.

Fluent Support gives each conversation a ticket record with status, priority, customer, product, business inbox, assigned agent, tags, notes, attachments, and activity. Agents work from the same operational state instead of interpreting an email thread independently.

## The ticket queue is designed for real daily support work

The current 2.x interface supports default, compact, and Grid views, along with filters for assignment, product, priority, status, ticket source, and other ticket properties. Agents can bookmark tickets, save advanced searches, merge conversations, add internal notes, use drafts, and see when another agent is already viewing or replying to a ticket.

![Fluent Support ticket list in Grid View for scanning ticket status, customer, product, priority, and assignment](https://pluginsuggest.com/wp-content/uploads/2026/10/fluent-support-ticket-display-settings-4-grid-scaled.webp)

Version 2.4.5 added more bulk actions, keyboard shortcuts for moving between tickets and closing them, a Ticket Stats sidebar widget, and filtering by ticket source. Those changes matter because support productivity is often lost through small repeated actions rather than one missing headline feature.

## The customer portal gives users a place to manage their own conversations

Customers can submit new tickets from the frontend, review previous conversations, filter by ticket status or product, search their ticket history, and reply again when needed. The portal can be embedded into a normal WordPress page with the Fluent Support block or shortcode.

![Fluent Support customer portal dashboard where customers can create, search, filter, and review support tickets](https://pluginsuggest.com/wp-content/uploads/2026/10/fluent-support-dashboard-of-customer-support-portal-1-1.webp)

The newer Remote Portal feature in Pro is useful for businesses that separate the help desk from the main customer-facing website. It can serve the portal on the main site while connecting back to the help-desk installation through a one-time key, which gives teams more deployment flexibility without making customers think about where support is technically hosted.

## Email piping can turn a support address into the ticket system

Fluent Support Pro can receive customer emails through business-email piping so a message sent to a normal support address becomes a ticket or ticket reply. Current annual licenses include different business-email piping allowances by plan while keeping email parsing unlimited.

Version 2.4.5 improved this workflow with auto-reply, bounce, and automated-mail handling, a loop guard, and reply threading based on signed email references. I would still test the full email path before launch: new inbound ticket, agent response, customer reply, attachments, forwarding behavior, bounce handling, and close/reopen behavior.

## Automation becomes important when the team has routing rules

Fluent Support Pro can run ticket workflows from triggers and conditions instead of asking agents to repeat the same triage manually. Typical actions include assigning agents, changing priority, adding tags, sending replies, updating ticket fields, and routing work according to customer or product context.

![Fluent Support automatic workflow configuration with multiple ticket actions](https://pluginsuggest.com/wp-content/uploads/2026/10/fluent-support-automatic-workflow-set-multiple-actions-7.webp)

The current release expanded automation with triggers for reopened tickets, agent responses, assignments, and customer feedback, plus conditions for tags, ticket source, agent priority, and feedback. This fits teams that already know how they want billing issues, technical incidents, pre-sales questions, VIP customers, or product-specific tickets routed.

## Reports now go beyond basic ticket counts

Fluent Support includes reporting for support activity, and the newer Pro Advanced Reports suite adds deeper Ticket Overview, Agent Performance, Product Insight, Business Boxes, Activity, Time Sheet, and AI Ticket Audit views. Historical Snapshots capture report data every six hours so managers can compare the current help desk against stored points in time.

![Fluent Support Ticket Overview report with workload, ticket volume, response, and distribution metrics](https://pluginsuggest.com/wp-content/uploads/2026/10/fluent-support-ticket-overview-dashboard.webp)

The reporting value is not only measuring whether an agent replied quickly. Product and business views can reveal which part of the company is generating pressure, while activity and time reports can show whether a backlog is caused by volume, assignment, complexity, or slow response patterns.

## AI assistance and AI Ticket Audit are optional productivity layers

Fluent Support Pro can connect OpenAI, Google Gemini, or Anthropic Claude with your own API key. The AI tools can draft responses, summarize long ticket threads, and analyze sentiment without requiring an agent to copy the conversation into another app.

The AI Ticket Audit report applies the configured provider to support conversations and returns a mood, sentiment score, and customer-perspective summary. This can help a support lead find frustrated or high-risk customers without manually reading every closed conversation. AI provider charges are separate from the Fluent Support license, so usage volume should be part of the operating cost.

![Fluent Support AI-generated reply assistance](https://pluginsuggest.com/wp-content/uploads/2026/09/AI-Generative-Answer-1024x517-1.webp)

## MCP is available even without Fluent Support Pro

Fluent Support 2.3.0 added Model Context Protocol support for compatible AI clients such as Claude, Cursor, and Codex. The MCP connection is available in the free version and uses the free FluentHub plugin plus WordPress Application Passwords.

This is different from the built-in Pro AI assistant. MCP lets an external AI client use permitted help-desk tools to search customers, read and manage tickets, post replies, and retrieve team context. The connection inherits the WordPress user’s Fluent Support permissions, so I would create access around the job an AI client actually needs rather than connecting everything with unrestricted administrator credentials.

### REST API and MCP are separate integration surfaces

Fluent Support also exposes a REST API for programmatic integrations. MCP is designed for compatible AI clients, while the REST API is the more conventional route for custom applications and scripted workflows. Treat them as separate access surfaces and grant only the permissions each integration needs.

## WordPress integrations can give agents useful customer context

The platform integrates with a wide range of WordPress products, including FluentCRM, Fluent Forms, FluentBooking, FluentCommunity, FluentCart, WooCommerce, Easy Digital Downloads, LearnDash, LifterLMS, Paid Memberships Pro, and other commerce, LMS, membership, and communication tools.

The practical benefit is context inside the ticket. A support agent can make a better decision when they can see the customer’s purchase, subscription, course, membership, or CRM information without opening several unrelated admin screens. Current workflow conditions can also use EDD and FluentCart purchase or license information where the required companion products are installed.

### Custom fields add structured ticket context

Custom fields can capture structured information that does not come from another plugin, such as issue type, environment, account tier, or a product-specific identifier. Use them for data agents repeatedly need during triage, not as a substitute for every piece of customer information already available through an integration.

## Fluent Support Free vs Pro

| Capability | Free | Pro |
| --- | --- | --- |
| Unlimited agents and tickets | Yes | Yes |
| Shared web inbox and ticket management | Yes | Yes |
| Customer portal | Yes | Yes |
| Internal notes, priority, filters, customer records | Yes | Yes |
| Ticket migration from supported help desks | Yes | Yes |
| MCP connection through FluentHub | Yes | Yes |
| Business email piping | No | Yes |
| Advanced automatic workflows | Limited / core operations | Yes |
| Advanced Reports and historical snapshots | No | Yes |
| AI response, summaries, sentiment, ticket audit | No | Yes, provider API key required |
| Remote Portal | No | Yes |
| Cloud file storage integrations such as S3/R2 | No | Yes |

I would start with Free when the main requirement is a structured support queue with several agents and a customer portal. Pro starts to make sense when support must run through a business email address, routing needs automation, managers want deeper reporting, or the team needs AI, external storage, Remote Portal, and other advanced operational features.

## Fluent Support pricing

 **Pricing checked October 15, 2026.**  Fluent Support currently offers a first-year 20% promotion. Single Site is $103 for the first year compared with a regular $129/year price. Agency is $199 for the first year compared with $249/year and covers 5 domains. The 50 Sites license is $319 for the first year compared with $399/year.

The plans are site-based rather than agent-based. Current pricing includes unlimited ticket parsing and lists business-email piping allowances of 10 addresses on Single Site, 50 on Agency, and 500 on the 50 Sites plan. All Pro plans include the commercial feature set, plugin updates for the license term, and priority support.

This pricing model can be attractive for a support team that would otherwise pay a SaaS help desk per agent. The trade-off is that WordPress hosting, backups, outgoing email, storage, maintenance, and any external AI API usage remain your responsibility.

## What to test before moving customer support into WordPress

### Agent permissions should match the support role

Before inviting the full team, test a real support-agent account and confirm it can work with tickets without receiving unrelated WordPress administration access. Permission design becomes more important when support data includes customer, commerce, membership, or license context.

- **Email round trip:**  create a ticket by email, reply as an agent, reply again as the customer, and test attachments and threading.
- **Agent permissions:**  confirm support staff can do their jobs without receiving unrelated WordPress administration access.
- **Portal privacy:**  use separate customer accounts and make sure one customer cannot access another customer’s tickets or attachments.
- **Automation:**  test routing rules, assignment, auto-close, tags, and notifications with realistic tickets before enabling them broadly.
- **Migration:**  import a representative sample first and verify customers, timestamps, conversation order, attachments, status, and ownership.
- **Backups and storage:**  include support data and protected attachments in the site’s disaster-recovery plan.
- **Performance:**  check the help desk with realistic ticket volume and background jobs, not only an empty test installation.

![Fluent Support agent permission settings](https://pluginsuggest.com/wp-content/uploads/2026/09/Fluent-Support-permission.webp)

## Who Fluent Support fits best

### Choose Fluent Support if

- You want ticket and customer-support data stored in your WordPress environment.
- You need several agents without paying a separate SaaS seat fee for each one.
- Your support team benefits from WordPress commerce, CRM, membership, LMS, or community context.
- You want the option to add email piping, workflows, advanced reports, AI, or Remote Portal as support operations mature.

### Keep it simpler or choose SaaS if

- One person can still handle support reliably from a normal inbox.
- You do not want WordPress hosting, backups, email delivery, and security to be part of help-desk operations.
- Your business needs a large omnichannel enterprise support ecosystem outside WordPress.
- Your team prefers a fully managed cloud help desk over owning the support infrastructure.

## PluginSuggest verdict

Fluent Support is most convincing for businesses that already treat WordPress as an operational platform rather than only a marketing website. The free version gives a team a real shared help desk with unlimited agents and tickets, while Pro adds the email, automation, reporting, AI, and deployment features that become useful as support volume grows.

I would shortlist it for product companies, agencies, stores, memberships, and course businesses that value owning support data and keeping customer context close to WordPress. I would choose a hosted help-desk service instead when outsourcing the infrastructure is more important than keeping the system self-hosted.

## Fluent Support FAQs

### Is Fluent Support free?

Yes. Fluent Support has a free WordPress.org version with the core ticket desk, customer portal, unlimited agents and tickets, customer management, and other day-to-day support features.

### How much does Fluent Support Pro cost?

As checked October 15, 2026, the current first-year promotion starts at $103 for one site, compared with the regular $129/year price. Five-site and 50-site plans are also available.

### Does Fluent Support charge per support agent?

No. Fluent Support uses site-based licensing and supports unlimited agents and tickets. Your own hosting and other operational services still have their normal costs.

### Can customers create and reply to tickets by email?

Yes. Fluent Support Pro includes business-email piping so incoming support emails can become ticket conversations. Version 2.4.5 improved automated-mail detection, loop prevention, bounce handling, and reply threading.

### Does Fluent Support have AI features?

Yes. Pro can use OpenAI, Google Gemini, or Anthropic Claude for response generation, ticket summaries, sentiment analysis, and AI Ticket Audit. You provide the AI provider API key and pay that provider’s usage costs separately.

### Is Fluent Support MCP available in the free version?

Yes. Fluent Support’s MCP connection is available in Free and Pro. It requires the free FluentHub plugin and uses WordPress permissions and Application Password authentication for compatible AI clients.

### Can I migrate from Zendesk, Freshdesk, or Help Scout?

Yes. Fluent Support includes migration tools for supported help desks including Zendesk, Freshdesk, and Help Scout. Test a small representative import before moving the full production history.

## Related PluginSuggest research

- Use case: [Build a Customer Support and Ticketing Website](https://pluginsuggest.com/use-cases/wordpress-customer-support-ticketing-website/)
