Use [dctc_support_user_tickets] to place the customer ticket list on its own WordPress page. The list can be separate from the ticket creation form and includes configurable search, filters, pagination size, headings, and an optional create-ticket button.
1. Add the customer ticket list
- Edit the WordPress page where customers should track their support requests.
- Add a Shortcode block and enter
[dctc_support_user_tickets]. - Save the page and test it with a customer account that has sample tickets.
- Confirm the list shows only the tickets the current user is permitted to access.
2. Configure the list
The shortcode supports these attributes in the current plugin source:
| Attribute | Purpose | Example |
|---|---|---|
status | Set the initial status filter: all, open, pending, resolved, or closed. | status="open" |
category | Set the initial category filter by category ID or slug; defaults to all. | category="billing" |
category_id | Provide a category ID for the initial category filter. | category_id="3" |
per_page | Set the number of tickets to load per page; defaults to 10. | per_page="20" |
limit | Alternate limit for the number of tickets to load; when set, it takes precedence over per_page. | limit="15" |
show_search | Show or hide the search control. | show_search="false" |
show_filters | Show or hide the filter controls. | show_filters="false" |
show_create_button | Show or hide the create-ticket button. | show_create_button="false" |
show_header | Show or hide the list heading and supporting text. | show_header="false" |
title | Override the list title. | title="My Support Requests" |
subtitle | Override the description below the title. | subtitle="Track your requests here." |
For example, show open tickets with search but without the filter controls or create button:
[dctc_support_user_tickets status="open" show_search="true" show_filters="false" show_create_button="false"]The implementation also accepts show_filter as an alias for show_filters. If both are supplied, the singular show_filter value takes precedence.
3. Understand customer access
The shortcode renders the ticket-list interface, but the available records are determined by the support portal’s access logic and the current visitor’s session. Test with a customer account that has tickets, another account that does not own those tickets, and a logged-out visitor. Do not rely on a page being publicly accessible as evidence that ticket records are public.
When a logged-in user visits the list, the plugin attempts to associate guest tickets with that account using the current user’s email. Review the guest access and email-confirmation flow before using the list as a public-facing support portal.
4. Troubleshoot an empty or incomplete list
- Confirm the shortcode is entered exactly as
[dctc_support_user_tickets]. - Check the initial
statusand category attributes; a filter may exclude the tickets you expect. - Verify the test customer is signed in with the account associated with the ticket.
- Check whether guest-ticket access or account-linking steps are required for the ticket being tested.
- Temporarily test without page caching or script optimization on staging if the list does not load or its filters do not respond.