Enterprise Helpdesk Support Tickets, 4-Mode SLA Triage Command Center, Tier-2 Escalations, Cross-ERP Dispatches & Governance Studio
A complete guide to managing multi-channel customer support requests, enforcing First-Response and Resolution Service Level Agreements (SLAs), escalating critical incidents to Tier 2, posting internal team whisper notes and dynamic macros, and dispatching Field Service Job Cards or Engineering Tasks directly from a ticket.
In This Article
1. Service Desk & SLA 101: First Response, Resolution Clocks & Cross-ERP Links
In most businesses, customer support lives in a disconnected email inbox or external helpdesk tool where support agents cannot see if a customer's account is overdue, whether a faulty serial number is still under warranty, or whether a field technician has already been dispatched.
Keystone X embeds an **Enterprise Helpdesk & SLA Engine** (`TKT-XXXXX`) directly inside your ERP so every support incident is connected to your **Customer Directory**, **Client Self-Service Portal**, **360° Serial & Warranty Tracker**, **Field Service Job Cards**, **Engineering Tasks**, and **Tax Invoices**:
Dual SLA Clocks: First Response vs. Final Resolution
Every ticket is governed by two independent Service Level Agreement (SLA) timers based on its **Category** and **Priority** (`Low`, `Medium`, `High`, `Urgent`):
• First Response SLA (`sla_response_due_at`): The maximum time allowed before an agent posts the first public reply to the customer. Posting a public reply automatically stamps `first_responded_at`.
• Resolution SLA (`sla_resolve_due_at`): The target deadline by which the incident must be marked `Resolved` or `Closed`. If the deadline passes while open, the ticket is flagged as **SLA Breached** on the live SLA Radar!
Public Customer Replies vs. Internal Whisper Notes
Support threads contain two distinct communication layers:
• Public Customer Replies: Emailed immediately to the customer (and visible inside their **Client Self-Service Portal** under `/portal`).
• Internal Team Whisper Notes (`is_internal = 1`): Highlighted in amber with a hidden-eye badge (`INTERNAL TEAM NOTE`). These technical notes, diagnostic logs, and escalation handoffs are strictly visible to internal staff and **never** shown to the customer.
SLA Contract Covered vs. Billable Support Cases
Each ticket can be marked as **SLA Covered (Non-Billable)** or **Billable Support (`is_billable = 1`)** with a configurable `hourly_rate`. Every time an agent posts a reply or whisper note, they can log the exact minutes spent (`time_logged_minutes`), which automatically accumulates total hours and calculates the live billable rand value (`R`) on the ticket!
Closed-Loop Field Job Card & Task Automation
If a support ticket cannot be solved remotely over the phone, 1 click on **Dispatch Job Card** converts the ticket into a Field Service Job Card (`JC-XXXX`). Later, when the field technician completes the on-site repair and the Job Card is converted to a Tax Invoice, Keystone X **automatically closes the originating Support Ticket** for you!
2. The 4-Mode Helpdesk & SLA Command Center (/ticket)
Navigate to **Support → Tickets** (`/ticket`) in the left sidebar to launch the **Helpdesk & Incident Desk Command Center**.
tickets-command-center-4modes.pngHow to capture this screenshot:
- Navigate to
/ticket(Queue View). - Ensure at least 3–4 sample tickets exist across different priorities (Urgent, High, Medium) with live SLA countdown badges and linked Job Card/Project pills.
- Capture the full screen showing the 4-Mode View Switcher (Queue, Triage Board, SLA Radar, Workload), the 5 Executive KPI Cards, the Multi-Dimension Filter Bar, and the Active Support Ticket Queue table.
The 5 Executive Helpdesk KPI Cards
| KPI Card Title | Primary Metric & Sub-Counters | What It Measures |
|---|---|---|
| 1. Active Queue | Open Ticket Count + New & In Progress |
Total unresolved tickets currently open in the helpdesk queue, broken down by newly arrived (`New`) vs. actively worked (`In Progress`). |
| 2. SLA Health & Radar | SLA Compliance % + Breached & Due <4h |
Percentage of tickets meeting their target resolution SLA window, with red alerts for currently `Breached` tickets and amber warnings for tickets expiring within the next 4 hours (`Due <4h`). |
| 3. Urgent & Escalations | High/Urgent Count + Tier-2 Escalated & Unassigned |
Counts open high-severity incidents, tickets escalated to Tier-2 Engineering (`is_escalated = 1`), and tickets waiting for an agent (`Unassigned`). |
| 4. Resolution & Effort | Resolved Count + Logged hrs & Awaiting Client |
Total tickets resolved or closed, cumulative support hours logged across all ticket replies, and tickets paused in `Awaiting Customer` stage. |
| 5. ERP Dispatches | Job Cards Dispatched + Projects & Billable (R) |
Counts tickets linked to Field Service Job Cards (`JC-XXXX`) and Projects (`PRJ-XXXX`), plus the total billable support value (`R`) accrued on billable tickets. |
Multi-Dimension Filter Bar
Directly below the KPI strip, you can filter all 4 view modes simultaneously by **Keyword / Ticket # / Serial #**, **Stage**, **Priority** (`Urgent`, `High`, `Medium`, `Low`), **Support Category**, and **Assigned Agent** (including a special `— Unassigned Queue —` filter to spot orphaned tickets immediately).
3. Deep-Dive: Queue, Triage Board, SLA Radar & Agent Workload Matrix
Use the **4-Mode View Switcher** in the top-right header to switch perspectives instantly:
- Ticket & SLA: Clickable `#TKT-XXXXX` link plus a live color-coded **SLA Countdown Pill**:
- SLA: Xh left (More than 4 hours remaining)
- Due in X.Xh (4 hours or less remaining)
- SLA Breached (-X.Xh) (Past target resolution deadline)
- SLA Completed (Ticket is Resolved or Closed)
- Customer & Contact: Displays the Customer account name and the specific individual stakeholder (`person_name`) who logged the issue.
- Subject & Category: Ticket summary, Category label, and a reply count badge (` X`).
- Linked ERP Entities: One-click pills jumping directly to the linked **Job Card (`JC#`)**, **Project (`PRJ#`)**, or **Engineering Task (`Task #`)**.
- Assigned Agent: Agent initials avatar and full name, or an amber `Unassigned` badge.
- Priority & Stage Badges: Visual pills for severity and current pipeline stage.
- Actions: **Open Ticket Cockpit (``)** and **Download Official Service Report PDF (``)**.
- Shows side-by-side status badges for **First Response SLA** (`Responded DD MMM HH:MM` vs. `Awaiting First Reply`) and **Resolution SLA Target** (`Due DD MMM HH:MM` vs. red `BREACHED`).
- Includes a 1-click ** Escalate Tier 2** button (`ticket/escalate/{id}`) right in the table row to immediately promote at-risk tickets to Tier-2 Engineering!
- Left Panel — Support Agent & Technician Workload Matrix: Lists every staff member with live counters for their **Active Queue**, **High / Urgent Load**, **Resolved / Closed Count**, and **Total Support Hours Logged (`hrs`)**.
- Right Panel — Active SLA Priority Matrix: Reference card showing your organization's First Response and Resolution hour targets per priority level (`Urgent`, `High`, `Medium`, `Low`) and whether `Auto-Escalate` is active.
4. Logging a Support Ticket (#addTicketModal)
Clicking **Log Support Ticket** in the top-right header opens the `#addTicketModal` dialog (`ticket/add`). Here is how its smart fields work together:
| Modal Field | Smart Behavior & Validation |
|---|---|
Ticket Number (ticket_number) |
Auto-generated sequential number (e.g., `TKT-10001`) based on your Studio prefix and sequence counter. |
| Support Category & Routing Department | Selecting a **Support Category** (`#modalCategorySelect`) automatically updates the **Routing Department** (`#modalDeptInput`) and **SLA Priority** (`#modalPrioritySelect`) using that category's routing rules! |
| Customer / Account & Contact Person | Selecting a **Customer** (`#ticket_customer_id`) triggers an instant AJAX lookup (`ticket/getContactsByCustomer/{id}`) that populates the **Reported By / Contact Person** dropdown (`#ticket_person_id`) with the customer's main contact plus all linked stakeholders from the **Contacts & People Directory**! |
| Subject & SLA Priority | Required incident headline (`subject`) and severity (`Low`, `Medium`, `High`, `Urgent`). Creating an `Urgent` ticket immediately fires a high-priority **Urgent Ticket Escalation** notification to all Administrators. |
| Assign To Agent, Linked Project & Asset Serial # | Assign to a specific agent (or leave on `Auto-Assign`), optionally link to an active **Project** (`project_id`), and record the faulty equipment's **Asset / Serial Number** (`asset_serial`). |
| Detailed Description, Attachments & Billable Toggle | Full symptom description, multi-file upload (`attachments[]`), and the **Billable Support Case** switch (`is_billable`). Upon submission, if `ticket_auto_email_customer` is enabled, Keystone X automatically emails a branded ticket confirmation to the customer. |
5. The Incident Resolution Cockpit (/ticket/viewTicket/{id})
Clicking any ticket number opens the **Executive Support Ticket & Incident Resolution Cockpit** (`/ticket/viewTicket/{id}`).
tickets-incident-resolution-cockpit.pngHow to capture this screenshot:
- Open an active ticket at
/ticket/viewTicket/{id}that has at least one public reply and one amber INTERNAL TEAM NOTE. - Capture the Cockpit Header (showing Escalate Tier 2, Dispatch Job Card, Spawn Task, and Service Report PDF buttons), the Interactive Lifecycle Stage Stepper, the 4 SLA & Effort Telemetry Cards, the Conversation Stream, and the right-hand Cross-ERP Links sidebar.
Cockpit Layout & Interactive Controls
- Interactive Lifecycle Stage Stepper Bar: Directly beneath the header, every configured ticket stage (`New`, `Triaged / Assigned`, `In Progress`, `Awaiting Customer`, `Escalated / Tier 2`, `Resolved`, `Closed`) is rendered as a 1-click button (`ticket/updateStatus/{id}`). Clicking `Resolved` or `Closed` stamps `resolved_at`, stops the SLA clock, and notifies Administrators.
- 4-Card SLA & Effort Telemetry Strip: Displays real-time status for **1. First Response SLA** (`Responded` timestamp vs. `Pending Reply`), **2. Resolution SLA Target** (`Resolved`, `Target Window`, or red `SLA Breached`), **3. Support Time Logged** (`Xh Ym` across `N` thread entries), and **4. Billing & Commercial Status** (`R X,XXX.XX Billable @ R650/hr` vs. `SLA Covered`).
- Right Sidebar — Agent Assignment & Ownership (`ticket/updateAssignment/{id}`): Reassign the ticket to any support agent or technician. Reassigning automatically sends both an email and an in-app notification (`Ticket Assigned to Me`) to the new owner.
- Right Sidebar — Cross-ERP Links, Classification & Billing Governance (`ticket/updateMetadata/{id}`): Update the ticket's **Category**, **Priority**, **Department**, **Linked Project Workspace**, **Linked Field Job Card**, **Linked Tax Invoice**, **Asset / Equipment Serial #**, **Billable Support Toggle & Hourly Rate**, and **Root Cause & Resolution Summary** at any time.
6. Smart Reply Composer, Internal Whisper Notes & Dynamic Macros
At the bottom of the conversation thread sits the **Smart Reply, Macro & Time Logging Composer** (`ticket/addReply/{id}`):
| Composer Control | How It Works |
|---|---|
+ Insert Canned Response Macro (#cannedMacroPicker) |
Selecting any pre-built macro from the dropdown instantly populates the reply box, replacing dynamic placeholders ({customer_name}, {ticket_number}, and {agent_name}) with the actual customer, ticket, and logged-in agent names! Even better, if the macro has a configured **Target Stage** (e.g., `Awaiting Customer` or `Resolved`) or **Internal Whisper Default**, the composer automatically sets those controls for you. |
Log Support Time (Minutes) (time_logged_minutes) |
Enter the minutes spent on this interaction (e.g., `15`, `30`, `60`). These minutes are added to the ticket's cumulative `time_spent_minutes` and displayed as a badge (`+15m logged`) on the reply card. |
Transition Stage on Reply (reply_status) |
Optionally change the ticket's workflow stage in the same click as posting your reply (e.g., reply to the customer and simultaneously move the ticket to `Awaiting Customer`). If left on `Keep Current` and the ticket is `New`, posting a public reply automatically advances it to `In Progress`. |
Attach Files (attachments[]) |
Attach screenshots, diagnostic logs, or PDFs directly to the reply. |
Internal Team Whisper Note Switch (is_internal) |
• **Unchecked (Default):** Posts a **Public Reply**, emails the customer immediately, and displays the message in the Client Portal. • **Checked:** Posts an amber **Internal Team Whisper Note** (`is_internal = 1`) that is completely hidden from the customer and never emailed externally. |
7. Cross-ERP Bridges: Tier-2 Escalation, Job Card Dispatch & Task Spawning
In the top-right corner of the Ticket Cockpit, 4 action buttons connect the Service Desk to the rest of Keystone X:
- Escalate Tier 2 (`ticket/escalate/{id}`): Immediately promotes the ticket's stage to `Escalated / Tier 2`, elevates its priority to `Urgent`, sets `is_escalated = 1`, and records an automated system audit event in the conversation timeline.
- Dispatch Job Card (`ticket/convertToJobcard/{id}`): Pre-populates the **Field Service Job Card Dispatch Wizard** (`/jobcard/add`) with the ticket's Customer, Contact Person, Linked Project, Subject, and Fault Description, transitions the ticket to `In Progress`, and links the two records. When that Job Card is later completed and invoiced, Keystone X automatically closes the ticket!
- Spawn Task (`ticket/convertToTask/{id}`): Creates an **Engineering / Operational Task** (`TSK-XXXX`) in `/task` pre-filled with the ticket number, subject, description, assigned agent, priority, SLA resolution due date, and billable flag, and links `task_id` directly to the ticket header.
- Service Report PDF (`ticket/pdf/{id}`): Generates a branded, print-ready **Official Service & Incident Report PDF** (`ServiceTicket_TKT-XXXXX.pdf`) containing your company logo, ticket metadata, SLA timestamps, root cause resolution summary, and public correspondence history.
8. The 4-Tab Support Desk & SLA Customization Studio (/ticket/settings)
Administrators can click **Customize** (`/ticket/settings`) to configure the **4-Tab Support Desk & SLA Customization Studio**:
tickets-sla-customization-studio.pngHow to capture this screenshot:
- Navigate to
/ticket/settings. - Capture Tab 1 (1. Numbering & Automation) or Tab 3 (3. Categories & SLA Matrix) showing the 4 navigation pills and the configuration cards.
| Studio Tab | Configurable Settings, SLA Rules & Macros |
|---|---|
Tab 1: Numbering & Automation (#tab-general) |
|
Tab 2: Triage Pipeline Stages (#tab-stages) |
Add (`#addTicketStageModal`) or remove custom triage stages, configure badge colors and sort orders, and inspect which stages stamp SLA resolution (`Stamps SLA Resolution` vs. `Active SLA Clock`). |
Tab 3: Categories & SLA Matrix (#tab-categories) |
Create support categories (`#addCategoryModal` → `ticket/saveCategory`), defining each category's **Category Name**, **Routing Department**, **Default Priority**, **First Response SLA (Hours)**, and **Resolution SLA (Hours)**. |
Tab 4: Canned Response Macros (#tab-macros) |
Build reusable smart reply templates (`#addMacroModal` → `ticket/saveMacro`) with **Macro Title**, **Category**, **Target Stage on Insert**, **Response Template Body** (supporting `{customer_name}`, `{ticket_number}`, `{agent_name}`), and a **Default to Internal Whisper Note** toggle. |