Awesome Support plugin review and common issues

Ticket visibility in Awesome Support is controlled by permissions and department assignment. Check: (1) in Awesome Support → Settings → Agents, verify the user has been assigned the “agent” role — WordPress users are not automatically support agents; (2) agents can be assigned to specific departments — a ticket in Department A is not visible to agents assigned only to Department B; (3) verify “All Tickets” vs “My Tickets” view is configured — agents may be viewing a filtered view; (4) in Awesome Support → Permissions, check which ticket viewing permissions are enabled for the agent role.

In Awesome Support → Settings → Emails, verify: (1) “New Ticket” agent notification is enabled; (2) the agent notification email address is configured (agent’s profile email); (3) WordPress email is functional — use WP Mail SMTP test email; (4) notifications may be configured to go to the department email rather than individual agents — verify which notification target is configured; (5) for Awesome Support’s email system to work correctly, WP Mail SMTP should be configured with a proper SMTP provider.

In Awesome Support → Settings → Emails → Customer Notifications, verify the “New Ticket (Customer)” notification is enabled. This sends a confirmation to the email address the customer used when submitting. Common issues: (1) the customer email notification is disabled; (2) WordPress email delivery fails — configure WP Mail SMTP; (3) the customer’s email address was mistyped in submission; (4) the confirmation email is going to spam.

In Awesome Support → Custom Fields → Add New, create custom fields for your ticket form: text fields, select dropdowns, checkboxes, etc. Configure each field: label, type, whether it’s required, and whether it appears on the submission form, agent view, or both. Common custom fields: Order Number (for e-commerce support), Browser/Device (for technical support), Urgency Level, Preferred Contact Time. Save and test with a new ticket submission to verify the fields appear and data is captured.

In Awesome Support → Departments, create departments matching your support structure: Sales, Technical Support, Billing, Shipping. In the ticket submission form settings, add the Department selector field — customers choose their department when submitting. Assign agents to departments in the agent profile settings. When a customer submits a ticket to a department, only agents assigned to that department receive notification and see the ticket in their queue. Configure department-specific email addresses for routing confirmation emails from the correct department.

Fluent Support is generally the better choice for WooCommerce stores in 2025 due to its more active development, native WooCommerce order context in the free-to-Pro tier, and the WPManageNinja ecosystem integration. Awesome Support’s WooCommerce integration requires a premium add-on that increases cost. For price-sensitive setups already using Fluent Support’s free version (2 agents), the upgrade to Fluent Support Pro for unlimited agents + WooCommerce provides better overall value than Awesome Support’s add-on system.

Fluent Support includes a migration tool specifically for Awesome Support — it reads ticket and customer data from Awesome Support’s database tables and imports them into Fluent Support. This makes migration straightforward for organizations ready to switch. SupportCandy also supports migration from Awesome Support. When migrating, verify ticket history, custom fields, and attachments are preserved — test the migration on a staging environment before switching in production.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.