The customer portal is the front-end workspace where your customers open tickets, follow the conversation and download attachments. It lives on a normal WordPress page that contains the Log in to open a support ticket and review your conversation history. shortcode or the AWP Support Portal block, and customers sign in with the WordPress account your site already gave them. This guide shows how to publish it, how customers use it and where its limits are.
What you need #
- AWP Support Desk installed and activated (see the installation guide).
- A page where the portal will live.
- A WordPress account for each customer, created as usual under Users → Add New or through your site’s own registration flow.
Add the portal to a page #
- Create a page, for example Support.
- In the content, insert the AWP Support Portal block, or add the
shortcode.Log in to open a support ticket and review your conversation history.
- Publish the page.
- Go to Support Desk → Settings, select the page under Customer portal page and save. Notification emails link back to this page.
The wizard in Support Desk → Setup can also do this for you: it publishes a new page with the portal shortcode and points the settings at it.
Shortcode or block #
Both options render the same portal, so choose by habit:
Shortcode |
AWP Support Portal block | |
|---|---|---|
| Add it from | Any content area that accepts shortcodes | The block editor inserter |
| Renders | The full portal | The full portal |
What customers can do #
- Open the portal page. If they are not logged in, they see a login prompt that leads to the WordPress login screen and returns to the portal afterwards.
- Once logged in, they see only their own tickets — no one else’s.
- The ticket list offers filters for status, priority and category, plus a search by reference or subject, with a results summary and pagination that keeps the active filters.
- The list includes past tickets, so customers can review their history instead of opening duplicates.
- They open a ticket to read the full conversation thread with your agents.
- They reply from the thread and can attach files to their messages.
- The New ticket form opens a fresh conversation with a subject, a body and optional attachments. Ticket creation is rate limited to protect the site.
Theming #
On a block theme, the portal inherits the theme’s palette, fonts, button styles and corner radius, with WCAG AA-checked colors. On a classic theme it falls back to an accessible appearance. The portal stays centered on full-width templates, and the ticket table turns into labelled cards on narrow screens, so it works on phones without extra work. No theme edits are needed on either path.
Attachments and security #
Attachments are validated by type and size, stored in a private directory under wp-content (wp-content/awp-support-attachments/ by default) with unguessable random file names, and downloaded through nonce-protected URLs. Apache sites get a .htaccess deny rule automatically. On nginx, add this deny block to your server configuration, because nginx ignores .htaccess files:
location ^~ /wp-content/awp-support-attachments/ { deny all; }
If your setup needs a different location, the storage directory can be moved with the awp/attachment_storage_dir filter.
What the portal does not include #
The Free portal is deliberately focused. It has no knowledge base and no satisfaction surveys, and it does not convert inbound email into tickets — those are part of the paid Pro add-on. Customers also interact only through the portal: they never see wp-admin. Automation beyond WP-CLI and the REST API is up to the site, whether that is scheduled tasks, custom code or an external tool.
Next steps #
Hand the page to your customers and watch the tickets arrive in the agent inbox. If you need to define who can see what, the roles and capabilities guide explains each role. The product page lists what the Pro add-on adds on top of the portal.