| 
1 |  | -======================================  | 
2 |  | -Allow customers to close their tickets  | 
3 |  | -======================================  | 
 | 1 | +===============  | 
 | 2 | +Closing tickets  | 
 | 3 | +===============  | 
4 | 4 | 
 
  | 
5 |  | -Allowing customers to close their own tickets gives them autonomy and minimizes misunderstandings  | 
6 |  | -around when an issue is considered solved or not. This results in operational capacity for support  | 
7 |  | -teams, and higher satisfaction for the customer.  | 
 | 5 | +Once work has been completed on a *Helpdesk* ticket in Odoo, there are several ways it can be  | 
 | 6 | +closed. Manually closing solved tickets keeps the pipeline up to date, while automatically closing  | 
 | 7 | +inactive tickets prevents unnecessary blocking issues. Allowing customers to close their own tickets  | 
 | 8 | +minimizes confusion around whether an issue is considered solved or not. This results in increased  | 
 | 9 | +operational capacity for support teams, and higher customer satisfaction.  | 
8 | 10 | 
 
  | 
9 |  | -Enable ticket closing  | 
10 |  | -=====================  | 
 | 11 | +Manually close solved tickets  | 
 | 12 | +=============================  | 
11 | 13 | 
 
  | 
12 |  | -Start by navigating to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and choose  | 
13 |  | -the appropriate team. Then click :guilabel:`Edit` and enable :guilabel:`Ticket closing` by  | 
14 |  | -checking the field box.  | 
 | 14 | +As work on a ticket progresses, it is moved along to the next stage in the pipeline. Once the issue  | 
 | 15 | +is solved, the ticket is moved to a *folded* stage. This marks the ticket as *closed*.  | 
15 | 16 | 
 
  | 
16 |  | -.. image:: close_tickets/close-ticket-settings.png  | 
17 |  | -   :alt: Ticket closing feature in Odoo Helpdesk.  | 
 | 17 | +To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and click on a team to open the  | 
 | 18 | +pipeline. Hover over a stage's heading, and then click the gear icon that appears in the top-right  | 
 | 19 | +corner of that stage's kanban column.  | 
18 | 20 | 
 
  | 
19 |  | -To designate which stage the ticket migrates to once it is closed, navigate to the ticket pipeline  | 
20 |  | -by going to :menuselection:`Helpdesk --> Overview` and clicking :guilabel:`Tickets` on the team's  | 
21 |  | -card.  | 
 | 21 | +.. image:: close_tickets/closing-edit-stage-gear.png  | 
 | 22 | +   :align: center  | 
 | 23 | +   :alt: View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage option.  | 
22 | 24 | 
 
  | 
23 |  | -There are two options: create a new Kanban stage or work with an existing one. For both scenarios,  | 
24 |  | -click the :guilabel:`Settings (gear)` icon next to the stage name, select :guilabel:`Edit Stage`,  | 
25 |  | -and enable :guilabel:`Closing Stage`. After checking the field box, click :guilabel:`Save` to  | 
26 |  | -finish.  | 
 | 25 | +.. warning::  | 
 | 26 | +   Clicking the gear icon also displays the option to :guilabel:`Fold` the stage. This setting folds  | 
 | 27 | +   the stage *temporarily* to simplify the kanban view. This does *not* close the tickets in this  | 
 | 28 | +   stage. It also does not permanently fold the stage. If a stage needs to be folded so the tickets  | 
 | 29 | +   can be marked as closed, continue following the steps below.  | 
27 | 30 | 
 
  | 
28 |  | -.. note::  | 
29 |  | -   If a closing stage is not specified, by default, the ticket is moved to the last stage in the  | 
30 |  | -   kanban. If more than one stage is set as a closing stage, the ticket is placed in the first  | 
31 |  | -   closing stage column.  | 
 | 31 | +From the menu that appears, select :guilabel:`Edit Stage`. This will open the stage's settings.  | 
 | 32 | +Check the box labeled :guilabel:`Folded in Kanban` towards the top of the window, and then  | 
 | 33 | +:guilabel:`Save & Close` to confirm the changes. Now, tickets that reach this stage will be  | 
 | 34 | +considered as *closed*.  | 
32 | 35 | 
 
  | 
33 |  | -With the ticket closing settings now complete, customers can now view the option to  | 
34 |  | -:guilabel:`Close this ticket` when they log into their portal.  | 
 | 36 | +   .. image:: close_tickets/closing-folded-setting.png  | 
 | 37 | +      :align: center  | 
 | 38 | +      :alt: Stage settings page.  | 
35 | 39 | 
 
  | 
36 |  | -.. image:: close_tickets/customer-view-close-ticket.png  | 
37 |  | -   :alt: Customer view of ticket closing in Odoo Helpdesk.  | 
 | 40 | +Automatically close inactive tickets  | 
 | 41 | +====================================  | 
 | 42 | + | 
 | 43 | +Tickets that are inactive for a set period of time can be automatically closed. At that point, they  | 
 | 44 | +will be moved to a folded stage.  | 
 | 45 | + | 
 | 46 | +Go to the team's settings page by going to :menuselection:`Helpdesk --> Configuration --> Teams`.  | 
 | 47 | +Under the :guilabel:`Self-Service` section, enable :guilabel:`Automatic Closing`.  | 
 | 48 | + | 
 | 49 | +If one of the team's stages is set to be folded in the kanban view, it will be the default selection  | 
 | 50 | +in the :guilabel:`Move to Stage` field. If the team has more than one folded stage, the stage that  | 
 | 51 | +occurs first in the pipeline will be the default. If no stage is folded, the default selection will  | 
 | 52 | +be the last stage in the pipeline.  | 
 | 53 | + | 
 | 54 | +The :guilabel:`After days of inactivity` field defaults to `7`, but can be adjusted if necessary.  | 
 | 55 | + | 
 | 56 | +.. warning::  | 
 | 57 | +   The :guilabel:`After days of inactivity` field does **not** take the working calendar into  | 
 | 58 | +   account when tracking the amount of time a ticket has been inactive.  | 
 | 59 | + | 
 | 60 | +If only certain stages should be used to track days of inactivity, they can be added to the  | 
 | 61 | +:guilabel:`In Stages` field.  | 
 | 62 | + | 
 | 63 | +.. example::  | 
 | 64 | +   A team's pipeline is created with the following stages:  | 
 | 65 | + | 
 | 66 | +   - `New`  | 
 | 67 | +   - `In Progress`  | 
 | 68 | +   - `Customer Feedback`  | 
 | 69 | +   - `Closed`  | 
 | 70 | + | 
 | 71 | +   Tickets can linger in the :guilabel:`Customer Feedback stage`, because once an issue is solved,  | 
 | 72 | +   customers may not respond immediately. At that point, the tickets can be closed automatically.  | 
 | 73 | +   However, tickets in the :guilabel:`New` and :guilabel:`In Progress` stages may remain inactive  | 
 | 74 | +   due to assignment or workload issues. Closing these tickets automatically would result in issues  | 
 | 75 | +   going unsolved.  | 
38 | 76 | 
 
  | 
39 |  | -Get reports on tickets closed by customers  | 
 | 77 | +   Therefore, the :guilabel:`Automatic Closing` settings would be configured as below\:\  | 
 | 78 | + | 
 | 79 | +   - :guilabel:`Automatic Closing`: *checked*  | 
 | 80 | +   - :guilabel:`Move to Stage`: `Solved`  | 
 | 81 | +   - :guilabel:`After``7`:guilabel:`days of inactivity`  | 
 | 82 | +   - :guilabel:`In Stages`: `Customer Feedback`  | 
 | 83 | + | 
 | 84 | +   .. image:: close_tickets/closing-automatic-settings-example.png  | 
 | 85 | +      :align: center  | 
 | 86 | +      :alt: Example of Automatic Closing settings.  | 
 | 87 | + | 
 | 88 | +Allow customers to close their own tickets  | 
40 | 89 | ==========================================  | 
41 | 90 | 
 
  | 
42 |  | -To analyze the tickets that have been closed by customers, go to :menuselection:`Helpdesk -->  | 
43 |  | -Reporting --> Tickets`. Then, click on the :guilabel:`Filters` menu and choose :guilabel:`Add  | 
44 |  | -Custom filter`. Next, set the custom filter parameters to :guilabel:`Closed by partner` and  | 
45 |  | -:guilabel:`is true`. Finally, click :guilabel:`Apply`.  | 
 | 91 | +Enabling the :guilabel:`Closure by Customers` setting allows customers to close their own ticket(s)  | 
 | 92 | +when they determine that their issue has been resolved.  | 
 | 93 | + | 
 | 94 | +Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams` and select a team. On  | 
 | 95 | +the team's settings page, scroll to the :guilabel:`Self-Service` section and check the box for  | 
 | 96 | +:guilabel:`Closure by Customers`.  | 
 | 97 | + | 
 | 98 | +.. image:: close_tickets/closing-by-customer-setting.png  | 
 | 99 | +   :align: center  | 
 | 100 | +   :alt: Customer closing setting in Odoo Helpdesk.  | 
 | 101 | + | 
 | 102 | +Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` button will be available  | 
 | 103 | +for customers when they view their ticket through the customer portal.  | 
 | 104 | + | 
 | 105 | +.. image:: close_tickets/closing-customer-view.png  | 
 | 106 | +   :align: center  | 
 | 107 | +   :alt: Customer view of ticket closing in Odoo Helpdesk.  | 
 | 108 | + | 
 | 109 | +.. note::  | 
 | 110 | +   Customers are able to view their tickets by clicking the :guilabel:`View the ticket` link they  | 
 | 111 | +   receive by email. The link is included in the :guilabel:`Request Acknowledgment` template, which  | 
 | 112 | +   is added to the first stage of a team by default. This link does not require a customer to have  | 
 | 113 | +   access to the portal to view or respond to their ticket.  | 
46 | 114 | 
 
  | 
47 |  | -.. image:: close_tickets/closed-by-search-filter.png  | 
48 |  | -   :alt: Filter for tickets closed by customers on Odoo Helpdesk's reporting page.  | 
 | 115 | +   Customers with access to the portal will be able to view their tickets under :menuselection:`My  | 
 | 116 | +   Account --> Tickets`.  | 
0 commit comments