ZenTop Triage

by ZenTop Consulting

Interactive product demo

Walk your Monday
morning queue.
Before you buy.

AI ticket triage and dispatch for ConnectWise and Halo MSPs. Sign in once and run the whole loop against a fictional MSP's messy board — triage, assign, escalate, and ask the dashboard anything.

Read-only identity claim. No forms. We never touch your tenant.

What you'll actually do ~4 minutes

LIVE AI

One quick thing before we start

This is a guided walkthrough on a fictional MSP — Reboot Pending Technologies, with made-up clients, tickets, and techs. Nothing here touches a real system, and nothing you click is stored.

It's fully on-rails — just follow the prompts and click through. When you're ready to see it run against your own ConnectWise or Halo data, that's the conversation at the end.

Setup

Connect your boards

Point Triage at Reboot Pending Technologies. This takes about ten minutes in the real thing.

ConnectWise Manage

PSA connection

Connected

Site

na.myconnectwise.net

Company ID

{{ s1Msp.companyId }}

API Member

{{ s1Msp.member }}

Private Key

••••••••••••••••

Boards to monitor

Toggle the boards Triage should watch. Type / subtype / item trees came straight from your PSA.

{{ b.name }}{{ b.tickets }} open

Priority mapping

How ConnectWise priorities line up with Triage severity.

Triage

Create a ticket

Follow the same intake, AI analysis, and classification review used in ZenOps.

This is the manual intake path. In production, Triage also watches designated boards and works new tickets from email, client portal, RMM, and PSA connectors automatically. This flow stays available for tickets that start with a technician, such as a client calling in.

Step {{ s2StepNumber }} of 3

Ticket Information

Select the customer, contact, and describe the issue

Select Customer

No customers found

✓ {{ s2SelectedClient }}

Select Contact

Select a customer first

No contacts found

✓ {{ s2SelectedContact }}

Describe the Issue

{{ s2InputCount }} characters · Minimum 10 characters required

✓ Ready to analyze

Relevant Knowledge Base

Searching live documentation and configuration items…

{{ kb.badge }} {{ kb.title }} {{ kb.score }}%

Internal Ticket

Raised by Alex Rivera — Client may not need to be contacted directly.

AI Analysis

Analyzing your issue and generating ticket classification...

Reasoning output

{{ s2ReasoningText }}▋

AI Classification Results

Review the AI-generated ticket classification before continuing

Analysis Complete

Confidence: {{ s2Result.confidencePct }}%

Ticket Title

Summary

Type

Subtype

Item

Priority

Destination Board

{{ s2Result.boardReasoning }} {{ s2Result.confidencePct }}% confident

Follow-up Questions

Answer these questions to help refine the ticket classification

{{ q.question }} ({{ q.context }})

Dispatch

Assign it

Triage suggests the best-fit tech. Confirm it, or click anyone else to override.

#4471ClickFirst InsuranceP1 · VIP

Credential phishing — finance director entered M365 credentials on spoofed page

Suggested: {{ s3Suggested.name }}

SUGGESTED

Load{{ t.loadLabel }}

Pro{{ s3ProDispatch }}

Assigned to {{ s3AssignedName }}

What the tech actually receives

PRO

That closes the triage loop for one ticket. The second Priya opens #4471, Pro has already assembled her first note — classification, past fixes, the runbook, asset context, and next steps. On Lite she opens a blank ticket.

#4471ClickFirst InsuranceVIPAssigned · Priya Nadella

ZenTop Triage · AI

Initial note · just now

Ready

Next up: the board — where the rest of the day's work lives.

Ticket Queue

{{ s4Count }} tickets need a human decision

Refresh

Tickets are triaged automatically on arrival. What is left is the queue of pending interventions — these are all in Customer Responded.

Filter by Status: Needs Attention ▾

#{{ t.id }} {{ t.client }}

Assigned

Budget

Queue Age

Updated {{ t.lastUpdate }} ago

Priority

Interventions cleared — inbox zero on the human calls.

Ticket Notes • {{ s4Modal.id }}

Total Time Worked: {{ s4Modal.totalWorked }} Budget: {{ s4Modal.budget }}

{{ n.author }}— {{ n.when }}{{ n.tag }}

Assign Ticket • {{ s4Modal.id }}

Send it back to the tech who worked it, in their next open slot.

{{ s4Modal.reassignSlot }} (Worked it before)

Service Board

{{ s5Count }} tickets

One is aging badly — red SLA timer, VIP flag, escalation suggested. Find it and escalate.

Filter by Status: All ▾

#{{ t.id }} {{ t.client }}

VIP

Assigned

Scheduled

Budget

Queue Age

{{ t.slaLabel }} · Escalation suggested — 3h 30m tracked over 2h budget, 4 touches

Notes

Escalated

Escalate

Resolve

Pro{{ s5ProCopy.touches.escalate }}

Escalate Ticket • 4471

Confirm the escalation contact and select the next eligible calendar slot.

Escalation reason

Escalation contact

Scheduled Duration

Dashboard

Overview of your triage and dispatch operations

Search Knowledge Base

Technical how-to search across your runbooks, resolved tickets, and config items — the same engine that powers triage.

All Clients ▾

Tickets KB Both

Try an example

Results ({{ s6ResultCount }})

{{ r.badgeLabel }}{{ r.heading }}{{ r.score }}% match

Summary

Demo complete

You just ran a full morning
in about four minutes.

On a normal Monday, that queue is a couple of hours of reading, sorting, and chasing. Here's what you got through:

Where the hours went

Every tech who picks up a Pro-triaged ticket starts with the enriched first note you saw after triage — past fixes, the runbook, and asset context already assembled. That is the difference between a blank ticket and a running start, on every ticket, all day.

~12h

a week of triage, sorting, and KB-hunting handed back to a five-tech desk.

average time from ticket arrival to fully classified and routed — no clicks.

SLA breach caught and escalated to a senior before it aged out.

{{ cProCopy.plan }} · {{ cProCopy.price }}{{ cProCopy.period }}

ZenTop Triage

Walk your Monday
morning queue.
Before you buy.

One quick thing before we start

Connect your boards

Create a ticket

Ticket Information

AI Analysis

AI Classification Results

Follow-up Questions

Assign it

What the tech actually receives

Ticket Queue

{{ t.summary }}

Ticket Notes • {{ s4Modal.id }}

Assign Ticket • {{ s4Modal.id }}

Service Board

{{ t.summary }}

Escalate Ticket • 4471

Dashboard

Search Knowledge Base

You just ran a full morning
in about four minutes.

Where the hours went

{{ cProCopy.closing.heading }}

Walk your Mondaymorning queue.Before you buy.

One quick thing before we start

Connect your boards

Create a ticket

Ticket Information

AI Analysis

AI Classification Results

Follow-up Questions

Assign it

What the tech actually receives

Ticket Queue

{{ t.summary }}

Ticket Notes • {{ s4Modal.id }}

Assign Ticket • {{ s4Modal.id }}

Service Board

{{ t.summary }}

Escalate Ticket • 4471

Dashboard

Search Knowledge Base

You just ran a full morningin about four minutes.

Where the hours went

{{ cProCopy.closing.heading }}

Walk your Monday
morning queue.
Before you buy.

You just ran a full morning
in about four minutes.