Get the plugin
WP MCP/Integrations/Support

Support integration

Fluent Support MCP

Fluent Support keeps a ticket as a row of its own tickets table with its thread in a conversations table, customers and agents both in a persons table. WP MCP Pro reads straight from those tables, kept to the tickets the plugin lets the current user see (everything for an administrator, otherwise the plugin's own agent visibility and mailbox restrictions), and never returns the ticket's hash or secret content. Writes go through the plugin's own services as the current user's agent record, the way its ticket screen does: a reply through its response service (which emails the customer), an internal note the same way, and a status change through its ticket service. A close runs silently, so neither the closing email nor the attachment purge on close runs and the close stays undoable, and a reopen sends no mail anyway. Writes need the plugin's ticket management permission and access to that ticket.

plugin-data-readplugin-data-write

In practice

How Fluent Support work goes with an agent.

Fluent Support keeps tickets in its own tables rather than as posts: a ticket row with a status of new, active or closed, a conversations table for the thread, and one persons table that holds both customers and agents. Customer data is the sensitive part. WP MCP Pro reads those tables through the plugin's own visibility rules, so an agent sees what that agent user could see on the ticket screen, with list emails masked and the ticket hash never returned. Writes are off until a site enables them, and a reply emails a real customer.

List my open tickets and tell me which have waited longest.

Runs fluent-support-list-tickets with status open, which covers new and active, limited to tickets the current agent may see. Customer emails come back masked, and dates show who replied last.

Read ticket 4821 and summarise the thread for a handover.

Runs fluent-support-get-ticket, which returns the customer and the thread oldest first, paged up to 100. This is personal data, shown in full for a ticket the caller may open.

Add an internal note to ticket 4821 saying billing needs to confirm the refund.

Runs fluent-support-add-ticket-note through the plugin's response service. Only agents see the note, nothing is mailed, and the op is snapshotted so rollback-operation removes it. Needs the write opt-in.

Reply to ticket 4821 with the refund steps.

Runs fluent-support-reply-to-ticket. It first answers with a preview naming the masked recipient, and only sends on confirm true. Undo removes the reply from the thread, but the email stays sent.

What your AI can do

Real Fluent Support operations, every write reversible.

  • List and read tickets within the plugin's own agent visibility
  • Reply to a customer through the plugin's own response service
  • Add an internal note to a ticket
  • Change a ticket's status, and close or reopen it
  • Close silently so the close stays undoable

Example prompts

Example Fluent Support prompts.

Show me the open tickets assigned to me.

Reply to ticket 4821 with the refund steps and close it.

Add an internal note to ticket 4821 flagging it for the billing team.

Under the hood

The Fluent Support calls, under the hood.

wpmcp, fluent-support

plugin-data-read({ integration: "fluent-support", operation: "fluent-support-get-ticket", args: { ticket_id: 4821 } }), no hash or secret content

plugin-data-write({ integration: "fluent-support", operation: "fluent-support-set-ticket-status", args: { ticket_id: 4821, status: "closed" } }), closes silently, undoable

Safety and access

What can be undone on Fluent Support, and what costs what.

Recoverable on Fluent Support

  • Notes and status changes are snapshotted and undone with rollback-operation.
  • Closing is done silently, with no closing email and no attachment purge on close, so a close stays fully undoable.
  • Undoing a reply removes it from the thread and puts the ticket state back, but cannot unsend the email.

Fluent Support limits and opt-ins

  • All three writes are off until a site enables them with the wpmcp_enable_helpdesk_write filter. Reads work without it.
  • A reply is a destructive operation: it needs confirm true, and the customer is emailed the way the ticket screen would.
  • Statuses are the plugin's own: new, active and closed. There is no solved status to set.
  • Writes need Fluent Support's permission to manage tickets and access to that ticket.

Free or Pro: Fluent Support is a Pro integration, added in 0.9.0, and the free plugin has no ticket operations for it. With Pro active, the reads work straight away. The three writes (reply, internal note and status change) stay off until the site turns on the wpmcp_enable_helpdesk_write filter, which also governs Awesome Support. Reading and writing are limited to what the signed in agent can do in Fluent Support itself.

Part of WP MCP Pro

The Fluent Support integration is part of WP MCP Pro.

One Pro licence unlocks the Fluent Support tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.

Frequently asked

Fluent Support MCP: questions, answered.

Does replying email the customer?

Yes. A reply goes through the plugin's own response service, which emails the customer the way the ticket screen does. A close, by contrast, runs silently so no closing email goes out and the close stays undoable.

Which tickets can an agent see?

Only what Fluent Support itself lets the current user see: everything for an administrator, otherwise the plugin's own agent visibility and mailbox restrictions. The ticket hash and secret content are never returned.

Are customer emails visible to the agent?

In lists they are masked, for example j***@example.com. Opening one ticket with fluent-support-get-ticket returns the address in full, because the caller must already be allowed to open that ticket. The ticket hash and secret content are never returned in either call.

Which statuses can a ticket be set to?

new, active and closed, which are Fluent Support's own. A list filter also accepts open (new plus active) and all. Setting a ticket to the status it already has is refused with already_done rather than recorded as a change.

Does the reply come from me or from a bot?

From the signed in WordPress user, as that user's Fluent Support agent record, the same way the ticket screen posts it. The user must be an agent with permission to manage tickets. There is no separate bot identity or hidden author.

Can the Fluent Support integration read draft responses or scheduled replies?

No. Fluent Support stores draft_response and schedule rows in the conversations table, and those are left out of the thread. The thread contains responses and notes only, so unsent agent drafts are not exposed to the model.

Point your AI at Fluent Support.