---
title: Ticket Center
description: >-
  Fuxam Base's internal help desk: requesters send tickets from the Support
  page, staff route, answer and resolve them under Management → Ticket Center.
sidebar:
  order: 5
  label: Overview
---

**Ticket Center** is the place in Fuxam Web where your institution collects, routes and answers internal support tickets. Staff work the queue under **Management → Ticket Center**. Everyone else sends and follows their requests on the **Support** page, which opens from the **Support** button in the sidebar footer.

:::info
Ticket Center is part of **Fuxam Base**. An admin has to turn on **Ticket Center** under **Settings → Configuration Wizard → Features** first. Each person also needs a Ticket Center permission in their role. Without both, the sidebar entry and the **Support** page stay hidden. See [Ticket Center permissions](/docs/fuxam-web/base/ticket-center/ticket-center-permissions).
:::

## Why it matters

When questions arrive by email, chat and in the hallway, some get lost and nobody can say how long answers take. With Ticket Center, every request becomes a numbered ticket. It goes to the right person automatically, has a response target, and keeps one history of public replies and internal notes. If your team can't solve a ticket, you can bring in the Fuxam team in a separate private thread without leaving the ticket.

## Who uses what

| Person | Where they work | What they do |
|---|---|---|
| **Requester** (anyone with **Create tickets**) | **Support** page (sidebar footer **Support**) | Creates tickets, replies, follows **Open requests** and **Resolved**, gives feedback |
| **Support staff** (**Edit tickets**) | **Management → Ticket Center** | Works the queue: assigns, replies, writes internal notes, changes status and priority, resolves |
| **Ticket Center admin** (**Configure Ticket Center**) | **Settings → Management → Ticket Center** and the **Triage** tab | Sets up categories, priorities, statuses, the catch-all assignee and triage rules |
| **Escalation lead** (**Forward tickets to Fuxam Team**) | **Fuxam** tab on a ticket | Brings in the Fuxam team for tickets the institution can't solve |
| **Analyst** (**View analytics**) | **Analytics** tab | Reads ticket volume, resolution time and first-response figures |

## Key concepts

| Term | Meaning |
|---|---|
| **Ticket** | One request with an ID, **Subject**, **Category**, **Description**, optional attachments and an optional **Priority**. |
| **Category** | What the ticket is about (for example access or exams). Required when you create a ticket. Each category can have a default assignee, people for routing, and a Responsible and Deputies. **Other** is the catch-all category. |
| **Priority** | How urgent the ticket is. Each priority has a color and a **Response target** for the first public staff reply. New tickets start with **No priority**. |
| **Status** | Where the ticket stands. Every status belongs to one of three groups: **Not started**, **In progress** or **Finished**. The default statuses are **Open**, **In progress** and **Resolved**. |
| **Catch-all assignee** | The person who gets the **Other** category and every ticket that no more specific rule matches. Set under **Ticket Triage** in the settings. |
| **Triage rule** | A rule that sends tickets with a given category and/or priority to a set of people before the category's own routing applies. |
| **Reply / Internal note** | A **Reply** is visible to the requester. An **Internal note** stays inside your team. |
| **Fuxam escalation** | A separate private thread with the Fuxam team, opened from the **Fuxam** tab. |

## Where things are

| Area | Path | Who sees it |
|---|---|---|
| Queue | **Management → Ticket Center → Open tickets** | **Edit tickets** |
| Resolved tickets | **Management → Ticket Center → Resolved** | **Edit tickets** |
| Triage | **Management → Ticket Center → Triage** | **Edit tickets** can view; **Configure Ticket Center** can edit |
| Feedback | **Management → Ticket Center → Feedback** | Staff, when feedback is turned on |
| Analytics | **Management → Ticket Center → Analytics** | **View analytics** |
| Your own requests | Sidebar footer **Support** → **Open requests**, **Resolved**, **Feedback** | **Create tickets** |
| Settings | **Settings → Management → Ticket Center** | **Configure Ticket Center** |

## A ticket's life

1. A requester clicks **Support** in the sidebar footer, then **Create ticket**, and fills in **Subject**, **Category** and **Description**.

2. Fuxam routes the ticket: matching triage rule first, then the category's people, then the category's default assignee, then the catch-all assignee. See [Set up triage and routing](/docs/fuxam-web/base/ticket-center/set-up-triage-and-routing).

3. The assignee gets a **Ticket assigned** notification and opens the ticket from **Open tickets**.

4. Staff answer with a **Reply** or coordinate with an **Internal note**. A staff comment on an **Open** ticket moves it to **In progress**.

5. Staff set the status to **Resolved**. The requester is notified. If anyone sends a public reply later, the ticket reopens to **In progress**.

## Mobile

Ticket Center is a Fuxam Web feature. Fuxam Mobile has no Ticket Center screens. Notifications about tickets can still reach you in-app, by email or as push messages, depending on your notification settings.

## Common pitfalls

| Pitfall | What happens | What to do |
|---|---|---|
| Feature on, but no permissions given | Nobody sees **Ticket Center** in the sidebar | Add the Ticket Center permissions to the right roles. |
| No catch-all assignee set | The **Other** category can't be created and requesters see "Ticket Center routing is not configured yet." | Set a **Catch-all assignee** under **Ticket Triage** in the settings. |
| Staff can't find a ticket | Without **See all tickets**, staff only see tickets assigned to them and categories where they are Responsible or Deputy | Give **See all tickets** or add the person under **Manage access** for the category. |
| Expecting the app to show tickets | Fuxam Mobile has no Ticket Center | Work tickets in Fuxam Web. |

## FAQ

**Is Ticket Center the same as the old Support Center?**

Yes. Support Center was renamed to Ticket Center. The page addresses still use "support-center", for example `/dashboard/support-center`.

**Who can create tickets?**

Anyone whose role has **Create tickets**. **Edit tickets** and **Configure Ticket Center** include it. People without any of these get the Fuxam help chat when they click **Support** in the sidebar footer.

**Can students use Ticket Center?**

Yes, if their role has **Create tickets**. Admins can also let students send feedback with the **Feedback** setting.

**Does the Fuxam team see our internal notes?**

No. When you bring in Fuxam, it sees the subject, description, public replies and diagnosis. Internal notes stay in your institution.

## In this section

**[Create a ticket](/docs/fuxam-web/base/ticket-center/create-a-ticket)**

Send a request, or log one for someone else.

**[Track your requests](/docs/fuxam-web/base/ticket-center/track-your-requests)**

Follow your tickets, reply and give feedback on the Support page.

**[Use the ticket queue](/docs/fuxam-web/base/ticket-center/use-the-ticket-queue)**

Filter, sort and bulk-assign tickets, and set your availability.

**[Work on a ticket](/docs/fuxam-web/base/ticket-center/work-on-a-ticket)**

Reply, write internal notes, change status, priority and assignee.

**[Forward a ticket to Fuxam](/docs/fuxam-web/base/ticket-center/forward-a-ticket-to-fuxam)**

Bring in the Fuxam team in a private thread.

**[Set up the Ticket Center](/docs/fuxam-web/base/ticket-center/set-up-the-ticket-center)**

Categories, priorities, statuses, feedback and support seats.

**[Set up triage and routing](/docs/fuxam-web/base/ticket-center/set-up-triage-and-routing)**

Decide who gets which ticket automatically.

**[View Ticket Center analytics](/docs/fuxam-web/base/ticket-center/view-ticket-center-analytics)**

Volume, resolution time and first response.

**[Ticket Center permissions](/docs/fuxam-web/base/ticket-center/ticket-center-permissions)**

What each permission allows and who sees which tickets.

