Work on a ticket
Reply to the requester, write internal notes, and change a ticket's status, priority and assignee.
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.
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
Open the ticket. The composer at the bottom is set to Reply.
Write your answer. Add files if needed (up to 10 per message, 50 MB each).
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
In the composer, switch from Reply to Internal note. The hint reads "Private team note — not visible to the requester."
Write the note and click Send. You see Internal note saved.
How to change the status
Click the status menu in the header. Statuses are grouped into Not started, In progress and Finished.
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
Click … (Ticket actions) in the header.
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.