documentation/content/applications/websites/livechat/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

45 lines
1.4 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
=======
Giving users the opportunity to rate their interactions can help you improving the experience you
offer. That means staying on top of your customers' needs, besides keeping track of your operators
performances.
Customer Rating
===============
| Once the user chooses to close the chat window, he can rate his interaction.
| If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing for an explanation
is shown.
| A copy of the conversation can also be sent by email.
.. image:: ratings/user_chatwindow.png
:align: center
:height: 400
:alt: View of the chat window from a users side for Odoo Live Chat
The rating is shown on the chat window itself for the operator.
.. image:: ratings/operator_chatwindow.png
:align: center
:alt: View of a chat window from an operators side highlighting a rating for Odoo Live Chat
And under :menuselection:`Report --> Customer Ratings`.
.. image:: ratings/customer_ratings.png
:align: center
:alt: View of the customer ratings page in Odoo Live Chat
Make the rating public
======================
Go to :menuselection:`Website --> Configuration --> Settings`, access your channel form, click on
*Go to Website* and on *Unpublished*, to publish the rating of that channel on your website.
.. image:: ratings/publish_ratings.png
:align: center
:alt: View of the public ratings in the website for Odoo Live Chat
.. seealso::
- :doc:`responses`