Lucrativeit Support Ticket Plus – Help Desk & Customer Support with AI replies

Installazione

Requirements

• WordPress 6.2+
• PHP 8.2+

Step-by-step install

1. Upload the plugin folder to wp-content/plugins/lucrativeit-support-ticket-plus/, or install the ZIP from Plugins → Add New → Upload Plugin.
2. Go to Plugins in WordPress admin and click Activate on LucrativeIt Support Ticket Plus.
3. On activation, the plugin creates a Support Portal page with the shortcode [lucrativeit_support_portal].
4. Open Pages → All Pages, find Support Portal, and click View. Add that page to your menu under Appearance → Menus so customers can find it.
5. Configure the basics under Support Ticket Plus → Settings (App Name, Ticket Prefix, Admin Notification Email, Max Attachment Size, Admin Ticket Options).
6. Create departments under Support Ticket Plus → Departments so tickets can be routed correctly. Enable Auto-assign for round-robin distribution among agents in that department.
7. Create projects under Support Ticket Plus → Projects (title only). Customers select a project when creating a ticket; admins can filter the ticket list by project.
8. (Optional) Configure Support Hours under Support Ticket Plus → Settings → General → Support Hours: enable the login-screen status widget, set timezone, working days, start/end times, and optional online/offline override.
9. (Optional) Grant staff permissions under Support Ticket Plus → Roles. Every logged-in user is a customer by default. Grant the Tickets permission to a WordPress role (for example Editor) to make those users support agents. Grant the Projects permission to roles that should manage project titles.

Manual portal page (if needed)

If the Support Portal page was deleted:

1. Pages → Add New
2. Add the shortcode [lucrativeit_support_portal]
3. Publish and link it from your menu

Knowledge base only (optional): [lucrativeit_knowledge_base]

Enable registration

Customers can register for an account, or submit tickets as a guest when Allow Guest Tickets is enabled (Settings → General → Portal Access). Registration is controlled in two places — both must allow sign-ups.

A. WordPress membership (required for registration)

1. Go to Settings → General (WordPress core settings, not the plugin).
2. Enable Membership → Anyone can register.
3. Save changes.

B. Plugin Auth setting

1. Go to Support Ticket Plus → Settings → Auth.
2. Set Allow Registration to Yes.
3. Click Save Changes.

To allow guest ticket submit without an account, go to Settings → General → Portal Access and set Allow Guest Tickets to Yes.

New accounts receive the Subscriber role and can create and view only their own tickets. Login details are emailed after registration (SMTP must be configured for reliable delivery). Guest submissions create a customer account from the provided email when needed and send a ticket confirmation.

Why SMTP and how to configure it

WordPress’s default mail() function often fails on shared hosting or lands in spam. Support Ticket Plus sends email for registration confirmation, new ticket alerts, reply notifications, and status/assignment updates. SMTP uses your mail provider’s authenticated server so messages are delivered reliably.

1. Go to Support Ticket Plus → Settings → SMTP.
2. Fill in the fields from your mail provider (Gmail, Microsoft 365, cPanel, SendGrid, etc.): SMTP Host, Port (465 SSL or 587 TLS), Username, Password (prefer app passwords for Gmail), From Email, From Name, Encryption.
3. Click Save Changes.

Set up a real WordPress cron job (recommended)

WordPress’s built-in WP-Cron only runs when someone visits your site. For reliable delayed Instant Replies, SLA checks, and (with Pro) Gmail inbound polling, configure a real server cron that hits wp-cron.php every minute:

1. In your host’s control panel (cPanel, Plesk, etc.) or SSH crontab, add a job that runs every minute.

2. Use a command like this (replace the URL with your site):

   */1 * * * * curl -s https://example.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1

   Or with wget:

   */1 * * * * wget -q -O – https://example.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1

3. (Optional but recommended) Disable the default visitor-triggered cron by adding this line to wp-config.php above the “That’s all, stop editing!” comment:

   define( ‘DISABLE_WP_CRON’, true );

Without a server cron, scheduled tasks still work, but they may run late on low-traffic sites.