Get the plugin
WP MCP/Integrations/Support

Support integration

Awesome Support MCP

Awesome Support keeps a ticket as its own ticket post, the customer its author, its state the post status and _wpas_status meta, its agents in assignee meta, and its thread as reply child posts. WP MCP Pro reads what Awesome Support lets the current agent see (every ticket when it lets them see all, otherwise the tickets they are assigned to), and writes through its own functions as the current user: a reply through wpas_add_reply() (whose hook emails the customer), open and closed through wpas_close_ticket() and wpas_reopen_ticket(), and the ticket state through wpas_update_ticket_status(). A close runs without its own close notification, so it stays undoable. The free plugin has no internal notes, so WP MCP does not pretend to add them. Capabilities are Awesome Support's own: an agent's edit_ticket for every op, reply_ticket for a reply and close_ticket for a close.

plugin-data-readplugin-data-write

In practice

How Awesome Support work goes with an agent.

Awesome Support treats a ticket as a post. The customer is the post author, the ticket state is the post status (queued, processing or hold, plus anything the site adds), whether it is open or closed lives in a separate status meta key, and agents are named in assignee meta. Replies are child posts. WP MCP Pro reads what the plugin lets the current agent see, which is every ticket or only assigned ones depending on its setting, and writes through the plugin's own functions. A close is made without the close notification, which keeps it undoable.

Which tickets assigned to me are in the hold state?

Runs awesome-support-list-tickets with status hold. The result follows Awesome Support's own visibility, so an agent limited to assigned tickets sees only theirs, with customer emails masked.

Read ticket 611 and tell me what the customer has already tried.

Runs awesome-support-get-ticket, which returns the customer and the reply thread oldest first. History and log child posts are the plugin's activity lines and are not returned.

Move ticket 611 to processing.

Runs awesome-support-set-ticket-status through wpas_update_ticket_status. The ticket is snapshotted first and rollback-operation restores the old state. Needs the helpdesk write opt-in.

Reply to ticket 611 that the fix is deployed, then close it.

Runs awesome-support-reply-to-ticket, which previews the masked recipient and sends only on confirm true, then awesome-support-set-ticket-status closed, with no close email. A reply cannot be unsent; undo removes it from the thread.

What your AI can do

Real Awesome Support operations, every write reversible.

  • List and read tickets within the agent's own visibility
  • Reply to a customer through Awesome Support's own reply function
  • Change a ticket's state through its own status function
  • Open or close a ticket, closing without the close email
  • Keep a close undoable

Example prompts

Example Awesome Support prompts.

List the tickets assigned to me that are still processing.

Reply to ticket 611 that the fix is deployed, and close it.

Reopen ticket 611; the customer says it is still happening.

Under the hood

The Awesome Support calls, under the hood.

wpmcp, awesome-support

plugin-data-read({ integration: "awesome-support", operation: "awesome-support-get-ticket", args: { ticket_id: 611 } }), within the agent's visibility

plugin-data-write({ integration: "awesome-support", operation: "awesome-support-set-ticket-status", args: { ticket_id: 611, status: "closed" } }), no close email, undoable

Safety and access

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

Recoverable on Awesome Support

  • Status changes, including closing and reopening, are snapshotted and undone with rollback-operation.
  • A close runs without Awesome Support's close notification, so no email is sent and the close stays undoable.
  • Undoing a reply removes it from the thread and restores the ticket, but the customer email stays sent.

Awesome Support limits and opt-ins

  • Replies and status changes are off until a site enables them with the wpmcp_enable_helpdesk_write filter.
  • There is no internal note. The free Awesome Support has none, so the op is not offered for it.
  • A reply needs confirm true and emails the customer. Status values are the plugin's own states plus closed.
  • Capabilities are Awesome Support's: edit_ticket for every op, reply_ticket for a reply and close_ticket for a close.

Free or Pro: Awesome Support is a Pro integration, added in 0.9.0, with no equivalent in the free plugin. Once Pro and Awesome Support are active, ticket lists and reads work immediately. Replies and status changes are off until the site enables the wpmcp_enable_helpdesk_write filter, shared with Fluent Support. Every call also needs the signed in user to hold Awesome Support's own agent capabilities, not just a WordPress role.

Part of WP MCP Pro

The Awesome Support integration is part of WP MCP Pro.

One Pro licence unlocks the Awesome 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

Awesome Support MCP: questions, answered.

Can the Awesome Support integration add an internal note?

No. The free Awesome Support has no internal notes, so WP MCP does not pretend to add them. It replies to the customer and changes state through the plugin's own functions.

Does closing a ticket email the customer?

A close runs without Awesome Support's own close notification, so no email goes out and the close stays undoable. A reply, by contrast, emails the customer the way the ticket screen does.

What states can a ticket have?

Awesome Support's own: queued, processing and hold by default, plus any state a site registers, and closed. WP MCP reads the list from the plugin, so a custom state appears automatically. The list filter also accepts open, closed and all.

Why is opening and closing separate from state?

Awesome Support tracks open or closed in its own status meta, apart from the post status that holds the state. WP MCP closes through wpas_close_ticket and reopens through wpas_reopen_ticket, so both stay in step. Choosing closed or an open state does the right call.

Who can see which tickets?

The plugin decides. If Awesome Support lets that agent see all tickets, so does WP MCP. Otherwise only tickets where the agent is the primary, secondary or tertiary assignee appear. A ticket outside that scope is refused, not hidden silently.

Is the customer email shown to the model?

Masked in ticket lists, for example j***@example.com. A single ticket read returns the address in full, since the agent could open it anyway. These tools return personal data, so connect them only to a client and model you trust with customer information.

Point your AI at Awesome Support.