Mission Control and Cards
Every ticket SmartTech handles becomes a card. Mission control sorts every card by what the agent is doing, and shows each technician what is waiting for them.
Mission Control
Columns
| Column | What you find there |
|---|---|
| Problem | Failure, failed triage, exhausted budget, machine offline for more than 24 h, approved fix that did not complete, PSA ticket not found or failed PSA publication |
| Needs info | A question from the agent, for example "Which machine?" |
| Approval | Commands or fixes waiting for approval |
| Active | The agent is working on the card |
| Waiting | New card, queued card, machine offline, client's time window not open yet, or approved fix on its way |
| To validate | Report ready: a technician must validate it |
| Done | Cards validated, rejected or closed automatically |
Each card shows the next step to take: approve or refuse the commands, answer the agent's question, check a security finding, review the report… or "Nothing to do: the virtual technician is working".
Display
- My cards / All — Cards reserved by you or assigned to you in the PSA, or every card.
- Board view / List view — Columns, or a list sortable by client, machine, priority and age.
- By client — One lane per client, under the same columns.
- Indicators — To validate, To approve, Security and Cost today (tokens used).
Re-read PSA Tickets
The "Re-read PSA tickets" button asks the PSA again for the tickets of the watched boards. The read runs in the background: its result (tickets read, new cards, updates) appears once it finishes.
Card Lifecycle
| State | Description |
|---|---|
| New | Ticket received from the PSA |
| Triage | The agent classifies the ticket and identifies the target machine |
| Out of scope | Ticket outside SmartTech's reach (not shown on the board) |
| Diagnosing | The agent reads the machine through the connector |
| Waiting for machine | The machine is offline |
| Waiting for approval | Commands are waiting for approval |
| To review | Report ready for a technician |
| Done | Card validated |
| Archived | Card archived |
Triage Categories
Windows, Network, Printer, Disk, Performance, Office, Identity and accounts, Other.
Working a Card
Approving Fixes
The agent's report proposes fixes. A command that needs approval waits in the Approval column:
- Approve adds the command to the device profile, then runs it.
- Refuse: the command is neither published nor run.
- If an approved command does not complete, run it again from the fix ("Run") or take the card over by hand.
See Command rules to learn which commands run on their own, which need approval and which are refused.
Recheck
After the fixes, the recheck runs the agent again: it reads the machine with targeted reads and rewrites its report (what is fixed, what remains, the next step).
Validate
- Read the report and the proposed internal note.
- Rate the diagnosis quality: Right, Partial or Wrong.
- Validate: the internal note is published on each open ticket of the card, and the ticket moves to the status chosen for after validation. The ST-… reference is assigned at validation.
Observation: for a client in observation mode, nothing is published to the PSA. The text stays visible on the card.
Creating a SmartDoc Article
A resolution rated "Right" with an applied fix is a good candidate for the knowledge base. SmartTech prefills a SmartDoc article draft; you review it, then publish it in SmartDoc. Emails and the names of contacts and machine users are removed automatically.
Manual Cards
A card can be created without a PSA ticket: triage, diagnosis and review work like the others, but nothing is published to the PSA.
Follow-up
| Page | Content |
|---|---|
| Dashboard | Today's essentials, at a glance |
| History | Finished cards, newest first |
| Statistics | Tickets per day, out-of-scope share, diagnosis quality (Right, Partial, Wrong), cost per ticket and review delay |
| Value | What SmartTech delivers, all clients |
| Log | Who did what, and when, in SmartTech |