---
title: Work on a ticket
description: >-
  Reply to the requester, write internal notes, and change a ticket's status,
  priority and assignee.
icon: message-square
sidebar:
  order: 4
  icon: message-square
---

**A ticket's page** is where staff answer the requester, coordinate with internal notes and change status, priority and assignee. Open any ticket from **Management → Ticket Center → Open tickets**.

:::info
You need **Edit tickets** (or **Configure Ticket Center**) and access to the ticket: it is assigned to you, it is in a category where you are Responsible or Deputy, or you have **See all tickets**.
:::

## Why it matters

Requesters only see public replies, so the team can discuss a case in internal notes without confusing anyone. Status and response targets show everyone what is waiting and what is late.

## Before you start

| Requirement | Detail |
|---|---|
| Permission | **Edit tickets** or **Configure Ticket Center** |
| Ticket access | Assigned, Responsible/Deputy for the category, or **See all tickets** |
| Fuxam tab | **Forward tickets to Fuxam Team** |

## What you see

The header shows the requester, category and priority, plus the status menu, the assignee picker and the **…** (**Ticket actions**) menu. Below are the tabs:

| Tab | Content |
|---|---|
| **Conversation** | The original request, all replies and internal notes |
| **Fuxam** | The private thread with the Fuxam team. Only with **Forward tickets to Fuxam Team**. |
| **Files** | Every file attached to any message |
| **Metadata** | ID, category, priority, response target, created, updated, requester, created by, assignee, status, resolved, resolved by and Fuxam escalation |

## How to reply to the requester

1. Open the ticket. The composer at the bottom is set to **Reply**.

2. Write your answer. Add files if needed (up to 10 per message, 50 MB each).

3. Click **Send** or press Ctrl/Cmd + Enter. You see **Public reply sent**, and the requester is notified.

Your first public reply is what the response target measures. A comment on a ticket in a **Not started** status moves it to **In progress**.

## How to write an internal note

1. In the composer, switch from **Reply** to **Internal note**. The hint reads "Private team note — not visible to the requester."

2. Write the note and click **Send**. You see **Internal note saved**.

## How to change the status

1. Click the status menu in the header. Statuses are grouped into **Not started**, **In progress** and **Finished**.

2. Choose the new status, for example **Resolved**. You see **Ticket status updated** (or **Ticket resolved**).

A finished ticket moves to the **Resolved** tab and the requester gets **Ticket resolved**. To reopen it, use **Reopen**. The ticket goes back to **In progress** and the response target starts again.

## How to change the assignee

Click the assignee picker in the header and choose a person. You see **Assignee changed**, and the new assignee is notified.

## How to change the priority

1. Click **…** (**Ticket actions**) in the header.

2. Choose the new priority. You see **Priority updated**.

## Automatic status changes

| Event | Result |
|---|---|
| Staff comment on a **Not started** ticket | Moves to **In progress** |
| Public reply (from requester or staff) on a finished ticket | Reopens to **In progress**; the composer warns "A public reply reopens this ticket." |
| Internal note on a finished ticket | No change |
| Bring in Fuxam on a resolved ticket | Moves back to **In progress** |

## Common pitfalls

| Pitfall | What happens | What to do |
|---|---|---|
| Writing a team remark as **Reply** | The requester sees it | Check that the composer says **Internal note** before you send. |
| Replying "closed" on a resolved ticket | A public reply reopens it | Use an internal note, or resolve the ticket again. |
| Only internal notes, no reply | The response target runs on and the ticket turns **Overdue** | Send a public reply first. |
| Changing priority on an old ticket | The original response target stays | Expected: tickets keep their target snapshot. |

## FAQ

**What is the Closed status?**

**Closed** can appear as a label, but you set statuses from the ones your admin configured. The default finished status is **Resolved**.

**Does a response target count weekends?**

Yes. Targets use running time, not business hours.

**Can I see who resolved a ticket?**

Yes. The **Metadata** tab shows **Resolved** and **Resolved by**.

## Related pages

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

Find and assign tickets.

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

Bring in the Fuxam team.

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

Statuses, priorities and categories.

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

Back to the section overview.

