Ticket Detail & Management
The comprehensive ticket management workspace where support agents handle the full lifecycle of a support request — from initial response through resolution. Includes real-time messaging, SLA tracking, file attachments, ticket linking, watcher management, internal notes, task creation, and customer feedback.
The Complete Ticket Workspace
The Ticket Detail page is where the actual support work happens. It uses a responsive three-column layout: the left panel (2/3 width) contains the conversation timeline with real-time messaging, while the right sidebar (1/3 width) contains all metadata, assignment controls, and supplementary cards. The sticky header shows the ticket number, live title, current status/priority badges, and a save button.
Page Layout
| Section | Location | Contents |
|---|---|---|
| Header | Top (sticky) | Back button, ticket number (#), live title, status badge, priority badge, Save button |
| Timeline | Left (2/3) | Message thread, activity log, real-time conversation |
| Details Card | Right sidebar | Title, Description, Priority, Status, Category fields |
| People Card | Right sidebar | Customer selector, Agent assignment, Tags |
| Tasks Card | Right sidebar | Linked sub-tasks for this ticket |
| Watchers Card | Right sidebar | Users monitoring this ticket for updates |
| Links Card | Right sidebar | Related, blocking, parent/child ticket relationships |
| SLA Card | Right sidebar | First response and resolution SLA timers with visual status |
| Notes | Right sidebar | Internal notes about the customer (visible only to agents) |
| Feedback Card | Right sidebar | Customer satisfaction rating and feedback text |
| Files | Right sidebar | File browser for attachments with upload, browse, and delete |
💬 Real-Time Conversation Timeline
The left panel contains the complete message history between agents and the customer. Support agents can compose responses, add internal notes (visible only to team members), and view the full activity log including status changes, assignment modifications, and system events. Messages support rich text formatting and file attachments inline.
📋 Editable Ticket Details
The Details card contains all core fields in an editable form: Title, Description (textarea), Priority (dropdown with 5 levels), Status (dropdown with 8 states — only visible in edit mode), and Category (dropdown with 8 options). All changes are saved when clicking the header Save button.
⏱️ Dual SLA Timer
The SLA card displays two separate countdown timers: First Response SLA — tracking time until the agent's first reply, and Resolution SLA — tracking time until the ticket is resolved. Each timer shows a color-coded status indicator: Blue (on track, >24h remaining), Amber (warning, <24h remaining), Red (breached, deadline exceeded), or Green (completed on time). Exact due dates and completion timestamps are displayed beneath.
🔗 Ticket Linking System
Connect tickets together using relationship types: Related (informational link), Blocks / Blocked By (dependency relationship), Parent / Child (hierarchical breakdown), and Duplicate (same issue reported multiple times). Links are bidirectional — creating a "Blocks" link on Ticket A automatically creates a "Blocked By" link on Ticket B.
👁️ Watchers
Add team members as watchers who receive notifications for all updates to this ticket without being the assigned agent. Useful for managers monitoring critical issues, or cross-team stakeholders who need visibility into specific customer problems.
📁 File Browser & Attachments
The integrated File Browser dialog provides full attachment management: upload new files directly, browse and attach existing files from the Media Library, view all ticket-level attachments (excluding message-level ones), and delete attachments when needed. The file count is displayed on the trigger button.
✅ Sub-Tasks
Create and track sub-tasks directly from the ticket detail page. This is essential when a ticket requires work from multiple teams — for example, a billing fix might require a database change (Engineering task) and a customer notification (Support task). Each sub-task links back to the parent ticket.
⭐ Customer Feedback
When a customer submits feedback after resolution, the Feedback Card displays their star rating (1–5) and any written comments. If the customer submitted feedback through multiple channels (e.g., widget and email), all feedback sources are displayed together for a complete satisfaction picture.
📝 Internal Notes
The Notes section allows agents to record internal observations about the customer that persist across tickets. These notes are only visible to support team members — never to the customer — and provide important context for future interactions.
Ticket Link Types
| Link Type | Reverse Link | Use Case |
|---|---|---|
| Related | Related | Two tickets about similar topics |
| Blocks | Blocked By | This ticket must be resolved before the linked ticket can proceed |
| Blocked By | Blocks | This ticket cannot proceed until the linked ticket is resolved |
| Parent | Child | This ticket is a high-level issue broken into smaller child tickets |
| Child | Parent | This ticket is a specific sub-task of a larger parent issue |
| Duplicate | Duplicate | Same issue reported by different customers or channels |
Step-by-Step: Resolving a Critical Ticket
- Open the ticket from the dashboard or via direct URL
/admin/tickets/{id}. - Review the customer's initial message and any subsequent conversation.
- Set Status to "In Progress" in the Details card to start the SLA clock acknowledgment.
- Compose Response in the timeline — ask for clarification or provide an initial solution.
- Attach Evidence: If needed, upload screenshots or logs via the File Browser.
- Create Sub-Tasks: If the fix requires engineering work, create a sub-task in the Tasks card and assign it.
- Link Related Tickets: If you discover other customers reported the same issue, link them as "Duplicate".
- Add Watchers: Add the customer success manager as a watcher for visibility.
- Resolve: Once the issue is fixed, write a final response explaining the resolution, and set Status to "Resolved".
- Save: Click the Save button in the header. The SLA card updates to show green checkmarks for completed timers.
Enterprise Use Case: Multi-Team Critical Incident Resolution
A SaaS platform's payment processing goes down across all regions. The first ticket (#4521) arrives from a customer in Europe. The on-call support agent opens the ticket detail page, immediately sets the Priority to "Critical" and Category to "Technical". They add 3 watchers: the VP of Engineering, the CTO, and the Customer Success Director. They create two sub-tasks: "Investigate payment gateway timeout" (assigned to Backend Engineering) and "Prepare customer communication" (assigned to Marketing). As more tickets arrive (#4522, #4523, #4524), the agent opens each one and links them to #4521 as "Duplicate". The engineering team resolves the root cause in 45 minutes. The agent writes a comprehensive resolution message on #4521, marks it as "Resolved", and all linked duplicate tickets are automatically flagged for review. The SLA card shows green checkmarks — first response was under 5 minutes, resolution under the 1-hour SLA target. Two hours later, the customer submits a 5-star feedback rating with the comment: "Fastest resolution we've ever experienced."
Comments
Leave a comment