- APPS
- Helpdesk Quality Control 19.0
| Lines of Code | 927 |
| Technical name | viin_quality_helpdesk |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/19.0/viin_quality_helpdesk |
| Required Apps | Discuss (mail) |
| Included Dependencies | Helpdesk Viindoo Base Quality |
Every resolved ticket can get its quality review, right on the ticket
For support teams that serve customers through helpdesk tickets
Review support quality with control points that create checks when a ticket reaches a stage.
Odoo Community Edition · Viindoo Cloud · License OPL-1 · English, Vietnamese
Extends Quality for helpdesk tickets.
What changes for your team
One review standard for the teams that need it
Each team leader reviews tickets in their own way, and many resolved tickets are never looked at again.
→ A control point names the helpdesk teams it checks, or every team, and the ticket stages that trigger it. A ticket entering such a stage gets its check.
Graded by the team, from the ticket
Reviews live in a spreadsheet, far from the ticket they judge.
→ Do Quality Checks opens the ticket's checks one after the other. A scorecard grades weighted criteria against a pass threshold, with the Helpdesk access right alone.
Service problems followed up, linked to their ticket
A problem found in a review is forgotten before anyone acts on it.
→ Report Quality Issue creates a quality alert with the ticket, its customer and the Customer source filled in, ready for the quality team's corrective actions.
Features
Plan what to review
- ✓ Choose the helpdesk teams each control point checks, or every team
- ✓ Pick the ticket stages that trigger a check
- ✓ Any test type of the Quality app, scorecards included
Checks that follow the ticket
- ✓ A check is created when a ticket enters a trigger stage
- ✓ Also when a ticket moves to another helpdesk team
- ✓ Frequency of the point: every ticket, a random share, or periodically
- ✓ No duplicate check to do; a ticket coming back gets a new one
Work from the ticket
- ✓ Do Quality Checks records the open checks one after the other
- ✓ Counts of checks, failed checks and alerts, one click away
- ✓ Report Quality Issue fills the alert with the ticket and its customer
Follow up as a quality team
- ✓ Checks searched and grouped by helpdesk team and ticket
- ✓ Alerts linked to their ticket and searched by ticket
Built for daily use
- ✓ A check never holds a ticket: a ticket with a failed check still closes
- ✓ Customers on the portal see no check, score or alert
- ✓ Support staff record checks without a Quality access right
- ✓ They never see checks or alerts of tickets they cannot read
- ✓ Deleting a judged check leaves an internal note on its ticket
- ✓ Each company's tickets use that company's control points
Ready on day one
Your helpdesk, unchanged
Tickets keep their stages and their flow; a check appears only where a control point names the team and the stage.
What you set up first
The teams and trigger stages of each control point, the scorecard that grades the support, and each person's access right; the Documentation tab covers each step.
Before you decide
Do support agents need a Quality access right?
No. With the Helpdesk access right they record the checks of the tickets they can read and read their alerts; they cannot create or delete checks.
Will customers see our internal reviews?
No. A customer opening the ticket on the portal sees no check, score or alert.
Does a failed check stop the ticket?
No. A ticket with a failed check still moves and closes; the Failed Checks count stays on the ticket.
Which tickets get a check?
A ticket that is created in, or moves to, a trigger stage of a control point covering its team, as often as the point's frequency says. Changing a point creates no check for tickets already in the stage.
What does it take to install and run?
Quality and Helpdesk; it installs by itself once both are present, with no extra Python package or server program. It is supported on Odoo Community Edition and Viindoo Cloud, not on Odoo Enterprise.
Try it, then ask us
Read the Documentation tab above, then try the live demo: v19demo-int.viindoo.com
Pre-sales & partnership
viindoo.com/contactusTechnical support
viindoo.com/ticketHelpdesk Quality Control
This guide is for the people who review the quality of the support delivered through helpdesk tickets: the quality administrator who decides which tickets are reviewed and how, the support staff who work on the tickets and record the checks, and the quality users who follow every check and alert.
Note
Extends Quality - see its documentation for the check dialog, scorecards, decisions, alerts and actions. This guide explains only what the link with helpdesk tickets adds. The tickets themselves are those of the Helpdesk app.
Overview
A support service is delivered through tickets. This module lets a ticket be reviewed like a delivered good: when a ticket reaches the stage where its handling is reviewed, it receives the quality checks that the control points call for, the support staff record them from the ticket, and a complaint becomes a quality alert linked to the ticket and to its customer. A quality check never holds the ticket back: the ticket moves on and closes whatever the result of its checks.
The process runs in these stages:
- The Quality Administrator chooses, on a control point, the helpdesk teams it reviews and the ticket stages that trigger it.
- When a ticket of those teams enters a trigger stage, the ticket receives one quality check for each control point that applies. The Support Agent who moves the ticket does nothing more.
- The Support Agent opens the checks of the ticket with Do Quality Checks and records the result.
- When something is wrong, the Support Agent uses Report Quality Issue on the ticket. The Quality User follows the alert from there, with the tools of the Quality app.
| Role | What they do | Access right to assign |
|---|---|---|
| Quality Administrator | Chooses the helpdesk teams and the trigger stages of a control point. | Quality: Administrator |
| Support Agent | Moves tickets through their stages, records the checks of the tickets they can read and reports quality issues about them. A team leader does the same on the tickets of the team. | Helpdesk: User |
| Quality User | Follows the checks and alerts of every ticket. | Quality: User |
Setup (for the Administrator)
Install the app
Open Apps and search for Helpdesk Quality Control. The app is installed by itself when the Quality app and the Helpdesk app are both installed; otherwise click Install.
The app works on Odoo Community Edition. Odoo Enterprise is not supported.
Give people their access right
- Open Settings ‣ Users & Companies ‣ Users and open the user.
- On the Access Rights tab, choose User on the Helpdesk line for every person who works on tickets. This is all a support agent needs to record the checks of the tickets they can read.
- Choose User or Administrator on the Quality line for the people who follow every check and alert, or who define the control points.
- Click Save.
Demonstration data
A database with demonstration data comes with a scorecard named Support review, a control point named Resolved ticket review that applies it to a share of the tickets of the Customer Support team reaching the Resolved stage, two checks on resolved tickets (one passed, one failed) and a quality alert about a ticket in progress. The examples of this guide use them.
Quality Administrator: choose which tickets are reviewed
Open Quality ‣ Quality Control ‣ Control Points and open or create a control point. The control point is described in the guide of the Quality app. When the module is installed the form has a Services group with two fields:
- Helpdesk Teams: the teams whose tickets this control point reviews. Leave it empty to review the tickets of every team.
- Ticket Stages: the stages that trigger the check. A ticket entering one of them gets a check of this control point. A control point without a ticket stage never applies to tickets.
Any test type applies. For the handling of a ticket, the Scorecard test type grades it against weighted criteria and a pass threshold; create the scorecard under Quality ‣ Configuration ‣ Scorecards and choose it on the control point.
Choose the teams and the stages
- Open the control point, or click New and type its Title.
- Choose the Test Type. For a scorecard, choose Scorecard and then the scorecard.
- In Helpdesk Teams, choose the teams to review, or leave the field empty for every team.
- In Ticket Stages, choose the stages where the handling of a ticket is reviewed, for example Resolved.
- Choose the Frequency, the Team and the Responsible. The Responsible is the person who is expected to record each check; the check takes it from the control point.
- Click Save.
Which tickets receive a check
A control point reviews a ticket when all of the following hold at the moment the ticket enters a trigger stage:
- The ticket is in one of the Ticket Stages. The stage itself counts, not its name.
- The ticket belongs to one of the Helpdesk Teams, or the control point lists none.
- The control point has no company, or its company is the company of the ticket. The company of the ticket is the one of the check; for a ticket without a company it is the company the user works in.
A ticket enters a trigger stage when its stage changes, when it is created in that stage, and when its helpdesk team changes while it is in that stage.
The Frequency of the control point decides whether a check is created when the ticket enters the stage. All Operations creates it every time. Randomly creates it for the share of tickets you set. Periodically creates it when the control point has had no check inside the period: when several tickets enter the stage in one operation, only the first of them is reviewed.
A check that is still to do is never created twice for the same ticket and control point. A ticket that comes back to the trigger stage after its check was recorded receives a new check.
Changing a control point creates no check by itself. A ticket that already sits in a stage you add as a trigger stage receives its check when it enters that stage again.
Find control points by helpdesk team
In the list of control points the search offers Helpdesk Teams. The columns Helpdesk Teams and Hidden Helpdesk Teams can be added from the optional columns menu of the list. The Ticket Stages are shown on the form of the control point only.
Helpdesk teams you cannot read
The access rules of the Helpdesk app decide who reads a team. A control point can list teams that you are not allowed to read. The form does not show them: it shows a message with their number and tells you to ask a Helpdesk Administrator to see them. They stay in the scope when you save the form and when you copy the control point, and you cannot add a team that you cannot read. Removing the visible teams from the field never removes the hidden ones.
Support Agent: work from the ticket
A support agent needs no Quality access right. The checks of a ticket are read and recorded by everyone who holds the Helpdesk access right User and can read the ticket. Open a ticket in Helpdesk ‣ Tickets ‣ All Tickets.
Receive the check
Move the ticket to a trigger stage by clicking the stage in the status bar, or by dragging the ticket to the stage in the kanban view. The ticket receives its checks at that moment. The Quality Checks button and the Do Quality Checks button appear on the ticket.
Record the checks
- Open the ticket and click Do Quality Checks. The dialog of the first check still to do opens.
- For a scorecard, click Pass, Fail or Not Applicable on each criterion. The dialog shows the score and whether it reaches the pass threshold. The Ticket line tells which ticket you are grading.
- Add a note if you wish, then click Confirm.
- The dialog moves on to the next check of the ticket still to do and closes after the last one.
Other test types work as described in the guide of the Quality app. A check that is already recorded is skipped. When no check is left to do, the Do Quality Checks button disappears.
See the checks and alerts of a ticket
The button box of the ticket shows three counters. Each one appears only when its number is above zero.
- Quality Alerts: the alerts about the ticket. One alert opens directly, several open as a list.
- Quality Checks: all the checks of the ticket.
- Failed Checks (in red): the checks of the ticket that failed.
Click a counter to open the records. A failed check does not stop anything: the ticket in the illustration is in the Resolved stage with a failed check, as a ticket can be.
Open a check to read its result. The form shows the Ticket it belongs to.
Find the checks of a team
Open Quality ‣ Quality Control ‣ Quality Checks. The list shows the checks assigned to you or followed by you, and the checks of every ticket you can read. Type a team name in the search box and choose Search Helpdesk Team, or choose Search Ticket for a ticket title. In the list view the optional column Ticket can be added, and Group By offers Helpdesk Team and Ticket. The kanban view does not show the ticket of a check.
Report a quality issue
Use this when you find a problem about the ticket, with or without a failed check.
- Open the ticket and click Report Quality Issue. The button is offered on a saved ticket.
- In Summary, say the problem in a few words. The summary is required.
- In Details, add what helps to understand it.
- Click Report. Click Discard instead and nothing is created.
The quality alert is created and opens. Its Source is Customer, its Partner is the contact of the ticket and its Ticket is the ticket. The alert belongs to the company of the ticket. You can read it, discuss it in the chatter and attach files; only a quality user edits it. The breadcrumb leads back to the ticket.
What you see
You see the checks and the alerts of the tickets you can read, whatever their status, also when the ticket is archived. The Helpdesk app decides which tickets you can read: a ticket you cannot read has no check, no alert and no counter for you. You record the results of the checks and you cannot create or delete a check.
The person named Responsible on a check also finds it in the Quality app. When that person cannot read the ticket, the check shows the ticket as a name, without a link.
Customers who open their ticket from the portal see nothing of its quality checks, scores or alerts: the quality review is internal.
Quality User: follow every ticket
A quality user sees every check and every alert, as in the Quality app, and uses the Ticket and Helpdesk Team fields to search and group them. The Quality app guide explains the decisions on a failed check and the follow-up of an alert.
When a quality user cannot read a ticket, the check and the alert still show the Ticket as a name, without a link to open it. A quality user who reports a quality issue from a check of such a ticket gets an alert that keeps the link to the ticket and the Customer source; the contact of the ticket is left empty, because the reporter cannot read the ticket.
When a judged check is deleted, a note records its name, its control point, its status and the person and date of the deletion. The note is internal, is written on the ticket, where only the people who read the ticket see it, and is never sent to the customer.
Troubleshooting
- I moved the ticket to the trigger stage and no check appeared.
- Open the control point. Check that the team of the ticket is in Helpdesk Teams (or that the field is empty), that the stage is one of the Ticket Stages, and that the control point has no other company than the ticket. A check still to do for the same control point also prevents a new one. With Randomly or Periodically a check is created only when the frequency calls for it.
- The Do Quality Checks button is missing.
- It appears only when the ticket has a check still to do.
- The counters of the quality checks are missing on a ticket.
- Each counter appears when its number is above zero. A portal user never sees them.
- The Report Quality Issue button is missing.
- The button is offered on a saved ticket. Save a new ticket first.
- I cannot edit the alert I reported.
- Without the Quality User access right the alert is read-only. Write in the discussion below the form.
- I cannot see a check that exists for a ticket.
- You see the checks of the tickets you can read. Ask the team leader or a Helpdesk Administrator for access to the ticket.
- A team of the control point is not shown on its form.
- You cannot read that team. The form shows how many teams are hidden; they stay in the scope.
FAQ
- Does a failed check block the ticket?
- No. A check never prevents the ticket from moving to another stage or from being closed. The counters tell what failed.
- Who is the Responsible of the check?
- The Responsible of the control point.
- Does a check exist for a ticket that was in the stage before the control point was created?
- No. Checks are created when a ticket enters a trigger stage.
- Can one ticket have several checks?
- Yes: one for each control point that applies, and a new one each time the ticket comes back to the stage after its check was recorded.
- Can a Quality User read a ticket they have no access to?
- No. The app opens no ticket to anyone: a person who cannot read a ticket sees its name on the check and nothing else.
- Does the customer see the review of their ticket?
- No. The checks, the scores and the alerts are internal.
This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file).
You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software.
The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.