PAY PER TICKET

The shop manager can now bind to any product (or variant) a number of questions that a user can ask. Once the product is purchased and the order is paid (or marked as completed), the plugin will automatically open a special Pay Per Ticket by which the admin can keep track of the user questions. The product quantity will affect the number of questions that the user will be able to ask.

To assign the number of questions to a product, just edit it and in the General tab, you will find an input field name Questions number. For variable products, the Question number setting will be editable for each variant via the Variations tab.

Example:

1. The admin binds 6 questions to Product 1
2. The user buys 2xProduct 1
3. Once the order will be paid, The plugin will open a Pay Per Ticket having 12 questions

A number of questions left can be editable by the admin using the ticket edit page.

The user can buy multiple products having questions bound to them. The plugin will open a ticket for each of them

Pay per ticket area is displayed in the frontend by using the special.

Number of questions left can be editable by the admin using the ticket edit page.

The user can buy multiple products having questions bound to them. The plugin will open a ticket for each of them

Pay per ticket area is displayed in the frontend by using the special [wcsts_pay_per_ticket_area] shortcode in any page supporting shortcodes. The ticket area will be displayed only for registered users, for non registered users will be displayed a login message. To customize the login message, just use the following format: [wcsts_pay_per_ticket_area]Type the message you want to display, html code is accepted[/wcsts_pay_per_ticket_area]

Note: if an order is deleted or marked as failed, canceled or refunded, the associated pay per tickets will be deleted too. Once a ticket reaches 0 questions left, the user will be automatically marked as closed.
Guest customer can access the order ticket via the Thank you page. The new ticket notification emails will generate a link to that page by using the {order_page_url} shortcode.

Note for WooCommerce Subscriptions users: In case of a subscription product, every time a renewal occurs, the plugin will reset the pay per ticket question number associated with it. The pay per ticket will be automatically created according to the order payment status, not the subscription status.

WooCommerce Support Ticket System GPl FILE ATTACHMENT

Optionally you can enable files attachment for reply messages and tickets. You can set the file size limit and configure which file types are accepted. Furthermore, thanks to the “chunk upload” system, the plugin allows to upload any file size!

USE CASE: FILE APPROVAL SYSTEM

The ticket system can be used also as a File approval system. Thanks to the file chunk upload system, your customers will be able to attach any file size to each ticket (you can, however, limit the number of the uploadable files, size, and types). You can then reject the upload(s) by simply reply to the ticket (optionally the user will be notified via email) and eventually attach files to your reply.
Each message will have its own attachments (that can be eventually deleted) in order to keep track of the attachment history!

PREDEFINED ANSWERS

Would you like to define a set of predefined answers that can be later recalled when managing a ticket? You can! Just access to the Predefined answers menu and create them! Those answers will be available to all the admins that will be lately answering the ticket!

RICH TEXT AND TINY MCE ON FRONTEND

Optionally you can also enable the Tiny MCE editor for frontend ticket text areas! In this way, your customers will be able to enter rich texts!
To enable this option just go in the plugin options menu and enable the Enable Tiny mce editor for ticket message area on frontend option.

WooCommerce Support Ticket System GPl BACKEND MANAGMENT

The shop admin via the backend Ticket system managment area will be able to keep track of all the submitted tickets. In the ticket list table, the shop admin can at once retrieve the following info:

1. Type: can be Order or User. It is needed to identify if the ticket is associated to a specific order or to a specific user
2. Associated User/Order id
3. Status: It can be Open, In Progress or Closed
4. Priority: priorities can be customized using the special menu
5. New message counter: it helps to better identify if an user replied to ticket
6. Subject: ticket subject
7. Ticekt open date
8. Ticekt last user reply date