QBR settings: brand, workflow and HaloPSA items

The QBR settings control how every review looks, who approves it, how the client link and e-mails behave and what is created in HaloPSA from a recommendation; this page covers the Brand kit, Workflow and Halo items tabs.

Written By Chris Scaminaci

Last updated About 4 hours ago

The QBR settings decide how every review looks, where satisfaction scores come from, who approves a review, what reaches HaloPSA and how the numbers and the AI behave. They apply to all of your organisation's reviews. The page has six tabs and one Save settings button for all of them. This page covers three of the tabs: Brand kit, Workflow and Halo items. The other three, CSAT sources, Metrics and AI, are on QBR settings: CSAT sources, metrics and AI.

Before you start: the QBR Reporting module must be on for your organisation, and you must be an Administrator or a Service Desk Manager. Customer Success users can use QBR Studio but do not see Settings.

Open the settings and save your changes

Open Settings in QBR Studio (route /qbr/settings).
Pick a tab: Brand kit, CSAT sources, Workflow, Halo items, Metrics or AI.
Change what you need. An Unsaved changes badge appears next to the page title.
Select Save settings. The button stays disabled until something has changed. To throw your edits away, select Discard changes.

One save covers all six tabs, so you can edit several tabs and save once. If a value is not allowed, the page says why, switches to the tab that holds it and marks that tab with an exclamation mark. Nothing is saved until every tab is valid.

If e-mail is not set up for your instance or your organisation, the page shows the warning E-mail is not configured. In that case review requests, reminders, "draft ready" e-mails, client-decision e-mails and client pre-reads are not sent, whichever Client e-mail option you choose. Copy the client link and send it yourself.

Set the brand kit

The brand kit is the look of every deck, PDF, PowerPoint and client page. It applies everywhere unless a review or a template carries its own theme (see QBR templates). A live Preview beside the form shows a sample cover and a sample KPI slide as you change things, drawn the same way a real review is.

Open the Brand kit tab.
Under Colours, set Primary and Accent. Use the colour picker or type a hex colour such as #0B6BCB. Primary is used for titles, the first chart series and accents; Accent for the second series and highlights.
Optionally build a Chart palette: select Add colour to add up to eight chart colours. Leave it empty and charts use shades of the primary and accent colours.
Under Slides, choose the Background, Light or Dark, and the Font: Inter / Segoe, Serif (Georgia), System UI or Monospace. These are web-safe, so the PDF matches the screen.
Under Identity, enter the Company name and, optionally, a Footer. The company name is shown on the cover and is also the sender name on client e-mails.
Under Logo, select Upload an image, or give a link in Or a link to it.
Select Save settings.

The logo can be a PNG, JPG, SVG or WebP file of up to 500 KB. SVG and WebP files are converted to PNG so that every export, PowerPoint included, shows the same logo. An uploaded logo is stored with your settings, so the PDF never has to fetch it. A link must start with https://, and it is switched off while an uploaded image is in place. Select Remove logo to clear either one.

Set up review, approval and defaults

The Workflow tab sets the gate between a draft and your client, and the defaults that new reviews and schedules start with. Each section below is a card on the tab.

Review and approval

Setting	What it does	Default
"A report must be approved before it can be published"	Nobody can publish a review until it has been approved.	On
Owners may approve their own report	When off and a report has reviewers, one of the reviewers has to approve it. Administrators can always approve.	On
E-mail the owner when a draft is ready	Sends the owner (and anyone listed in Also tell on a schedule) an e-mail when a generated draft is ready.	On

Defaults for new reports and schedules

Setting	What it does	Default
Default owner e-mail and Default owner name	New reports and schedules start with this owner. Empty means whoever creates them. Suggestions come from your HaloPSA agents.	Empty
Default reviewers	Reviewers added to new reports and schedules.	None
Default template	The template new reviews use. It is the same choice as Make default on the Templates page.	The default template
Draft lead time	How many days before the meeting a scheduled draft is generated, from 0 to 90.	10 days
Reminder	How many days before the meeting to remind an owner whose report is not approved, from 0 to 30. Enter 0 for never.	2 days
"Also remind owners of reports created by hand, not only scheduled ones"	A report with a meeting date that is still not approved gets the reminder too, using the days above.	On

If your organisation has no template yet, the Default template list is empty and says that the first report creates the Strategic QBR template and makes it the default.

Client link and decisions

Setting	What it does	Default
Link expires after	How many days a published client link works, from 1 to 365. Owners can extend a link later.	30 days
"Clients can accept, defer or decline recommendations on the page"	The default for new reports; each report can change it. Decisions carry into the next review and the decision log.	On
"E-mail the owner when a client records a decision"	Tells the owner each time the client decides on a recommendation.	On

What happens after a client decides is covered in Recommendations and the decision log.

Choose how the pre-read reaches the client

Under Client e-mail, pick how the pre-read goes to the client before the meeting:

Your Halo mailbox (recommended) sends it as an e-mail action on a HaloPSA ticket for the client. It comes from your own address and the reply lands in HaloPSA. If the owner has no HaloPSA agent of their own, Send as Halo agent names the agent to send as. Left empty, it uses the report owner's HaloPSA agent.
The QuantumOps sender (donotreply@qops.app) sends it from the shared QuantumOps address. Replies go to the report owner. If e-mail is not set up, client pre-reads are not sent, whichever option you choose. Copy the client link and send it yourself.

Sender name is optional and sets the name shown as the sender of the pre-read. Leave it empty to use the company name from the brand kit. How a pre-read is sent for a particular review is covered in Review, publish and share with the client.

Choose what HaloPSA items recommendations create

When a client accepts a recommendation, the decision log can open the work in HaloPSA with one click. Nothing is created without that click. The Halo items tab sets what is created. The lists on this tab come from your HaloPSA; select Reload from Halo to fetch them again. If HaloPSA does not return a list, the tab says so and saved choices still show.

Open the Halo items tab.
Choose the Ticket type and the Team for tickets created from accepted recommendations. Left on Customer Success default, they use the defaults set in Customer Success settings.
Choose the Opportunity type. None: no opportunities is the default. Once you pick a type, the decision log offers Create opportunity. If HaloPSA has not flagged any ticket type as an opportunity, every type is listed and you pick the one your sales pipeline uses.
Choose the Impact and Urgency the new item starts with. If HaloPSA does not return its levels, the standard 1 to 5 levels are offered. The default is level 3 for both.
Under Site, keep Log it against the client's main site ticked to attach the item to the client's main site.
Select Save settings.

QBR settings: CSAT sources, metrics and AI covers the other three tabs.
Review, publish and share with the client shows how approval, the client link and the pre-read work in a review.
Recommendations and the decision log shows where the HaloPSA items are created.
Customer Success settings holds the fallback ticket type and team.

Was this helpful?

Still need help? Ask the team