Fluent Support
Fluent Support is a Help Desk and customer support desk plugin for WordPress that allows easy management of support tickets and inquiries right from inside WordPress. It offers a WP alternative to platforms like Help Scout, Zendesk and FreshDesk.
Recipe items
What you can automate with Fluent Support
Every recipe has two parts: a trigger that starts it and the actions it runs. Use these with any other plugin or app.
Triggers
A trigger starts a recipe. When it happens on your site, the recipe runs.For logged-in users Behaviors that can be tracked for logged-in users.
LiteA ticket is closed by a customer
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket assignee username
- Ticket assignee email
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
LiteA ticket is opened by a customer
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
LiteA ticket receives a reply from a customer
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket response
- Ticket assignee username
- Ticket assignee email
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
LiteA user's ticket receives a reply from an agent
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket response
- Ticket assignee username
- Ticket assignee email
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
ProA ticket for a product is closed by a customer or an agent
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket assignee username
- Ticket assignee email
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
ProA ticket for a product is opened by a customer or an agent
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
ProA ticket for a product is replied to by a customer
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket response
- Ticket assignee username
- Ticket assignee email
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
ProA ticket for a product is replied to by an agent
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket response
- Ticket assignee username
- Ticket assignee email
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
ProA ticket with a priority is closed by a customer or an agent
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket assignee username
- Ticket assignee email
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
ProA ticket with a priority is opened by a customer or an agent
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
ProA ticket with a priority is replied to by a customer
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket response
- Ticket assignee username
- Ticket assignee email
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
ProA ticket with a priority is replied to by an agent
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket response
- Ticket assignee username
- Ticket assignee email
- Ticket admin URL
- Customer email
- Customer first name
- Customer last name
- Customer job title
- Customer note
- Customer status
- Customer address line 1
- Customer city
- Customer state
- Customer zip code
- Customer country
For everyone Behaviors that can be tracked for both logged-in users and guests.
LiteA ticket is opened
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket admin URL
- Customer email
ProA ticket is closed
Tokens you can use in the next steps Data from triggers that can be used in a recipe's actions, making them much more powerful and customizable.
- Ticket ID
- Ticket subject
- Ticket details
- Ticket priority
- Ticket product
- Ticket admin URL
- Customer email
- Customer ID
Actions
An action is what the recipe does once it starts, like sending an email or adding a tag.ProCreate a ticket
Tokens you can use in the next steps Data from actions that can be used in other actions, making automations much more powerful and customizable.
- Action fields
- Ticket URL
- Ticket ID
AI abilities
What your AI app (ChatGPT, Claude and others) can do in this plugin once it is connected to Uncanny Automator.Connect your AI
Ask your AI to set up Fluent Support for you
ChatGPT, Claude, Gemini, Copilot, Perplexity or any AI app that supports remote MCP servers. Ask in plain English and it gets done.
When a Fluent Support agent responds to a ticket, use AI to generate a Heroic Knowledge Base article draft from the response
When a Fluent Support ticket is closed, send a satisfaction survey email and log the resolution to Google Sheets
When a support ticket is created, draft an AI-powered response for agents and send it on Slack
No AI subscription? Uncanny Agent is built in.
Recipes
Fluent Support recipes to start from
Ideas for what you can build with Fluent Support.
When a Fluent Support agent responds to a ticket, use AI to generate a Heroic Knowledge Base article draft from the response
RequiresWhen a Fluent Support ticket is closed, send a satisfaction survey email and log the resolution to Google Sheets
RequiresConnections
See how they work together
Pick one to see what Fluent Support and that plugin or app can do together, with recipes for the pair.
Get started
Install free. Connect your AI.
Install the free plugin, connect your AI, and ask for the first thing on your list.
Every recipe you build keeps running without the chat.