Ticket Detail Page
Review ticket details, replies, notes, activity, tasks, and linked records.
The ticket detail page is the workspace for one support or service request.
Open a Ticket
Open CRM > Tickets, then select a ticket row. The detail page shows the ticket header, replies, notes, activity, tasks, and details panel.
Open the detail page before replying to a customer, changing status, or handing the request to another teammate. The detail view is where scattered context becomes one decision-ready record.
If the ticket came from a form, mailbox, or integration, confirm the requester and linked contact before replying. Imported or forwarded messages can sometimes need cleanup before the customer sees a response.
Main Tabs
- Replies for customer-visible conversation.
- Notes for internal context.
- Activity for ticket history.
- Tasks for related work.
- Details for status, priority, assignment, due date, and linked records.
Use replies for anything the customer should read. Use notes for diagnosis, handoff context, internal decisions, or sensitive information that should not be sent to the requester.
Do not place passwords, private HRM details, payment credentials, or internal blame in customer-visible replies. Use internal notes for sensitive diagnosis and keep the customer reply focused on the fix or next step.
Edit Ticket Details
Use edit when the ticket subject, description, status, priority, due date, assignment, visibility, type, source, reference number, or linked records need to change.
Before saving, check whether the change affects ownership or urgency. Status, priority, assignee, due date, and linked records are the fields most likely to change how the team works the ticket.
If you change the status to waiting, blocked, or resolved, add enough context in a reply, note, or task so the next person understands why the ticket is no longer actively moving.
Linked Records
Review linked account, contact, project, invoice, and task details before responding. This gives the team the context needed to resolve the request.
If a ticket is linked to the wrong customer or invoice, fix the link before replying. A correct link helps future activity, reports, and handoffs make sense.
When a ticket affects billing, project delivery, or a document, open the linked record before making promises. The ticket may describe the issue, but the linked record proves the current state.
Resolve Or Handoff
Before marking a ticket resolved, confirm:
- The customer question or issue was answered.
- Any promised task, invoice change, file, or appointment was completed.
- Internal notes explain anything the next teammate would need.
- The status and priority match the final outcome.
For handoffs, assign the ticket to the next owner and add an internal note with the last action taken, blocker, and expected next step.
Follow-Up Discipline
Create a task when the ticket requires work outside the reply thread. Add an owner and due date so the request does not rely on someone remembering an internal note.
Use tasks for engineering fixes, finance corrections, file preparation, appointment follow-up, project work, or any action that should be tracked after the current support conversation.
Ticket Review Checklist
Before replying or resolving:
- confirm requester and linked contact
- check internal notes for sensitive context
- open linked records that affect the answer
- confirm owner, priority, and due date
- create tasks for work outside the thread
- add a final internal note when handing off