Skip to content
Integration

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.
Add Internal NoteAdd an internal note to a ticket, visible only to agents, not the customer.
Add or Remove Ticket TagsAdd or remove tags on a ticket, optionally creating new tags by name in the same call.
Assign Ticket to AgentAssign a single ticket to a specific agent.
Bulk Ticket ActionClose, assign, or tag up to 50 tickets at once, more efficiently than looping individual calls.
Close TicketClose a ticket, optionally sending a final reply and/or an internal note first, or closing silently.
Create Saved ReplyCreate a new saved/canned reply for reuse across tickets.
Create Support TicketCreate a new support ticket on behalf of a customer, auto-creating the customer if needed.
Create Ticket TagCreate a new ticket tag for categorization and reporting, without attaching it to a ticket.
Delete Saved ReplyPermanently delete a saved reply.
Delete TicketPermanently delete a support ticket and all its responses, attachments, and metadata.
Get Agent MentionsGet tickets where you've been @mentioned in internal notes or replies.
Get Customer TicketsGet a customer's tickets by email, name, or ID, the go-to for "show me tickets from [customer]".
Get Support ContextOne-call session starter: your identity, queue, tickets needing attention, and reference data.
Get Support InsightsGet performance analytics: response/resolution times, waiting durations, and per-agent stats.
Get Ticket Activity LogGet the activity timeline for a ticket, creation, responses, status changes, and assignments.
Get Ticket DetailsGet full ticket details with the conversation thread, customer history, and integration/CRM data.
List Saved RepliesList your saved/canned replies, optionally filtered by search text or product.
List Support TicketsList and filter support tickets with triage signals like who spoke last and reply counts.
List WorkflowsList automation workflows to see what automatic actions are already configured.
Merge TicketsMerge duplicate tickets into one target ticket; the merged tickets are deleted.
Reopen TicketReopen a closed ticket, setting its status back to active and clearing its resolved date.
Reply to TicketSend a customer-visible reply on a ticket, optionally assigning and/or closing it in the same call.
Search CustomersSearch for customers by name or email, returning profiles with location and ticket counts.
Update Saved ReplyUpdate an existing saved reply's title, content, or product scope.
Update Ticket PropertiesUpdate a ticket's title, priority, status, product, mailbox, or assigned agent.

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

Connect your AI to ask anything…

No AI subscription? Uncanny Agent is built in.

Recipes

Fluent Support recipes to start from

Ideas for what you can build with Fluent Support.

Sample recipe

When a Fluent Support agent responds to a ticket, use AI to generate a Heroic Knowledge Base article draft from the response

RequiresFluent SupportOpenAIHeroic Knowledge Base
Sample recipe

When a Fluent Support ticket is closed, send a satisfaction survey email and log the resolution to Google Sheets

RequiresFluent SupportEmailsGoogle Sheets

See all Fluent Support recipes

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.

This page may contain affiliate links. Once in a while, we may earn a commission from those links. But with or without commissions, we only recommend products we like.
Back To Top