NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
21b604e0db
documentation/locale/sources/services.pot
Martin Trigaux 62a362f30a [I18N] *: export source terms 
closes 

X-original-commit: d53ba8c7e2
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
2023-04-13 17:57:26 +02:00

1936 lines
103 KiB
Plaintext
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.

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-16.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-04-13 08:42+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../content/applications/services.rst:5
msgid "Services"
msgstr ""
#: ../../content/applications/services/fsm.rst:8
msgid "Field Service"
msgstr ""
#: ../../content/applications/services/fsm.rst:11
msgid "`Odoo Tutorials: Field Service <https://www.odoo.com/slides/field-service-49>`_"
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:3
msgid "User default warehouse"
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:5
msgid "Setting up a **default warehouse** can be useful for field technicians who keep a supply in their van or those who always resupply from the same warehouse."
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:8
msgid "Products in sales orders created during field interventions are always pulled from the same warehouse, keeping the inventory accurate with the default warehouse feature."
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:12
msgid ":doc:`../../inventory_and_mrp/inventory`"
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:15
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:13
#: ../../content/applications/services/project/project_management.rst:17
msgid "Configuration"
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:17
msgid "To set up a user default warehouse, the :doc:`storage locations <../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations>` and :ref:`multi-step routes <use-routes/routes-rules>` features need to be activated. It is also necessary to have more than one warehouse in your database."
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:23
msgid ":doc:`../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations`"
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:24
msgid ":doc:`../../inventory_and_mrp/inventory/routes/concepts/use_routes`"
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:27
msgid "User account"
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:29
msgid "To set up a default warehouse for a specific user, go to :menuselection:`Settings --> Users --> Manage users`, open a user, then go to the :guilabel:`Preferences` tab, scroll down to :guilabel:`Inventory`, and select the default warehouse from the drop-down menu."
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:-1
msgid "Selection of a default warehouse on a user profile."
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:37
msgid "Default warehouse in field service tasks"
msgstr ""
#: ../../content/applications/services/fsm/default_warehouse.rst:39
msgid "Once a default warehouse has been configured for a user, the materials used for a sales order linked to a Field Service task are pulled from that specific warehouse. In the sales order, go to the :guilabel:`Other Info` tab, then scroll down to :guilabel:`Delivery`. The default warehouse is applied correctly."
msgstr ""
#: ../../content/applications/services/fsm/helpdesk.rst:5
#: ../../content/applications/services/helpdesk.rst:8
msgid "Helpdesk"
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:3
msgid "Plan onsite interventions from helpdesk tickets"
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:5
msgid "The integration with the Helpdesk app lets your helpdesk team manage intervention requests directly. Planning field service tasks from tickets speeds up your processes."
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:9
msgid "Configure the helpdesk team"
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:11
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select a team and enable *Onsite Interventions*."
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:-1
msgid "Onsite interventions setting in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:18
msgid "The helpdesk tickets of the team now display the *Plan Intervention* button. Click on it to create a new task under your field service project."
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:-1
msgid "Plan intervention from helpdesk ticket in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/fsm/sales.rst:5
msgid "Sales"
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:3
msgid "Create onsite interventions from sales orders"
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:5
msgid "Allowing your sales team to open onsite interventions creates a seamless experience for your customers. They can receive a quotation they first have to approve before the work even starts."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:9
msgid "Configure a product"
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:11
msgid "Go to :menuselection:`Field Service --> Configuration --> Products` and create or edit a product."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:13
msgid "Under the *General Information* tab, select *Service* as *Product Type*."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:14
msgid "Under the *Sales* tab, select *Timesheets on tasks* as *Service Invoicing Policy*."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:15
msgid "Select *Create a task in an existing project* as *Service Tracking*."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:16
msgid "Select your *Project*."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:17
msgid "If you use them, select your *Worksheet Template* and then click on *Save*."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:-1
msgid "Product configuration to create tasks from sales orders in Odoo Field Service"
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:23
msgid "From the *Sales* app, create a quotation with the product and confirm it. A task is automatically set up under your Field Service project. It is directly accessible from the sales order."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:-1
msgid "Field Service task on a sales order in Odoo Sales"
msgstr ""
#: ../../content/applications/services/helpdesk.rst:11
msgid "`Odoo Tutorials: Helpdesk <https://www.odoo.com/slides/helpdesk-51>`_"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced.rst:5
msgid "Advanced"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:3
msgid "After Sales Features"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:5
msgid "As your business grows, having the right tool to support your helpdesk team on recording, tracking and managing issues raised easy and efficiently, is key. Odoo’s Helpdesk application allows you to generate credit notes, manage returns, products, repairs, grant coupons, and even plan onsite interventions from a ticket’s page."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:11
msgid "Set up the after sales services"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:13
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable the after sales options: *Refunds, Returns, Coupons, Repairs and Onsite Interventions*."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:20
msgid "Generate credit notes from tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:22
msgid "You can use a credit note to refund a customer or adjust the amount due. For that, simply go to your ticket page, click on *Refund* and select the corresponding *Invoice*. Clicking on *Reverse* generates a credit note, and you can *Post* it while still being in the *Helpdesk* app."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:30
msgid "Allow product returns from tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:32
msgid "The process of a product return from your customer back to your warehouse is taken into action when, at the ticket page, you choose the option *Return*."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:39
msgid "Grant coupons from tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:41
msgid "First, be sure to have your *Coupon Program* planned in the *Sales* or *Website* application. Then, in *Helpdesk*, open your ticket, click on *Coupon*, and choose the respective one."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:48
msgid "Repairs from tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:50
msgid "Clicking on *Repair* option, on your ticket page, a new repair order form is shown. Fill in the information as needed and choose the next step."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:57
msgid "Plan onsite interventions from tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:59
msgid "At the ticket's page click on *Plan Intervention*, and set up your onsite intervention exactly the same way as if you were on the *Field Service* application."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:67
msgid "`Coupons <https://www.odoo.com/slides/slide/coupon-programs-640?fullscreen=1>`_"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
msgid "Closing tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
msgid "Once work has been completed on a *Helpdesk* ticket in Odoo, there are several ways it can be closed. Manually closing solved tickets keeps the pipeline up to date, while automatically closing inactive tickets prevents unnecessary blocking issues. Allowing customers to close their own tickets minimizes confusion around whether an issue is considered solved or not. This results in increased operational capacity for support teams, and higher customer satisfaction."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12
msgid "Manually close solved tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14
msgid "As work on a ticket progresses, it is moved along to the next stage in the pipeline. Once the issue is solved, the ticket is moved to a *folded* stage. This marks the ticket as *closed*."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17
msgid "To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and click on a team to open the pipeline. Hover over a stage's heading, and then click the gear icon that appears in the top-right corner of that stage's kanban column."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1
msgid "View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage option."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26
msgid "Clicking the gear icon also displays the option to :guilabel:`Fold` the stage. This setting folds the stage *temporarily* to simplify the kanban view. This does *not* close the tickets in this stage. It also does not permanently fold the stage. If a stage needs to be folded so the tickets can be marked as closed, continue following the steps below."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31
msgid "From the menu that appears, select :guilabel:`Edit Stage`. This will open the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` towards the top of the window, and then :guilabel:`Save & Close` to confirm the changes. Now, tickets that reach this stage will be considered as *closed*."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
msgid "Stage settings page."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41
msgid "Automatically close inactive tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43
msgid "Tickets that are inactive for a set period of time can be automatically closed. At that point, they will be moved to a folded stage."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46
msgid "Go to the team's settings page by going to :menuselection:`Helpdesk --> Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable :guilabel:`Automatic Closing`."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49
msgid "If one of the team's stages is set to be folded in the kanban view, it will be the default selection in the :guilabel:`Move to Stage` field. If the team has more than one folded stage, the stage that occurs first in the pipeline will be the default. If no stage is folded, the default selection will be the last stage in the pipeline."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54
msgid "The :guilabel:`After days of inactivity` field defaults to `7`, but can be adjusted if necessary."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57
msgid "The :guilabel:`After days of inactivity` field does **not** take the working calendar into account when tracking the amount of time a ticket has been inactive."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60
msgid "If only certain stages should be used to track days of inactivity, they can be added to the :guilabel:`In Stages` field."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64
msgid "A team's pipeline is created with the following stages:"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66
msgid "`New`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67
msgid "`In Progress`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68
msgid "`Customer Feedback`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69
msgid "`Closed`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71
msgid "Tickets can linger in the :guilabel:`Customer Feedback stage`, because once an issue is solved, customers may not respond immediately. At that point, the tickets can be closed automatically. However, tickets in the :guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due to assignment or workload issues. Closing these tickets automatically would result in issues going unsolved."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
msgid "Therefore, the :guilabel:`Automatic Closing` settings would be configured as below\\:\\"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79
msgid ":guilabel:`Automatic Closing`: *checked*"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80
msgid ":guilabel:`Move to Stage`: `Solved`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
msgid ":guilabel:`After``7`:guilabel:`days of inactivity`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82
msgid ":guilabel:`In Stages`: `Customer Feedback`"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
msgid "Example of Automatic Closing settings."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89
msgid "Allow customers to close their own tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91
msgid "Enabling the :guilabel:`Closure by Customers` setting allows customers to close their own ticket(s) when they determine that their issue has been resolved."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94
msgid "Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams` and select a team. On the team's settings page, scroll to the :guilabel:`Self-Service` section and check the box for :guilabel:`Closure by Customers`."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1
msgid "Customer closing setting in Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102
msgid "Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` button will be available for customers when they view their ticket through the customer portal."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:-1
msgid "Customer view of ticket closing in Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110
msgid "Customers are able to view their tickets by clicking the :guilabel:`View the ticket` link they receive by email. The link is included in the :guilabel:`Request Acknowledgment` template, which is added to the first stage of a team by default. This link does not require a customer to have access to the portal to view or respond to their ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115
msgid "Customers with access to the portal will be able to view their tickets under :menuselection:`My Account --> Tickets`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview.rst:5
#: ../../content/applications/services/timesheets/overview.rst:5
msgid "Overview"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:3
msgid "Forum and eLearning"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:6
msgid "Forum"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:8
msgid "To go above and beyond email, live chat, web forms, and phone lines, offer your customers a support forum. This way, customers might become more attached to your company as they would be investing time to get into details of your business. You also encourage the exchange of experiences and knowledge, supporting the feeling of belonging to a community (your community!)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:14
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:52
#: ../../content/applications/services/helpdesk/overview/ratings.rst:10
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:11
msgid "Set up"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:16
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and enable *Help Center*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "Overview of the settings page of a helpdesk team emphasizing the help center feature in\n"
"Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:23
msgid "Create, or edit a forum by clicking on the external link. Among the editing options, choose if you would like the *Forum Mode* to be *Questions*: only one answer is allowed per question or *Discussions*: multiple answers are allowed per question."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "Overview of a forum’s settings page in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:31
msgid "From now on, logged in users can start their discussions. To keep track of posts, go to :menuselection:`Website --> Forum --> Posts`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "Overview of the Forums page of a website to show the available ones in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:38
msgid "Turn tickets into forum posts by simply clicking on *Share on the Forum* on the ticket's page."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:45
msgid "eLearning"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:47
msgid "In addition to a forum, offer online courses. When doing so, you link your customers and users’ needs and questions to useful content, helping to boost efficiency as they can also find their answers there."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:54
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *eLearning*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "Overview of the settings page of a customer care team emphasizing the feature elearning in\n"
"Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:61
msgid "Once the structure and content of your course are ready, *Publish* it by clicking on *Unpublished*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "View of a course being published for Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:67
msgid "To keep track of your course statistics, go to *eLearning* and *View Course*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:-1
msgid "View of the elearning applications dashboard for Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:73
msgid "Todo"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/forum_and_elearning.rst:73
msgid "DETAILS/INFO SHOULD COME FROM ELEARNING DOCS. THEREFORE, LINK DOCS ONCE AVAILABLE!"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:3
msgid "Getting started with Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:5
msgid "Odoo :guilabel:`Helpdesk` is a ticket-based customer support application. Teams can track, prioritize, and solve customer issues from their pipeline, which is organized in customizable stages. Multiple teams can be configured and managed in one dashboard."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:10
msgid "Create Helpdesk teams"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:12
msgid "Setting up multiple teams allows for tickets to be grouped by location or by support type."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:14
msgid "To view or modify *Helpdesk* teams, go to :menuselection:`Helpdesk --> Configuration --> Teams`. To create a new team, click on the :guilabel:`New` button in the top left of the dashboard. From there, name the new team, and fill out the remaining fields as defined in the following sections on the form."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1
msgid "View of the Helpdesk teams page in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:24
msgid "Assignment & Visibility"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:27
msgid "Determine to whom the team will be visible"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:29
msgid "Under the :guilabel:`Visibility` section, determine who can view this team and its tickets."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:31
msgid ":guilabel:`Invited internal users` have access to the team and tickets they are following. This can be modified on each individual ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:33
msgid ":guilabel:`All internal users` have access to the team and all of its tickets without being a follower."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:35
msgid ":guilabel:`Invited portal users and all internal users` have access to the team without being a follower. Portal users will only be able to access tickets that they are following."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:39
msgid "A `Customer Support` team intended to handle general issues with shipping and product issues would have the visibility setting :guilabel:`Invited portal users and all internal users`. However, a `Financial Services` team handling tickets related to accounting or tax information would only need to be visible to :guilabel:`Invited internal users`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:45
msgid "Automatically assign new tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:47
msgid "When tickets are received, they will need to be assigned to a member of the support team. This can be done manually on each ticket individually, or through :guilabel:`Automatic Assignment`. Check the box next to :guilabel:`Automatic Assignment` to enable the feature for this team."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1
msgid "View of a Helpdesk team settings page emphasizing the assignment and visibility features\n"
"in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:56
msgid "Select one of the following assignment methods, based on how workload should be allocated across the team:"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:60
msgid ":guilabel:`Each user is assigned an equal number of tickets` assigns tickets to team members"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:60
msgid "based on total ticket count, regardless of the number of open or closed tickets they are currently assigned."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:64
msgid ":guilabel:`Each user has an equal number of open tickets` assigned tickets to team members based"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:63
msgid "on how many open tickets they are currently assigned. This option is useful for automatically delegating a heavier workload to high-performers who tend to close tickets quickly."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:66
msgid "Finally, add the :guilabel:`Team Members` who will be assigned tickets for this team. Leave the field empty to include all employees who have the proper assignments and access rights configured in their user account settings."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:71
msgid "If an employee has time off scheduled in the :guilabel:`Time Off` application, they will not be assigned tickets during that time. If no employees are available, the system will look ahead until there is a match."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:76
msgid ":ref:`Manage users <users/add-individual>`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:77
msgid ":doc:`Access rights </applications/general/users/access_rights>`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:80
msgid "Create or modify kanban stages"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:82
msgid ":guilabel:`Stages` are used to organize the *Helpdesk* pipeline and track the progress of tickets. Stages are customizable, and can be renamed to fit the needs of each team."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:85
msgid "To view or modify *Helpdesk* stages, go to :menuselection:`Helpdesk --> Configuration --> Stages`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:88
msgid ":ref:`Developer mode <developer-mode>` must be activated in order to access the stages menu. To activate developer mode go to :menuselection:`Settings --> General Settings --> Developer Tools` and click on :guilabel:`Activate the developer mode`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:92
msgid "The list view shows an overview of all the stages currently available in Helpdesk. They are listed in the order they appear in the pipeline. To change the order of the stages, use the arrow buttons on the left side of the list."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:97
msgid "Change the stage order on the kanban view by dragging and dropping individual columns."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1
msgid "View of the stage list page emphasizing the option to create a new stage"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:104
msgid "To create a new stage, click on the :guilabel:`New` button in the top left of the dashboard. Next, choose a name for the new stage, and add a description (though it is not required). Fill out the remaining fields following the steps below."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1
msgid "View of a stage's settings page in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:113
msgid "Add email and SMS templates to stages"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:115
msgid "When an :guilabel:`Email Template` is added to a stage, an email is automatically sent to the the customer when a ticket reaches that specific stage in the helpdesk pipeline. Likewise, adding an :guilabel:`SMS Template` will result in an SMS text message being sent to the customer."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:120
msgid "SMS Text Messaging is an In-App Purchase (IAP) service that requires prepaid credits to work. Refer to `SMS Pricing FAQ <https://iap-services.odoo.com/iap/sms/pricing>`_ for additional information."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:124
msgid "To select an existing email template, select it from the :guilabel:`Email Template` field. Click on the arrow key to the right of the field to edit the template."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:127
msgid "To create a new template, click the field and begin typing a new template title. Then select :guilabel:`Create and edit`, and complete the form details."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:130
msgid "Follow the same steps to select, edit, or create an :guilabel:`SMS Template`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:-1
msgid "View of an SMS template setup page in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:137
msgid ":doc:`/applications/general/email_communication/email_template`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:140
msgid "Assign stages to a team"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:142
msgid "Make a selection in the :guilabel:`Teams` field on the :guilabel:`Stages` form. More than one team may be selected, since the same stage(s) can be assigned to multiple teams."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:0
msgid "View of stage setup emphasizing teams field"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:150
msgid "Fold a stage"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:152
msgid "Check the :guilabel:`Folded in Kanban` box on the :guilabel:`Stages` form to display this stage as *folded* by default in the kanban view for this team."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:156
msgid "Tickets that reach a *folded* stage are considered closed. Closing a ticket before the work is completed can result in reporting and communication issues. This setting should only be enabled for stages that are considered *closing* stages."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:160
msgid "Alternatively, stages can be temporarily folded in the kanban view, by clicking on the settings icon and selecting :guilabel:`Fold`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:164
msgid "Manually folding a stage from the kanban view will not close the tickets in the stage."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:3
msgid "Ratings"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:5
msgid "Allow customers to rate their experience with your helpdesk teams to strengthen your credibility and gain their trust. Reviews can also influence a customer’s decision and open space for feedback that can help you improve the quality of your services."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:12
msgid "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."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:-1
msgid "Overview of the settings page of a helpdesk team emphasizing the rating on ticket feature\n"
"in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:21
msgid "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*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:-1
msgid "Overview of a helpdesk team kanban view emphasizing the menu edit stage in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:28
msgid "Now, once a ticket reaches the stage(s) designated as the *Closing Stage*, an email is sent to the customer."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:-1
msgid "View of a standard helpdesk customer review email template for Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:35
msgid "Ratings can be seen on the chatter of each ticket, under the *See Customer Satisfaction* link on the main dashboard, and through *Reporting*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:39
msgid "Ratings visible on the customer portal"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:41
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and enable *Display Rating on Customer Portal*. Now, by clicking on the helpdesk team’s name on their ticket, customers can see its ratings."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:-1
msgid "View of the helpdesk ticket from a user’s portal emphasizing the link to the helpdesk team\n"
"in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:51
msgid ":doc:`../advanced/close_tickets`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:3
msgid "Start receiving tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:5
msgid "Odoo *Helpdesk* offers multiple channels where customers can reach out for assistance, such as email, live chat, and through a website's submission form. The variety of these contact options provides customers with multiple opportunities to receive support quickly, while also giving the support team the ability to manage multi-channel support tickets from one central location."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:11
msgid "Enable channel options to submit tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:13
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Teams` and choose an existing team, or click :guilabel:`New` to :doc:`create a new team <getting_started>`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:16
msgid "On the team's settings page, scroll down to :guilabel:`Channels`. Select one or more channel(s) to enable by checking the respective box(es)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:19
msgid ":guilabel:`Email Alias`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:20
msgid ":guilabel:`Website Form`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:21
msgid ":guilabel:`Live Chat`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:24
msgid "Email Alias"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:26
msgid "The *Email Alias* setting automatically creates tickets from messages sent to that team's specified email alias."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:29
msgid "To alter a *Helpdesk* team's email alias, navigate to the :guilabel:`Teams` settings page. Find :guilabel:`Email Alias`, under the :guilabel:`Channels` heading, and then type in the desired team alias in the field."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:33
msgid "When a new *Helpdesk* team is created, an :guilabel:`Email Alias` is created, as well. This alias can be changed in the :guilabel:`Alias` field."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:37
msgid "If the database does not have a custom domain already configured, click :guilabel:`Configure a custom domain` to be redirected to the :guilabel:`Settings` page. From there, enable :guilabel:`Custom Email Servers`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1
msgid "View of the settings page of a helpdesk team emphasizing the email alias feature in Odoo\n"
"Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:46
msgid "When an email is received, the subject line from the email becomes the title of a new *Helpdesk* ticket. The body of the email is also added to the ticket under the :guilabel:`Description` tab and in the ticket's :guilabel:`Chatter` section."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:51
msgid "The configuration steps outlined above are for **Odoo Online** and **Odoo.sh** databases. For **On-premise** databases, additional configuration for custom email servers and email aliases may be required."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:56
msgid "Website Form"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:58
msgid "Enabling the *Website Form* setting adds a new page to the website with a customizable form. A new ticket is created once the required form fields are filled out and submitted."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:61
msgid "To activate the website form, navigate to a team's settings page under :menuselection:`Configuration --> Teams`. Find the :guilabel:`Website Form` feature under the :guilabel:`Channels` section, and check the box."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:65
msgid "After the feature is activated, click the :guilabel:`Go to Website` smart button at the top of the that :guilabel:`Teams` settings page to view and edit the new website form, which is created automatically by Odoo."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:70
msgid "After enabling the website form, the *Teams* settings page may need to be refreshed before the *Go to Website* smart button appears."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:73
msgid "As well, if a *Help Center* is published, the smart button will navigate there first. Simply click the :guilabel:`Contact Us` button at the bottom of the forum to navigate to the ticket submission form."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1
msgid "View of the settings page of a helpdesk team emphasizing the Go to Website button in\n"
"Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:83
msgid "Customize the website ticket form"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:85
msgid "To customize the default ticket submission form, click the :guilabel:`Edit` button in the upper right corner of the page. Then click on one of the fields in the form."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:88
msgid "Add, remove, or update fields as necessary to alter the information submitted by customers. Fields can be made marked as :guilabel:`Required`, by toggling the switch from gray to blue in the website builder's editor window, located under the :guilabel:`Field` section. As well, other pertinent field information can be edited here, such as:"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:93
msgid ":guilabel:`Type`: which matches an Odoo model value to the field (e.g. `Customer Name`)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:94
msgid ":guilabel:`Input Type`: to determine what time of input the field should be, like `Text`, `Email`, `Telephone` or `URL`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:96
msgid ":guilabel:`Label`: to give the form field a label (e.g. `Full Name`, `Email Address`, etc.). Also control the label position on the form by using the nested :guilabel:`Position` options."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:98
msgid ":guilabel:`Description`: which, optionally, adds an editable line under the input box to provide additional contextual information related to the field."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:100
msgid ":guilabel:`Placeholder`: to add a sample input value."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:101
msgid ":guilabel:`Default value`: to add common use case values that most customers would find valuable"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:102
msgid ":guilabel:`Required`: which sets the field as mandatory before the form can be submitted."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:103
msgid ":guilabel:`Visibility`: to allow for absolute or conditional visibility of the field. Nested options, such as device visibility, appear when certain options are selected."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:107
msgid "Text blocks can be added in the farthest 1/3 column of the ticket form page, next to the ticket form. This is an ideal place to include team information such as additional contact details, hours, or common helpful articles that link to the :guilabel:`Forum`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1
msgid "View of the unpublished website form to submit a ticket for Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:115
msgid "Once the form has been optimized and is ready for public use, :guilabel:`Save` the changes, and then publish the form by clicking on the :guilabel:`Unpublished` button."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:119
msgid "Live Chat"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:121
msgid "The *Live Chat* feature allows website visitors to connect directly with a support agent or chatbot. During these conversations, *Helpdesk* tickets can be instantly created by using the :doc:`response command </applications/websites/livechat/responses>` `/helpdesk`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:125
msgid "To enable *Live Chat*, navigate to the :menuselection:`Configuration --> Teams` list view, select a team, and on the :guilabel:`Teams` settings page, click the check box next to :guilabel:`Live Chat`, under the :guilabel:`Channels` heading."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:130
msgid "If this is the first time *Live Chat* has been enabled on the database, the page may need to be saved manually and refreshed before any further steps can be taken."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:133
msgid "With the :guilabel:`Live Chat` setting engaged, click on :guilabel:`View Channels`. Then, on the :guilabel:`Website Live Chat Channels` dashboard, select the kanban card for the channel that was created for the *Helpdesk* team, or create a :guilabel:`New` one if necessary. When a kanban card is selected, additional options await on the channel's form."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:139
msgid "Customize the live chat channel"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:141
msgid "When an individual channel is clicked on the :guilabel:`Website Live Chat Channels` dashboard, Odoo directs the page to the channel form. From there, the :guilabel:`Channel Name` can be edited, however Odoo names this to match the *Helpdesk* team's kanban pipeline, by default."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:146
msgid "If a *Helpdesk* team is named `Customer Care`, a *Live Chat* channel will be created with the same name."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:0
msgid "View of the kanban cards for the available Live Chat channels."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:153
msgid "On the channel form, navigate through the tabs to complete the setup."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:156
msgid "Add operators"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:158
msgid "*Operators* are the users who will act as agents and respond to live chat requests from customers. The user who originally created the live chat channel will be added by default."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:161
msgid "To add additional users, navigate and click on the live chat channel from the :guilabel:`Website Live Chat Channels` dashboard, and on the :guilabel:`Operators` tab, click :guilabel:`ADD`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:164
msgid "Then, click the check box next to the users to be added, and click :guilabel:`SELECT`. :guilabel:`New` operators can be created and added to the list, as well, by filling out the :guilabel:`Create Operators` form and then clicking :guilabel:`SAVE & CLOSE` (or :guilabel:`SAVE & NEW` for multiplerecord creations)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:169
msgid "As well, current operators can be edited or removed by clicking on their respective boxes in the :guilabel:`Operators` tab, and then adjusting their form values, or by using one of the form buttons located at the bottom of the form, such as :guilabel:`REMOVE`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:174
msgid "Users can add themselves as an operator by clicking the :guilabel:`Join` button on a *Live Chat* channel."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:178
msgid "Modify channel options"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:180
msgid "The :guilabel:`Options` tab contains the visual and text settings for the live chat window."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:182
msgid "Change the text in the :guilabel:`Text of the Button` field to update the greeting displayed in the text bubble when the live chat button appears on the website."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:185
msgid "Edit the :guilabel:`Welcome Message` to change the message a visitor sees when they open the chat window. This message will appear as though it is sent by a live chat operator, and should be an invitation to continue the conversation."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:189
msgid "Edit the :guilabel:`Chat Input Placeholder` to change the text that appears in the box where visitors will type their replies."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:192
msgid "Change the :guilabel:`Livechat Button Color` and and the :guilabel:`Channel Header Color` by clicking a color bubble to open the color selection window. Click the refresh icon to the right of the color bubbles to reset the colors to the default selection."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:197
msgid "Color selection, for the button or header, can be made manually, or through RGB, HSL or HEX code selection. Different options will be available, depending on your operating system."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:201
msgid "Create channel rules"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:203
msgid "The :guilabel:`Channel Rules` tab determines when the live chat window opens on the website by logic of when a :guilabel:`URL Regex` action is triggered (e.g., a page visit)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:206
msgid "Edit existing rules, or create a new one by clicking :guilabel:`Add a line`, and fill out the pop-up form details based on how the rule should apply."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:209
msgid "If a :guilabel:`Chatbot` will be included on this channel, select it from the dropdown. If the chatbot will only be active when no operators are available, check the box labeled :guilabel:`Enabled only if no operator`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:214
msgid "If a chatbot is added to a live chat channel, then 3 new smart buttons will appear on the channel settings form: :guilabel:`Chatbots`, :guilabel:`Sessions`, and :guilabel:`% Happy`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:217
msgid "The :guilabel:`Chatbots` smart button is where the chatbot can be programmed with a :guilabel:`Script`. Each line in the :guilabel:`Script` contains a :guilabel:`Message`, :guilabel:`Step Type`, :guilabel:`Answers`, and conditional :guilabel:`Only If` logic that applies when certain pre-filled answers are chosen. To create more steps in the :guilabel:`Script`, click :guilabel:`Add a line` and fill out the script steps form according to the desired logic."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:223
msgid ":guilabel:`Sessions` is where live chat sessions are recorded in order of descending :guilabel:`Session Date`, by default. Each record includes the :guilabel:`Attendees` involved in the live chat session, the :guilabel:`# Messages`, as well as any :guilabel:`Rating` that was received when the session ended."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:227
msgid "The :guilabel:`% Happy` smart button includes a log of ratings that were left by live chat attendees, and are labeled by date, time, and the support agent who was responsible for the live chat session."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:231
msgid "Add the URL for the pages this channel will be applied to in the :guilabel:`URL Regex` field. If this channel will only be available to users in specific countries, add them to the :guilabel:`Country` field. If this field is left blank, the channel will be available to all site visitors."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:241
msgid "Use the live chat widget"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:243
msgid "The :guilabel:`Widget` tab on the live chat channel form offers an embeddable website widget, or a shortcode for instant customer/supplier access to a live chat window."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:246
msgid "The live chat :guilabel:`Widget` can be applied to websites created through Odoo by navigating to the :menuselection:`Website --> Configuration --> Settings`. Then scroll to the :guilabel:`Live Chat` section, and select the channel to add to the site. Click :guilabel:`Save` to apply."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:250
msgid "To add the widget to a website created on a third-party platform, click :guilabel:`COPY` and paste the code into the `<head>` tag on the site."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:253
msgid "Likewise, to send a live chat session to a customer or supplier, click the second :guilabel:`COPY` button which contains a link to join directly."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:257
msgid "Create a support ticket from a live chat session"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:259
msgid "Once live chat is enabled, operators will be able to communicate with site visitors in real time."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261
msgid "During the conversation, an operator can use the shortcut :doc:`command </applications/websites/livechat/responses>` `/helpdesk` to create a ticket without leaving the chat window. The transcript from the conversation will be added to the new ticket, under the :guilabel:`Description` tab."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:267
msgid "Prioritizing tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:269
msgid "All tickets include a :guilabel:`Priority` field. The highest priority tickets will appear at the top of the kanban and list views."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1
msgid "View of a team's kanban view and the prioritized tasks in Odoo Helpdesk."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:276
msgid "The priority levels are represented by stars:"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:278
msgid "0 stars = *Low Priority*"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:279
msgid "1 star = *Medium Priority*"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:280
msgid "2 stars = *High Priority*"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:281
msgid "3 stars = *Urgent*"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:283
msgid "Tickets will be set to low priority (0 stars) by default. To change the priority level, select the appropriate number of stars on the kanban card, or on the ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:287
msgid "As priority levels can be used as criteria for assigning :doc:`SLAs <sla>`, changing the priority level of a ticket can alter the :abbr:`SLA (Service Level Agreement)` deadline."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:291
msgid ":doc:`/applications/services/helpdesk/advanced/close_tickets`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:292
msgid ":doc:`/applications/general/email_communication/email_servers`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293
msgid ":doc:`/applications/websites/livechat`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:3
msgid "Reports for a Better Support"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:5
msgid "An efficient customer service solution should have a built-in reporting option. Reports allow you to track trends, identify areas for improvement, manage employees’ workloads and, most importantly, meet your customer’s expectations."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:10
msgid "Cases"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:12
msgid "Some examples of the reports Odoo Helpdesk can generate include:"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:14
msgid "The number of tickets *grouped by* team and ticket type."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:17
msgid "In this manner, you are able to evaluate which ticket types have been the most frequent ones, plus the workload of your teams."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:19
msgid "Apply *Time Ranges* if you would like to make comparisons to a *Previous Period* or a *Previous Year*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:-1
msgid "View of a helpdesk ticket analysis by team and ticket type in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:25
msgid "The number of tickets closed per day, per team."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:27
msgid "Get an overview of how many requests each team is closing per day in order to measure their performance. Identify productivity levels to understand how many requests they are able to handle."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:-1
msgid "View of a helpdesk ticket analysis by team and close date in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:35
msgid "Filter it by *Assignee* to see Key Performance Indicators (KPI) per agent."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:37
msgid "The number of hours tickets are taking to be solved, grouped by team and ticket type."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:39
msgid "Check if your expectations are met by *measuring* the *Time to close (hours)*. Your customers not only expect fast responses but they also want their issues to be handled quickly."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:-1
msgid "View of helpdesk ticket analysis of the hours to close by ticket type and team in\n"
"Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:48
msgid "Save filters"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:50
msgid "Save the filters you use the most and avoid having to reconstruct them every time they are needed. To do so, set the groups, filters, and measures needed. Then, go to *Favorites*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:-1
msgid "View of helpdesk ticket analysis emphasizing the option to add a filter as a favorite one\n"
"in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:59
msgid ":doc:`receiving_tickets`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/reports.rst:60
msgid ":doc:`sla`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:3
msgid "Service Level Agreements (SLA)"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:5
msgid "A Service Level Agreement (SLA) defines the level of service a customer can expect from a supplier. SLAs provide a timeline that tells customers when they can expect results, and keeps the support team on target."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:10
msgid "Create a new SLA policy"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:12
msgid "To create a new :abbr:`SLA (Service Level Agreement)` Policy, navigate to the team's page under :menuselection:`Helpdesk --> Configuration --> Teams`. Select a team, scroll to the :guilabel:`Performance` section, and then check the selection box next to :guilabel:`SLA Policies` to enable it for that specific team."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of a team page in Helpdesk focusing on the SLA Policies setting"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:22
msgid "The value indicated next to the :guilabel:`Working Hours` field is used to determine the deadline for :abbr:`SLA (Service Level Agreement)` policies. By default, this is determined by the value set in the :guilabel:`Company Working Hours` field under :menuselection:`Settings app --> Employees --> Work Organization`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:27
msgid "To create a new policy, click the smart button on the team`s settings page or go to :menuselection:`Helpdesk --> Configuration --> SLA Policies`, and click :guilabel:`New`. Start by entering a :guilabel:`Title` and a :guilabel:`Description` for the new policy, and proceed to fill out the form using the steps below."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:33
msgid "Define the criteria for an SLA policy"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:35
msgid "The :guilabel:`Criteria` section is used to identify what tickets this policy will be applied to. Fill out the following fields to adjust the selection criteria:"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:38
msgid ":guilabel:`Team`: a policy can only be applied to one team. *This field is required.*"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:39
msgid ":guilabel:`Priority`: the priority level for a ticket is identified by selecting the number of stars representing the priority level on the kanban card or the ticket itself. The :abbr:`SLA (Service Level Agreement)` will only be applied once the priority level has been updated on the ticket to match the :abbr:`SLA (Service Level Agreement)` criteria. If no selection is made in this field, this policy will only apply to tickets marked as `Low Priority` (zero stars)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:44
msgid ":guilabel:`Types`: ticket types can be helpful when indicating when a ticket is a customer question, that can be solved with a quick response, or an issue, that may require additional investigation. Multiple ticket types can be selected for this field. If no selection is made, this policy will apply to all ticket types."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:48
msgid ":guilabel:`Tags`: tags are applied to briefly indicate what the ticket is about. Multiple tags can be applied to a single ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:50
msgid ":guilabel:`Customers`: individual contacts or companies may be selected in this field."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:51
msgid ":guilabel:`Sales Order Items`: this field is available only if a team has the *Timesheets* app enabled. This allows the ticket to tie directly to a specific line on a sales order, which must be indicated on the ticket in the :guilabel:`Sales Order Item` field."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:56
msgid "Unless otherwise indicated, multiple selections can be made for each field. (i.e. multiple :guilabel:`Tags` can be included in a policy, but only one :guilabel:`Priority` level)"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of a blank SLA policy record"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:64
msgid "Establish a target for an SLA policy"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:66
msgid "The :guilabel:`Target` is the stage a ticket needs to reach, and the time alloted to reach that stage, in order to satisfy the :abbr:`SLA (Service Level Agreement)` policy. Any stage assigned to a team may be selected for the :guilabel:`Reach Stage` field. Time spent in stages selected in :guilabel:`Excluding Stages` will not be included in the calculation of the :abbr:`SLA (Service Level Agreement)` deadline."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:73
msgid "An :abbr:`SLA (Service Level Agreement)` titled `8 Hours to Close` tracks the working time before a ticket is completed, and would have `Solved` as the :guilabel:`Reach Stage`. However, if the :abbr:`SLA (Service Level Agreement)` was titled `2 Days to Start`, it tracks the working time before work on a ticket has begun, and would have `In Progress` as the :guilabel:`Reach Stage`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:79
msgid "Meeting SLA deadlines"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:81
msgid "Once it is determined that a ticket fits the criteria of an :abbr:`SLA (Service Level Agreement)` policy, a deadline is calculated. The deadline is based on the creation date of the ticket, and the targeted working hours. The deadline is then added to the ticket, as well as a white tag indicating the name of the :abbr:`SLA (Service Level Agreement)` applied."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:91
msgid "If a ticket fits the criteria for more than one :abbr:`SLA (Service Level Agreement)`, the earliest occurring deadline will be displayed on the ticket. Once that deadline has passed, the next deadline will be displayed."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:95
msgid "Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the :abbr:`SLA (Service Level Agreement)` tag turns green, and the :guilabel:`Deadline` field disappears from view on the."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:102
msgid "If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level Agreement)` has failed, the red tag will stay on the ticket, even after the ticket is moved to the :guilabel:`Reach Stage`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of a ticket's form with a failing and passing SLA in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:112
msgid "Analyzing SLA performance"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:114
msgid "The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA (Service Level Agreement)` is fulfilled, as well as the success rate of individual policies. Navigate to the report and corresponding pivot table by going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:120
msgid "Using the Pivot view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:122
msgid "By default, the report is displayed in a :guilabel:`Pivot` view, and is filtered to show the number of SLAs failed and the failure rate over the last 30 days, grouped by team."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of the SLA status analysis report in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:129
msgid "To add the number of SLAs passed or in progress, click the :guilabel:`Measures` button to reveal a drop-down menu of reporting criteria, and choose from the options available based on the measurements preferred. Whenever a measurement is picked, a check mark will appear in the drop-down menu to indicate that that measurement is included, and a corresponding new column will emerge in the pivot table to show the relevant calculations."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:135
msgid "To add a group to a row or column, click the plus :guilabel:` + ` button next to :guilabel:`Total`, and then select one of the groups. To remove one, click the minus :guilabel:` - ` button and deselect."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:140
msgid "Using the Graph view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:142
msgid "The :guilabel:`Status Analysis` report can also be viewed as a :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between these views by selecting the appropriate icon at the top of the chart."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:148
msgid "Bar Chart"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "View of the SLA status analysis report in bar view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:154
msgid "Line Chart"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "View of the SLA status analysis report in line view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:160
msgid "Pie Chart"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:0
msgid "View of the SLA status analysis report in pie chart view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:167
msgid "Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed :guilabel:`Stacked`. This presents two or more groups to appear on top of each other instead of next to each other, making it easier to compare data."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:172
msgid "Using the Cohort view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:174
msgid "The :guilabel:`Cohort` view is used to track the changes in data over a period of time. To display the :guilabel:`Status Analysis` report in a :guilabel:`Cohort` view, click the icon in the top right corner above the chart."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of the SLA status analysis report in cohort view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:183
msgid ":ref:`Reporting views <reporting/views>`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:184
msgid ":doc:`Allow customers to close their tickets </applications/services/helpdesk/advanced/close_tickets>`"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice.rst:5
msgid "Timesheet and Invoice"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:3
msgid "Invoice Time Spent on Tickets (Prepaid Support Services)"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:5
msgid "Have the option to work with prepaid support services, meaning that a sales order and a corresponding invoice are issued and, once the service is done, you can deduct the time spent. Odoo allows it to happen because the applications are fully integrated, resulting in faster responses to your customer needs."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:14
msgid "Step 1: Set up a helpdesk team"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:17
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, create or edit an existing team, and enable *Timesheet on Ticket* and *Time Reinvoicing*."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:20
msgid "Select or create a project under *Timesheet on Ticket*. The selected/created is the one at which employees timesheet on by default. However, it can be ultimately modified on each ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1
msgid "View of a helpdesk team settings page emphasizing the timesheet on ticket and time\n"
"reinvoicing features in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:28
msgid "Step 2: Set up a service"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:31
msgid "Go to :menuselection:`Sales --> Configuration --> Settings` and enable *Units of Measure* to optionally be able to choose *hours* (for example) as the unit of measure of your service."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:33
msgid "Then, go to :menuselection:`Sales --> Products --> Products`, create or edit an existing one, and set its *Product Type* as *Service*."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1
msgid "View of a product's form emphasizing the product type and unit of measure fields in Odoo\n"
"Sales"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:40
msgid "Now, select the invoicing management you would like to have under the *Sales* tab. We recommend the following configuration:"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1
msgid "View of a product form and the invoicing options under the tab sales in Odoo Sales"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:47
msgid "This configuration ensures that the customer is invoiced by the number of hours predicted in the sales order, meaning that less or extra hours recorded are not taken into account. It also ensures that every time a sales order is confirmed, a new task is created under the right project, automating the process."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:53
msgid "We recommend setting up a specific project, as it was done for this flow example. The important thing to remember is that the sales order item needs to be set on the corresponding project or task, in order to reinvoice the time spent on a ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:58
msgid "Prevision an invoice and record time"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:61
msgid "Step 1: Place an order"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:63
msgid "Go to :menuselection:`Sales --> Orders --> Orders` and create one for the helpdesk service product you have previously set up, with the customer who needs the ticket to be opened. Set the number of hours needed to assist the customer and *Confirm* the order."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1
msgid "View of a sales order emphasizing the order lines in Odoo Sales"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:72
msgid "Step 2: Invoice the customer"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:74
msgid "In *Sales*, select the respective sales order to *Create Invoice*."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1
msgid "View of a sales order emphasizing the create invoice button in Odoo Sales"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:82
msgid "Step 3: Link the task to the ticket"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:84
msgid "Now, in *Helpdesk*, create or edit the respective ticket and link it to the task created by the confirmation of the sales order."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1
msgid "View of a helpdesk ticket emphasizing the field task in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:92
msgid "Step 4: Record the time spent"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:94
msgid "Still on the respective helpdesk ticket, record the hours performed under the *Timesheets* tab."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1
msgid "View of a helpdesk ticket emphasizing the timesheets tab in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:100
msgid "Note that the hours recorded on the ticket form are shown on the *Delivered* column in the sales order."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:-1
msgid "View of a sales order emphasizing the delivered column in Odoo Sales"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:108
msgid "Hours recorded on the ticket are automatically shown in *Timesheets* and on the dedicated task."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:111
msgid ":doc:`reinvoice_from_project`"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:112
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:104
msgid ":doc:`/applications/inventory_and_mrp/inventory/management/products/uom`"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:3
msgid "Invoice Time Spent on Tickets (Postpaid Support Services)"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:5
msgid "The :guilabel:`Timesheets` integration provides more control and transparency over how clients are charged, and what they're specifically billed for."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:8
msgid "In Odoo, the Helpdesk agent can use the ticket to record timesheets. Once a ticket is solved, the client can be billed for the time spent on the ticket. Odoo will pull from the ticket's timesheet to accurately bill the client."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:15
msgid "To turn on the :guilabel:`Timesheets` feature, go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, select a Helpdesk team, and then, click :guilabel:`Edit`. Next, enable the options :guilabel:`Timesheets` and :guilabel:`Time Billing`. Then, click :guilabel:`Save` to apply these changes to the Helpdesk team settings."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:20
msgid "Once the :guilabel:`Timesheets` feature is enabled, a :guilabel:`Project` drop-down option will appear below :guilabel:`Timesheets`. The :guilabel:`Project` drop-down option will automatically be set to a project that Odoo created for the Helpdesk team. The tickets' timesheets will be stored in the selected project."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:26
msgid "Create a sales order"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:28
msgid "After a ticket comes into the pipeline, go to :menuselection:`Sales --> Create`. Then, add the customer from the ticket to the :guilabel:`Customer` field in the new quotation. In the :guilabel:`Order Lines` tab, create or select a product to charge the customer for the time spent on their Helpdesk ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:33
msgid "If creating a new product from the sales order form, first give the product a name by typing it in the :guilabel:`Product` column. Then, click :guilabel:`Create and edit`."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:36
msgid "First, in the :guilabel:`General Information` tab, set the :guilabel:`Product Type` to :guilabel:`Service` and the :guilabel:`Sales Price` to the Helpdesk agent's service rate. Then, set the :guilabel:`Invoicing Policy` to :guilabel:`Based on Timesheets`. Finally, click :guilabel:`Save` to create the new product and add it to the quotation."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:41
msgid "Once the product is added, click :guilabel:`Confirm` to turn the quotation into a sales order."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:-1
msgid "Create a sales order and add a product."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:48
msgid "Record a timesheet"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:50
msgid "To record a timesheet, jump back to the Helpdesk ticket by going to the :guilabel:`Helpdesk` dashboard, clicking :guilabel:`Tickets` on the team's card, and locating the correct ticket. Then, click :guilabel:`Edit` and use the :guilabel:`Timesheets` tab to record the time spent on the ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:-1
msgid "Record time spent on a ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:60
msgid "The ticket's timesheets can be recorded before or after the sales order is made, the order doesn't matter."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:64
msgid "Link the Helpdesk ticket to the SO"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:66
msgid "To link the :guilabel:`Sales Order` to the ticket, start on the ticket form and click :guilabel:`Edit`. Next, select the :guilabel:`Sales Order` that was created earlier from the :guilabel:`Sales Order Item` drop-down menu. Odoo will automatically filter the options to only show sales orders that are connected to the ticket's customer. Lastly, click :guilabel:`Save` to connect the ticket and the :guilabel:`Sales Order Item`."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:-1
msgid "Link the SO item to the ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:77
msgid "The :guilabel:`Sales Order Item` can be connected to the ticket before or after any timesheets are recorded, the order doesn't matter."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:81
msgid "Modify billing rates"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:83
msgid "If a timesheet entry is recorded, but the agent does not want to bill the client for that time, go to the :guilabel:`Timesheets` tab and toggle on the visibility of the :guilabel:`Sales Order Item` column. When filling out the information for the timesheet entry, make sure to leave the non-billable timesheet entry's :guilabel:`Sales Order Item` field blank."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:88
msgid "If the agent wants to charge a different rate for a timesheet entry, first, add a new product to the connected :abbr:`SO (Sales Order)` priced at the new rate. Then, select the new product in the timesheet entry's :guilabel:`Sales Order Item` field."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:93
msgid "Create the invoice"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:95
msgid "When the Helpdesk ticket is completed and the client is ready to be billed for time, begin by clicking the :guilabel:`Sales Order` smart button on the ticket form to navigate to the sales order. The :guilabel:`Delivered` column should match the number of hours recorded on the ticket's timesheet. After checking and filling out the relevant information, click :guilabel:`Create Invoice` to bill the client for the time spent on the ticket. Odoo will automatically generate an invoice to send to the client and the Helpdesk ticket can officially be closed."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:103
msgid ":doc:`invoice_time`"
msgstr ""
#: ../../content/applications/services/project.rst:8
msgid "Project"
msgstr ""
#: ../../content/applications/services/project.rst:10
msgid "Odoo Project is a tool to manage your ongoing projects. Schedule tasks, assign activities to coworkers, and keep track of each project's profitability."
msgstr ""
#: ../../content/applications/services/project.rst:14
#: ../../content/applications/services/timesheets.rst:11
msgid "`Odoo Tutorials: Project and Timesheets <https://www.odoo.com/slides/project-and-timesheets-21>`_"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:3
msgid "Project management"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:5
msgid "Odoo Project uses the **Kanban** project management system. This means all projects are broken down into tasks, which are categorized on a whiteboard according to what production phase they are in."
msgstr ""
#: ../../content/applications/services/project/project_management.rst:8
msgid "Did you know?"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:10
msgid "The word **Kanban** comes from Japanese and refers to the \"visual board\" management method."
msgstr ""
#: ../../content/applications/services/project/project_management.rst:13
msgid "`Odoo Tutorials: Kanban Project Management <https://www.odoo.com/slides/slide/kanban-project-management-1664>`_"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:19
msgid "Open the **Project** app and click :guilabel:`Create` to start a new project. Enter a :guilabel:`Name` for your project and click :guilabel:`Create Project`."
msgstr ""
#: ../../content/applications/services/project/project_management.rst:22
msgid "You can customize your existing **projects** from the dashboard by clicking the drop-down toggle button (:guilabel:`⋮`) on your project's **card**."
msgstr ""
#: ../../content/applications/services/project/project_management.rst:-1
msgid "Project card"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:29
msgid "This enables a new menu divided into four parts:"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:31
msgid ":guilabel:`View`: see an overview of your project's components, such as its :guilabel:`Tasks`, :guilabel:`Milestones` and :guilabel:`Project Updates`. Depending on which apps you have activated, more options may be available, such as :guilabel:`Documents`. All uploaded files can be found under this menu, as well as in the **Documents** app, under :guilabel:`Projects`;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:35
msgid ":guilabel:`Reporting`: analyze your project's progress and profitability through graphics and statistics;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:37
msgid "**Color**: make a line of color appear on the left side of the card so that your project is more recognizable;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:39
msgid ":guilabel:`Settings`: you can change the following:"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:41
msgid "the :guilabel:`Name` of the project;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:42
msgid "the :guilabel:`Name of the tasks` found under that project;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:43
msgid "the :guilabel:`Customer` for whom the project is intended;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:44
msgid "the :guilabel:`Tags` used for filtering;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:45
msgid "the :guilabel:`Company` responsible for the project;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:46
msgid "the employee designated as :guilabel:`Project Manager`;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:47
msgid "the :guilabel:`Planned Date` of the project;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:48
msgid "the total :guilabel:`Allocated Hours` for that project."
msgstr ""
#: ../../content/applications/services/project/project_management.rst:50
msgid "Additionally, you can mark the project as :guilabel:`Favorite`, allowing you to find it using the :guilabel:`My Favorites` filter on the Kanban view;"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:-1
msgid "Project settings"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:58
msgid "`Odoo Tutorials: Customize your project <https://www.odoo.com/slides/slide/customize-your-project-1662?fullscreen=1>`_"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:61
msgid "Further settings are available under the :guilabel:`Settings` tab. Most of them are *only* available depending on the activated apps."
msgstr ""
#: ../../content/applications/services/project/project_management.rst:65
msgid "Scheduling activities"
msgstr ""
#: ../../content/applications/services/project/project_management.rst:67
msgid "You can schedule **activities** (ex. :guilabel:`Call`, :guilabel:`Meeting`, etc.) per project by clicking on the **clock** icon on a project. Doing so opens a list with already scheduled activities and allows planning **new** activities by clicking :guilabel:`+ Schedule an activity`. On the pop-up window, select the :guilabel:`Activity Type`, enter a :guilabel:`Summary` for that activity, a :guilabel:`Due Date`, and assign it to an employee. According to the :guilabel:`Activity Type`, you may have **additional options** available."
msgstr ""
#: ../../content/applications/services/project/project_management.rst:75
msgid "If an activity is **already** scheduled, the icon may change to a **phone**, **group of people**, or other."
msgstr ""
#: ../../content/applications/services/project/tasks.rst:5
msgid "Tasks"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:3
msgid "Create Project's Tasks from an Email Alias"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:5
msgid "When you already have an email address that customers know from the top of their heads, changing it is the last thing you want to do. Instead, link that address to your project and transform those conversations into structured work. It automatically creates a task in the first stage of a project."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:11
msgid "Set up an incoming email server"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:14
msgid "On the *Settings* application, enable *External Email Servers* and define the incoming email alias you would like to use."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:15
msgid "**For more information**: :doc:`/applications/general/email_communication/email_servers`"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:18
msgid "Configure the email alias in your project"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:22
msgid "Now that you have the incoming email server set up, go to :menuselection:`Project --> Configuration --> Projects --> Edit`. Under the *Emails* tab, define the wanted email alias and choose the policy to receive a message."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:23
msgid "In addition, you can now directly set it when creating a new project."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:-1
msgid "In the settings of your project, define the emails alias under the tab email in Odoo Project"
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:30
msgid "All the recipients of the email (To/Cc/Bcc) are automatically added as followers of the task."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:32
msgid "The email can be seen under the name of your project on the dashboard."
msgstr ""
#: ../../content/applications/services/project/tasks/email_alias.rst:-1
msgid "View of the email alias chosen on the dashboard view in Odoo Project"
msgstr ""
#: ../../content/applications/services/timesheets.rst:8
msgid "Timesheets"
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:3
msgid "Create Timesheets upon Time Off Validation"
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:5
msgid "Odoo automatically timesheets on project/tasks upon time off requests. This allows for better overall control over the validation of timesheets, as it does not leave place for forgetfulness and questions after hours that have not been timesheeted by the employee."
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:9
msgid "Activate the :ref:`developer mode <developer-mode>`, go to *Timesheets*, and change the *Project* and *Task* set by default, if you like."
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:-1
msgid "View of Timesheets setting enabling the feature record time off in Odoo Timesheets"
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:16
msgid "Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select or create the needed type, and decide if you would like the requests to be validated or not."
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:-1
msgid "View of a time off types form emphasizing the time off requests and timesheets section in\n"
"Odoo Time Off"
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:26
msgid "Now, once the employee has requested his time off and the request has been validated (or not, depending on the setting chosen), the time is automatically allocated on *Timesheets*, under the respective project and task."
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:27
msgid "On the example below, the user requested *Paid Time off* from July 13th to 15th."
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:-1
msgid "View of the time off request form in Odoo Time Off"
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:33
msgid "Considering that validation is not required, the requested time off is automatically displayed in *Timesheets*. If validation is necessary, the time is automatically allocated after the responsible person for validating does it so."
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:-1
msgid "Video of timesheets emphasizing the requested time off from the employee in Odoo Timesheets"
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:41
msgid "Click on the magnifying glass, hovering over the concerned cell, to access all the aggregated data on that cell (day), and see details regarding the project/task."
msgstr ""
#: ../../content/applications/services/timesheets/overview/time_off.rst:-1
msgid "View of the details of a project/task in Odoo Timeheets"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:7
msgid "What can I expect from the support service?"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:11
msgid "5 days a week"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:13
msgid "Your Odoo Online subscription includes **unlimited 24hr support at no extra cost, Monday to Friday**. Our teams are located around the world to ensure you have support, no matter your location. Your support representative could be communicating to you from San Francisco, Belgium, or India!"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:18
msgid "Our support team can be contacted through our `online support form <https://www.odoo.com/help>`__."
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:22
msgid "What kind of support is included?"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:24
msgid "Providing you with relevant material (guidelines, product documentation, etc...)"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:26
msgid "Answers to issues that you may encounter in your standard Odoo database (eg. “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:28
msgid "Questions related to your account, subscription, or billing"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:29
msgid "Bug resolution (blocking issues or unexpected behaviour not due to misconfiguration or customization)"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:31
msgid "Issues that might occur in a test database after upgrading to a newer version"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:33
msgid "*Odoo Support does not make changes to your production database without your agreement and gives you the material and knowledge to do it yourself!*"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:37
msgid ":ref:`upgrade/sla`"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:38
msgid ":doc:`/administration/maintain/supported_versions`"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:42
msgid "What kind of support is not included?"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:44
msgid "Questions that require us to understand your business processes in order to help you implement your database"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:46
msgid "Training on how to use our software (we will direct you to our many resources)"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:47
msgid "Import of documents into your database"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:48
msgid "Guidance on which configurations to apply inside of an application or the database"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:49
msgid "How to set up configuration models (Examples include: Inventory Routes, Payment Terms, Warehouses, etc)"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:51
msgid "Any intervention on your own servers/deployments of Odoo"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:52
msgid "Any intervention on your own third party account (Ingenico, Authorize, UPS, etc)"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:53
msgid "Questions or issues related to specific developments or customizations done either by Odoo or a third party (this is specific only to your database or involving code)"
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:57
msgid "You can get this type of support with a `Success Pack <https://www.odoo.com/pricing-packs>`__. With a pack, one of our consultants will analyze the way your business runs and tell you how you can get the most out of your Odoo Database. We will handle all configurations and coach you on how to use Odoo."
msgstr ""
#: ../../content/services/support/what_can_i_expect.rst:63
msgid ":doc:`/administration/upgrade`"
msgstr ""
Reference in New Issue View Git Blame Copy Permalink