documentation/locale/it/LC_MESSAGES/services.po

1250 lines
46 KiB
Plaintext
Raw Permalink Normal View History

# 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.
#
# Translators:
# Giovanni Perteghella <giovanni@perteghella.org>, 2021
# Paolo Valier, 2021
# Sergio Zanchetta <primes2h@gmail.com>, 2022
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-08-10 09:10+0000\n"
"PO-Revision-Date: 2021-05-18 05:18+0000\n"
"Last-Translator: Sergio Zanchetta <primes2h@gmail.com>, 2022\n"
"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: it\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../content/applications/services.rst:5
msgid "Services"
msgstr "Servizi"
#: ../../content/applications/services/fsm.rst:8
msgid "Field Service"
msgstr "Assistenza sul campo"
#: ../../content/applications/services/fsm.rst:11
msgid ""
"`Odoo Tutorials: Field Service <https://www.odoo.com/slides/field-"
"service-49>`_"
msgstr ""
#: ../../content/applications/services/fsm/helpdesk.rst:5
#: ../../content/applications/services/helpdesk.rst:8
msgid "Helpdesk"
msgstr "Assistenza clienti"
#: ../../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:4
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:8
msgid "Configure the helpdesk team"
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:9
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select"
" a team and enable *Onsite Interventions*."
msgstr ""
#: ../../content/applications/services/fsm/helpdesk/plan_onsite.rst:16
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/sales.rst:5
msgid "Sales"
msgstr "Vendita"
#: ../../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:4
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:8
msgid "Configure a product"
msgstr "Configurazione prodotto"
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:9
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:11
msgid ""
"Under the *General Information* tab, select *Service* as *Product Type*."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:13
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:17
msgid "Select your *Project*."
msgstr ""
#: ../../content/applications/services/fsm/sales/onsite_tasks_from_sales_orders.rst:19
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:25
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/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 "Avanzate"
#: ../../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. Odoos Helpdesk application allows you to generate credit notes, manage"
" returns, products, repairs, grant coupons, and even plan onsite "
"interventions from a tickets 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 "Consente i resi dei prodotti dalle segnalazioni"
#: ../../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 "Allow Customers to Close their Tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
msgid ""
"Allowing customers to close their tickets gives them autonomy and minimize "
"misunderstandings about when an issue is considered solved, or not. It makes"
" communication and actions more efficient."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:9
msgid "Configure the feature"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:11
msgid ""
"To configure the feature go to :menuselection:`Helpdesk --> Settings --> "
"Helpdesk Teams --> Edit` and enable *Ticket closing*."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:18
msgid ""
"In order to designate to which stage the ticket migrates to once it is "
"closed, go to :menuselection:`Helpdesk --> Overview --> Tickets`."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:25
msgid ""
"You can either create a new Kanban stage or work with an existing one. For "
"both scenarios, go to :menuselection:`Helpdesk --> Settings --> Edit Stage` "
"and enable *Closing Stage*."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:32
msgid ""
"If a closing stage is not specified, by default, the ticket is moved to the "
"last stage; contrarily, if you have more than one stage set as closing, the "
"ticket is put in the first one."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:36
msgid "The Costumer Portal"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:38
msgid ""
"Now, once the user logs into his Portal, the option *Close this ticket* is "
"available."
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:45
msgid "Get reports on tickets closed by costumers"
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:47
msgid ""
"To do an analysis of the tickets that have been closed by costumers go to "
":menuselection:`Helpdesk --> Reporting --> Tickets --> Filters --> Add "
"Custom filter --> Closed by partner --> Applied`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview.rst:5
#: ../../content/applications/services/timesheets/overview.rst:5
msgid "Overview"
msgstr "Panoramica"
#: ../../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 "Forum"
#: ../../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: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: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: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 "E-learning"
#: ../../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: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: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:73
msgid "Todo"
msgstr "Da fare"
#: ../../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"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:5
msgid ""
"Helpdesk teams provide your customers with support to queries or errors they"
" might encounter while using your product/service. Therefore, a successful "
"scheme where you can organize multiple teams with their customized pipeline,"
" visibilities settings, and ticket traceability is essential."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:10
msgid "Set up teams"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:12
msgid ""
"To modify or create teams, go to :menuselection:`Helpdesk --> Configuration "
"--> Helpdesk Teams`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:14
msgid ""
"Setting up multiple teams allows you to group tickets by your channels "
"(example: BE/US), or by your support services' types (example: IT, "
"accounting, admin, etc.)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:21
msgid "Teams productivity and visibility"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:23
msgid ""
"Teams can have individual *Assignment Methods* to ensure that tickets get "
"redirected to the right person:"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:26
msgid ""
"*Manually*: tickets are manually assigned, allowing employees to manage "
"their own workload and target tickets they are experts at;"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:28
msgid ""
"*Random*: tickets are randomly assigned and everyone gets the same amount. "
"This method ensures that all tickets are handled as the assignment happens "
"automatically;"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:30
msgid ""
"*Balanced*: tickets are assigned to the person with the least amount of "
"tickets so that everyone fairly gets the same amount. Thereby, you ensure "
"that all tickets get to be taken care of."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:40
msgid ""
"For the *Random* and *Balanced* assignment methods, you can set the *Team "
"Members* among whom tickets are assigned. Leave the field empty to include "
"all employees (with the proper access rights)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:43
msgid ""
"The *Team Visibility* feature allows you to specify who can see and access "
"the teams tickets. Therefore, tickets with sensible information are only "
"seen by the right people. Leave the field empty to include all employees "
"(with the proper access rights)."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:46
msgid "Set up stages and share it among teams"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:48
msgid ""
"To set up stages, go to :menuselection:`Helpdesk --> Configuration --> "
"Stages`. Then, create and/or edit stages as you need and set specific teams "
"to use certain stages under *Team*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:55
msgid ""
"Stages can be shared between one or multiple teams, allowing you to adapt "
"the pipeline to your individual needs. They also apply a visibility and "
"access rule, as other teams are not able to see or use the stage."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/getting_started.rst:64
msgid ":doc:`/applications/general/users`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:3
msgid "Ratings"
msgstr "Valutazioni"
#: ../../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 customers 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: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: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: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"
" teams name on their ticket, customers can see its ratings."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/ratings.rst:51
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:88
#: ../../content/applications/services/helpdesk/overview/sla.rst:47
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 ""
"Offering a variety of channels from where your customers can contact you "
"grants them flexibility and the right to choose the best one for themselves."
" And, in order to make sure inquiries across all channels get addressed, it "
"is essential to have a solution where all interactions come in one place."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:11
msgid "Channels options to submit tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:13
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, and "
"enable the following features as you want them to be available to your "
"users."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:21
msgid "Email Alias"
msgstr "Alias e-mail"
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:24
msgid ""
"Let your customers submit tickets by sending an email to your support email "
"address. The subject line of the email becomes the title of the ticket and "
"the content is shown in the Chatter."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:26
msgid ""
"Select *Configure domain name* to be redirected to *Settings* and, from "
"there, enable *External Email Servers* to determine or change your *Alias "
"Domain*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:35
msgid ""
"Using your own email server is required to send and receive emails in Odoo "
"Community and Enterprise. Online users benefit from a ready-to-use email "
"server."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:39
msgid "Website Form"
msgstr "Modulo del sito web"
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:41
msgid ""
"Allow your customers to submit a ticket by filling in a form through your "
"website."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:42
msgid ""
"Once the feature is activated, get redirected to your website by clicking on"
" *Go to Website*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:49
msgid ""
"From the website page customize the form as you like. Then, publish it by "
"clicking on *Unpublished*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:56
msgid "Live Chat"
msgstr "Chat dal vivo"
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:59
msgid ""
"Through live interactions with your website visitors, helpdesk tickets can "
"be instantly created and redirected to the right person."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:61
msgid ""
"Click on your helpdesk team's name - for the example below: *Customer Care* "
"- and :doc:`set up your channel "
"</applications/websites/livechat/overview/get_started>`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:68
msgid ""
"Now, your operators can create tickets by using the :doc:`command "
"</applications/websites/livechat/overview/responses>` */helpdesk "
"(subject_of_ticket)*."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:72
msgid "Prioritize tickets"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:74
msgid ""
"Use the stars to prioritize your tickets. The most urgent ones appear at the"
" top of your list on the Kanban view."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:77
msgid "1 star = *Low priority*"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:78
msgid "2 stars = *High priority*"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:79
msgid "3 stars = *Urgent*"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:87
#: ../../content/applications/services/helpdesk/overview/reports.rst:60
msgid ":doc:`sla`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:89
msgid ":doc:`/applications/productivity/discuss/advanced/email_servers`"
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 customers "
"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: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: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: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:59
msgid ":doc:`receiving_tickets`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:3
msgid "Service Level Agreements (SLA)"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:5
msgid ""
"Service Level Agreements (SLA) are commitments you make with your customers "
"to outline how a service is delivered. It bolsters trust between you and "
"your customers as it makes clear what needs to be done, to what standard, "
"and when."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:10
msgid "Create your policies"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:13
msgid ""
"First, enable the feature on the settings of the team you would like "
"policies to be applied, going to :menuselection:`Helpdesk --> Configuration "
"--> Helpdesk Teams`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:15
msgid ""
"Create your policies through the teams settings page or go to "
":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:23
msgid ""
"Choose to which **Team** the policy is relevant and the **Minimum Priority**"
" a ticket needs to have for the policy to be applied."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:27
msgid ""
"**Target** is the stage a ticket needs to reach within the period defined to"
" satisfy the SLA. The period is based on the tickets creation date, and a "
"deadline is set on the tickets form once it matches an SLA policy rule. If "
"a ticket has more than one policy applied to it, the closest deadline of all"
" SLAs is the one considered."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:29
msgid ""
"When a ticket has satisfied an SLA policy, the SLA tag appears in green and "
"the deadline field is not shown anymore."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:37
msgid "SLA Analysis"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:39
msgid ""
"Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply"
" *Filters* and *Group by* to identify tickets that should be prioritized and"
" keep track of upcoming deadlines."
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: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: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: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: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: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: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: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: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
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 ""
"Directly pull the billable time you have tracked on your helpdesk tickets "
"into sales orders and invoices through a project task. It gives you more "
"control over what you charge your client, and it is more efficient."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:10
msgid "Configuration"
msgstr "Configurazione"
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:13
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk team --> Edit`"
" and enable the options *Timesheet on Ticket* and *Time Reinvoicing*."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:15
msgid ""
"Under *Timesheet on Ticket*, choose the *Project* to which tickets (and "
"timesheets) will be linked by default. Open its *External link* to enable "
"the feature *Bill from tasks*."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:22
msgid "Create a sales order and an invoice"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:24
msgid ""
"Now, once you have recorded the time you spent on the helpdesk ticket, under"
" the *Timesheets* tab, access the task clicking on its name."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:31
msgid "*Create Sales Order* and proceed to create the invoice."
msgstr ""
#: ../../content/applications/services/project.rst:8
msgid "Project"
msgstr "Progetto"
#: ../../content/applications/services/project.rst:11
#: ../../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/tasks.rst:5
msgid "Tasks"
msgstr "Lavori"
#: ../../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/productivity/discuss/advanced/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: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/timesheets.rst:8
msgid "Timesheets"
msgstr "Fogli ore"
#: ../../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: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: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: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: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/services/support/what_can_i_expect.rst:7
msgid "What can I expect from the support service?"
msgstr "Cosa attendersi dal servizio di assistenza"
#: ../../content/services/support/what_can_i_expect.rst:11
msgid "5 days a week"
msgstr "5 giorni alla settimana"
#: ../../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 ""
"L'iscrizione a Odoo Online include **supporto illimitato 24/24 senza costi "
"aggiuntivi, dal lunedì al venerdì**. I nostri team sono localizzati in varie"
" parti del mondo per assicurare un supporto completo. L'addetto "
"all'assistenza potrebbe fornire supporto da San Francisco, dal Belgio, "
"oppure dall'India."
#: ../../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 ""
"Il team di supporto può essere contattato attraverso il nostro `modulo "
"online <https://www.odoo.com/help>`__."
#: ../../content/services/support/what_can_i_expect.rst:22
msgid "What kind of support is included?"
msgstr "Tipo di assistenza inclusa"
#: ../../content/services/support/what_can_i_expect.rst:24
msgid ""
"Providing you with relevant material (guidelines, product documentation, "
"etc...)"
msgstr ""
"Messa a disposizione di materiale pertinente (linee guida, documentazione "
"prodotto ecc.)"
#: ../../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 ""
"Risposte a problematiche che si possono incontrare usando il database Odoo "
"ordinario (es. “Non riesco a chiudere il punto vendita” oppure “Non riesco a"
" trovare gli ICP delle vendite”)"
#: ../../content/services/support/what_can_i_expect.rst:28
msgid "Questions related to your account, subscription, or billing"
msgstr "Domande relative all'account, iscrizione o fatturazione"
#: ../../content/services/support/what_can_i_expect.rst:29
msgid ""
"Bug resolution (blocking issues or unexpected behaviour not due to "
"misconfiguration or customization)"
msgstr ""
"Risoluzione bug (problema bloccante o comportamento inatteso non dovuto a "
"errata configurazione o personalizzazione)"
#: ../../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 ""
"Problemi riscontrati in un database di test dopo l'avanzamento a una nuova "
"versione"
#: ../../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:38
msgid "What kind of support is not included?"
msgstr "Tipo di assistenza non inclusa"
#: ../../content/services/support/what_can_i_expect.rst:40
msgid ""
"Questions that require us to understand your business processes in order to "
"help you implement your database"
msgstr ""
"Domande che richiedono la comprensione dei processi aziendali per aiutare a "
"implementare il database"
#: ../../content/services/support/what_can_i_expect.rst:42
msgid ""
"Training on how to use our software (we will direct you to our many "
"resources)"
msgstr ""
"Formazione nell'utilizzo del software (reindirizzamento ai nostri vari "
"esperti)"
#: ../../content/services/support/what_can_i_expect.rst:43
msgid "Import of documents into your database"
msgstr "Importazione di documenti nel database"
#: ../../content/services/support/what_can_i_expect.rst:44
msgid ""
"Guidance on which configurations to apply inside of an application or the "
"database"
msgstr ""
"Assistenza che riguarda la configurazione da utilizzare all'interno di "
"un'applicazione o in un database"
#: ../../content/services/support/what_can_i_expect.rst:45
msgid ""
"How to set up configuration models (Examples include: Inventory Routes, "
"Payment Terms, Warehouses, etc)"
msgstr ""
"Come impostare modelli di configurazione (esempi includono: rotte di "
"magazzino, termini di pagamento, magazzini ecc.)"
#: ../../content/services/support/what_can_i_expect.rst:47
msgid "Any intervention on your own servers/deployments of Odoo"
msgstr "Qualsiasi intervento a server/installazioni Odoo personali"
#: ../../content/services/support/what_can_i_expect.rst:48
msgid ""
"Any intervention on your own third party account (Ingenico, Authorize, UPS, "
"etc)"
msgstr ""
"Qualsiasi intervento ad account personali di terze parti (Ingenico, "
"Authorize, UPS ecc.)"
#: ../../content/services/support/what_can_i_expect.rst:49
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 ""
"Domande o problematiche relative a sviluppi o personalizzazioni particolari "
"effettuati da Odoo o da terze parti (specifici del database o del codice "
"coinvolto)"
#: ../../content/services/support/what_can_i_expect.rst:53
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 ""