Support Ticket Plus — Product Documentation

By LucrativeIT.com · Live demo: wpticket.lucrativeit.com · Purchase Pro

Support Ticket Plus is a WordPress help desk plugin for managing customer support from ticket creation through resolution. Customers use a public support portal (with optional guest ticketing and magic-link access); staff manage tickets from WordPress admin or the same portal.

1. Installation

Requirements

RequirementMinimum
WordPress6.2+
PHP8.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:
General Settings

Settings → General

SettingPurpose
App NameDisplay name on the portal (e.g. Support Ticket Plus)
Ticket PrefixPrefix for ticket IDs (e.g. TKT#TKT-1007)
Admin Notification EmailWhere staff alerts are sent
Max Attachment Size (MB)Upload limit for ticket files
Allow Guest TicketsLet visitors submit tickets with name and email without logging in
Enable Turnstile for Guest TicketsShow Cloudflare Turnstile CAPTCHA on the guest form
Site Key / Secret KeyCloudflare Turnstile keys (secret stored encrypted)
Admin Ticket OptionsToggle create / view / reply in WordPress admin
  1. Create departments under Support Ticket Plus → Departments so tickets can be routed correctly:
Departments

Departments with auto-assign (round-robin)

Enable Auto-assign for round-robin distribution among agents in that department.

  1. (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.

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]

2. Enable registration

Customers can open tickets with a registered account, or as a guest without logging in (see section 2.1). For registered users, sign-up is controlled in two places — both must allow registrations.

A. WordPress membership (required)

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

Without this, WordPress rejects new accounts even if the plugin Register button is visible.

B. Plugin Auth setting

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

Settings → Auth → Allow Registration

What customers see

Visitors who open the support portal while logged out see a login prompt. With registration enabled, they also get a Register option (modal on the portal).

To promote a user to support staff, grant their WordPress role the Tickets permission under Support Ticket Plus → Roles.

2.1 Guest tickets (no login required)

When Allow Guest Tickets is enabled under Settings → General → Portal Access (on by default), visitors can submit a support request without creating an account or logging in.

What the visitor sees

On the portal login screen, a Submit a Ticket as Guest link appears below the Register option:

Submit a Ticket as Guest link on login screen

Portal login — guest ticket entry point

Guest create-ticket flow

  1. Click Submit a Ticket as Guest.
  2. Enter Your Name and Email (required).
  3. Complete the standard ticket fields: subject, order number (optional), department, priority, description, and attachments.
  4. Complete the Turnstile CAPTCHA if enabled (see section 2.2).
  5. Click Submit Ticket.

The footer note reads: We will email you a confirmation and a secure link to track this ticket.

What happens after submit

Disable guest tickets

Set Allow Guest Tickets to No under Settings → General. Visitors must then log in or register to submit tickets.

2.2 Cloudflare Turnstile CAPTCHA

Protect the guest create-ticket form from spam with Cloudflare Turnstile — a free CAPTCHA alternative. Turnstile applies to guest submissions only; logged-in users do not see it.

Configure Turnstile

  1. Create a Turnstile widget in the Cloudflare dashboard and copy the Site Key and Secret Key.
  2. Go to Support Ticket Plus → Settings → General.
  3. Under Cloudflare Turnstile, set Enable Turnstile for Guest Tickets to Yes.
  4. Paste the Site Key and Secret Key.
  5. Click Save Changes.
Cloudflare Turnstile settings

Settings → General — Cloudflare Turnstile

SettingPurpose
Enable Turnstile for Guest TicketsShow the CAPTCHA widget on the guest create-ticket form
Site KeyPublic key from your Cloudflare Turnstile widget
Secret KeyPrivate key; stored encrypted. Leave blank to keep the current secret.
Turnstile widget on guest ticket form

Guest create-ticket form with Turnstile verification

If verification fails, the form redisplays with: Please complete the captcha verification and try again.

3. Why SMTP and how to configure it

Why SMTP matters

WordPress’s default mail() function often fails on shared hosting or lands in spam. Support Ticket Plus sends email for:

SMTP uses your mail provider’s authenticated server so messages are delivered reliably and appear from your brand address.

How to configure SMTP

  1. Go to Support Ticket Plus → Settings → SMTP.
  2. Fill in the fields from your mail provider (Gmail, Microsoft 365, cPanel, SendGrid, etc.).
  3. Click Save Changes.
SMTP Settings

Settings → SMTP

FieldExampleNotes
SMTP Hostsmtp.yourdomain.com or smtp.gmail.comFrom your provider
Port465 (SSL) or 587 (TLS)Match encryption
Usernameinfo@yourdomain.comUsually the full email
PasswordApp password or mailbox passwordPrefer app passwords for Gmail
From Emailinfo@yourdomain.comSender address customers see
From NameSupport Ticket PlusDisplay name in the inbox
EncryptionSSL or TLSSSL → port 465; TLS → port 587

Recommended checklist

4. Create a ticket

Customer portal (logged in)

  1. Open the Support Portal page and log in.
  2. Click Create Ticket in the sidebar, or New Ticket on the dashboard.
User dashboard

Customer portal dashboard

Complete the form:

Create New Ticket (customer)

Create New Ticket form

FieldDescription
SubjectShort summary of the issue
Order NumberOptional link to a purchase (e.g. ORD-123456)
DepartmentRoutes the ticket to the right team
PriorityLow, Medium, High, or Urgent (SLA targets shown on the form)
DescriptionFull details of the problem
AttachmentsPDF, PNG, JPG, DOC, ZIP (size limited by settings, default 10 MB)

Submit the ticket. It receives an ID such as #TKT-1001 and appears under My Tickets.

My Tickets

My Tickets list

Guest (no login)

Guests use the same create-ticket form with additional Your Name and Email fields. See section 2.1 for the full guest workflow, Turnstile CAPTCHA, and magic link access after submit.

Staff / admin

Agents can create tickets from:

Create ticket (staff portal)

Staff create-ticket view

5. Reply to a ticket

Customer

  1. Go to Tickets (or My Tickets) in the portal.
  2. Click the eye icon on a ticket row to open the conversation.
  3. Type a reply, attach files if needed, and send.

Customers only see public messages (not internal staff notes).

Agent / admin

  1. Open Tickets in the portal or Support Ticket Plus → Tickets in WordPress admin.
Ticket list (staff)

Staff ticket list with filters

  1. Open a ticket with the eye icon.
  2. Use the reply composer:
    • Public Reply — visible to the customer; triggers notifications.
    • Internal Note — staff-only; not shown to the customer.
  3. Click Send Reply.

Ensure Enable Reply in Admin is set to Yes under Settings → General if agents reply from WordPress admin.

Filters on the ticket list (status, priority, department, agent) help agents find work quickly. The admin dashboard shows volume, open queue, and SLA breaches:

Admin dashboard

Admin Support Overview dashboard

Guest customers access their ticket through a signed URL sent by email after submission. They can view the conversation and post public replies without a WordPress login.

  1. After submitting a guest ticket, the browser opens the ticket via a URL containing lit_view=ticket, lit_ticket, and lit_token.
  2. A green banner explains: You are viewing this ticket via a secure email link. You can reply here without logging in.
  3. Use Copy Link to save the private URL and return anytime within the link validity period (30 days by default).
  4. Public replies work the same as for logged-in customers; internal notes are staff-only.
Copy magic link banner on ticket view

Guest ticket view — secure magic link with Copy Link button

Tip: Configure SMTP (section 3) so confirmation emails with the magic link are delivered reliably. Guests who lose the link can check their inbox for the original email.

6. Notifications

Support Ticket Plus uses in-app notifications and email (via SMTP).

In-app notifications (portal)

  1. Open Notifications in the portal sidebar.
  2. Unread items show a red badge on the menu and an UNREAD count on the page.
  3. Example: Agent replied on ticket TKT-1000.
  4. Click the eye icon to open the related ticket, or Mark All Read to clear the list.
Notifications

Portal notifications center

Email notifications

When SMTP is configured, the plugin can email customers and staff for events such as:

Configure:

LocationWhat to set
Settings → GeneralAdmin Notification Email
Settings → SMTPDelivery server
Settings → Email TemplatesSubject and body for each event

6.1 Email templates & branding PRO

With Lucrative Support Ticket Pro active, Support Ticket Plus → Settings → Email Templates opens the full email template manager. Without Pro, the same tab shows a notice and only basic subject/body fields per template.

The manager has two layers:

  1. Email header & branding — a shared HTML wrapper applied to every notification email.
  2. Per-event templates — subject lines and body copy for each notification type.

Configure SMTP first (section 3) so preview and test emails can be delivered.

Email header & branding

Email header and branding settings

Settings → Email Templates — header logo, colors, and footer

This section controls the look of the outer email shell (header bar, colors, and footer). Changes apply to all notification emails, not just one template.

SettingPurpose
Header logoUpload or change the image shown in the colored header bar. Use Remove logo to fall back to the App Name text from General settings.
Logo positionAlign the logo Left, Center, or Right in the header.
Logo width (px)Set logo width from 40–600 px (default 180).
Primary colorBackground of the header bar (default #0058be).
BackgroundOuter email background behind the card (default #f4f6f8).
Card surfaceMain content card background (default #ffffff).
Text colorBody text inside the card (default #191c1e).
Muted textFooter and secondary text (default #424754).
Footer textCustom footer copy. Leave blank to use © {year} {company}.

Click Save branding to store these settings. They are independent of individual template saves.

Notification templates

Email notification template editor

Per-event templates with sidebar navigation and merge tags

Use the left sidebar to pick a template. Templates are grouped by audience:

GroupTemplatesWhen sent
Customer notificationsTicket Created, Reply ReceivedCustomer creates a ticket or receives a public reply
Agent notificationsTicket Assigned, Ticket Unassigned, Status Changed, Priority Changed, Department ChangedAssignment or ticket field updates affecting agents
SLA alertsSLA Warning, SLA BreachedApproaching or missed SLA deadline
Admin alertsAdmin: New Customer Ticket, Admin: Customer Reply (Unassigned)New ticket or customer reply on an unassigned ticket

Each template editor includes:

ControlDescription
Enable this templateTurn the notification on or off without deleting custom copy. Disabled templates are not sent.
Subject lineEmail subject. Supports placeholders (see below).
Email bodyPlain-text message inserted into the branded HTML wrapper. Line breaks are preserved.
Insert placeholderClick a tag to insert {{placeholder}} into the focused subject or body field. Available tags vary by template.
Save templateSave subject, body, and enabled state for the selected template only.
PreviewRender a live HTML preview with sample data and current branding.
Send test emailSend a sample to your logged-in WordPress user email using the current subject and body.
Reset to defaultRestore the built-in subject and body for this template.

Placeholders (merge tags)

Use double curly braces in the subject or body. They are replaced when the email is sent.

PlaceholderReplaced with
{{recipient_name}}Name of the person receiving the email
{{ticket_number}}Ticket ID (e.g. TKT-1001)
{{subject}}Ticket subject line
{{status}} / {{old_status}}Current or previous status
{{priority}} / {{old_priority}}Current or previous priority
{{department_name}} / {{old_department_name}}Current or previous department
{{customer_name}}Ticket owner
{{agent_name}}Assigned agent
{{assigner_name}}User who assigned the ticket
{{actor_name}}User who changed status, priority, or department
{{replier_name}}User who posted the reply
{{message}}Reply body text
{{ticket_url}}Link to open the ticket in the portal
{{sla_deadline}}Formatted SLA due date/time
{{app_name}}App Name from General settings

Example — Ticket Created subject:

[{{ticket_number}}] Your ticket has been created

Example — Ticket Created body:

Hello {{recipient_name}},

Your support ticket {{ticket_number}} has been created.

Subject: {{subject}}
Priority: {{priority}}
Department: {{department_name}}

View your ticket: {{ticket_url}}

Recommended workflow

  1. Set Email header & branding to match your site (logo, colors, footer).
  2. Click Preview on a template to confirm the wrapper looks correct.
  3. Customize subject and body per notification type.
  4. Use Send test email to verify delivery and formatting in a real inbox.
  5. Disable any template you do not want sent using Enable this template.

7. Pro features PRO

Install the optional add-on Lucrative Support Ticket Pro (lucrativeit-support-ticket-pro) after Support Ticket Plus is active. Pro adds email-to-ticket, Gmail inbound, AI reply suggestions, and Google login. Purchase Pro.

7.1 Custom SMTP (included in Plus)

Built-in SMTP (see section 3) is part of Support Ticket Plus so outbound mail works without a third-party SMTP plugin.

7.2 Email Ticketing PRO

Turn inbound email into tickets and thread replies into existing conversations.

Email Ticketing

Settings → Email Ticketing

  1. Go to Support Ticket Plus → Settings → Email Ticketing.
  2. Set Enable Email Ticketing to Yes.
  3. Keep Thread Email Replies on Yes so replies with [TKT-1001] (or matching thread headers) attach to the same ticket instead of creating a new one.
  4. Set Inbound Reply Address (used as Reply-To on notification emails).
  5. Copy the Webhook URL and Webhook Secret into Mailgun, SendGrid, or another inbound provider.
Important: Email Ticketing alone does not fetch mail. You must also configure Gmail Inbound or a provider webhook.

7.3 Gmail Inbound PRO

Poll a Gmail inbox and pull replies into tickets.

Gmail Inbound

Settings → Gmail Inbound

  1. Enable the PHP IMAP extension on the server (php_imap). Without it, Gmail Inbound cannot run.
  2. Go to Settings → Gmail Inbound.
  3. Set Enable Gmail Inbound to Yes.
  4. Enter the Gmail Address (same address used as Reply-To when possible).
  5. Enter a Google App Password (not the normal Gmail password).
  6. Set Folder (usually INBOX) and optionally Mark as Read.
  7. Save changes.

WP-Cron polls Gmail about once per minute by default. On production sites, use a real server cron hitting wp-cron.php.

7.4 AI reply suggestions PRO

Help agents draft replies faster with an AI provider.

AI settings

Settings → AI

  1. Go to Settings → AI.
  2. Set Enable AI Suggestions to Yes.
  3. Choose Provider (e.g. OpenAI).
  4. Set Model (e.g. gpt-4o-mini).
  5. Enter your API Key.
  6. Optionally add a System Prompt to match your support tone.
  7. Save. Agents see AI tools in the ticket reply composer.

7.5 Other Pro capabilities

FeatureDescription
Google loginOptional sign-in via Google on the Auth settings tab
Email template managerBranding, preview, merge tags, test emails — see section 6.1
Webhook email-to-ticketREST endpoint for Mailgun / SendGrid inbound
Threaded email repliesCustomer replies by email stay on the same ticket

Plus features worth highlighting

These ship with Support Ticket Plus (no Pro required):

FeatureWhere
SLA tracking & breach alertsDashboard, Reports, create-ticket SLA table
Departments & round-robin auto-assignDepartments
Knowledge BasePortal Knowledge Base / admin KB
Guest tickets & magic linksSettings → General → Allow Guest Tickets
Turnstile CAPTCHASettings → General → Cloudflare Turnstile
Reports (volume, SLA, agent performance)Reports
Roles & permissions on existing WP rolesRoles
File attachmentsCreate / reply forms
Email templatesSettings → Email Templates
Reports

Reports — SLA and agent performance

Knowledge Base

Customer Knowledge Base

8. Quick reference

Admin menu (WordPress)

Menu itemPurpose
DashboardMetrics: total, open, in progress, resolved, SLA breached
TicketsList, filter, view, reply
UsersLink to WordPress user management
RolesStaff permissions per WordPress role
DepartmentsTeams, emails, auto-assign
ReportsSLA compliance, volume trends, agent performance
Knowledge BaseSelf-service articles
SettingsGeneral, SMTP, Auth, Email Templates (+ Pro tabs)

Portal URLs (examples)

Replace the path with your portal page slug:

ViewURL pattern
Dashboard/lucrativeit-support-ticket-plus/
My tickets?lit_view=tickets
Create ticket?lit_view=create
Guest create ticket?lit_view=create (when not logged in and guest tickets enabled)
Guest ticket (magic link)?lit_view=ticket&lit_ticket=12&lit_token=…
Notifications?lit_view=notifications
Knowledge base?lit_view=knowledge-base
Single ticket?lit_view=ticket&lit_ticket=12

First-time setup checklist