Overview #

Fluent Support is a WordPress help desk with customer portals, business inboxes, agents, tickets, notifications, and integrations. The Pro add-on extends automation, email piping, reporting, and other support operations according to the active edition.

When to use it. Use it when a team wants ticket management inside WordPress and can define agent roles, inbox ownership, service expectations, email routing, and data retention.

Before You Begin #

Platform compatibility. Use a WordPress and PHP combination supported by the current developer release. Minimum versions can change; verify the current official product page or plugin/theme metadata before production deployment. Do not bypass an activation or compatibility warning without identifying its cause.

Requirements and dependencies #

• – The free Fluent Support plugin must remain installed and active.
• – A public or protected portal page for customers.
• – Reliable email delivery and, if used, verified email-piping configuration.
• – Named agents with appropriate WordPress permissions.

Pre-installation checks #

• – Back up the Database and map support addresses, current tickets, agents, inboxes, SLAs, and integrations.
• – Decide whether the portal, email piping, or both will create tickets.
• – Prepare a test customer address outside the site’s Domain.

Installation #

1. 1. Install and activate Fluent Support Free from Plugins > Add New Plugin.
2. 2. Go to Plugins > Add New Plugin > Upload Plugin, upload the Fluent Support Pro ZIP, install, and activate it.
3. 3. Open Fluent Support and complete the portal/business setup.
4. 4. Confirm the free core remains active.
5. 5. Create a test business inbox and agent.

License Activation #

1. 1. Open Fluent Support Dashboard > Global Settings > License Management.
2. 2. Enter a valid Fluent Support Pro key, select Verify License, and confirm the active status.
3. 3. The archive alone does not grant a WPManageNinja account, updates, or support.

Important. A premium download does not automatically establish ownership of the original developer’s account, license key, automatic-update service, cloud features, or direct support. Use only Credentials that are valid for this site and were supplied through an authorized account or an explicit Nippy Launch entitlement.

Initial Setup #

1. 1. Create or assign the customer portal page and verify its access behavior.
2. 2. Configure business inbox name, support email, agents, and notifications.
3. 3. Set business hours, priorities, statuses, saved replies, and automation only as needed.
4. 4. Configure email piping through the current official method if required.
5. 5. Submit, reply to, close, and reopen a complete test ticket.

Recommended Configuration #

• – Give agents only the permissions they need.
• – Use one authoritative intake route per mailbox to avoid duplicate tickets.
• – Define response ownership and escalation before automating assignments.
• – Keep sensitive data out of ticket subjects and public portal URLs.
• – Test customer and agent notifications separately and monitor piping failures.

Main Features #

The installed edition can provide the following primary capabilities. Availability may depend on the active plan, add-ons, and current release.

• – Customer support portal
• – Business inboxes and ticket lifecycle
• – Agents, notes, replies, and saved responses
• – Email notifications and optional piping
• – Automation, reporting, and integrations in Pro

How to Use It #

Practical starting workflow. Create a test customer, submit a portal ticket, reply as an agent, add an internal note, change priority, reply by email if piping is enabled, close and reopen the ticket, and verify every notification and permission boundary.

Integrations #

• – FluentCRM and Fluent Forms
• – WooCommerce, membership, and LMS context where supported
• – Email piping/provider
• – Slack/webhook or other documented automation integrations

Enable an integration only after its account ownership, permissions, data flow, and failure behavior have been tested. Keep secret Credentials out of page content and screenshots.

Common Issues & Troubleshooting #

• – Portal page is blank. Check the assigned page/shortcode, login requirements, theme conflict, cache exclusion, and plugin activation.
• – Email reply does not enter the ticket. Verify piping route, mailbox/provider rules, token/secret, sender matching, and delivery logs.
• – Duplicate tickets are created. Remove duplicate forwarding/piping routes and confirm message IDs are preserved.
• – Agent cannot see an inbox. Review agent assignment, role permissions, inbox access, and status filters.
• – License verification fails. Confirm key, Domain allocation, and outbound HTTPS.

If the problem persists, reproduce it on staging, capture the exact error and relevant logs, and compare the behavior with nonessential plugins temporarily disabled. Restore the production site rather than troubleshooting destructively in place.

Updating the Plugin or Resource #

1. 1. Back up tickets and pause high-volume changes when appropriate.
2. 2. Update core and Pro together on staging.
3. 3. Retest portal submission, agent replies, email piping, notifications, automations, and permissions.

• – Confirm that the backup completed and can be accessed independently of WordPress.
• – Review the official changelog and compatibility notes.
• – Update during a low-risk window and keep a tested rollback path.
• – Clear relevant caches and perform the product-specific functional tests listed above.

Uninstallation #

1. 1. Export or retain required ticket records, attachments, customer data, inboxes, and agent assignments.
2. 2. Disable mail forwarding/piping before deleting the plugin.
3. 3. Replace public support links and communicate the new support channel.

Deactivation and deletion are not the same as data removal. Confirm the product’s current cleanup options, Database tables, uploaded files, remote data, connected accounts, and continuing external billing or scheduled actions before removal.

Security & Best Practices #

• – Use least privilege, HTTPS, and strong agent authentication.
• – Protect attachments and ticket exports.
• – Do not collect payment Credentials or unnecessary sensitive data in tickets.
• – Define retention and deletion for support records.
• – Use unique administrator accounts, least-privilege roles, HTTPS, and multi-factor authentication where supported.
• – Keep the resource, WordPress, PHP, theme, and dependencies on supported versions.
• – Store backups and recovery instructions outside the WordPress site.

Final Checklist #

• ✅A restorable backup was created before installation or major configuration.
• ✅All required core plugins, themes, services, and accounts are active.
• ✅The resource is installed and activated without WordPress or PHP errors.
• ✅The product-specific initial and recommended settings are complete.
• ✅The practical workflow was tested as an administrator and as the intended visitor/customer/member.
• ✅Email, payments, webhooks, cron, cache, and integrations were tested where applicable.
• ✅Security, privacy, consent, data retention, and access rules were reviewed.