AWP Support Desk

By AWP Software

0+ active installationsVersion 1.0.1

Self-hosted support tickets for WordPress teams. Unlimited tickets, unlimited agents, your data on your own server.

Description

AWP Support Desk is a support ticket system built for companies that already run on WordPress: WooCommerce stores, membership sites, LMS platforms and corporate CMS installs.

The Free plugin is fully functional on its own. There are no ticket limits, no agent limits, no trial and no locked features.

Free features

  • Self-hosted architecture: tickets and messages live in your own database, not on a third-party service.
  • Customer portal as a shortcode ([awp_support_portal]) or a dynamic block: open tickets, review history and reply, and find tickets fast with the built-in filters (status, priority, category and reference/subject search), with a results summary and paginated links that keep the active filters.
  • The portal inherits the active block theme’s palette, fonts, button styles and corner radius, and its buttons, form fields and tables follow the theme with WCAG AA-checked colors and accessible fallbacks for classic themes. It stays centered on full-width templates and turns the ticket table into labelled cards on narrow screens.
  • Secure attachments: validate type and size, store files privately and download them with a per-file nonce.
  • Agent inbox with status, priority, category, assignee and search filters, plus a ticket detail screen with public replies, internal notes, status, priority, category and assignment controls.
  • Editable catalogues under Support Desk → Settings: add, rename, reorder and deactivate the statuses and priorities agents can pick, without breaking the tickets that already use them.
  • Ticket categories: group tickets by topic with a first-class taxonomy, show the category to the customer, filter the inbox and the portal by it, and set it from the ticket sidebar, the REST API or WP-CLI. A category in use cannot be deleted; deactivate it instead.
  • Canned replies: a staff library under Support Desk → Canned replies to save reusable reply templates and load them into the ticket reply composer — review and edit before sending, always; nothing is sent by loading a template.
  • Basic reports under Support Desk → Reports for managers and administrators: tickets created, open load, resolved tickets and the mean time to first response and to resolution, with 7, 30 and 90-day periods.
  • Email notifications: the notification mailbox receives new tickets and customer replies; customers receive agent replies and closure notices; assigned agents receive an assignment notice. Plain text, in the site language for staff and in the customer or assignee profile language for their mail, with links back to the portal or the ticket. Internal notes are never emailed.
  • Dedicated customer and agent roles with granular capabilities (awp_agent, awp_manager, awp_customer, awp_admin).
  • REST API awp/v1 for tickets, messages and attachments, using the same permissions as the screens: cookie plus X-WP-Nonce or WordPress application passwords, role-scoped lists, moderator-only internal notes and nonce-protected attachment downloads.
  • WP-CLI ticket commands for automation and migrations: wp awp ticket list, wp awp ticket create and wp awp ticket assign, with table, JSON, CSV, id and count output.
  • GDPR tools: the WordPress personal data exporter and eraser are integrated out of the box, a Data and privacy card in Settings erases the whole desk on request, and a suggested privacy policy text is published for Settings → Privacy (see Privacy below).
  • Built with the WordPress coding standards and released as GPL-2.0-or-later. The package carries no translation catalogues: English comes from the source strings and every other language is installed from translate.wordpress.org.
  • No account required and no telemetry. If you choose to share a reason when deactivating, one feedback email is sent (see Privacy below).

Pro add-on (separate plugin, sold outside WordPress.org)

  • Email piping (IMAP/POP3) and multiple mailboxes.
  • Workflows, SLA policies, teams and round-robin assignment.
  • WooCommerce/EDD context inside the ticket.
  • Advanced reports, CSAT, knowledge base and AI with your own API key.

The Pro add-on is a separate plugin. Nothing in this plugin is disabled, limited or time-locked waiting for a purchase.

Privacy

Email notifications only travel between your site and the addresses you configure in Settings and WordPress; no external service is involved.

There is no telemetry. The plugin sends no usage statistics, analytics, crash reports or site data anywhere, and it makes no external request while active: no remote scripts, fonts, images or APIs. There is no installation id, no licence check and no tracking option to switch on.

When you deactivate it from the Plugins screen, an optional screen asks why. If you pick a reason and choose Send feedback and deactivate, one email is sent through your site’s own mailer to the developer: the selected reason, plugin name and version, WordPress version, PHP version, site locale, whether the network is multisite, and a timestamp. The reason is a closed list (no free-text field), so no personal data is typed into the message. The payload contains no site URL, ticket content, user records or email addresses. If you choose Deactivate without sending feedback, nothing is emailed. Bulk and WP-CLI deactivations never email, and on multisite the optional screen only appears for single-site deactivations.

The recipient is fixed in the plugin code: it is not displayed on the screen, not stored as an option and not configurable, so it cannot be read or redirected from the site. Developers who must block outbound mail can disable the email with add_filter( 'awp/feedback/send_deactivation_notice', '__return_false' );.

Export and erasure (GDPR)

The plugin registers a personal data exporter and eraser with the WordPress privacy tools under the name AWP Support Desk. An export (Tools → Export Personal Data) includes the tickets opened with the requested email address, every message and attachment authored with that account, and the audit events linked to it, in paginated groups. An erasure request (Tools → Erase Personal Data) deletes those tickets (messages, meta, attachments and stored files included), deletes messages and uploads the account made on other people’s tickets, and anonymizes the audit trail by removing the user id and the IP address while keeping the event rows so ticket history stays complete.

What may legitimately remain after an erasure request: audit events without personal data (kept for security and abuse prevention), backups under the site’s own retention policy, and emails already delivered to a mailbox. Erasure is destructive and cannot be undone; the WordPress user account itself is not deleted.

Administrators can also wipe the whole desk from Support Desk → Settings → Data and privacy: the card lists what the site holds and deletes every ticket, reply, internal note, attachment file, audit event, canned reply and category, together with the desk configuration, after the word DELETE is typed by hand. Roles, capabilities and user accounts are kept and the desk stays active with an empty history. Deleting the plugin keeps the data by default; the same card holds the opt-in that also deletes the data when the plugin is uninstalled.

A suggested privacy policy text is published for Settings → Privacy → Privacy Policy Guide, so the site owner can copy an accurate description into their own policy. The full data map (tables, visibility, retention, export groups, erasure behaviour and its limits) lives in docs/PRIVACY.md.

Installation

  1. Upload the awp-support-desk folder to /wp-content/plugins/.
  2. Activate the plugin through the Plugins screen in WordPress.
  3. Open Support Desk in the admin menu to use the agent inbox.
  4. Create a page for customers and add the [awp_support_portal] shortcode or the AWP Support Portal block.

FAQ

Does it work without WooCommerce?

Yes. WooCommerce integration is optional and lives in the Pro add-on.

Where is the data stored?

Tickets and messages live in your own WordPress database. No ticket content is sent to AWP servers.

How do personal data export and erasure work?

The plugin plugs into the WordPress privacy tools: Tools → Export Personal Data and
Tools → Erase Personal Data. An export includes the tickets opened with the email address, the
messages and attachments authored with that account, and the audit events linked to it. An erasure
request deletes those tickets, messages and attachments (files included) and anonymizes the audit
trail without the user id or IP address. To wipe the whole desk instead, Support Desk → Settings →
Data and privacy
deletes all of its content and configuration after you type DELETE. See
docs/PRIVACY.md for the full list of what is kept and what is removed.

Is the Free plugin limited?

No. Tickets, agents and customers are unlimited. Features that require automation, external channels or business integrations are part of the separate Pro add-on.

Can I use the REST API?

Yes. The plugin exposes awp/v1 routes for tickets, messages and attachments under /wp-json/awp/v1/. Requests authenticate with the standard WordPress stack: a logged-in cookie plus the X-WP-Nonce header for same-origin clients, or application passwords for server-to-server integrations. Permissions match the screens, so customers only see their own tickets, internal notes are staff-only and attachments download through a nonce-protected URL. The full contract is in docs/REST-API.md in English and Spanish.

How do I protect attachments on nginx?

Attachments are stored in a private directory (wp-content/uploads/awp-support-desk-attachments/ by default, resolved with wp_upload_dir()) with an Apache .htaccess deny rule and an IIS web.config rule; both are rewritten whenever they are missing. Nginx ignores .htaccess, so on nginx add a deny block to your server config, or move the directory outside the web root:

location ^~ /wp-content/uploads/awp-support-desk-attachments/ { deny all; }

The storage directory can be relocated with the awp/attachment_storage_dir filter. Direct downloads always go through a nonce-protected endpoint and the files use unguessable random names, but the deny block restores the same guarantee Apache has.

What happens when I delete the plugin?

Deleting the plugin keeps tickets, settings and the AWP roles by default, so deleting it by accident does not destroy your support history. To remove everything on uninstall, set the awp_delete_data_on_uninstall option to true (or filter awp/uninstall/delete_data) before deleting the plugin. On multisite the cleanup runs for every site, and users who only had an AWP role are moved to the Subscriber role instead of being left without one.

Can I manage tickets from the command line?

Yes. Three WP-CLI commands cover the common operations:

wp awp ticket list --status=open --assignee=3 --format=json lists tickets with the same filters as the inbox.
wp awp ticket create --customer=12 --subject="…" --body="…" opens a ticket with the `cli` channel.
wp awp ticket assign 7 --agent=3 assigns a ticket; `--unassign` clears the assignee.

Every command enforces the same capability as its screen, so run them with --user=<admin> (or another user that holds the capability). Output supports table, JSON, CSV, ids and count.

Screenshots

Changelog

1.0.1

  • Review hardening: attachment files now live in a protected folder inside the WordPress uploads
    directory (uploads/awp-support-desk-attachments/, resolved with wp_upload_dir()), with the
    .htaccess and web.config deny rules rewritten whenever they are missing or stale, and a
    one-time migration for files stored by 1.0.0 under wp-content/.
  • The REST ticket list additionally requires the awp_view_tickets grant, so a role whose view
    capability was revoked can no longer receive ticket subjects and metadata.
  • Multisite: the network Deactivate action restores the standard WordPress flow; the optional
    feedback screen now appears only for single-site (and per-site) deactivations.
  • Translation catalogues no longer ship in the package; translations are served from
    translate.wordpress.org.
  • The bundled autoloader is resolved only relative to the plugin directory.
  • Plugin and Author URIs corrected to awp-software.com.

1.0.0

  • First stable release. The plugin is feature-complete for the Free plan: no ticket limits, no agent
    limits, no trial and no locked features.
  • Customer portal (shortcode and block): open tickets, list history and reply, with status, priority,
    category and search filters.
  • Agent inbox and ticket detail: filters, replies, internal notes, status, priority, category and
    assignment, with the notification email for new tickets, replies, closures and assignments.
  • Editable status and priority catalogues, ticket categories and canned replies.
  • Basic reports: ticket volume, open load, resolved tickets and response/resolution averages.
  • REST API awp/v1, WP-CLI ticket commands and WordPress privacy export/erase tools.
  • Secure attachments stored outside the media library, nonce-protected downloads and the opt-in
    uninstall that keeps data by default.
  • Accessibility pass to WCAG 2.2 AA with automated contrast, markup and browser (axe-core) checks.
  • English and Spanish catalogues with a CI gate for domains, literals, completeness, POT freshness
    and compiled-catalogue parity.
  • Data and privacy card under Settings: content inventory, the uninstall deletion opt-in and a
    whole-desk erasure that needs the word DELETE typed by hand. The plugin ships no telemetry.

0.1.0

  • Initial public development release: plugin foundation, roles and capabilities, status screen.
  • Customer portal (shortcode and block): open tickets, list history and reply.
  • Agent inbox and ticket detail: filters, replies, internal notes, status, priority, category and assignment.
  • Editable status and priority catalogues: add, rename, reorder and deactivate without breaking existing tickets.
  • Ticket categories: first-class taxonomy with inbox and portal filters, ticket assignment, REST and WP-CLI support.
  • Canned replies: staff library with load-into-reply templates for agents.
  • Basic reports: ticket volume, open load, resolved tickets and response/resolution averages.
  • REST API awp/v1 for tickets, messages and attachments.
  • WP-CLI ticket commands: wp awp ticket list, create and assign.
  • Accessibility pass to WCAG 2.2 AA with automated contrast, markup and browser (axe-core) checks.
  • Inbox tuned for 10k tickets: site-scoped indexes (schema revisions 0002 and 0003), one user-cache
    prime per page instead of a lookup per row, and documented pagination and search limits.
  • English and Spanish catalogues (384 strings) with a CI gate for domains, literals, completeness, POT freshness and compiled-catalogue parity.