Customising Template Files
KB Support utilises template files to display content on the front end of your website. These files can be customised as described below.
KB Support utilises template files to display content on the front end of your website. These files can be customised as described below.
You can use the KB Support REST API to retrieve information regarding Tickets, Customers and Agents via 3rd party applications. You can also use the REST API to remotely create content such as tickets and replies.
When the KBS Email Support extension connects to your mailbox, it does so using the standard IMAP flags. These include the mailbox server host name, the protocol to use (IMAP/POP3), the port number and the transport security.
However, from time to time, you may need to send additional flags in order to obtain a successful connection. This article describes how.
KB Support has a number of built-in messages that are displayed to customers during various activities taking place on the front end of your website – for example, when a ticket is submitted. We’ll refer to these messages as notices.
These front end notices can be changed if you want to do so with a small amount of code by hooking into the kbs_get_notices
filter.
By default, only support workers with the Support Manager role are able to view customer details as well as add and edit customers, however, it is very easy to allow agents to add and edit customers if you need them need to do so.
WordPress locks posts whenever they are accessed in order to prevent multiple users from accessing and modifying the post at the same time.
This can be a hindrance to a support organisation and therefore, sometimes, it is necessary to enable multiple people to access and work on a ticket at the same time.
Similarly to the core KB Support plugin, and its extensions, Ratings and Satisfaction can be customised beyond the options that are available within settings.
This document, aimed at our more advanced user base, will detail some of the advanced customisation’s that can be achieved. As always, we highly recommend that any changes are implemented within your child theme to avoid being overwritten during future updates.
Sometimes the four statuses that are included within KB Support core are not enough to support your workflow and you need to add more.
If the default ticket status labels from KB Support do not match your preferred names, you can change them with some simple lines of code.
The global labels used throughout KB Support for Ticket, Tickets, KB Article and KB Articles are extremely easy to change if there is a term you would prefer to use for either, or both.