Polanger Ticket System for WooCommerce

Descripción

Polanger Ticket System helps you centralize customer communication in a clean, ticket-based system integrated into WooCommerce.

Customers can create and manage tickets directly from their account page, while store owners handle support requests from a structured admin interface with real-time updates and clear workflow control.

Designed for simplicity in the free version and scalability with Pro, Polanger adapts from small stores to growing support teams.

Core Features (Free Version)

  • Chat-style ticket messaging interface
  • Real-time updates without page refresh
  • Agent collision detection (Agent Lock)
  • WooCommerce order & product linking
  • Customizable categories & priorities
  • Email notifications for tickets and replies
  • Customer ticket closing option
  • Auto-close inactive tickets
  • Maximum active ticket limit per customer
  • HPOS fully compatible
  • Fully translatable (i18n ready)

Ticket Management

  • Create Tickets – Customers can open tickets from My Account
  • Track Status – Open, In Progress, Waiting, Resolved, Closed
  • Priority Levels – Custom urgency system
  • Categories – Organize and route tickets
  • Order & Product Context – Full WooCommerce integration

Chat Interface

  • Real-time message updates
  • Chat-style conversation layout
  • Customer/Admin message separation
  • Time-based message display
  • Avatar support

Security & Control

  • Agent Lock (collision prevention system)
  • Active viewer tracking (heartbeat)
  • Auto-remove inactive viewers
  • Nonce-protected AJAX requests
  • Role & capability checks

WooCommerce Integration

  • My Account ticket tab
  • Order-based ticket context
  • Product linking
  • Optional purchase requirement
  • HPOS support

Developer Friendly

  • Action & filter hook system
  • Clean and extendable codebase
  • Custom database tables
  • Translation ready
  • Debug logging support

Language Support

Polanger Ticket System includes translation template support (.pot) and currently ships with ready .po language files for:

  • Russian (ru_RU)
  • Chinese – Simplified (zh_CN)
  • Turkish (tr_TR)
  • Spanish (es_ES)
  • French (fr_FR)
  • German (de_DE)
  • Arabic (ar)
  • Portuguese (pt_PT)
  • Hindi (hi_IN)
  • Japanese (ja)
  • Italian (it_IT)

You can extend or refine translations with any PO editor by using the files in the /languages directory.

Pro Version

The Pro version transforms Polanger into a full support operations system with modular addons and advanced team workflows.

Pro Highlights

  • Frontend Support Panel for agents (no wp-admin required)
  • Real-time team collaboration tools
  • Advanced analytics & reporting
  • Modular addon architecture
  • Internal communication layer (Operations Desk)
  • Department-based team structure
  • Extendable developer platform

Support Panel (Core Pro Feature)
A complete frontend support workspace for agents.

Manage tickets, reply in real time, claim ownership, view customer/order data, and collaborate with your team — all without entering the WordPress admin panel.

Agent 360
Advanced agent analytics including performance score, workload insights, and activity tracking.

Agent Invite
Invite other agents into a ticket without transferring ownership. Designed for collaboration without breaking workflow control.

Departments
Organize agents into teams and route collaboration more efficiently.

Operations Desk
Internal communication layer for agents and managers.

Coordinate actions, escalate issues, and manage operations in real time without leaving the support environment.

SLA Management
Track response and resolution times with working hours, pause logic, and breach detection.

Auto Assignment
Automatically assign tickets using smart distribution strategies.

Canned Responses
Reusable replies with dynamic placeholders and shortcuts.

File Attachments
Secure file uploads with drag & drop and validation controls.

Analytics Dashboard
Real-time insights into tickets, agents, SLA, and performance.

Developer Platform (Addon System)
Build and integrate custom addons as standalone plugins.

Extend the system safely using hooks and modular architecture without modifying core files.

More information:

Instalación

Automatic Installation

  1. Go to Plugins > Add New in your WordPress admin
  2. Search for “Polanger Ticket System”
  3. Click Install Now and then Activate
  4. Go to Tickets in the admin menu to configure settings

Manual Installation

  1. Download the plugin zip file
  2. Go to Plugins > Add New > Upload Plugin
  3. Upload the zip file and click Install Now
  4. Activate the plugin
  5. Go to Tickets in the admin menu to configure settings

After Activation

  1. Navigate to Tickets > Settings to configure general options
  2. Go to Tickets > Settings > Categories & Priorities to customize categories and priorities
  3. Customers can now access tickets from their My Account > Support Tickets page

FAQ

Does this plugin require WooCommerce?

Yes, WooCommerce 5.0 or higher is required. The plugin integrates directly with WooCommerce’s My Account page.

Where do customers access their tickets?

Customers can access their tickets from the “Support Tickets” tab in their WooCommerce My Account page.

Can I customize ticket categories and priorities?

Yes! Navigate to Tickets > Settings and click on the Categories & Priorities tab. You can add, edit, delete, and reorder both categories and priorities. Each can have a custom name, color, and default status.

How does collision detection work?

When an admin opens a ticket, the system registers them as a “viewer” using a heartbeat system. If another admin opens the same ticket, both will see a warning message showing who else is viewing the ticket. This prevents duplicate responses and confusion.

Can customers close their own tickets?

Yes, this is enabled by default. You can disable it in Tickets > Settings by unchecking “Allow Customers to Close Tickets”.

How do I limit the number of tickets a customer can create?

Go to Tickets > Settings and set the “Max Active Tickets Per Customer” option. Set to 0 for unlimited tickets.

Is the plugin compatible with HPOS?

Yes! Polanger Ticket System is fully compatible with WooCommerce’s High-Performance Order Storage (HPOS).

Can I translate the plugin?

Yes, the plugin is fully translatable. A .pot file is included in the /languages folder. You can use tools like Poedit or Loco Translate to create translations.

How do email notifications work?

When enabled, the plugin sends:
– Email to admin when a new ticket is created
– Email to customer when admin replies to their ticket

You can configure the admin email address and enable/disable notifications in Tickets > Settings.

Are there additional extensions?

Yes, additional features are available through separate extensions. See the Extensions section above for details.

Reseñas

20 de Abril de 2026 1 respuesta
There are a few alignment/shifting issues on the admin dashboard on mobile, but other than that, it’s a really good plugin
Leer 1 comentario

Colaboradores & Desarrolladores

“Polanger Ticket System for WooCommerce” es software de código abierto. Las siguientes personas han contribuido a este plugin.

Colaboradores

Historial de cambios

1.2.8

  • Fix: Resolved an undefined variable issue in the ticket priority save process (sort_order) and ensured correct ordering during updates.
  • Fix: Corrected endpoint title filtering to prevent unintended modifications to global the_title outputs.
  • Improvement: Improved ticket creation flow by introducing transaction-based inserts for better data consistency.
  • Improvement: Centralized plugin version management by binding runtime version to PGTS_VERSION.
  • Security: Strengthened query handling by refactoring ticket queries to use a single prepared statement.
  • Security: Hardened create_ticket() by restricting inputs to known columns and sanitizing all fields.
  • Performance: Optimized unread badge queries to run only on relevant WooCommerce My Account pages.
  • Reliability: Enhanced WooCommerce detection with an additional runtime class existence check.
  • Reliability: Added login validation to the customer ticket close AJAX endpoint.

1.2.7

  • Internationalization: Expanded and refined multilingual infrastructure for broader global readiness.
  • Language Pack Update: Added 10 new language files to the plugin language set for faster localization rollout.
  • Translation Quality: Improved translation consistency and string coverage across key frontend and admin ticket workflows.

1.2.6

  • Fix: Resolved a role-based access issue affecting new ticket creation and handling workflows.
  • Fix: Fixed a mobile-specific issue that could cause unintended looping in the customer support request form.
  • Improved: Enhanced ticket priority sorting logic for more consistent and predictable behavior.
  • Improved: Polished admin interface by resolving alignment and layout inconsistencies.

1.2.5

  • Permission Consistency: Admin ticket AJAX endpoints now use the same centralized access model as the admin ticket panel, reducing role/capability mismatch risk.
  • Timeout Unification: Sticky owner lock timeout now consistently uses PGTS_owner_lock_timeout_minutes as a single source of truth.
  • Collision Layer Sync: Ticket collision AJAX checks were aligned with the same admin access helper used across admin reply/update endpoints.
  • Pro Summary Update: Pro addons list now reflects Agent 360 and total addon count is updated to 11.

1.2.4

  • Reply Ownership: Introduced sticky owner lock for admin replies. The first staff replier on an unassigned ticket becomes owner; assigned tickets now enforce owner-only replying at the server level.
  • Controlled Takeover: Added configurable inactivity timeout setting PGTS_owner_lock_timeout_minutes (default 60). If the owner is inactive and not viewing the ticket, ownership is auto-released for takeover.
  • Settings: Added new “Reply Ownership Timeout (minutes)” option in Ticket System settings (0 disables auto-release).
  • Admin UI: Redesigned ticket detail ownership information block and now show configured takeover timeout clearly for agents/admins.

1.2.3

  • Mobile: Improved admin ticket detail page flow on small screens. Conversation/reply area now appears first and full-width; customer/details widgets are moved below and full-width for easier handling.
  • Mobile: Improved Categories & Priorities settings tables with horizontal scroll support, preventing cramped cells and broken slug wrapping on narrow screens.
  • Mobile: Improved slug column readability in settings tables with safer min-width and no-wrap behavior for values like urgent, high, and custom slugs.
  • Performance: Optimized admin ticket listing workflow with cleaner server-side filtering/search handling and per-page limits, reducing unnecessary rows rendered on large stores.

1.2.2

  • Admin UX: Added advanced filters on the All Tickets screen with mobile-friendly layout (search by Subject/Customer, dynamic Priority filter, and per-page selector with 20/50/100/All options). Default view now shows 20 tickets.
  • Admin Sorting: Ticket list ordering now uses dynamic priority sort order from the Priorities table (instead of hardcoded urgent/high/normal/low), so newly created priorities are sorted correctly.
  • Admin Priority Management: Added editable “Priority Order (1 = highest)” field in Priority create/edit modal and displayed priority order in the settings table. This makes ordering explicit and fully controllable for built-in and custom priorities.
  • Admin Safety: Closed tickets are always pushed to the bottom of the ticket list to reduce accidental focus on completed items.
  • Collision/Lock Enforcement: Upgraded collision detection from warning-only behavior to server-enforced reply blocking. If another admin owns the active lock, reply submission is blocked at the AJAX endpoint.
  • Collision Ownership: Lock ownership now follows first-viewer semantics (first admin entering the ticket holds lock), and only later viewers are blocked.
  • Collision Timeout: Added 30-minute lock-owner timeout without reply activity. If owner times out, next replying admin can claim lock and continue.
  • Security Hardening: Added capability check (manage_woocommerce) to ticket leave endpoint for collision handling consistency.

1.2.1

  • Added: Permanent ticket deletion from the admin ticket list and ticket detail screen.
  • Improved: Ticket deletion now requires confirmation before execution.
  • Security: Deletion is restricted to closed tickets only; server-side validation prevents removal of open or in-progress tickets, even for tampered requests.
  • Security: Added nonce-protected AJAX and capability checks (manage_woocommerce) to control deletion permissions.
  • Developer: Expanded “Available Hooks for Developers” documentation in the readme with a complete list of PGTS_ actions and filters, including descriptions and parameter notes.

1.2.0

  • Performance: Improved My Account ticket list polling with debouncing and reduced unnecessary reflows during background updates.
  • Performance: Optimized admin ticket detail scripts with more efficient event handling and faster AJAX reply processing.
  • Performance: Reduced redundant option and settings reads when rendering ticket badges on the frontend.
  • Performance: Optimized ticket list queries with more efficient column selection for large datasets.
  • Mobile: Improved tap targets, spacing, and readability on ticket forms and chat threads for small screens (~480px and below).
  • Mobile: Enhanced reply composer behavior when the on-screen keyboard opens (better scroll positioning and iOS safe-area support).

1.0.0

  • Initial release
  • Complete ticket management system
  • Customer frontend integration with WooCommerce My Account
  • Admin dashboard with gradient design
  • Real-time chat-style messaging
  • Agent lock / collision detection system
  • Email notifications for new tickets and replies
  • Customizable categories with colors
  • Customizable priorities with colors
  • Order and product association
  • Customer ticket closing option
  • Maximum active tickets per customer limit
  • Auto-close inactive tickets setting
  • Require product purchase option
  • Custom no-purchase message with WYSIWYG editor
  • Status-based row coloring in ticket lists
  • Unread ticket badge in My Account menu
  • Full HPOS compatibility
  • Complete i18n support
  • WordPress Coding Standards compliant
  • Extensive hook system for developers