documentation/content/applications/services/helpdesk/overview/ratings.rst
Antoine Vandevenne (anv) 250bc3ab21 [MOV] content/*: move resource files into their related page's directory
Since odoo/documentation#903, the guideline for the location of new
resource (images, downloadable files, RST includes...) files is to place
those inside the directory of the RST page that references them.

For example, if `doc1.rst` has a reference to `image.png` and to
`download.zip`, the file structure should look like this:

├── parent_doc/
│     └── doc1/
│     │     └── image.png
│     │     └── download.zip
│     └── doc1.rst
│     └── doc2.rst
├── parent_doc.rst

Before this commit, most of the resource files were still located inside
'media' directories holding all the resource files referenced by RST
pages located at the same level as these directories. In the example
above, a single 'media' directory would hold all the resource files
referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from
figuring out easily which resource file was referenced by which RST page
and, thus, lead to unused resource files piling up in the repository. It
also made it more complicated to define codeowners regex rules because a
team could not simply be assigned to `/some_page.*` but needed to be
assigned to both `/some_page\.rst` and to the location of 'media'.

In order to help new content writers figure out the guideline when
taking examples from other RST pages, this commit retroactively applies
the guideline to existing resource files and 'media' directories. The
left-over resource files that are not referenced by any RST page are
removed.

task-2497965

Part-of: odoo/documentation#2066
2022-05-20 14:48:37 +02:00

52 lines
1.9 KiB
ReStructuredText
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

=======
Ratings
=======
Allow customers to rate their experience with your helpdesk teams to strengthen your credibility and
gain their trust. Reviews can also influence a customers decision and open space for feedback that
can help you improve the quality of your services.
Set up
======
Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *Ratings on
tickets*. The feature automatically adds a default email template on the non-folded *closing
stage(s)* of that team.
.. image:: ratings/ratings_on_tickets.png
:align: center
:alt: Overview of the settings page of a helpdesk team emphasizing the rating on ticket feature
in Odoo Helpdesk
To edit the email template and the stage(s) set as the closing ones, go to the Kanban view of your
helpdesk team and click on *Settings*, then on *Edit Stage*.
.. image:: ratings/edit_stage.png
:align: center
:alt: Overview of a helpdesk team kanban view emphasizing the menu edit stage in Odoo Helpdesk
Now, once a ticket reaches the stage(s) designated as the *Closing Stage*, an email is sent to the
customer.
.. image:: ratings/email_customer_feedback.png
:align: center
:alt: View of a standard helpdesk customer review email template for Odoo Helpdesk
Ratings can be seen on the chatter of each ticket, under the *See Customer Satisfaction* link on the
main dashboard, and through *Reporting*.
Ratings visible on the customer portal
--------------------------------------
Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *Display Rating on
Customer Portal*. Now, by clicking on the helpdesk teams name on their ticket, customers can see
its ratings.
.. image:: ratings/customer_portal.png
:align: center
:alt: View of the helpdesk ticket from a users portal emphasizing the link to the helpdesk team
in Odoo Helpdesk
.. seealso::
- :doc:`../advanced/close_tickets`