Chat with Qubit
Chat with Qubit is the assistant you open from any page of the QuantumOps web app to ask about tickets, clients and your documentation in plain words.
Written By Chris Scaminaci
Last updated About 1 hour ago
Chat with Qubit is the assistant you open from any page of the QuantumOps web app. Everyone who signs in can ask it, in plain words, about tickets, clients, anything in your PSA and your documentation; Qubit looks things up and asks for your approval before it changes anything.
Before you start: Sign in with your QuantumOps account. No module or role is needed. If your session has no account identity, the chat still answers but shows the notice Chat works, but sign in with your QuantumOps account to use tools and approvals, and to keep your conversations. Without an account identity the chat cannot connect MCP sources, approve actions, attach files or keep a conversation list. The chat windows that open inside HaloPSA are a separate, smaller experience; see Chat with Qubit from a HaloPSA dashboard.
Ask Qubit a question
- Select Chat with Qubit, the button at the bottom right of the page. The chat opens over the page.
- Select one of the suggested prompts under Ask Qubit, or type your own question in the message box (Ask Qubit…). A new conversation about no particular record offers What tickets need attention today?, Show my open tickets and Which clients have SLA breaches?. A conversation you started in the browser extension about a ticket shows the ticket number beside the tools button when you reopen it here.
- Press Enter to send. Press Shift+Enter to start a new line.
- Read the answer as it arrives. While Qubit works, the box shows Qubit is working… and the send button turns into Stop.
Select Stop to end an answer early. The answer keeps what has arrived and ends with a red card that reads Stopped. and The run was stopped. The card only confirms that you stopped the answer; nothing went wrong.
Some screens, such as Agent Runners, open the chat as a new conversation with an instruction already typed in the box. Nothing is sent until you press Send.
Choose the model and the tools
The bar under the header holds the choices for the conversation:
- The model list starts with Tenant default model, which is the model your administrators chose for the Chat & Conversations operation (see Override the model for one operation), followed by the other models QuantumOps offers. Your choice applies to this conversation only.
- The tools button, labelled All sources until you narrow it, controls what Qubit may use for the next answer. See What Qubit can use: tools and sources.
- Standing approvals, the shield button, lists the tools you have approved for a conversation or for good. See Approving Qubit's actions.
The model list and the tools button are off while an answer is running.
Resize the chat or use full screen
- Drag the top-left corner of the chat (Drag to resize) to make it larger or smaller.
- Select Full screen to fill the page, and Exit full screen to go back.
- Select Close to put the chat away. The conversation is kept.
QuantumOps remembers the size, whether the chat was open, and your last conversation in this browser.
Read an answer
An answer can contain more than text:
- Reasoning is a folded section that shows how Qubit worked the question out, when it has reasoning to show. Select it to read it.
- Each look-up Qubit makes appears as a row with the tool's name and its state: running, done or failed. Select the row to see its Arguments and Result.
- Where Qubit used your documentation, the text carries numbered markers such as [1] and the sources are listed under the answer. See What Qubit can use: tools and sources.
- A chart or a file Qubit made appears in the answer. See Files and charts in chat.
- An Approval needed card appears when Qubit wants to do something that changes data. See Approving Qubit's actions.
- Under a finished answer, Copy answer copies the text. A small line beside it gives the model that answered, the tokens read and written (for example 1,200→340 tok) and how long the answer took.
When something goes wrong, a red card shows the message, a short code in brackets and, for the common cases, a hint:
- An MCP source needs your authorisation. Connect it under Settings → MCP Sources, then retry. The card carries an Open MCP Sources link.
- This conversation no longer exists on the server. Start a new thread. Select New conversation and ask again.
Leave and come back
An answer keeps running if you close the chat, reload the page or lose your connection. A chain of look-ups can take minutes, and nothing is lost. Open the chat again, or open the conversation from the list, and it picks up where the answer is and shows the rest as it arrives. While it finishes, the message box is off.
Work with your conversations
- Select Conversations, the history button at the left of the header. The button is missing when you are not signed in and off while an answer is running.
- Find the conversation. Your conversations are listed newest first, up to the 60 most recent, in two groups:
- In the portal holds the conversations you started in the web app.
- From your other surfaces holds your conversations from the browser extension, Slack and Teams. Each row is labelled Browser extension, Slack or Teams.
- Select a row to open the conversation. A conversation that has no title yet shows as Untitled conversation; QuantumOps titles it from your first message.
- Continue it. A conversation you started in the browser extension can be continued here. A Slack or Teams conversation opens read-only: the box shows Read-only here and the notice This conversation lives in Slack — continue it there, or start a new thread here. (or Teams).
- To remove a conversation from your list, select Delete conversation. You cannot reopen it afterwards, and your organisation's usage history still counts it.
- To start over, select New conversation. QuantumOps creates the conversation when you send the first message or attach the first file, not before.
When the list is empty it says No conversations yet. Ask Qubit something to start one.
Who can read your conversations
Each person sees only their own conversations. Administrators can read conversation transcripts in Chat analytics, so write in the chat as you would in any work record.
In this section
Using chat
- What Qubit can use: tools and sources: what Qubit can look up and how to narrow it.
- Approving Qubit's actions: the approval card and standing approvals.
- Files and charts in chat: attaching files and asking for charts and documents.
- Chat with Qubit from a HaloPSA dashboard: the smaller chat windows that open inside HaloPSA.
For administrators
- MCP sources: connect StackJack, HaloPSA's native MCP or any other tool server.
- StackJack: set up StackJack so each person signs in with their own account.
- HaloPSA's native MCP source: add HaloPSA's own MCP endpoint, with one sign-in per technician.
- Tool Governance: decide which tools are allowed, need approval or are denied.
- Agent Runners: governed AI jobs that run on a schedule, on an event or on demand.
- Connecting external AI clients over MCP: let an AI client such as Claude Desktop read your tickets, documentation and support memory.
- Support memory: what QuantumOps remembers from your tickets.
- The Memory Graph screen: search, correct and remove what support memory holds.
Related pages
- Chat tab: the same assistant in the browser extension's side panel.
- Qubit in Slack and Teams: asking Qubit from those apps.
- Chat analytics: how Administrators see usage and read transcripts.
Was this helpful?
Still need help? Ask the team