documentation/locale/ko/LC_MESSAGES/services.po

# 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:
# JH CHOI <hwangtog@gmail.com>, 2023
# Martin Trigaux, 2023
# Sarah Park, 2023
# 
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-05-15 06:38+0000\n"
"PO-Revision-Date: 2022-10-04 12:54+0000\n"
"Last-Translator: Sarah Park, 2023\n"
"Language-Team: Korean (https://app.transifex.com/odoo/teams/41243/ko/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ko\n"
"Plural-Forms: nplurals=1; plural=0;\n"

#: ../../content/applications/services.rst:5
msgid "Services"
msgstr "서비스"

#: ../../content/applications/services/field_service.rst:8
msgid "Field Service"
msgstr "현장 서비스"

#: ../../content/applications/services/field_service.rst:11
msgid ""
"`Odoo Tutorials: Field Service <https://www.odoo.com/slides/field-"
"service-49>`_"
msgstr "`Odoo 튜토리얼: 현장서비스 <https://www.odoo.com/slides/field-service-49>`_"

#: ../../content/applications/services/field_service/default_warehouse.rst:3
msgid "User default warehouse"
msgstr "사용자 기본 창고 기능"

#: ../../content/applications/services/field_service/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. It also allows field workers to switch between warehouses from "
"their profiles."
msgstr ""
"**기본 창고** 기능을 설정해두면 비품을 밴에 보관해야 하는 현장 기술자나 동일한 창고에서 재보급 작업을 해야하는 분들이 유용하게 "
"사용하실 수 있습니다. 현장 작업자가 프로필 메뉴에서 창고 간 전환을 할 수 있는 기능도 있습니다."

#: ../../content/applications/services/field_service/default_warehouse.rst:9
msgid ""
"Products in sales orders created during field interventions are always "
"pulled from the default warehouse, keeping the inventory accurate."
msgstr "현장 출동 중에 생성된 판매 주문의 제품은 항상 기본 창고에서 가져와 재고를 정확하게 유지합니다."

#: ../../content/applications/services/field_service/default_warehouse.rst:13
msgid ":doc:`../../inventory_and_mrp/inventory`"
msgstr ":doc:`../../inventory_and_mrp/inventory`"

#: ../../content/applications/services/field_service/default_warehouse.rst:16
#: ../../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/field_service/default_warehouse.rst:18
msgid ""
"To set up a user default warehouse, the :doc:`storage locations "
"<../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations>`"
" feature needs to be activated in the **Inventory** app. It is also "
"necessary to have more than one warehouse in your database."
msgstr ""
"사용자 기본 창고를 설정하려면 **재고** 앱에서 :doc:`저장고 위치 "
"<../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations>`"
" 기능을 활성화해야 합니다. 또한 데이터베이스에 있는 창고가 최소 두 개 이상이어야 합니다. "

#: ../../content/applications/services/field_service/default_warehouse.rst:23
msgid ""
"You can either set it up :ref:`for your profile <default-warehouse/my-"
"profile>`, or :ref:`for all users <default-warehouse/all-users>`."
msgstr ""
"두 가지 :ref:`프로필 <default-warehouse/my-profile>` 또는 :ref:`모든 사용자 <default-"
"warehouse/all-users>` 중 하나로 설정할 수 있습니다."

#: ../../content/applications/services/field_service/default_warehouse.rst:27
msgid ""
":doc:`../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations`"
msgstr ""
":doc:`../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations`"

#: ../../content/applications/services/field_service/default_warehouse.rst:32
msgid "For your profile"
msgstr "프로필 설정"

#: ../../content/applications/services/field_service/default_warehouse.rst:34
msgid ""
"To set up a default warehouse for yourself, click your **profile icon** in "
"the upper right corner of the screen, then, go to :menuselection:`My Profile"
" --> Preferences --> Default Warehouse`. Select the default warehouse from "
"the drop-down menu."
msgstr ""
"기본 창고를 직접 설정하려면 화면 오른쪽 상단에 있는 **프로필 아이콘**을 클릭하여 :menuselection:`내 프로필 --> 기본"
" 설정 --> 기본 창고`로 이동합니다. 드롭다운 메뉴에서 기본 창고를 선택합니다."

#: ../../content/applications/services/field_service/default_warehouse.rst:41
msgid "For all users"
msgstr "모든 사용자"

#: ../../content/applications/services/field_service/default_warehouse.rst:43
msgid ""
"To set up a default warehouse for a specific user, go to "
":menuselection:`Settings --> Users --> Manage users`, select 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 ""
"특정 사용자 대상으로 기본 창고를 설정하려면 :menuselection:`설정 --> 사용자 --> 사용자 관리`에서 사용자를 선택한 "
"다음 :guilabel:`개인 설정` 탭으로 이동하십시오. 아래로 스크롤하여 :guilabel:`재고` 드롭다운 메뉴에서 기본 창고를 "
"선택합니다."

#: ../../content/applications/services/field_service/default_warehouse.rst-1
msgid "Selection of a default warehouse on a user profile."
msgstr "사용자 프로필에서 기본 창고 선택."

#: ../../content/applications/services/field_service/default_warehouse.rst:51
msgid "Use in field service tasks"
msgstr "현장 서비스 작업에 사용하기"

#: ../../content/applications/services/field_service/default_warehouse.rst:53
msgid ""
"Once a default warehouse has been configured for a user, the materials used "
"for a sales order related to a Field Service task are pulled from that "
"specific warehouse. Open the related sales order, go to the :guilabel:`Other"
" Info` tab, then scroll down to :guilabel:`Delivery`. The default warehouse "
"is applied correctly."
msgstr ""
"사용자에 대해 기본 창고가 구성되면 현장 서비스 작업의 판매발주서 상에 필요한 자재를 해당하는 특정 창고에서 가져오게 됩니다. 관련된 "
"발주서를 열어서 :guilabel:`기타 정보` 탭에 있는 아래 메뉴 중 :guilabel:`배송`으로 이동합니다. 기본으로 설정해놓은 "
"창고가 올바르게 적용되고 있음을 확인할 수 있습니다."

#: ../../content/applications/services/field_service/default_warehouse.rst:58
msgid ""
"Once the Field Service task is marked as done, the stock of the default "
"warehouse is automatically updated."
msgstr "현장 서비스 작업을 완료로 표시하면 기본 창고에서의 재고 상태가 자동으로 업데이트됩니다."

#: ../../content/applications/services/field_service/onsite_interventions.rst:3
msgid "Onsite interventions planning"
msgstr "현장 출동 계획"

#: ../../content/applications/services/field_service/onsite_interventions.rst:6
msgid "From a sales order"
msgstr "판매주문서에서 가져오기"

#: ../../content/applications/services/field_service/onsite_interventions.rst:8
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/field_service/onsite_interventions.rst:11
msgid ""
"Go to :menuselection:`Field Service --> Configuration --> Products` and "
"create or edit a product."
msgstr ":menuselection:`현장 서비스 --> 구성 --> 품목`으로 이동하여 품목을 생성하거나 편집합니다."

#: ../../content/applications/services/field_service/onsite_interventions.rst:13
msgid ""
"Under the :guilabel:`General Information` tab, select :guilabel:`Service` as"
" :guilabel:`Product Type`."
msgstr ":guilabel:`일반 정보` 탭에서 :guilabel:`서비스`를 :guilabel:`제품 유형`으로 선택하십시오."

#: ../../content/applications/services/field_service/onsite_interventions.rst:15
msgid ""
"Under the :guilabel:`Sales` tab, select :guilabel:`Timesheets on tasks` as "
":guilabel:`Service Invoicing Policy`."
msgstr ""
":guilabel:`판매` 탭에 있는 :guilabel:`업무별 작업시간표`에서 :guilabel:`서비스 청구 방침`을 선택합니다."

#: ../../content/applications/services/field_service/onsite_interventions.rst:17
msgid ""
"Select :guilabel:`Create a task in an existing project` as "
":guilabel:`Service Tracking`."
msgstr ":guilabel:`서비스 추적`에서 :guilabel:`기존 프로젝트에서 작업 생성`을 선택합니다."

#: ../../content/applications/services/field_service/onsite_interventions.rst:18
msgid "Select your :guilabel:`Project`."
msgstr ":guilabel:`프로젝트`를 선택합니다."

#: ../../content/applications/services/field_service/onsite_interventions.rst:19
msgid "If you use them, select your :guilabel:`Worksheet Template`, and save."
msgstr ":guilabel:`워크시트 서식`을 업무에 사용하시고자 한다면 이 항목을 선택하고 저장합니다."

#: ../../content/applications/services/field_service/onsite_interventions.rst-1
msgid ""
"Product configuration to create tasks from sales orders in Odoo Field "
"Service"
msgstr "Odoo 현장서비스 판매주문서에서 작업을 불러오도록 품목 구성하기"

#: ../../content/applications/services/field_service/onsite_interventions.rst:25
msgid ""
"From the :doc:`Sales <../../sales/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 ""
":doc:`판매 <../../sales/sales>` 앱에서 제품으로 견적을 생성하고 확인합니다. 현장서비스 프로젝트 하에서 작업이 "
"자동으로 설정됩니다. 판매주문서에서 직접 사용할 수 있습니다."

#: ../../content/applications/services/field_service/onsite_interventions.rst-1
msgid "Field Service task on a sales order in Odoo Sales"
msgstr "Odoo 판매앱에서의 주문서에 대한 현장서비스 작업"

#: ../../content/applications/services/field_service/onsite_interventions.rst:34
msgid "From helpdesk tickets"
msgstr "헬프데스크 상담 관련"

#: ../../content/applications/services/field_service/onsite_interventions.rst:36
msgid ""
"The integration with the :doc:`Helpdesk <../helpdesk>` app lets your "
"helpdesk team manage intervention requests directly. Planning field service "
"tasks from tickets speeds up your processes."
msgstr ""
"헬프데스크 <../helpdesk>` 앱과의 통합으로 헬프데스크 팀이 출동 요청을 직접 관리할 수 있습니다. 상담 내용을 검토하여 "
"현장서비스 작업을 계획할 수 있기 때문에서 진행 속도가 한층 더 빨라지게 됩니다."

#: ../../content/applications/services/field_service/onsite_interventions.rst:40
msgid "Configure the helpdesk team"
msgstr "헬프데스크 팀 구성"

#: ../../content/applications/services/field_service/onsite_interventions.rst:42
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select"
" a team and enable :guilabel:`Onsite Interventions`."
msgstr ""
":menuselection:`헬프데스크 --> 구성 --> 헬프데스크 팀`으로 이동합니다. 팀을 선택한 후 :guilabel:`현장 "
"출동`을 활성화합니다."

#: ../../content/applications/services/field_service/onsite_interventions.rst-1
msgid "Onsite interventions settings in Odoo Helpdesk"
msgstr "Odoo 헬프데스크에서 현장 출동 항목 설정"

#: ../../content/applications/services/field_service/onsite_interventions.rst:49
msgid ""
"The helpdesk tickets of the team now display the :guilabel:`Plan "
"Intervention` button. Click on it to create a new task under your field "
"service project."
msgstr ""
"이제 헬프데스크 상담 항목에 :guilabel:`출동 계획` 버튼이 표시됩니다. 현장서비스 프로젝트 하에서 새로운 작업을 생성하려면 해당"
" 버튼을 클릭하십시오."

#: ../../content/applications/services/field_service/onsite_interventions.rst-1
msgid "Plan intervention from helpdesk tickets in Odoo Helpdesk"
msgstr "Odoo 헬프데스크앱의 상담 내역에서 출동 계획하기"

#: ../../content/applications/services/helpdesk.rst:8
msgid "Helpdesk"
msgstr "고객센터"

#: ../../content/applications/services/helpdesk.rst:11
msgid "`Odoo Tutorials: Helpdesk <https://www.odoo.com/slides/helpdesk-51>`_"
msgstr "`Odoo 튜토리얼: 헬프데스크 <https://www.odoo.com/slides/helpdesk-51>`_"

#: ../../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 ""
"비즈니스가 커 나감에 따라, 문제가 발생했을 때 헬프데스크에서 이를 효율적으로 기록하고 추적 및 관리할 수 있도록 적절한 도구를 갖추고 "
"있도록 지원하는 것이 무엇보다도 중요합니다. Odoo의 헬프데스크 애플리케이션을 사용하면 대변전표를 생성하거나, 반품된 물건이나 품목 "
"관리, 수리 처리를 지원하며 고객에게 쿠폰을 증정하거나 상담 중에 현장 출동을 계획하는 기능까지 모든 지원됩니다. "

#: ../../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 ""
":menuselection:`헬프데스크 --> 구성 --> 헬프데스크 팀`으로 이동하여 *환불, 반품, 쿠폰, 수리 및 현장 출동* "
"애프터서비스 선택 사항을 활성화합니다."

#: ../../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 ""
"`쿠폰 <https://www.odoo.com/slides/slide/coupon-programs-640?fullscreen=1>`_"

#: ../../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 ""
"Odooj *헬프데스크*에서 상담이 완료되었을 때 다음과 같은 방법으로 상담을 종료할 수 있습니다. 완료된 상담 건을 수기로 종료시키면 "
"파이프라인을 업데이트 시킬 수 있으며, 비활성화된 상담은 자동으로 종료되도록 하면 차단 등의 문제를 사전에 방지할 수 있습니다. 상담 "
"고객이 직접 상담을 종료할 수 있도록 하면 고객측의 문제가 해결되었는지 여부를 쉽게 확인할 수 있습니다. 이런 방식으로 고객지원팀의 운영"
" 능력을 제고시키고 고객 만족도를 향상시킬 수 있게 됩니다. "

#: ../../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 ""
"단계를 접음 처리하려면 :menuselection:`헬프데스크` 현황판에서 팀을 클릭하여 파이프라인으로 이동합니다. 단계 제목 위로 "
"마우스를 댄 후, 해당되는 단계의 칸반 열에서 화면 오른쪽 상단에 나타나는 톱니바퀴 아이콘을 클릭합니다."

#: ../../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 ""
"톱니바퀴 아이콘을 클릭하면 단계에 대해서도 :guilabel:`접음` 선택을 할 수 있습니다. 이 설정을 해두면 칸반 화면을 간략하게 "
"보기 위해서 단계를 *일시적으로* 접게 됩니다. 이렇게 하더라도 현재 단계에서 상담이 종료되는 것은 *아닙니다*. 단계를 완전히 접음 "
"처리하는 것 역시 아닙니다. 상담이 종료된 것으로 표시될 수 있도록 단계를 접음 처리해야 하는 경우에는 아래의 내용을 참고하여 진행하시기"
" 바랍니다. "

#: ../../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 ""
"표시되는 메뉴에서 :guilabel:`단계 편집`을 선택합니다. 단계 설정을 할 수 있는 항목이 열립니다. 상단에 있는 "
":guilabel:`칸반에서 접음`이라고 표시되어 있는 상자를 선택한 다음 :guilabel:`저장하고 닫기`를 클릭한 후 변경된 내용을"
" 확인합니다. 이제 상담 현재 단계에 도달하면 *종료*된 것으로 간주합니다."

#: ../../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 ""
":menuselection:`헬프데스크 --> 구성 --> 팀`으로 이동하여 팀 설정 페이지로 이동합니다. :guilabel:`셀프 "
"서비스` 섹션에서 :guilabel:`자동 종료` 항목을 활성화하십시오."

#: ../../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 ""
"팀 메뉴에 있는 단계를 칸반 화면에서 접음 처리가 되도록 설정한 경우에는, 이 내용이 :guilabel:`단계로 이동`에서의 기본값이 "
"됩니다. 접음 단계가 두 개 이상 있는 경우에는 파이프라인 상에서 처음으로 발생하는 단계가 기본값이 됩니다. 접음 단계가 없으면 "
"파이프라인에서의 마지막 단계가 기본 선택값이 됩니다."

#: ../../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 ":guilabel:`다음 기간동안 비활성화인 경우` 항목은 기본값은 7로 되어 있으나, 필요시 변경할 수 있습니다. "

#: ../../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 ""
"상담이 비활성화된 기간을 추적할 때는 :guilabel:`다음 기간동안 비활성화인 경우` 항목에서 작업 캘린더를 고려하지 "
"**않습니다**."

#: ../../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 "특정 단계에 대해서만 비활성화 기간을 추적해야 하는 경우에는 :guilabel:`진행 단계`에 추가하여 사용하면 됩니다."

#: ../../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 ""
"문제가 해결된 후에는 고객이 바로 응답하지 않는 경우가 많으므로 이런 경우에는 상담 건이 :guilabel:`고객 피드백 단계`에 계속 "
"남아있게 됩니다. 여기에서 상담이 자동으로 종료될 수 이습니다. 그러나 상담이 :guilabel:`신규` 및 :guilabel:`진행 "
"중` 단계에 잇는 경우에는 관련된 작업 중이거나 상담량이 많은 경우 비활성화될 수 있습니다. 이런 경우에는 상담을 자동으로 종료시켜버리면"
" 고객 측의 문제가 계속 해결되지 못한 상태로 남게 됩니다. "

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
msgid ""
"Therefore, the :guilabel:`Automatic Closing` settings would be configured as"
" below\\:\\"
msgstr "따라서 :guilabel:`자동 종료` 설정을 아래와 같이 구성합니다\\:\\"

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79
msgid ":guilabel:`Automatic Closing`: *checked*"
msgstr ":guilabel:`자동 종료`: *확인 완료*"

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80
msgid ":guilabel:`Move to Stage`: `Solved`"
msgstr ":guilabel:`단계로 이동`: `해결 완료`"

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
msgid ":guilabel:`After``7`:guilabel:`days of inactivity`"
msgstr ":guilabel:`다음 기간이 지난 경우``7`:guilabel:`비활성화된 기간`"

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82
msgid ":guilabel:`In Stages`: `Customer Feedback`"
msgstr ":guilabel:`진행 단계`: `고객 피드백`"

#: ../../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 ""
":guilabel:`고객 종료 허용` 설정을 할 경우, 문제가 해결되었다고 생각되면 고객이 본인 상담을 종료할 수 있습니다. "

#: ../../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 ""
":menuselection:`헬프데스크 --> 구성 --> 팀` 메뉴에서 팀을 선택합니다. 팀 항목의 설정 페이지에서 "
":guilabel:`셀프서비스` 로 스크롤을 내려서 :guilabel:`고객 종료 허용` 상자에 표시하십시오."

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
msgid "Customer closing setting in Odoo Helpdesk."
msgstr "Odoo 헬프데스크에서의 고객 종료 설정."

#: ../../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 ""
"상담 종료 설정을 활성화시켜 놓으면 고객 포털을 통해서 상담 항목에 대해 고객이 :guilabel:`상담 종료` 버튼을 사용할 수 "
"있습니다."

#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
msgid "Customer view of ticket closing in Odoo Helpdesk."
msgstr "Odoo 헬프데스크에서 상담 종료를 확인할 수 있는 고객 화면."

#: ../../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 ""
"고객은 이메일로 받은 :guilabel:`상담 확인` 링크를 클릭하여 상담 내역을 확인할 수 있습니다. 팀 항목의 첫 단계에 있는 기본 "
"값으로 :guilabel:`확인 요청` 서식에 링크가 포함되어 있습니다. 링크만 있으면 고객이 상담 내역을 확인하거나 응답하기 위해서 "
"포털에 접속할 필요가 없습니다. "

#: ../../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 ""
"고객이 포털을 통해서 이용할 경우에는 :menuselection:`내 계정 --> 상담`에서 본인 상담 항목을 확인할 수 있습니다."

#: ../../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/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 ":menuselection:`헬프데스크 --> 구성 --> 헬프데스크 팀` 메뉴로 이동하여 *헬프데스크*를 활성화합니다."

#: ../../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 "Odoo 헬프데스크에서 헬프 센터 기능이 선택되어 있는 헬프데스크 팀 설정 화면"

#: ../../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 "Odoo 헬프데스크의 포럼 설정 화면"

#: ../../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 ""
"이제 사용자가 로그인하면 글을 올릴 수 있습니다. 게시물을 추적하려면 :menuselection:`웹사이트 --> 포럼 --> 게시글` "
"메뉴를 확인하십시오."

#: ../../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 "Odoo 헬프데스크에서 사용할 수 있는 내용을 표시해놓은 포럼 웹사이트 화면"

#: ../../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 ":menuselection:`헬프데스크 --> 구성 --> 헬프데스크 팀`으로 이동하여 *온라인 학습* 메뉴를 활성화합니다."

#: ../../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 "Odoo 헬프데스크에서 온라인 학습 항목이 선택되어 있는 고객지원팀 설정 화면"

#: ../../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 "Odoo 헬프데스크에서 게시가 완료된 교육 과정 화면"

#: ../../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 "Odoo 헬프데스크용 온라인 학습앱에서의 현황판 화면"

#: ../../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 ""
"Odoo :guilabel:`헬프데스크`는 상담을 기반으로 하는 고객 지원용 애플리케이션입니다. 저희 고객지원팀은 단계별로 커스터마이징할"
" 수 있는 파이프라인 상에 있는 고객들의 문제를 추적하고 우선순위를 정하여 해결해드릴 수 있도록 합니다. 단일 현황판에서 여러 팀을 "
"구성하고 관리할 수 있습니다. "

#: ../../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 ""
"*헬프데스크* 팀 항목을 확인하거나 수정하려면 :menuselection:`헬프데스크 --> 구성 --> 팀` 메뉴를 선택합니다. 새로운"
" 팀을 만들려면 현황판 화면의 왼쪽 상단에 있는 :guilabel:`신규` 버튼을 클릭하십시오. 여기에서 새 팀 이름을 지정하고 양식에 "
"나와있는 다음 항목들에서 나머지를 입력합니다."

#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1
msgid "View of the Helpdesk teams page in Odoo Helpdesk"
msgstr "Odoo 헬프데스크에서의 헬프데스크 팀 페이지 화면"

#: ../../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 ":guilabel:`검토` 항목에서 해당되는 팀과 상담 건을 확인할 수 있는 담당자를 선택합니다."

#: ../../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 ""
":guilabel:`승인된 내부 사용자`인 경우에는 팀 항목과 상담건을 팔로우하면 확인할 수 있게 됩니다. 이는 개별 상담 건별로 수정할"
" 수 있습니다. "

#: ../../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 ":guilabel:`내부 사용자 전체`로 설정하면 팔로워가 아니더라도 팀 내역과 전체 상담 건을 확인할 수 있게 됩니다."

#: ../../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 ""
":guilabel:`승인된 포털 사용자 및 내부 사용자 전체`는 팔로워가 아니더라도 팀 항목에 접근 권한을 갖게 됩니다. 포털 사용자는 "
"팔로우하는 상담 건만 확인할 수 있습니다."

#: ../../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 ""
"'고객지원' 팀에서 일반적인 배송 및 제품 문제 처리용으로는 검토 항목 설정을 :guilabell:'승인된 포털 사용자 및 내부 사용자 "
"전체'로 설정해놓습니다. 그러나 회계나 세금과 관련된 상담을 처리하는 `금융 서비스` 팀에서는 관련 내용을 :guilabel:`승인된 "
"내부 사용자`만 확인할 수 있도록 하고 있습니다."

#: ../../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 ""
"상담 요청을 받게 되면 지원팀의 구성원들에게 상담 건을 배정해줍니다. 개별적인 상담 건별로 수기로 배정하거나 :guilabel:`자동 "
"배정`을 통해 진행할 수 있습니다. 이 기능을 활성화하려면 :guilabel:`자동 배정` 옆의 선택란을 표시하시면 됩니다."

#: ../../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 "Odoo 헬프데스크의 배정 및 검토 기능이 선택되어 있는 헬프데스크 팀 설정 페이지 화면"

#: ../../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 ":guilabel:'모든 사용자에게 상담건수를 동일하게 배정하기'로 상담을 배정합니다."

#: ../../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 ":guilabel:'모든 사용자에게 접수된 상담건수를 동일하게 배정하기'로 상담을 배정하며"

#: ../../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 ""
"마지막으로, 팀 내에서 상담을 배정받을 :guilabel:`팀원`을 추가합니다. 사용자 계정 설정에서 구성해놓은대로 배정 및 접근 권한이"
" 있는 직원 전체를 대상으로 할 경우에는 필드를 비워 두시면 됩니다. "

#: ../../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 ""
"직원이 :guilabel:`휴가관리` 애플리케이션에서 휴가를 신청한 경우 해당 기간 동안에는 상담을 배정하지 않습니다. 근무 중인 직원이"
" 없는 경우에는 가능한 내용을 찾을 때까지 시스템에서 미리 확인합니다. "

#: ../../content/applications/services/helpdesk/overview/getting_started.rst:76
msgid ":ref:`Manage users <users/add-individual>`"
msgstr ":ref:`사용자 관리 <users/add-individual>`"

#: ../../content/applications/services/helpdesk/overview/getting_started.rst:77
msgid ":doc:`Access rights </applications/general/users/access_rights>`"
msgstr ":doc:`액세스 권한 </applications/general/users/access_rights>`"

#: ../../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 ""
":guilabel: *헬프데스크*에서 파이프라인을 구성하고 상담 진행 상황을 관리하기 위해 `단계`를 사용됩니다. 단계는 커스터마이징할 "
"수 있으며 필요에 따라서 이름을 변경할 수 있습니다."

#: ../../content/applications/services/helpdesk/overview/getting_started.rst:85
msgid ""
"To view or modify *Helpdesk* stages, go to :menuselection:`Helpdesk --> "
"Configuration --> Stages`."
msgstr "*헬프데스크* 단계를 보거나 수정하려면 :menuselection:`헬프데스크 --> 구성 --> 단계`로 이동하십시오."

#: ../../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 ""
"단계 메뉴를 사용하려면 :ref:`개발자 모드 <developer-mode>`를 활성화합니다. 개발자 모드 활성 방법은 "
":menuselection:`설정 --> 일반 설정 --> 개발자 도구`로 이동하여 :guilabel:`개발자 모드 활성화`를 클릭하면 "
"됩니다."

#: ../../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 ""
"새로 단계를 생성하려면 현황판 왼쪽 상단에 있는 :guilabel:`신규` 버튼을 클릭하십시오. 그 다음 새로운 단계로 만들 이름을 "
"선택하고 설명을 추가합니다 (필수 항목 아님). 아래의 단계에 따라 나머지 필드를 입력하십시오."

#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1
msgid "View of a stage's settings page in Odoo Helpdesk"
msgstr "Odoo 헬프데스크에서의 단계 설정 페이지 화면"

#: ../../content/applications/services/helpdesk/overview/getting_started.rst:113
msgid "Add email and SMS templates to stages"
msgstr "단계에 이메일 및 SMS 서식 추가하기"

#: ../../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 ""
"단계에 :guilabel:`이메일 서식`을 추가할 경우, 헬프데스크 파이프라인 상의 특정 단계로 상담 건이 이동하게 되면 고객에게 "
"자동으로 이메일을 전송합니다. 마찬가지로 :guilabel:`SMS 서식`을 추가하면 고객에게 SMS로 문자 메시지를 전송합니다."

#: ../../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 ""
"SMS 문자 메시지는 선불 크레딧으로 사용하실 수 있는 인앱 구매(IAP) 서비스입니다. 자세한 내용은 `SMS 요금 안내 FAQ "
"<https://iap-services.odoo.com/iap/sms/pricing>`_를 참고하시기 바랍니다."

#: ../../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 ""
"기존 이메일 서식을 선택하려면 :guilabel:`이메일 서식` 필드에서 항목을 선택합니다. 서식을 편집하려면 필드 오른쪽에 있는 화살표"
" 키를 클릭하면 됩니다."

#: ../../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 ""
"새로운 서식을 생성하려면 해당되는 필드를 클릭하여 새 서식 제목을 입력하는 것으로 시작합니다. 그 후 :guilabel:`생성 후 "
"편집하기`을 선택하고 양식의 세부 내용을 입력합니다."

#: ../../content/applications/services/helpdesk/overview/getting_started.rst:130
msgid ""
"Follow the same steps to select, edit, or create an :guilabel:`SMS "
"Template`."
msgstr "같은 방법으로 :guilabel:`SMS 서식`을 선택한 후 편집하거나 생성합니다."

#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1
msgid "View of an SMS template setup page in Odoo Helpdesk"
msgstr "Odoo 헬프데스크의 SMS 서식 설정 페이지 화면"

#: ../../content/applications/services/helpdesk/overview/getting_started.rst:137
#: ../../content/applications/services/helpdesk/overview/ratings.rst:60
msgid ":doc:`/applications/general/email_communication/email_template`"
msgstr ":doc:`/applications/general/email_communication/email_template`"

#: ../../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 ""
":guilabel:`단계` 양식에 있는 :guilabel:`팀` 필드에서 선택합니다. 같은 단계를 여러 팀에 배정할 수 있으므로 여러 "
"개의 팀을 선택할 수 있습니다."

#: ../../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 ""
"해당 팀에 대한 칸반 기본 상태를 *접기* 상태로 나타나게 하려면 :guilabel:`단계` 양식의 :guilabel:`칸반에서 접기 "
"처리` 선택란에 표시하십시오."

#: ../../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 "또는 설정 아이콘을 클릭하여 :guilabel:`접기`를 선택하면 칸반 화면에서 단계를 임시로 접기 처리할 수 있습니다."

#: ../../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 "Customer ratings"
msgstr "고객 평가"

#: ../../content/applications/services/helpdesk/overview/ratings.rst:5
msgid ""
"Asking customers to rate the support they received from a *Helpdesk* team "
"provides an opportunity to gauge team performance and track customer "
"satisfaction. Ratings can be published to the portal, providing customers "
"with a general overview of the team's performance."
msgstr ""
"*헬프데스크* 팀에서 지원받은 내용에 대해 고객이 평가하도록 하면 팀의 성과 측정이나 고객 만족도를 추적할 수 있게 됩니다. 포털에 평가"
" 내용을 게시하여 팀이 어떤 성과를 보이고 있는지 전체적인 기본 내용을 보여줄 수 있습니다. "

#: ../../content/applications/services/helpdesk/overview/ratings.rst:10
msgid "Enable customer ratings on a Helpdesk team"
msgstr "헬프데스크 팀에서 고객 평가 기능 사용하기"

#: ../../content/applications/services/helpdesk/overview/ratings.rst:12
msgid ""
"To enable *customer ratings* on a helpdesk team by going to "
":menuselection:`Helpdesk --> Configuration --> Teams`. Select a team from "
"the list and navigate to the settings page. Scroll to the "
":guilabel:`Performance` section, and check the box for :guilabel:`Customer "
"Ratings`."
msgstr ""
":menuselection:`헬프데스크 --> 구성 --> 팀`으로 이동하여 헬프데스크 팀 항목에서 *고객 평가*를 활성화합니다. "
"해당되는 팀을 목록에서 선택하고 설정 페이지로 이동합니다. 화면 아래에 있는 :guilabel:`성과` 섹션으로 이동하여 "
":guilabel:`고객 평가` 선택란에 표시합니다. "

#: ../../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 "Odoo 헬프데스크 상담 평가 항목이 선택되어 있는 헬프데스크 팀의 설정 페이지 화면."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:22
msgid "Set a ratings request email template on a stage"
msgstr "단계에서 평가를 요청하는 이메일 서식 설정하기"

#: ../../content/applications/services/helpdesk/overview/ratings.rst:24
msgid ""
"To automatically request ratings from customers once their tickets have "
"closed, an email template should be added to the appropriate stage."
msgstr "상담이 종료된 후 자동으로 고객 평가를 요청하도록 하려면 해당 단계에 이메일 서식을 추가해야 합니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:27
msgid ""
"Once the :guilabel:`Customer Ratings` setting has been enabled on the team's"
" settings page, (see above) click the :guilabel:`Set an Email Template on "
"Stages` link. Select a stage from the list, or click :guilabel:`New` to "
"create a new stage."
msgstr ""
"팀 설정 페이지에서 `고객 평가` 항목을 활성화시킨 후 (위의 내용 참조) :guilabel:`단계에서 이메일 서식 설정` 링크를 "
"클릭하십시오. 목록에서 단계를 선택하거나 :guilabel:`신규`를 클릭하여 새로운 단계를 생성합니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:32
msgid ""
"Customers should only be asked to rate tickets once an issue has been "
"resolved and their ticket is closed. Therefore, a *ratings request* email "
"should only be added to a stage that is **folded** in the kanban, as tickets"
" in a *folded stage* are considered closed."
msgstr ""
"고객 문제가 해결되어 상담켓이 종료된 후에만 고객에게 상담에 대한 평가를 요청해야 합니다. 따라서 *접기 처리된 단계*에서는 상담이 "
"종료된 것으로 간주되므로 칸반에서 **접기** 되어 있는 단계에만 *평가 요청* 이메일을 추가해야 합니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:36
msgid ""
"On the stage's settings page, select `Helpdesk: Ticket Rating Request` in "
"the :guilabel:`Email Template` field. This template has been pre-configured "
"with ratings customers can use to provide feedback. To view the template, "
"click the arrow button to the right of the field."
msgstr ""
"단계 설정 페이지에서 :guilabel:`이메일 서식` 필드의 `헬프데스크: 상담 평가 요청`을 선택합니다. 이 서식은 고객으로부터 "
"피드백을 받을 수 있도록 미리 구성되어 있습니다. 서식을 확인하려면 필드 오른쪽에 있는 화살표 버튼을 클릭합니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:40
msgid ""
"Once the template has been added to the stage, it will automatically send a "
"message when a ticket is moved to that stage. Customers will be asked to "
"rate the support they received with colored icons."
msgstr ""
"서식이 단계에 추가되면 해당 단계로 상담이 이동하게 될 경우 자동으로 메시지가 전송됩니다. 고객은 색상으로 구별된 아이콘을 선택하여 지원"
" 내용에 대해서 평가해달라는 요청을 받게 됩니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:43
msgid "*Green smiling face* - Satisfied"
msgstr "*초록색 스마일* - 만족"

#: ../../content/applications/services/helpdesk/overview/ratings.rst:44
msgid "*Yellow neutral face* - Okay"
msgstr "*노란색 보통* - 양호"

#: ../../content/applications/services/helpdesk/overview/ratings.rst:45
msgid "*Red frowning face* - Dissatisfied"
msgstr "*빨간색 찌푸린 얼굴* - 불만"

#: ../../content/applications/services/helpdesk/overview/ratings.rst-1
msgid ""
"View of a standard helpdesk customer review email template for Odoo "
"Helpdesk."
msgstr "Odoo 헬프데스크용으로 만들어진 헬프데스크 고객 리뷰 이메일 표준 서식 화면."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:51
msgid ""
"After selecting a rating, customers are taken to a webpage where they can "
"provide specific written feedback to support their rating. Once a rating is "
"submitted, it is added to the chatter on the ticket."
msgstr ""
"고객이 평가 결과를 선택한 후 자신이 평가한 내용에 대해 구체적으로 피드백을 작성할 수 있는 웹페이지로 이동합니다. 고객 평가는 제출 후"
" 상담 대화창에 추가됩니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:56
msgid ""
"Customer ratings can also be viewed through the :guilabel:`Customer Ratings`"
" report. To view this report, go to :menuselection:`Helpdesk --> Reporting "
"--> Customer Ratings`."
msgstr ""
"고객 평가는 :guilabel:`고객 평가` 보고서를 통해서도 확인할 수 있습니다. 이 보고서는 :menuselection:`헬프데스크 "
"--> 보고 --> 고객 평가` 메뉴에서 볼 수 있습니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:63
msgid "Publish ratings on the customer portal"
msgstr "고객 포털에 평가 내용 게시"

#: ../../content/applications/services/helpdesk/overview/ratings.rst:65
msgid ""
"After enabling the :guilabel:`Customer Ratings` setting, an option to "
"publish ratings on the team's website appears. Enabling this setting "
"provides portal users with an overview of the ratings the team has received "
"over the last thirty days. Specific written feedback will not be included; "
"only statistics of the team's performance will be visible."
msgstr ""
":guilabel:`고객 평가` 설정을 활성화시키면 팀의 웹사이트에 평점을 게시하는 옵션이 표시됩니다. 이 설정 항목을 활성화시키면 지난"
" 30일 동안 팀에서 받은 평가에 대한 전체적인 내용을 포털 사용자들이 확인할 수 있습니다. 여기에는 구체적 피드백 내용은 포함되지 "
"않으며 팀의 성과에 대한 통계 수치만 표시됩니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:71
msgid ""
"In order to display ratings on the customer portal, a team has to have their"
" visibility setting set to :guilabel:`Invited portal users and all internal "
"users`. This setting is found on the team's settings page under "
":guilabel:`Visibility`."
msgstr ""
"고객 포털에 평가 내용이 표시되도록 하려면 팀 설정에서 검토 가능성 항목이 :guilabel:`승인된 포털 사용자 및 내부 사용자 "
"전체`로 설정되어 있어야 합니다. 해당되는 설정 항목은 :guilabel:`검토 가능성` 아래에 있는 팀 설정 페이지에서 확인하실 수 "
"있습니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:75
msgid ""
"Next, to publish the ratings, go to :menuselection:`Helpdesk --> "
"Configuration --> Teams` and select a team. Scroll to "
":guilabel:`Performance` and enable :guilabel:`Publish this team's ratings on"
" your website`."
msgstr ""
"다음으로, 평가 결과를 게시하려면 :menuselection:`헬프데스크 --> 구성 --> 팀`으로 이동하여 팀을 선택하십시오. 화면 "
"아래로 이동하여 :guilabel:`성과`에 있는 :guilabel:`팀 평가를 웹사이트에 게시` 항목을 활성화합니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:79
msgid ""
"To view the ratings for a team, a customer will log into the portal and "
"navigate to one of their tickets. After clicking on the team name in the "
":guilabel:`Managed By` field, they will be directed to a page with the "
"team's ratings over the past thirty days."
msgstr ""
"팀에 대한 평가 결과를 확인하려면 고객은 포털에 로그인하여 본인의 상담 내역 중 하나를 선택합니다. :guilabel:`관리 주체` "
"필드에서 팀 이름을 클릭하면 지난 30일 동안의 평가가 나와있는 페이지로 이동합니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst-1
msgid "View of the ratings performance overview from the customer portal."
msgstr "고객 포털에서 평가 실적에 대한 전체적인 내용이 나와있는 화면."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:88
msgid "Manually hide individual ratings"
msgstr "개별 평가 내용을 수기로 숨김 처리하기"

#: ../../content/applications/services/helpdesk/overview/ratings.rst:90
msgid ""
"Individual ratings can be manually hidden from the portal. This allows for "
"specific ratings to be kept out of the performance metrics that are shown to"
" customers."
msgstr ""
"포털에서 개별 평가 항목을 수동으로 숨길 수 있습니다. 이를 통해 고객에게 표시되는 실적표에서 특정 등급을 제외할 수 있습니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:93
msgid ""
"To make a rating visible only to internal users, navigate to the page for a "
"rating. This can be done in one of the following ways:"
msgstr "내부 사용자에게만 평가 내용을 보이게 하려면 평가 페이지로 이동하십시오. 다음의 방법 중 하나를 선택하시면 됩니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:96
msgid ""
"Go to :menuselection:`Helpdesk --> Reporting --> Customer Ratings` and click"
" on one of the kanban cards for an individual rating."
msgstr ""
":menuselection:`헬프데스크 --> 보고 --> 고객 평가`로 이동하고 개별 평가 항목에 대한 칸반 카드 중 하나를 "
"클릭합니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:98
msgid ""
"Navigate to :menuselection:`Helpdesk --> Tickets --> All Tickets` and remove"
" the :guilabel:`Open` filter from the search bar. Then filter by "
":guilabel:`Satisfied`, :guilabel:`Okay` and/or :guilabel:`Dissatisfied`. "
"Select a ticket from the results. Click the :guilabel:`Rating` smart button."
msgstr ""
":menuselection:`헬프데스크 --> 상담 --> 전체 상담`으로 이동한 후 검색창에서 :guilabel:`접수된 상담` 필터를"
" 삭제합니다. 그런 다음 :guilabel:`만족`, :guilabel:`양호` 및/또는 :guilabel:`불만`으로 필터를 "
"입력합니다. 검색된 상담 내용을 선택합니다. :guilabel:`평가` 스마트 버튼을 클릭합니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:103
msgid ""
"Once on the rating details page, check the :guilabel:`Visible Internally "
"Only` box."
msgstr "평가 세부 정보에서 :guilabel:`내부 검토만 허용` 선택란에 표시합니다."

#: ../../content/applications/services/helpdesk/overview/ratings.rst:110
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:291
msgid ":doc:`/applications/services/helpdesk/advanced/close_tickets`"
msgstr ":doc:`/applications/services/helpdesk/advanced/close_tickets`"

#: ../../content/applications/services/helpdesk/overview/ratings.rst:111
msgid ":doc:`/applications/services/helpdesk/overview/reports`"
msgstr ":doc:`/applications/services/helpdesk/overview/reports`"

#: ../../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 ""
"Odoo *헬프데스크*에서는 이메일, 실시간 채팅, 웹사이트 양식 제출 등 다양한 채널을 통해 고객 서비스를 지원해드리고 있습니다. "
"저희쪽으로 연락할 수 있는 다양한 방법 중에서 고객들께서 선택할 수 있으므로 신속하게 지원받을 수 있는 동시에 고객지원팀이 중심이 되어 "
"여러 개의 지원 채널을 통한 상담을 관리할 수 있도록 기능하고 있습니다. "

#: ../../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 ""
":menuselection:`헬프데스크 --> 구성 --> 팀`으로 이동하여 입력되어 있는 기존 팀을 선택하거나 "
":guilabel:`신규`를 클릭하여 :doc:`새로운 팀 만들기 <getting_started>`로 이동합니다."

#: ../../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 ""
"팀 설정 페이지에서 화면 아래쪽의 :guilabel:`채널`까지 이동합니다. 해당하는 선택란에 표시하여 활성화시킬 채널을 하나 이상 "
"선택합니다."

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:19
msgid ":guilabel:`Email Alias`"
msgstr ":guilabel:`이메일 별칭`"

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:20
msgid ":guilabel:`Website Form`"
msgstr ":guilabel:`웹사이트 양식`"

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:21
msgid ":guilabel:`Live Chat`"
msgstr ":guilabel:`실시간 채팅`"

#: ../../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 ""
"*헬프데스크* 팀에서 사용하는 이메일 별칭을 변경하려면 :guilabel:`팀` 설정 페이지로 이동합니다. :guilabel:`채널` "
"제목 아래이 엤는 :guilabel:`이메일 별칭`에서 원하는 별칭을 입력하십시오."

#: ../../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 ""
"새로 *헬프데스크* 팀을 생성하면 :guilabel:`이메일 별칭`도 새로 만들어집니다. 해당 항목은 :guilabel:`별칭` 필드에서"
" 변경할 수 있습니다."

#: ../../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 ""
"데이터베이스에 미리 구성해놓은 커스텀 도메인이 없는 경우에는 :guilabel:`커스텀 도메인 구성`을 클릭한 후 "
":guilabel:`설정` 페이지로 이동합니다. 거기에서 :guilabel:`이메일 서버 사용자 지정` 항목을 활성화시킵니다."

#: ../../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 "Odoo헬프데스크의 이메일 별칭 기능을 선택되어 있는 헬프데스크 팀의 설정 페이지 화면"

#: ../../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 ""
"이메일을 수신할 경우, 이메일 제목이 신규 *헬프데스크* 상담 건의 제목이 됩니다. 이메일 본문 내용은 상담의 :guilabel:`설명`"
" 탭 및 :guilabel:'메시지 창` 섹션에도 추가됩니다."

#: ../../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 ""
"위에서 설명한 구성 단계는 **Odoo 온라인** 및 **Odoo.sh** 데이터베이스 전용입니다. **온프레미스** 데이터베이스의 "
"경우에는 이메일 서버를 커스터마이징하시거나 이메일 별칭에 대해서 추가 구성하셔야 할 수 있습니다."

#: ../../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 ""
"웹사이트 양식을 활성화시키려면 :menuselection:`구성 --> 팀` 메뉴에서 팀 설정 페이지로 이동합니다. "
":guilabel:`채널` 섹션 아래에서 :guilabel:`웹사이트 양식` 항목을 찾아 선택란에 표시하시면 됩니다."

#: ../../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 ""
"기능을 활성화시킨 후, :guilabel:`팀` 설정 페이지 상단에 있는 :guilabel:`웹사이트 바로가기` 스마트 버튼을 클릭하면 "
"Odoo에서 자동으로 생성된 새 웹사이트 양식을 확인하여 편집할 수 있습니다."

#: ../../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 ""
"또한 *헬프 센터*가 있는 경우에는 스마트 버튼을 통해 먼저 해당 내용을 검색하게 됩니다. 포럼의 하단에 있는 "
":guilabel:`연락하기` 버튼을 클릭하여 상담 요청 페이지로 이동하십시오."

#: ../../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 "Odoo 헬프데스크에서 웹사이트 바로가기 버튼을 강조해서 보여주는 헬프데스크 팀의 설정 페이지 화면."

#: ../../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 ""
"기본 상담 요청 양식을 커스터마이징하려면 페이지 상단에서 우측 끝에 있는 :guilabel:`편집` 버튼을 클릭하십시오. 그 후 양식에 "
"있는 필드 중 하나를 클릭합니다."

#: ../../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 ""
"고객이 제출한 내용을 변경하려면 필드를 필요에 따라 추가하거나 삭제 또는 업데이트합니다. 필드를 :guilabel:`필수` 항목으로 "
"표시하려면 :guilabel:`필드` 섹션 하단에 있는 웹사이트 빌더 편집기 창에서 스위치를 회색에서 파란색으로 전환하면 됩니다. 또한 "
"다음과 같은 기타 필드 항목을 여기에서 편집할 수 있습니다."

#: ../../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 ":guilabel:`유형`: 필드 (예: `고객명`)에 해당하는 Odoo 모델 값입니다."

#: ../../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 ""
":guilabel:`입력 유형`: `텍스트`, `이메일`, `전화번호` 또는 `URL` 항목과 같이 필드에 입력할 유형을 선택합니다."

#: ../../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 ""
":guilabel:`라벨`: 양식에서의 필드값에 라벨을 지정합니다 (예: `전체 이름`, `이메일 주소` 등). 또한 "
":guilabel:`위치` 옵션을 사용하여 양식에서 라벨 위치를 관리합니다."

#: ../../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 ""
":guilabel:`설명`: 선택 사항으로, 추가로 필드와 관련된 내용에 대한 정보를 제공하기 위해 입력 상자 아래에 편집할 수 있도록 "
"줄을 추가합니다."

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:100
msgid ":guilabel:`Placeholder`: to add a sample input value."
msgstr ":guilabel:`입력 예시`: 예시로 보여줄 입력값을 추가합니다."

#: ../../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 ":guilabel:`기본값`: 고객들 대부분에게 적용될 수 있는 일반적인 내용을 값으로 추가합니다. "

#: ../../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 ":guilabel:`필수 항목`: 양식을 제출하려면 해당 필드를 작성하도록 필수 항목으로 설정합니다. "

#: ../../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 ""
":guilabel:`검토 가능성`: 필드에서 항상 보기 또는 조건에 따라 검토할 수 있도록 관리합니다. 디바이스 검토와 같은 기본 옵션 "
"기능은 특정 내용을 선택하면 표시됩니다. "

#: ../../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 ""
"텍스트 블록은 상담 양식 페이지에서 양식 옆 가장 끝부분 1/3 열에 추가할 수 있습니다. 세부적인 추가 연락처나 시간 또는 유용할만한 "
"정보와 같은 팀 안내 사항을 입력해놓기에 가장 알맞은 자리입니다. "

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1
msgid ""
"View of the unpublished website form to submit a ticket for Odoo Helpdesk."
msgstr "Odoo 헬프데스크에 상담 요청용으로 아직 제출하기 전인 웹사이트 양식 화면."

#: ../../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 ""
"편집이 완료되어 양식이 일반에게 공개할 준비가 되었다면, 변경 사항을 저장한 후 :guilabel:`미게시` 버튼을 클릭하여 양식을 "
"게시하십시오."

#: ../../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 ""
"*실시간 채팅* 기능을 사용하면 웹사이트 방문자를 지원 담당 직원이나 챗봇 채팅으로 직접 연결시킬 수 있습니다. 채팅 중에 "
":doc:`응답 명령 ` `/helpdesk`를 사용하여 즉시 *헬프데스크* 상담 건을 생성할 수 있습니다."

#: ../../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 ""
"*실시간 채팅* 기능을 활성화시키려면 :menuselection:`구성 --> 팀` 목록 화면으로 이동하여 팀을 선택한 후 "
":guilabel:`팀` 설정 페이지에서 :guilabel:`채널` 제목 아래에 있는 :guilabel:`실시간 채팅` 옆에 있는 "
"선택란에 표시하십시오. "

#: ../../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 ""
":guilabel:`실시간 채팅` 설정을 활성화시킨 상태에서 :guilabel:`채널 보기`를 클릭합니다. 그런 다음 "
":guilabel:`웹사이트 실시간 채팅 채널` 현황판에서 *헬프데스크* 팀용으로 만들어져있는 채널 칸반 카드를 선택하거나 필요시 카드를"
" :guilabel:`신규`로 생성합니다. 칸반 카드를 선택할 경우 채널 양식에서 사용할 추가 옵션 항목이 있습니다"

#: ../../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 ""
"웹사이트 실시간 채팅 채널의 현황판에 있는 개별 채널을 클릭하면 Odoo에서 채널 양식으로 이동하게 됩니다. 여기에서 "
":guilabel:`채널명`을 편집할 수 있으나, 기본적으로 Odoo에서는 *헬프데스크* 팀에 있는 칸반 파이프라인과 같은 이름으로 "
"지정되고 있습니다."

#: ../../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 ""
"다른 사용자를 추가하려면 웹사이트 실시간 채팅 채널의 현황판에서 실시간 채팅 채널을 검색하여 선택한 후 :guilabel:`운영자` "
"탭에서 :guilabel:`추가`를 클릭합니다."

#: ../../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 ""
"그 후, 추가할 사용자 옆의 선택란에 표시하고 :guilabel:`선택`을 클릭합니다. :guilabel:`신규` 운영자를 생성하여 "
"목록에 추가할 수도 있습니다. :guilabel:`운영자 생성` 양식을 작성한 다음 :guilabel:`저장하고 닫기`(또는 추가로 "
"생성하려면 :guilabel:`저장하고 새로 만들기`를 클릭)를 선택합니다."

#: ../../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 ""
"또한 현재 운영자 정보를 편집하거나 삭제하려면 :guilabel:`운영자` 탭에서 해당 선택란에 표시한 다음 양식에 있는 값을 변경하거나"
" 양식의 하단에 있는 :guilabel:`삭제`버튼과 같은 양식 전용 버튼을 사용하시면 됩니다."

#: ../../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 "*실시간 채팅* 채널에서 :guilabel:`참가` 버튼을 클릭하면 사용자 자신을 운영자로 추가할 수 있습니다."

#: ../../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 ":guilabel:`옵션` 탭에서 실시간 채팅 창에서 사용할 수 있는 효과 및 텍스트 설정을 할 수 있습니다."

#: ../../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 ""
"웹사이트에 실시간 채팅 버튼이 표시될 때 말풍선으로 인사말을 나타나게 하려면 :guilabel:`버튼용 텍스트` 필드에 있는 텍스트 "
"내용을 변경하십시오."

#: ../../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 ""
"방문자가 채팅창을 들어올 때 표시되는 메시지를 변경하려면 :guilabel:`환영 메시지`를 편집하시면 됩니다. 실시간 채팅 상담원이 "
"보낸 메시지처럼 나타나며 대화를 계속하도록 하는 초대하는 메시지여야 합니다. "

#: ../../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 "방문자가 응답을 입력할 채팅창에 표시할 텍스트를 변경하려면 :guilabel:`채팅 입력 예시` 항목을 편집하십시오."

#: ../../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 ""
":guilabel:`실시간 채팅 버튼 색상` 및 :guilabel:`채널 제목 색상'을 변경하려면 색상 선택창을 열어서 색상표를 "
"클릭합니다. 색상표 오른쪽에 있는 새로고침 표시를 클릭하면 기본 선택 색상으로 초기화됩니다. "

#: ../../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 ""
"색상을 직접 선택하거나 RGB, HSL 또는 HEX 코드를 선택하여 버튼이나 제목 색상을 선택할 수 있습니다. 운영 체제에 따라 선택 "
"사항이 달라질 수 있습니다. "

#: ../../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 ""
":guilabel:`채널 규칙` 탭에서 웹사이트에서 실시간 채팅창이 언제 열리도록 할 것인지를 결정할 수 있으며, 이는 "
":guilabel:`URL 규칙`에 따라서 결정되게 됩니다. "

#: ../../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 ""
"기존 규칙을 편집하거나 새로운 규칙을 :guilabel:`라인 추가하기`로 만들수 있으며, 규칙을 적용하는 방법에 따라 팝업 양식의 세부"
" 정보를 입력합니다."

#: ../../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 ""
"채널에 :guilabel:`챗봇`을 사용하려고 할 경우 드롭다운 메뉴에서 선택합니다. 가능한 운영자가 없을 때만 챗봇을 사용하려고 하는 "
"경우에는 :guilabel:`:`운영자가 없는 경우에만 사용` 선택란에 표시하십시오."

#: ../../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 ""
"실시간 채팅 채널에 챗봇을 추가하면 채널 설정 양식에 :guilabel:`챗봇`, :guilabel:`세션` 및 :guilabel:`% "
"만족도`의 새로운 3가지 스마트 버튼이 표시됩니다."

#: ../../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 ""
":guilabel:`챗봇` 스마트 버튼은 챗봇을 :guilabel:`스크립트` 프로그래밍하는 기능입니다. :guilabel:`스크립트`의"
" 각 줄에는 :guilabel:`메시지`, :guilabel:`단계 유형`, :guilabel:`답변` 및 선택 사항으로 "
":guilabel:`Only If` 규칙이 있어서 미리 작성되어 있는 답변을 선택하게 됩니다. :guilabel:`스크립트`에서 더 많은"
" 단계를 추가하려면 :guilabel:`라인 추가하기`를 선택하여 원하는 규칙에 따라 스크립트 단계 양식을 입력하십시오."

#: ../../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 ""
":guilabel:`세션'에는 기본값으로 :guilabel:`세션 일자`가 내림차순에 따라 기록되어 있습니다. 각 레코드에는 실시간 채팅"
" 세션에 대한 :guilabel:`참여자`, :guilabel:`# 메시지` 및 세션 종료 시 받게 되는 :guilabel:`평가`에 "
"대한 전체 내용이 포함됩니다."

#: ../../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 ""
":guilabel:`% 만족도` 스마트 버튼은 실시간 채팅 이용자가 남긴 평가 기록에 대한 항목이며, 날짜, 시간 및 실시간 채팅 세션을"
" 담당한 상담원으로 라벨이 지정됩니다."

#: ../../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 ""
"이 채널을 사용할 페이지 URL을 :guilabel:`URL 규칙` 필드에 추가하십시오. 특정 국가 사용자만 이 채널을 사용하도록 할 "
"경우에는 :guilabel:`국가` 필드에 해당 채널을 추가하십시오. 필드를 비워두면 사이트 방문자은 누구든지 채널을 사용할 수 "
"있습니다."

#: ../../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 ""
"라이브 채팅 채널 양식에 있는 :guilabel:`위젯` 탭을 통해서 웹사이트 위젯을 추가하거나 실시간 채팅창에서 고객이나 공급업체가 "
"바로 사용할 수 있도록 단축 코드를 만들 수 있습니다. "

#: ../../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 ""
":menuselection:`웹사이트 --> 구성 --> 설정`으로 이동하여 Odoo를 통해 생성된 웹사이트에서 라이브 채팅 "
":guilabel:`위젯`을 삽입할 수 있습니다. 그런 다음 :guilabel:`실시간 채팅` 섹션으로 이동하여 사이트에 추가할 채널을 "
"선택합니다. :guilabel:`저장`을 클릭하면 적용됩니다."

#: ../../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 ""
"타사 플랫폼을 통해 제작한 웹사이트에 위젯을 추가하려면 :guilabel:`복사`하여 사이트의 `<head>` 태그에 코드를 "
"붙여넣습니다."

#: ../../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 ""
"마찬가지로, 고객이나 업체를 실시간 채팅으로 초대하려면 참여 링크가 포함되어 있는 두번째 :guilabel:`복사` 버튼을 클릭하십시오."

#: ../../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 ""
"채팅 중 운영자는 :doc:`명령어 </applications/websites/livechat/responses>` `/helpdesk`"
" 바로가기를 통해 채팅창을 닫지 않고도 상담 건을 생성할 수 있습니다. 채팅 내용은 신규 상담의 :guilabel:`설명` 탭 아래에 "
"추가됩니다."

#: ../../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 ""
"모든 상담 항목마다 :guilabel:`우선순위` 필드가 있습니다. 칸반 및 목록 화면의 상위에 우선순위가 가장 높은 상담이 표시됩니다."

#: ../../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 "Odoo 헬프데스크에서 해당 팀 칸반 및 우선순위가 매겨져 있는 작업 화면."

#: ../../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 "별 0개 = *우선순위 낮음*"

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:279
msgid "1 star = *Medium Priority*"
msgstr "별 1개 = *우선순위 중간*"

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:280
msgid "2 stars = *High Priority*"
msgstr "별 2개 = *우선순위 높음*"

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:281
msgid "3 stars = *Urgent*"
msgstr "별 3개 = *긴급*"

#: ../../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 ""
"상담 기본 설정은 우선순위 낮음 (별 0개)으로 설정되어 있습니다. 우선순위 레벨을 변경하려면 칸반 카드나 상담 상에 별 개수를 적절하게"
" 선택하십시오."

#: ../../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 ""
"우선순위 레벨은 :doc:`SLAs <sla>` 배정 기준으로도 사용될 수 있으므로 상담 우선순위 레벨 변경 시 :abbr:`SLA "
"(서비스 수준 계약)` 기한이 변경될 수 있습니다."

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:292
msgid ":doc:`/applications/general/email_communication/email_servers`"
msgstr ":doc:`/applications/general/email_communication/email_servers`"

#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293
msgid ":doc:`/applications/websites/livechat`"
msgstr ":doc:`/applications/websites/livechat`"

#: ../../content/applications/services/helpdesk/overview/reports.rst:3
msgid "Reporting"
msgstr "보고"

#: ../../content/applications/services/helpdesk/overview/reports.rst:5
msgid ""
"Odoo *Helpdesk* includes several reports that provide the opportunity to "
"track trends for customer support tickets, identify areas for improvement, "
"manage employee workloads, and confirm when customer expectations are met."
msgstr ""
"Odoo *헬프데스크*에서 사용할 수 있는 다양한 보고서를 통해 고객지원 상담 추세를 추적하고, 개선해야 할 부분이 있는지 파악하며 "
"영역을 식별하며, 직원들의 업무량 관리와 함께 고객 만족 달성 여부를 확인할 수 있습니다. "

#: ../../content/applications/services/helpdesk/overview/reports.rst:10
msgid "Available reports"
msgstr "사용할 수 있는 보고서 종류"

#: ../../content/applications/services/helpdesk/overview/reports.rst:12
msgid ""
"Details about the reports available in Odoo *Helpdesk* can be found below. "
"To view the different reports, go to :menuselection:`Helpdesk --> "
"Reporting`."
msgstr ""
"Odoo *헬프데스크* 보고서에 대한 자세한 내용은 아래에서 확인할 수 있습니다. 보고서를 확인하시려면 "
":menuselection:`헬프데스크 --> 보고` 메뉴로 이동하십시오."

#: ../../content/applications/services/helpdesk/overview/reports.rst:16
msgid "Ticket Analysis"
msgstr "티켓 분석"

#: ../../content/applications/services/helpdesk/overview/reports.rst:18
msgid ""
"The *Ticket Analysis* report (:menuselection:`Helpdesk --> Reporting --> "
"Ticket Analysis`) provides an overview of every customer support ticket in "
"the database. This includes the number of tickets assigned among teams and "
"individual users."
msgstr ""
"*상담 분석* 보고서 (:menuselection:`헬프데스크 --> 보고 --> 상담 분석`)에서는 데이터베이스에 있는 고객 지원 "
"상담에 대한 내용 전체를 확인할 수 있습니다.여기에는 팀별 혹은 개인 사용자 별로 배정된 상담 숫자가 포함되어 있습니다. "

#: ../../content/applications/services/helpdesk/overview/reports.rst:22
msgid ""
"This report is useful in identifying where teams are spending the most time,"
" and helps determine if there is an uneven workload distribution among the "
"support staff. The default report counts the number of tickets per team and "
"groups them by stage."
msgstr ""
"이 보고서는 관련 팀에서 시간이 가장 많이 소요되는 부분을 파악하기 위한 목적으로 유용하게 사용할 수 있으며 지원을 담당하는 직원 간에 "
"업무량이 적절하게 배분되었는지 검토할 수 있도록 합니다. 기본 보고서에서는 팀별로 상담 건수를 계산하여 단계별로 분류하고 있습니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
msgid "View of Ticket Analysis report default view."
msgstr "상담 분석 보고서의 기본 화면."

#: ../../content/applications/services/helpdesk/overview/reports.rst:30
msgid ""
"Alternative measures can be selected to track where the most time is spent "
"at different points in the workflow. To change the measures used for the "
"report that is currently displayed, or to add more, click the "
":guilabel:`Measures` button, and select one or more options from the drop-"
"down menu:"
msgstr ""
"작업 과정의 여러 지점 중 어느 부분에서 가장 업무 시간이 많이 소요되는지 추적하기 위해 다른 방법을 사용할 수도 있습니다. 현재 보고 "
"있는 보고서 측정값을 변경하거나 추가하려면 :guilabel:`측정값` 버튼을 클릭하여 드롭다운 메뉴에서 옵션을 선택합니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:35
msgid ""
":guilabel:`Average Hours to Respond`: average number of working hours "
"between a message sent from the customer and the response from the support "
"team. *This is does not include messages sent when the ticket was in a "
"folded stage*"
msgstr ""
":guilabel:`평균 응답 시간`: 고객 메시지를 받은 시간부터 지원 팀이 응답하기까지 걸린 작업 시간의 평균값입니다. *접음 단계에"
" 있는 상담건에서 받은 메시지는 포함하지 않습니다*"

#: ../../content/applications/services/helpdesk/overview/reports.rst:38
msgid ""
":guilabel:`Hours Open`: number of hours between the date the ticket was "
"created and the closed date. If there is no closed date on the ticket, the "
"current date is used. **This measure is not specific to working hours**"
msgstr ""
":guilabel:`진행 시간`: 상담이 생성된 날짜부터 종료된 날짜까지의 시간입니다. 상담에 종료 날짜가 없는 경우에는 현재 당일 "
"날짜를 사용합니다. **근무 시간으로만 국한하여 측정되는 것이 아닙니다**"

#: ../../content/applications/services/helpdesk/overview/reports.rst:41
msgid ""
":guilabel:`Hours Spent`: number of *Timesheet* hours logged on a ticket. "
"*This measure is only available if Timesheets are enabled on a team, and the"
" current user has the access rights to view them*"
msgstr ""
":guilabel:`소요 시간`: 상담에 기록된 *작업시간* 수치입니다. *작업시간표가 팀에서 활성화되어 있으며 현재 사용자에게 접근 "
"권한이 있는 경우에만 이 방법을 사용할 수 있습니다*"

#: ../../content/applications/services/helpdesk/overview/reports.rst:44
msgid ""
":guilabel:`Hours to Assign`: number of working hours between the date on "
"which the ticket was created and when it was assigned to a team member"
msgstr ":guilabel:`배정 소요 시간`: 상담이 생성된 날짜와 담당자에게 배정되기까지 근무 시간 기준의 시간입니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:46
msgid ""
":guilabel:`Hours to Close`: number of working hours between the date on "
"which the ticket was created and the date it was closed"
msgstr ":guilabel:`종료 시간`: 상담이 생성된 날짜와 종료되기까지의 날짜 사이의 근무 시간 기준의 시간입니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:48
msgid ""
":guilabel:`Hours to First Response`: number of working hours between the "
"date on which the ticket was received and the date one which the first "
"message was sent. *This does not include email sent automatically when a "
"ticket reaches a stage*"
msgstr ""
":guilabel:`최초 응답 시간`: 상담이 접수된 날짜와 처음으로 메시지를 보낸 날짜 사이의 근무 시간 기준의 시간입니다. *여기에는"
" 상담 단계마다 자동 전송되는 이메일은 포함되지 않습니다*"

#: ../../content/applications/services/helpdesk/overview/reports.rst:51
msgid ""
":guilabel:`Hours to SLA Deadline`: number of working hours remaining to "
"reach the last :abbr:`SLA (Service Level Agreement)` deadline on a ticket"
msgstr ""
":guilabel:`SLA 기한일까지의 시간`: 상담에서 :abbr:`SLA (서비스 수준 계약)` 최종 기한까지 남은 근무 시간 기준의"
" 시간입니디."

#: ../../content/applications/services/helpdesk/overview/reports.rst:53
msgid ""
":guilabel:`Rating /5`: number valued assigned to the rating received from a "
"customer (Dissatisfied = 1, Okay/Neutral = 3, Satisfied = 5)"
msgstr ""
":guilabel:`평점 /5`: 고객으로부터 받은 평가를 점수로 환산한 값(불만족 = 1, 좋음/보통 = 3, 만족 = 5)입니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:55
#: ../../content/applications/services/helpdesk/overview/reports.rst:99
msgid ":guilabel:`Count`: number of tickets in total"
msgstr ":guilabel:`Count`: 상담 건수 총계"

#: ../../content/applications/services/helpdesk/overview/reports.rst:58
msgid ""
"*Working hours* are calculated based on the default working calendar. To "
"view or change the working calendar, go to the :menuselection:`Settings` "
"application and select :menuselection:`Employees --> Company Working Hours`."
msgstr ""
"*근무 시간*은 기본 근무 일정을 기준으로 계산됩니다. 작업 일정을 보거나 변경하려면 :menuselection:`설정` 애플리케이션으로"
" 이동하여 :menuselection:`직원 --> 회사 근무 시간`을 선택하십시오."

#: ../../content/applications/services/helpdesk/overview/reports.rst:63
msgid "SLA Status Analysis"
msgstr "SLA 상태 분석"

#: ../../content/applications/services/helpdesk/overview/reports.rst:65
msgid ""
"The *SLA Status Analysis* report (:menuselection:`Helpdesk --> Reporting -->"
" SLA Status Analysis`) tracks how quickly an SLA (Service Level Agreement) "
"is fulfilled, as well as the success rate of individual policies."
msgstr ""
"*SLA 상태 분석* 보고서 (:menuselection:`헬프데스크 --> 보고 --> SLA 상태 분석`)는 SLA (서비스 수준 "
"계약)가 얼마나 신속하게 이행될 수 있었는지와 함께 정책별 성공률을 추적합니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:69
msgid ""
"By default, this report is filtered to show the number of :abbr:`SLAs "
"(Service Level Agreements)` failed, as well as the failure rate over the "
"last 30 days, grouped by team."
msgstr ""
"보고서 기본 설정으로 계약에 실패한 SLA (서비스 수준 계약) 수치와 지난 30일 동안의 실패율을 팀별로 묶어서 보여주도록 필터가 "
"적용되어 있습니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
msgid "View of Group by options of Ticket Analysis report."
msgstr "상담 분석 보고서에 그룹 필터가 적용되어 있는 화면."

#: ../../content/applications/services/helpdesk/overview/reports.rst:76
msgid ""
"To change the measures used for the report that is currently displayed, or "
"to add more, click the :guilabel:`Measures` button, and select one or more "
"options from the drop-down menu:"
msgstr ""
"현재 확인하고 있는 보고서 측정값을 변경하거나 추가하려면 :guilabel:`측정값` 버튼을 클릭하고 드롭다운 메뉴에서 옵션을 "
"선택합니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:79
msgid ""
":guilabel:`% of Failed SLA`: percentage of tickets that have failed at least"
" one :abbr:`SLA (Service Level Agreement)`"
msgstr ":guilabel:`SLA 실패율`: :abbr:`SLA (서비스 수준 계약)가 실패한 건이 있는 상담 비율"

#: ../../content/applications/services/helpdesk/overview/reports.rst:81
msgid ""
":guilabel:`% of SLA in Progress`: percentage of tickets that have at least "
"one :abbr:`SLA (Service Level Agreement)` still in progress, and have not "
"failed any :abbr:`SLAs (Service Level Agreements)`"
msgstr ""
":guilabel:`SLA 진행률`: :abbr:`SLA (서비스 수준 계약)`에 대해서 하나 이상 아직 진행 중이며 실패한 항목이 없는"
" 상담 비율"

#: ../../content/applications/services/helpdesk/overview/reports.rst:84
msgid ""
":guilabel:`% of Successful SLA`: percentage of tickets where all :abbr:`SLAs"
" (Service Level Agreements)` have been successful"
msgstr ":guilabel:`SLA 성공률`: :abbr:`SLA (서비스 수준 계약)` 전체를 성사한 상담 비율"

#: ../../content/applications/services/helpdesk/overview/reports.rst:86
msgid ""
":guilabel:`Number of SLA Failed`: number of tickets that have failed at "
"least one :abbr:`SLA (Service Level Agreement)`"
msgstr ":guilabel:`SLA 실패 수`: :abbr:`SLA (서비스 수준 계약)` 성사 실패한 건이 있는 상담 수"

#: ../../content/applications/services/helpdesk/overview/reports.rst:88
msgid ""
":guilabel:`Number of SLA Successful`: number of tickets where all "
":abbr:`SLAs (Service Level Agreements)` have been successful"
msgstr ":guilabel:`SLA 성공 수`: :abbr:`SLA (서비스 수준 계약)` 전체가 성사된 상담 수"

#: ../../content/applications/services/helpdesk/overview/reports.rst:90
msgid ""
":guilabel:`Number of SLA in Progress`: number of tickets that have at least "
"one :abbr:`SLA (Service Level Agreement)` still in progress, and have not "
"failed any :abbr:`SLAs (Service Level Agreements)`"
msgstr ""
":guilabel:`SLA 진행 수`: :abbr:`SLA (서비스 수준 계약)`가 아직 하나 이상 진행 중이며 실패한 항목이 없는 상담"
" 수"

#: ../../content/applications/services/helpdesk/overview/reports.rst:93
msgid ""
":guilabel:`Working Hours to Assign`: number of working hours between the "
"date on which the ticket was created and when it was assigned to a team "
"member"
msgstr ":guilabel:`할당할 근무 시간`: 상담 생성 날짜와 담당자에게 할당된 날짜까지의 근무 시간 기준의 시간"

#: ../../content/applications/services/helpdesk/overview/reports.rst:95
msgid ""
":guilabel:`Working Hours to Close`: number of working hours between the date"
" on which the ticket was created and the date it was closed"
msgstr ":guilabel:`종료까지의 근무 시간`: 상담 생성 날짜와 종료된 날짜 사이의 근무 시간 기준의 시간"

#: ../../content/applications/services/helpdesk/overview/reports.rst:97
msgid ""
":guilabel:`Working Hours to Reach SLA`: number of working hours between the "
"date on which the ticket was created and the date the :abbr:`SLA (Service "
"Level Agreement)` was satisfied"
msgstr ""
":guilabel:`SLA 까지의 근무 시간`: 상담 생성 날짜와 :abbr:`SLA  (서비스 수준 계약)`가 완료된 날짜 사이의 근무"
" 시간 기준의 시간"

#: ../../content/applications/services/helpdesk/overview/reports.rst:102
msgid ""
"To see the number of tickets that were able to achieve the stated :abbr:`SLA"
" (Service Level Agreement)` objectives, and track the amount of time it took"
" to achieve those objectives, click :menuselection:`Measures --> Number of "
"SLA Successful` and :menuselection:`Measures --> Working Hours to Reach "
"SLA`."
msgstr ""
"해당 :abbr:`SLA (서비스 수준 계약)` 목표를 달성한 상담 건수를 확인하고 목표 달성에 걸린 시간을 추적하려면 "
":menuselection:`측정값 --> SLA 성공 수` 및 :menuselection:`측정값 --> SLA까지의 근무 시간`을 "
"클릭하십시오."

#: ../../content/applications/services/helpdesk/overview/reports.rst:107
msgid ""
"To sort these results by the team members assigned to the tickets, select "
":menuselection:`Total --> Assigned to`."
msgstr "상담을 배정한 담당자별로 결과를 정렬하려면 :menuselection:`전체 --> 할당 대상`을 선택하세요."

#: ../../content/applications/services/helpdesk/overview/reports.rst:111
msgid ""
":doc:`Service Level Agreements (SLA) "
"</applications/services/helpdesk/overview/sla>`"
msgstr ""
":doc:`서비스 수준 계약 (SLA: Service Level Agreements) "
"</applications/services/helpdesk/overview/sla>`"

#: ../../content/applications/services/helpdesk/overview/reports.rst:114
msgid "Customer Ratings"
msgstr "고객 평가"

#: ../../content/applications/services/helpdesk/overview/reports.rst:116
msgid ""
"The *Customer Ratings* report (:menuselection:`Helpdesk --> Reporting -- "
"Customer Ratings`) displays an overview of the ratings received on "
"individual support tickets, as well as any additional comments submitted "
"with the rating."
msgstr ""
"*고객 평가* 보고서 (:menuselection:`헬프데스크 --> 보고 -- 고객 평가`)에서는 상담 건별 평가에 대한 전체 내용과 "
"함께 추가 코멘트를 확인할 수 있습니다. "

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
msgid "View of the kanban display in the Customer Ratings report."
msgstr "고객 평가 보고서의 칸반 표시 화면."

#: ../../content/applications/services/helpdesk/overview/reports.rst:124
msgid ""
"Click on an individual rating to see additional details about the rating "
"submitted by the customer, including a link to the original ticket."
msgstr "개별 평가 내용을 클릭하면 원본 상담 링크를 포함하여 고객으로부터 받은 평가 관련 추가 세부 정보를 볼 수 있습니다. "

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
msgid "View of the details of an individual customer rating."
msgstr "개별 고객 평가의 세부 정보 화면."

#: ../../content/applications/services/helpdesk/overview/reports.rst:132
msgid ""
"On the rating's details page, select the :guilabel:`Visible Internally Only`"
" option to hide the rating from the customer portal."
msgstr ""
"세부 평가 정보 페이지에서 :guilabel:`내부 검토만 허용` 옵션을 선택하면 고객 포털에서 평가 내용이 보이지 않게 됩니다"

#: ../../content/applications/services/helpdesk/overview/reports.rst:135
msgid ""
"The *Customer Ratings* report is displayed in a kanban view by default, but "
"can also be displayed in graph, list, or pivot view."
msgstr "*고객 평가* 보고서는 기본 설정이 칸반 보기로 되지만 그래프, 목록 또는 피벗으로도 나타낼 수 있습니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:139
msgid ":doc:`Ratings </applications/services/helpdesk/overview/ratings>`"
msgstr ":doc:`평가 </applications/services/helpdesk/overview/ratings>`"

#: ../../content/applications/services/helpdesk/overview/reports.rst:142
msgid "View and filter options"
msgstr "보기 및 필터 옵션"

#: ../../content/applications/services/helpdesk/overview/reports.rst:144
msgid ""
"On any Odoo report, the view and filter options vary, depending on what data"
" is being analyzed, measured, and grouped. See below for additional "
"information on the available views for the *Helpdesk* reports."
msgstr ""
"Odoo 보고서에서는 보기 및 필터 옵션은 분석이나 측정 대상 및 그룹화 대상이 되는 데이터에 따라 각각 다릅니다. *헬프데스크* 보고서"
" 화면에 대한 추가 정보는 아래 내용을 참조하십시오."

#: ../../content/applications/services/helpdesk/overview/reports.rst:149
msgid ""
"Only one measure may be selected at a time for graphs, but pivot tables can "
"include multiple measures."
msgstr "그래프의 측정값은 한 번에 하나만 선택할 수 있지만 피벗 테이블에는 측정값을 여러 개 넣을 수 있습니다. "

#: ../../content/applications/services/helpdesk/overview/reports.rst:153
msgid "Pivot view"
msgstr "피벗 보기"

#: ../../content/applications/services/helpdesk/overview/reports.rst:155
msgid ""
"The *pivot* view presents data in an interactive manner. All three "
"*Helpdesk* reports are available in pivot view."
msgstr ""
"*피벗*은 인터렉티브한 방식으로 데이터를 표시합니다. *헬프데스크*에서 사용되는 보고서 3 가지 모두 피벗 화면을 사용할 수 있습니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:158
msgid ""
"The pivot view can be accessed on any report by selecting the "
":guilabel:`grid icon` at the top right of the screen."
msgstr "피벗 화면에 있는 오른쪽 상단 :guilabel:`그리드 아이콘`을 클릭하면 어떤 보고서든 확인할 수 있습니다. "

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
msgid "View of the SLA status analysis report in Odoo Helpdesk."
msgstr "Odoo 헬프데스크의 SLA 상태 분석 보고서 화면."

#: ../../content/applications/services/helpdesk/overview/reports.rst:165
msgid ""
"To add a group to a row or column to the pivot view, click the :guilabel:`➕ "
"(plus sign)` next to :guilabel:`Total`, and then select one of the groups. "
"To remove one, click the :guilabel:`➖ (minus sign)` and de-select the "
"appropriate option."
msgstr ""
"피벗 화면의 행이나 열에 그룹을 추가하려면 :guilabel:`총계` 옆에 있는 :guilabel:`➕ (더하기 기호)`를 클릭한 다음 "
"그룹 중에서 하나를 선택합니다. 삭제하려면 :guilabel:`➖ (빼기 기호)`를 클릭하여 선택되어 있는 해당 옵션을 취소합니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:170
msgid "Graph view"
msgstr "그래프 보기"

#: ../../content/applications/services/helpdesk/overview/reports.rst:172
msgid ""
"The *graph* view presents data in either a *bar*, *line*, or *pie* chart."
msgstr "*그래프* 화면에서는 *막대*, *선* 또는 *원* 그래프로 데이터를 표시합니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:174
msgid ""
"Switch to the graph view by selecting the :guilabel:`line chart icon` at the"
" top right of the screen. To switch between the different charts, select the"
" *related icon* at the top left of the chart, while in graph view."
msgstr ""
"화면 오른쪽 상단에 있는 :guilabel:`선 그래프 아이콘`을 선택하면 그래프 화면으로 전환됩니다. 다른 차트 보기로 바꾸려면 그래프"
" 화면에서 그래프 왼쪽 상단에 있는 *관련 아이콘*을 선택하세요."

#: ../../content/applications/services/helpdesk/overview/reports.rst:180
msgid "Bar chart"
msgstr "막대 그래프"

#: ../../content/applications/services/helpdesk/overview/reports.rst:0
msgid "View of the SLA status analysis report in bar view."
msgstr "막대 그래프로 나타낸 SLA 상태 분석 보고서 화면."

#: ../../content/applications/services/helpdesk/overview/reports.rst:186
msgid "Line chart"
msgstr "선 그래프"

#: ../../content/applications/services/helpdesk/overview/reports.rst:0
msgid "View of the Customer Ratings report in line view."
msgstr "선 그래프로 나타낸 고객 평가 보고서 화면."

#: ../../content/applications/services/helpdesk/overview/reports.rst:192
msgid "Pie chart"
msgstr "원 그래프"

#: ../../content/applications/services/helpdesk/overview/reports.rst:0
msgid "View of the Ticket analysis report in pie chart view."
msgstr "원 그래프로 나타낸 상담 분석 보고서 화면."

#: ../../content/applications/services/helpdesk/overview/reports.rst:199
msgid ""
"Both the *bar chart* and *line chart* can utilize the *stacked* view option."
" This presents two (or more) groups of data on top of each other, instead of"
" next to each other, making it easier to compare data."
msgstr ""
"*막대 그래프*와 *선 그래프*에서 *누적* 보기 옵션을 활용할 수 있습니다. 이렇게 하면 데이터 그룹이 두 개 (또는 그 이상)여도 "
"나란히 표시되는 것이 아니라 서로 위에 표시되게 하여 데이터를 쉽게 비교할 수 있습니다. "

#: ../../content/applications/services/helpdesk/overview/reports.rst:204
msgid "Save and share a favorite search"
msgstr "즐겨찾는 검색 항목 저장 및 공유하기"

#: ../../content/applications/services/helpdesk/overview/reports.rst:206
msgid ""
"The *Favorites* feature found on *Helpdesk* reports allows users to save "
"their most commonly used filters without having to reconstruct them every "
"time they are needed."
msgstr ""
"*헬프데스크* 보고서에서 *즐겨찾기* 기능을 사용하면 가장 일반적으로 사용하는 필터를 저장하여 필요할 때마다 다시 설정하지 않아도 "
"됩니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:209
msgid ""
"To create and save new *Favorites* on a report, follow the steps below:"
msgstr "보고서에 새로운 *즐겨찾기* 항목을 생성하여 저장하려면 다음의 단계대로 진행하십시오."

#: ../../content/applications/services/helpdesk/overview/reports.rst:211
msgid ""
"Set the necessary parameters using the :guilabel:`Filters`, :guilabel:`Group"
" By` and :guilabel:`Measures` options."
msgstr ""
":guilabel:`필터`, :guilabel:`그룹` 및 :guilabel:`측정값` 옵션으로 필요한 매개변수를 설정합니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:213
msgid "Click :menuselection:`Favorites --> Save current search`."
msgstr ":menuselectio:`즐겨찾기 --> 현재 검색 저장`을 클릭합니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:214
msgid "Rename the search."
msgstr "검색명을 변경합니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:215
msgid ""
"Select :guilabel:`Use by default` to have these filter settings "
"automatically displayed when the report is opened. Otherwise, leave it "
"blank."
msgstr ""
"보고서를 열 때 설정해놓은 필터를 자동으로 표시하게 하려면 :guilabel:`기본으로 사용`을 선택하십시오. 그렇지 않을 경우에는 "
"공란으로 둡니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:217
msgid ""
"Select :guilabel:`Share with all users` to make this filter available to all"
" other database users. If this box is not checked, it will only be available"
" to the user who creates it."
msgstr ""
"다른 데이터베이스 사용자 모두가 이 필터를 사용할 수 있도록 하려면 :guilabel:`모든 사용자와 공유`를 선택하십시오. 선택란에 "
"표시하지 않는 경우에는 필터를 만든 사람만 사용할 수 있습니다."

#: ../../content/applications/services/helpdesk/overview/reports.rst:219
msgid "Click :guilabel:`Save` to preserve the configuration for future use."
msgstr "나중에 사용할 수 있도록 설정 내용을 저장하려면 :guilabel:`저장`을 클릭하십시오."

#: ../../content/applications/services/helpdesk/overview/reports.rst-1
msgid "View of the save favorites option in Odoo Helpdesk."
msgstr "Odoo 헬프데스크의 즐겨찾기 저장 옵션 화면."

#: ../../content/applications/services/helpdesk/overview/reports.rst:226
msgid ""
":doc:`Start receiving tickets "
"</applications/services/helpdesk/overview/receiving_tickets>`"
msgstr ""
":doc:`상담 접수 시작 </applications/services/helpdesk/overview/receiving_tickets>`"

#: ../../content/applications/services/helpdesk/overview/reports.rst:227
msgid ":doc:`Odoo reporting </applications/general/reporting>`"
msgstr ":doc:`Odoo 보고 </applications/general/reporting>`"

#: ../../content/applications/services/helpdesk/overview/sla.rst:3
msgid "Service Level Agreements (SLA)"
msgstr "SLA (SLA: 서비스 수준 계약)"

#: ../../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 ""
"서비스 수준 계약 (SLA: Service Level Agreements)은 고객이 공급자에게서 받을 수 있는 서비스 수준을 정의합니다."
" SLA에는 고객이 결과를 받아볼 수 있는 기한이 제시되어 있으며 지원팀의 목표하는 내용에 대한 일정을 확인할 수 있습니다."

#: ../../content/applications/services/helpdesk/overview/sla.rst:10
msgid "Create a new SLA policy"
msgstr "신규 SLA 정책 수립"

#: ../../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 ""
"새로운 SLA (서비스 수준 계약)` 정책을 만드려면 :menuselection:`헬프데스크 --> 구성 --> 팀`에서 팀 페이지로 "
"이동합니다. 팀을 선택하고, 아래에 있는 :guilabel:`성과` 섹션으로 이동한 후, SLA 정책 옆의 선택란에 표시하여 특정 팀을 "
"활성화시킵니다."

#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of a team page in Helpdesk focusing on the SLA Policies setting"
msgstr "SLA 정책 설정 항목에 맞추어져 있는 헬프데스크의 팀 페이지 화면"

#: ../../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 ""
":guilabel:`근무 시간` 필드 옆에 표시되어 있는 값으로 서비스 수준 계약 (SLA: Service Level "
"Agreements) 정책의 기한이 결정됩니다. 이는 기본값으로 :menuselection:`설정 앱 --> 직원 --> 근무 기관` "
"아래에 있는 :guilabel:`회사 근무 시간` 필드 설정값으로 결정됩니다."

#: ../../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 ""
"새로운 정책을 만드려면 팀의 설정 페이지에 있는 스마트 버튼을 클릭하거나 :menuselection:`헬프데스크 --> 구성 --> "
"SLA 정책` 메뉴에서 :guilabel:`새로 만들기`를 클릭하십시오. 새로운 정책에 사용할 :guilabel:`제목` 및 "
":guilabel:`설명`을 입력을 시작으로 아래에 있는 단계대로 양식을 작성하십시오."

#: ../../content/applications/services/helpdesk/overview/sla.rst:33
msgid "Define the criteria for an SLA policy"
msgstr "SLA 정책 상의 항목 정의"

#: ../../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 ""
":guilabel:`기준` 섹션은 어떤 상담에 정책을 적용할 수 있을지 검토하는 목적으로 사용합니다. 선택 기준을 조정하려면 다음의 "
"필드를 입력하십시오."

#: ../../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 ":guilabel:`팀`: 한 팀에 한 항목만 적용시킬 수 있습니다. *필수 항목입니다.*"

#: ../../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 ""
":guilabel:`우선순위`: 상담의 우선순위 레벨은 칸반 카드나 상담 자체에 있는 우선순위 별 숫자로 파악하게 됩니다. "
":abbr:`SLA (서비스 수준 계약)`은 상담에 있는 우선순위 레벨이 :abbr:`SLA (서비스 수준 계약)` 기준에 맞도록 "
"업데이트한 경우에만 적용할 수 있습니다. 이 필드에서 선택한 내용이 없는 경우 이 정책은 '우선순위 낮음' (별 0개)로 표시된 상담에만"
" 적용됩니다."

#: ../../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 ""
":guilabel:`유형`: 상담 유형 항목은 고객 질문이 간단한 답변으로 해결될 수 있거나 아니면 추가로 알아봐야 할 내용이 있는 "
"경우에 유용하게 사용할 수 있습니다. 이 항목에서는 상담 유형을 여러 개 선택할 수 있습니다. 선택한 내용이 없는 경우에는 모든 상담 "
"유형에 이 항목이 적용됩니다."

#: ../../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 ""
":guilabel:`태그`: 태그는 상담 내용이 무엇인지 간략하게 나타낼 수 있습니다. 한 건의 상담에 여러 개의 태그를 적용시킬 수 "
"있습니다."

#: ../../content/applications/services/helpdesk/overview/sla.rst:50
msgid ""
":guilabel:`Customers`: individual contacts or companies may be selected in "
"this field."
msgstr ":guilabel:`고객`: 개인별 연락처나 회사를 선택할 수 있습니다."

#: ../../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 ""
":guilabel:`판매주문서 아이템`: 이 항목은 팀에서 *작업시간* 앱을 사용하는 경우에만 사용할 수 있습니다. 이를 통해 상담 건의"
" :guilabel:`판매주문서 아이템` 에 표시할 판매주문서의 항목으로 상담 건을 직접 연결해 놓을 수 있습니다."

#: ../../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 ""
"별도로 안내해놓지 않는 이상, 필드에서 여러 개의 항목을 선택할 수 있습니다. (예를 들어, :guilabel:`태그`는 여러 개가 "
"정책에 포함될 수 있지만 :guilabel:`우선순위` 레벨은 하나만 선택할 수 있음)"

#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of a blank SLA policy record"
msgstr "내용이 입력되지 않은 SLA 정책 화면"

#: ../../content/applications/services/helpdesk/overview/sla.rst:64
msgid "Establish a target for an SLA policy"
msgstr "SLA 정책에 대한 목표 설정"

#: ../../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 ""
":guilabel:`목표`는 SLA (서비스 수준 계약)` 정책대로 상담이 도달해야 하는 단계이자 해당 단계까지 오는데 소요된 "
"시간입니다. :guilabel:`단계 도달` 항목에서 팀에 어떤 단계를 할당할 지 선택할 수 있습니다. :guilabel:`단계 제외`로"
" 제외된 단계에서 소요된 시간은 :abbr:`SLA (서비스 수준 계약)` 기한 계산에 포함하지 않습니다. "

#: ../../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 ""
":abbr:`SLA (서비스 수준 계약)` 제목이 `종료까지 8시간'으로 되어 있는 경우, 상담이 종료되기 전까지의 작업 시간을 추적하고"
" :guilabel:'단계 도달' 항목으로 '해결 완료'를 설정하게 됩니다. 그러나 :abbr:`SLA (서비스 수준 계약)` 제목이 "
"`시작까지 2일`인 경우에는 상담 작업을 시작하기 전에 작업 시간을 추적하고 티켓 작업이 시작되기 전에 작업 시간을 추적하고 "
":guilabel:`단계 도달` 항목으로 `진행 중`이 표시됩니다. "

#: ../../content/applications/services/helpdesk/overview/sla.rst:79
msgid "Meeting SLA deadlines"
msgstr "SLA 기한 충족"

#: ../../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 ""
"상담이  :abbr:`SLA (서비스 수준 계약)` 정책의 기준에 부합하는 경우, 해당되는 기한을 계산합니다. 기한은 상담 생성 날짜와 "
"목표로 하는 작업 시간을 기준으로 합니다. 상담 항목에 기한이 추가되고 적용된  :abbr:`SLA (서비스 수준 계약)`명을 흰색 "
"태그로 추가합니다."

#: ../../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 "Odoo 헬프데스크의 상담에 있는 공개 SLA 기한에 초점이 맞추어져 있는 상담 양식 화면"

#: ../../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 ""
"상담이 복수의 :abbr:`SLA (서비스 수준 계약)` 기준에 부합하는 경우에는 상담에 가장 빠른 날짜가 기한으로 표시됩니다. 기한 "
"일자가 경과되는 경우 다음 기한일이 표시됩니다. "

#: ../../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 ""
"상담이 :abbr:`SLA (서비스 수준 계약)` 정책 내용에 부합하는 경우 :abbr:`SLA (서비스 수준 계약)` 태그가 녹색으로 "
"바뀌고 :guilabel:`기한` 항목이 보기에서 사라집니다."

#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk"
msgstr "Odoo 헬프데스크에서 SLA 내용을 충족하는 상담 양식 화면"

#: ../../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 ""
":abbr:`SLA (서비스 수준 계약)` 기한이 경과했는데도 상담이 :guilabel:`단계 도달`항목으로 이동되지 않은 경우에는 "
":abbr:`SLA (서비스 수준 계약)` 태그가 빨간색으로 바뀝니다. :abbr:`SLA (서비스 수준 계약)`이 성사되지 못한 경우 "
"상담이 :guilabel:`단계 도달`로 이동되더라도 상담에 빨간색 태그가 남아 있게 됩니다."

#: ../../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 "Odoo 헬프데스크에서 SLA가 실패하거나 통과한 상담 양식 화면"

#: ../../content/applications/services/helpdesk/overview/sla.rst:112
msgid "Analyzing SLA performance"
msgstr "SLA 성과 분석"

#: ../../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 ""
":guilabel:`SLA 상태 분석` 보고서는 개별 정책의 성공률 뿐만 아니라 SLA (서비스 수준 계약)`가 얼마나 빨리 이행될 수 "
"있는지를 확인합니다. :menuselection:`헬프데스크 --> 보고 --> SLA 상태 분석`에서 보고서 및 해당 피벗 테이블로 "
"이동합니다."

#: ../../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 ""
"기본 설정으로 보고서는 :guilabel:`피벗` 화면으로 표시되며 팀별 그룹으로 지난 30일 동안 SLA 실패 건수와 실패율을 "
"표시하도록 필터가 설정되어 있습니다."

#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of the SLA status analysis report in Odoo Helpdesk"
msgstr "Odoo 헬프데스크에서의 SLA 상태 분석 보고서 화면"

#: ../../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 ""
"SLA가 통과되었거나 진행 중인 숫자를 추가하려면 :guilabel:`측정값` 버튼을 클릭하여 보고 항목에 대한 드롭다운 메뉴에서 원하는"
" 측정 내용에 따라서 값을 선택하십시오. 측정값을 클릭하면 드롭다운 메뉴에 해당 측정값이 선택되었다고 체크 표시로 표시되고 피벗 테이블에"
" 이에 해당하는 새로운 열이 추가되어 값이 계산됩니다."

#: ../../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 ""
"행이나 열에 그룹을 추가하려면 :guilabel:`총계` 옆에 있는 더하기 :guilabel:` + ` 버튼을 클릭하여 그룹 내에서 "
"선택합니다. 삭제하려면 빼기 :guilabel:` - ` 버튼을 클릭하여 선택을 취소합니다."

#: ../../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 ""
":guilabel:`상태 분석` 보고서는 :guilabel:`막대`, :guilabel:`선` 또는 :guilabel:`원` 그래프로도 "
"확인할 수 있습니다. 그래프 상단에서 아이콘을 선택하여 화면을 전환하여 볼 수 있습니다. "

#: ../../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 "막대 그래프로 표시한 SLA 상태 분석 보고서 화면"

#: ../../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 "선 그래프로 표시한 SLA 상태 분석 보고서 화면"

#: ../../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 "원 그래프로 표시한 SLA 상태 분석 보고서 화면"

#: ../../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 ""
":guilabel:`막대 그래프`와 :guilabel:`선 그래프` :guilabel:`누적` 화면으로 표시할 수 있습니다. 이렇게 하면"
" 그룹이 여러 개일 때 나란히 표시하지 않고 서로 위에 표시하여 데이터를 쉽게 비교할 수 있습니다."

#: ../../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 ""
":guilabel:`특정 집단`은 일정 기간 동안의 데이터 변화를 추적하는 데 사용합니다. :guilabel:`상태 분석` 보고서를 "
":guilabel:`특정 집단`을 이용하여 표시하려면 그래프 위에서 오른쪽 상단 끝에 있는 아이콘을 클릭하십시오."

#: ../../content/applications/services/helpdesk/overview/sla.rst-1
msgid "View of the SLA status analysis report in cohort view"
msgstr "특정 집단으로 표시한 SLA 상태 분석 보고서 화면"

#: ../../content/applications/services/helpdesk/overview/sla.rst:183
msgid ":ref:`Reporting views <reporting/views>`"
msgstr ":ref:`보고 화면 <reporting/views>`"

#: ../../content/applications/services/helpdesk/overview/sla.rst:184
msgid ""
":doc:`Allow customers to close their tickets "
"</applications/services/helpdesk/advanced/close_tickets>`"
msgstr ""
":doc:`고객쪽에서 상담을 종료할 수 있도록 허용 "
"</applications/services/helpdesk/advanced/close_tickets>`"

#: ../../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 ""
"선불 지원 서비스로 진행할 수 있도록 선택할 수 있습니다. 즉, 판매주문서와 청구서를 발행하여 서비스가 종료되면 소요된 시간을 공제할 수"
" 있습니다. Odoo 애플리케이션들은 완전히 통합되어 있어서 고객들의 요구에 더욱 빠르게 대응할 수 있기에 가능한 일입니다. "

#: ../../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 ""
"Odoo 프로젝트는 진행하고 있는 프로젝트를 관리하는 툴입니다. 작업 일정을 수립하고, 동료에게 업무를 배정하거나, 각 프로젝트별 "
"수익성을 관리할 수 있습니다.  "

#: ../../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 ""
"`Odoo 튜토리얼: 칸반 프로젝트 관리 <https://www.odoo.com/slides/slide/kanban-project-"
"management-1664>`_"

#: ../../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 ":ref:`upgrade/sla`"

#: ../../content/services/support/what_can_i_expect.rst:38
msgid ":doc:`/administration/maintain/supported_versions`"
msgstr ":doc:`/administration/maintain/supported_versions`"

#: ../../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 ":doc:`/administration/upgrade`"