Summary, client and Q-Notice commands

These commands let you ask QuantumOps for a team status, a manager summary, ticket research or a client summary, flag a client as high risk, and manage Q-Notices without leaving Slack. A few are also available in Microsoft Teams. Agents, managers and administrators all use them.

Before you start:

• An administrator must add each command to your Slack app, one command at a time. See Setting up the Slack app.
• /summary, /research and /clientsummary take several minutes. They answer you at once, then post the result through the incoming webhook set under Slack Webhook URL on Configuration → Q-Director Config → Messaging. The result appears in the channel that webhook posts to.
• /morningsummary, /helpdesksummary and /qops need your Slack ID to be mapped to an agent. The others do not check the mapping. See Q-Director: Slack, Teams and agent mapping.
• /qnotice needs something different: your chat account must be linked to a QuantumOps account whose role may issue Q-Notices. See Who can use the Q-Notice commands.
• The commands that change your own status are on Agent status commands.

Show the team status

/morningsummary and /helpdesksummary post the Agent Status Update to the channel, where everyone can see it. It shows:

• the Primary SDM and Secondary SDM, and who is currently in control: the Primary SDM, the Secondary SDM, or Dispatch when neither is available;
• every active team member whose agent role is SDM Primary, SDM Secondary, Agent or Dispatch, grouped by agent role, with their status, the time they are due back from lunch or leave, and any lunch or leave they have scheduled; a team member who is not offline and has nothing scheduled shows "No breaks scheduled";
• a footer saying that times are shown in each agent's local time zone, and when the status was last updated.

Ask for a manager summary

/summary asks QuantumOps to summarise the open tickets for a manager. /summary -nopending leaves out pending tickets.

1. Type /summary or /summary -nopending.
2. Only you see the first reply, for example "Processing summary request for 42 open tickets. This will take 5-10 minutes." The -nopending version says it will take a few minutes.
3. When the summary is ready it is posted through the incoming webhook.

Mark a client as high risk

/monitor puts a client on the high-risk monitoring list, and /unmonitor takes it off. Give either the client's exact name or its HaloPSA client ID:

/monitor Contoso
/unmonitor 1042

The confirmation is posted in the channel for everyone, for example "Client 'Contoso' has been added to the high-risk monitoring list." If no client matches, the reply says "Client with identifier 'Contoso' not found." A client on the list shows a High Risk badge on its Client Dashboard.

Research a ticket

/research 123456 researches the ticket with that HaloPSA number. You first see "Researching ticket #: 123456. This may take a few minutes." The result lists similar past incidents and web search findings for the ticket, and is posted through the incoming webhook.

Summarise a client

/clientsummary <client name> <hours> summarises a client's tickets for the last number of hours:

/clientsummary Contoso 72

The client is everything before the last number, and must match a client name in QuantumOps exactly. You can give the HaloPSA client ID instead of the name. The summary is posted through the incoming webhook, and a PDF copy is uploaded to the channel where you typed the command. Uploading the PDF needs the files:write permission on the Slack app; see Setting up the Slack app.

If no client matches the name or ID, nothing more is posted after the first reply. Check the name on the client's dashboard and try again.

Create and manage Q-Notices from chat

A Q-Notice is operational context that QuantumOps shares with your team and, optionally, with its AI. For what the types, severities and scopes mean, see Q-Notices and Issuing a Q-Notice.

For a new notice:

• Type is beacon, intel, directive, sentinel or signal. The default is signal.
• Severity is info, advisory, warning, alert or critical. The default is info.
• Scope is ticket:1234, client:42 or user:7. With no scope the notice applies to the whole organisation.
• Flags are --llm (include the notice in AI processing), --expires 2h or --expires 1d (expire after hours or days), --permanent, and --broadcast (in Slack, also deliver the notice to the real-time dashboard and to Teams).

/qnotice beacon warning ticket:1234 "Customer reporting full outage" --expires 2h
/qnotice directive critical "Deployment freeze in effect" --permanent --llm
/qnotice intel advisory client:42 "Client on holiday this week"

A notice created this way is posted in the channel for everyone to see. Before anything runs, QuantumOps checks who you are; see the next section.

In Teams the form is @qops qnotice, with the same list, expire and create forms, and the same check. --llm, --expires and --permanent work the same way. --broadcast also sends the notice to the real-time dashboard and to Slack. It works only while the Qubit assistant is off for Teams, and only for people mapped to an agent. The list and any notice you create are posted in the conversation, so in a channel everyone there sees them.

Who can use the Q-Notice commands

Being in your Slack workspace or Teams tenant is not enough. For every form of the command (list, expire and create), QuantumOps looks up the QuantumOps account your chat account is linked to and checks its role. The command runs only for the roles that can open the Q-Notice Center: Administrator, Service Desk Manager, Dispatcher, Customer Success, Technician, Q-Notice Creator, Q-Notice Editor and Q-Notice Admin. See Q-Notices. You link by sending Qubit link, or an administrator's agent mapping links you on your first message to Qubit; both go through Qubit, so Qubit must be switched on for your workspace or tenant while you link, and the link stays if Qubit is switched off later. See Linking your Slack or Teams account.

When the command does not run, you see one of these replies. In Slack only you see it. In Teams it appears as a card headed Command Error.

QuantumOps reuses a "may" or "may not" answer for about five minutes, so a role change can take about that long to reach the command.

Show the command list

While Qubit is off in Slack, /qops shows the classic command list. Once an administrator turns Qubit on for Slack, /qops behaves exactly like /qubit. See Commands and private answers and Channel Assistant settings.

Command summary for Slack

In Teams, every answer is posted in the conversation where you typed the command.

Related pages

• Agent status commands: set your own status and change another agent's.
• Commands and private answers: the Qubit commands and /qubit.
• Q-Director: Slack, Teams and agent mapping: the mapping some of these commands need.
• Setting up the Slack app: how an administrator adds each command.