> For the complete documentation index, see [llms.txt](https://docs.spurtcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spurtcommerce.com/addons/support-ticket-addon.md).

# Support Ticket Addon

### Frontend Setup - Seller Panel:

Follow these steps to set up the front end for the Support Ticket addon in Spurtcommerce Seller Panel.

Step 1: Install the Addon:

Locate the Spurtcommerce addon package, typically named seller.addOns.zip.

Extract the zip file and copy the support-ticket folder into the addOns folder in your project.

projectFolder -> addOns

After this step, the structure should look like:

projectFolder -> addOns -> support-ticket

Once completed, proceed to update the configuration.

### Step 2: Update the Configuration

After installing the addon, update the add-ons.constant.ts file to include the necessary plugins:

```
// ----------------------Support Ticket--------------------------
import * as supportTicket from './support-ticket/support-ticket-constant';
// components paths
export const supportTicketComponent = supportTicket.ticketComponentList;
// route paths
export const supportTicketRoutes = supportTicket.routePath;

```

If you wish to uninstall or remove the Support Ticket addon, replace the component paths and route paths with an empty array.

```
// ---------------------Support Ticket Routes---------------------
import * as supportTicket from './support-ticket/support-ticket-constant';
// components paths
export const supportTicketComponent = [];
// route paths
export const supportTicketRoutes = [];

```

Step 3: Run the Application:

To run the application with the integrated Support Ticket addon, use the following command:

```
$ npm run large-serve

```

After executing this command, the addon will be available on Spurtcommerce on the designated page.

Step 4: Build the Application

Finally, to prepare the application for deployment, run the build command:

```
$ npm run large-build
```

The latest build files will then be ready to deploy to the server.