Skip to main content
Q-Missions

Q-Missions overview

What Q-Missions adds, who does what, how points and Zinc rewards fit together, and what an administrator switches on and sets up first.

Last updated 21 days ago

Q-Missions lets you hand your agents specific work and pay for it. A bounty is a one-off job with a number of slots: the first agents to claim one get a time limit to finish it. A quest is work given to named agents or to a team, and a mission groups quests toward one goal. The pay is points, which land in the same pool as CSAT points, or a physical product that QuantumOps orders for the agent through Zinc. For work tied to a HaloPSA ticket, QuantumOps watches Halo and pays when the work is done. For anything else a Mission Manager confirms it. Agents hear about new work as short cards on the page they are looking at, in the browser extension.

This page is the map: who does what, how the pieces fit and what to set up first. Each piece has its own page.

Before you start.

  • The Q-Missions module must be on. It starts on for every organization. An administrator can switch it off and on under Module Management; see What has to be switched on.
  • Work goes to HaloPSA agents. A quest can be given to any active agent in your HaloPSA roster, and a quest that HaloPSA checks still completes and adds the points to that agent's balance when nobody has linked a sign-in to them. A person whose sign-in is not linked to their HaloPSA agent cannot see their work, claim a bounty or mark work done, and the pages say so. An administrator links a login to an agent in Team Management.
  • Agents get the most from Q-Missions in the browser extension, version 0.21 or later. Agents can also claim, finish and be paid from the web pages.

The pieces

PieceWhat it doesWhere to read
BountiesA one-off job with a number of slots, a time limit for each claim and a reward. Agents claim a slot, finish the job and are paid.Bounties
Quests and missionsWork given to named agents or to a team, with a due date. A mission groups quests and can pay a completion reward.Quests and missions
Completion from HaloHow QuantumOps decides from HaloPSA that work is done, and when a manager confirms instead.How Halo completes bounties and quests
The hubThe Mission Manager's page: post, follow, confirm, extend and close.Missions, quests and bounties
My missionsThe agent's page: claim, finish or release, and follow quests and earnings.My missions
Points and the leaderboardOne pool of points from ratings, badges, quests, missions and bounties, and the ranking that counts them.Leaderboard
Zinc rewardsPhysical rewards ordered through your own Zinc wallet: set-up, products, orders and budget.Rewards admin, Setting up Zinc for rewards, Catalog, orders and budget
My RewardsWhere an agent spends points, chooses where a reward ships and follows an order.My Rewards
Missions tab and MomentsThe agent's panel for work, and the cards that announce new work, rewards and messages.Missions tab, Moments and alerts
Direct Q-NotifyA short message from a dispatcher to one agent, with an Acknowledge, Busy or written answer.Direct Q-Notify
Click-to-callA Call button in the extension that lists a person's numbers and dials one.Call a customer from the side panel, Dial prefixes for click-to-call

Who does what

WhoWhat they can do
An agentAnyone whose login is linked to a HaloPSA agent. Claim and finish bounties, release a claim, work quests, answer Q-Notify messages, earn points, redeem rewards and choose where they ship. No special role is needed.
Mission ManagerPost bounties, create quests and missions, extend or close them, and confirm work that Halo cannot check. Pays in points, or no reward.
Rewards AdminEverything a Mission Manager does, plus connecting Zinc, choosing the products, approving orders and setting the budget. Only a Rewards Admin can pay in a Zinc product.
AdministratorHolds both roles without being given them.
Administrator, Service Desk Manager, Dispatcher, Customer SuccessSend a direct Q-Notify from the dispatch board. A Mission Manager who uses the board can also post a bounty on a ticket from it.

The two roles are given in Team Management; Roles and access lists what each one opens. A Rewards Admin can open everything a Mission Manager can. A Mission Manager cannot open Rewards admin.

How points and rewards fit together

Every point an agent earns goes into one pool: the points from customer ratings and badges and the points from quests, missions and bounties are the same balance. The agent spends it on My Rewards, and the Leaderboard ranks the points earned, so spending never lowers anyone's place.

A mission, quest or bounty chooses its reward when it is created: nothing, a number of points, or a specific Zinc product from your catalog. A Zinc product is a physical item that Zinc buys from a shop such as Amazon or Walmart and ships to your office, or to the agent's home if the agent opts in and you allow it. You pay for it from your own Zinc wallet. QuantumOps never holds your money, and you decide the monthly budget and which orders need your approval.

Missions, quests, bounties and rewards belong to one QuantumOps instance and are not shared with other instances.

What has to be switched on

WhatWhereWhat happens without it
The Q-Missions moduleModule ManagementThe Missions and Rewards admin links disappear, their pages show a notice, and nobody can claim or be paid.
A linked HaloPSA agent for each agentTeam ManagementThe person cannot see their work, claim a bounty or mark work done. A quest that HaloPSA checks still completes and pays their balance.
The extension, version 0.21 or laterThe browser extensionWork still shows on the web pages. Cards, the Missions tab, Q-Notify, the Call button and the bounty menu need the extension.
Missions turned on for the extension on your instanceWhat each part of the extension needsThe Missions tab is missing from the extension; see Troubleshooting the extension.
The dispatch boardThe dispatch board at a glanceA dispatcher cannot send a Q-Notify, and the Q-Notify section of the Missions tab is missing. Direct Q-Notify has no switch of its own.
CallsCall a customer from the side panelThe Call button is missing. It follows the Calls switch, but not the Call tab's roles.

Set it up

  1. Open the Q-Missions card in Module Management and check that the module is on.
  2. In Team Management, give the Missions role to the people who will post work and the Rewards role to the people who will run Zinc rewards. The roles apply at each person's next sign-in; see Inviting people, roles and agent links.
  3. Check that each agent's login is linked to their HaloPSA agent. Team Management shows the link state on every row.
  4. Roll out extension version 0.21 or later. Rolling out the extension covers a managed rollout, and Moments and alerts covers the two optional alert switches each person can turn on.
  5. If you want physical rewards, follow Setting up Zinc for rewards. A Zinc product can be attached to a mission, quest or bounty once it is in the catalog, but no order can be placed until a key is saved, so connect Zinc before you offer one.
  6. If your staff call customers from the extension, set the dial prefixes.
  7. Post a first bounty, or a quest for one agent, and watch it arrive on the agent's screen. Missions, quests and bounties walks through the hub.

Where agents find their work

  • On the web: Missions in the left menu opens My missions for an agent and the hub for a Mission Manager. Leaderboard and My Rewards sit next to it when the CSAT & Surveys module is on.
  • In the extension: the Missions tab in the More menu, with a badge for what is waiting.
  • On the screen: Moments, the cards that drop in at the top of a HaloPSA or QuantumOps page. A card can also be a desktop alert, and with the "Show alerts on every site" setting it can appear on any https page. See Moments and alerts.
  • In chat: a bounty announcement can also reach an agent as one Slack or Teams message when the extension has been quiet for ten minutes. Bounties explains the rule.

Good to know

  • The person who claims, finishes or releases is always the signed-in agent. A form or a link can never name someone else.
  • A bounty cannot be edited after it is posted. Post it again with the changes and cancel the old one.
  • A payout that fails does not undo the completion. QuantumOps keeps trying to pay.
  • Zinc orders cost real money, so the monthly budget and the approval rules are the controls to set first. A test key spends nothing.

Was this helpful?

Still need help? Ask the team