Primerjava izbranih različic
Prikazane so razlike med izbrano in trenutno različico strani.
| Both sides previous revision Prejšnja revizija Naslednja revizija | Prejšnja revizija | ||
|
us:slobase:manual:c_modules:h_support [dd/mm/Y H:i] mgregorc |
us:slobase:manual:c_modules:h_support [dd/mm/Y H:i] (Trenutna) admin |
||
|---|---|---|---|
| Vrstica 1: | Vrstica 1: | ||
| ====== HelpDesk ====== | ====== HelpDesk ====== | ||
| - | Produs IO makes feasible main and common management, solving and managing tickets, remarks and wishes of buyers. Tickets are usually entered by users that are in contact with omogoča tudi centralno in skupinsko vodenje, reševanje in upravljanje z reklamacijami, pripombami in željami kupcev. Običajno zahteve kupcev vnašajo osebe, ki so v stiku s stranko ali delajo v klicnem centru. Kasneje se zahteve razporejajo in njih reševanje nadzira. | + | Produs IT enables central and common management, solving and managing tickets and remarks or wishes of buyers. Tickets are usually entered by users that are in Contact with an Account or work in a call center. Tickets are arranged later and their solutions are supervised. |
| - | S pomočjo Produs IO lahko na enem mestu zbirate zahteve, vprašanja, pripombe in težave, ki so povezane s posameznimi izdelki, ki ste jih prodali svojim strankam. Po eni strani je zelo uporaben za skupino vzdrževalcev in po drugi strani izredno pregleden za prodajni tim, ki lahko hitro ugotovi kakšno je stanje pri posamezni stranki ali z določenim izdelkom, ki ga želi prodati. | + | Produs IT helps you choose demands, questions, annotations and problems, connected with particular products, sold to your customers. It is very applicable for maintenance and very easily examined by a sales team, which can quickly determine the condition with an individual customer or product you wish to sell. |
| - | ===== Zahteve ===== | ||
| - | Zahteve imenujemo vse reklamacije, pripombe in želje, ki so prišle s strani naših strank in tudi tiste, ki smo jih zabeležili sami. Pomembno je, da jih shranimo v sistem. Poglejmo si, kako zabeležimo novo zahtevo. | + | ===== Ticket ===== |
| - | Če želite ustvariti novo zahtevo, kliknite na //Nova zahteva// na [[../../../b_usage:d_loginpage#podrocja| področju vnosa]]. Odprla se vam bo nova stran, kot je prikazana na spodnji sliki. | + | Tickets by definition are reclamations, remarks and wishes of Accounts and also what we have noted ourselves. It is important to save them into the system. Let us take a look at how to note a new ticket. |
| + | |||
| + | Click //New Ticket// on [[../../../b_usage:d_loginpage#podrocja| entry section]] to create a new Ticket. A new page opens (see picture below). | ||
| {{si:slobase:manual:c_modules:newticket.png?450}} | {{si:slobase:manual:c_modules:newticket.png?450}} | ||
| - | V prikazan obrazec lahko vnesete podatke o zahtevi. Če podatke vnaša več uporabnikov, svetujemo, da se dogovorite in določite standarde vnosov. Tako bodo vneseni podatki enotni. Odvečna polja, ki jih pri svojem delu ne potrebujete lahko pustite prazna ali nas kontaktirajte in jih bomo po vaši želji odstranili. | + | Enter the Ticket data. If there are more users entering the data, our advice is to agree and define entry standards. In this way all the entered data is unified. Redundant fields should be left empty or just give us a call and we will remove them. |
| - | Vpišite čim več podatkov. Uporabite vse možnosti za opis zahteve: določite prioriteto, resnost in kategorijo. Tako boste zahteve lažje razvrščali v reševanje in jih poiskali. | + | Enter as much data as you can. Use all options for Ticket description: define Priority, Severity and Category in order to sort the Ticket in solutions and to make it easy to find later on. |
| - | Večina polj ne potrebuje podrobne razlage, nekatera pa le omenimo: | + | Most fields do not need detailed axplanation, but let us mention few of them: |
| - | * Zadolžen | + | * Appointed |
| - | Za reševanje lahko zadolžite osebo ali skupino, ki so evidentirani kot uporabniki sistema. Ta oseba ali skupina bo zadolžena za reševanje zahteve ali za odgovor na podano vprašanje. | + | One user or a group of users can be appointed to solving Tickets. This person or group will be appointed to solving ticket or answering a given question. |
| - | * Prioriteta, Resnost in Kategorija | + | * Priority, Severity and Category |
| - | S pomočjo teh polj lahko določite pomembnost reševanja določene zahteve. Tako si izvajalci lažje splanirajo svoje aktivnosti, prodajalci in s tem stranke pa so o tem obveščeni. | + | This fields can help you define the importance of solving a specific Ticket so that persons appointed can plan their activities while salesmen and customers are informed of it. |
| - | * Zadeva | + | * Subject |
| - | Vsaka zahteva naj bi imela edinstven naziv. | + | Every ticket should have a title. |
| - | * Kontakti in stranke | + | * Contacts and accounts |
| - | Zadevo lahko povežete s kontaktno osebo ali stranko, ki jo je podala ali pa želi odgovor na vprašanje. V praksi zahteve povezujemo s strankami, v ime zahteve ali opis pa vpišemo ime osebe, ki je zahtevo podala. | + | The subject can be linked to the Contact person or an Account the person has given or the one that wishes to get an answer to a question. In practice we connect Tickets to Accounts, we name the subject and enter the name of the person who passed the Ticket. |
| - | * Naziv izdelka | + | * The Name of the product |
| - | Zadevo lahko povežete tudi s posameznim izdelkom ali storitvijo, ki jo vaše podjetje ponuja. | + | Subject can also be linked to a specific product or service your company offers. |
| * Status | * Status | ||
| - | Nastavite dejanski status zahteve. | + | Set the actual status of the Ticket. |
| - | * Opis | + | * Description |
| - | Poleg določitve imena zahteve, jo je dobro še podrobneje opisati, da bo njeno reševanje učinkoviteje. | + | It is good to describe the Ticket beside just naming it, so its solving will be more effective. |
| - | Poleg omenjenih polj lahko izpolnite še dodatne informacije. | + | You can fill in additional information. |
| - | * Rok | + | * Appointed time |
| - | V polje lahko vpišete datum do kdaj želi stranka prejeti rešitev zahteve. | + | You can enter a date untill the Account wishes to receive a solution to the Ticket. |
| - | * Planiran čas, dejanski čas | + | * Planned time, actual time |
| - | Polji sta namenjeni za spremljanje planiranega in dejanskega časa reševanja zahtev. Spremljanje je uporabno za nadaljnje planiranje in razporejanje reševanja zahtev. | + | Fields serve for observing the planned and the actual time of resolving Tickets. |
| + | Observing these two fields proves to be useful in further planning and arranging Ticket solving. | ||
| - | * Začasna rešitev | + | * Temporary solution |
| - | V polje lahko vpišete začasno rešitev ali t.i. "workaround", ki se ga lahko ponudi stranki dokler ne pripravite prave rešitve. | + | You can enter a temporary solution or the so-called "workaround", offered to the Account untill the real solution is prepared. |
| - | * Ključne besede | + | * Key-words |
| - | Pri veliki količini zahtev nam ključne besede pomagajo, da vidimo sorodne zahteve, ki so že splanirane za reševanje ali celo rešene. | + | Key-words help us see related Tickets that have already been planned for solving or have even been resolved. |
| - | Spodaj na sliki je prikazano polje za vnos ključnih besed ob katerem se nahajata dve ikoni. | + | On the picture below you can see a field for entering key-words with two icons beside it. |
| {{si:slobase:manual:c_modules:keywords.png}} | {{si:slobase:manual:c_modules:keywords.png}} | ||
| - | S klikom na ikono z mapo se nam bo pokazal seznam ključnih besed, ki jih je vnesel sistemski administrator. | + | Clicking the folder icon will show a list of key-words, entered by the system administrator. |
| {{si:slobase:manual:c_modules:picklist.png}} | {{si:slobase:manual:c_modules:picklist.png}} | ||
| - | S klikom na drugo ikono (krožni puščici) se nam bo prikazal seznam zahtev, ki imajo v nazivu, opisu, rešitvi,... navedeno to besedo. | + | Clicking the other icon (circular arrows) will show list of Tickets with the same key-word in its title, description, solution, etc. |
| - | Z zeleno barvo se obarvajo zahteve, ki so imele vpisano vsaj eno isto ključno besedo. | + | |
| + | Tickets with at least one same key-word will be coloured green. | ||
| {{si:slobase:manual:c_modules:keywordslist.png?450}} | {{si:slobase:manual:c_modules:keywordslist.png?450}} | ||
| - | ===== Delo z zahtevami ===== | + | ===== Working with Tickets ===== |
| - | S klikom na zavihek //Podpora// se vam odpre seznam zahtev. S klikom na naziv zahteve, boste odprli njen detajlni pregled. Odprla se vam bo nova stran, kot je prikazana na spodnji sliki. | + | Clicking the //Support// tab will open a list of Tickets. Clicking the Ticket's title will open its detailed overview. A new page will open, as shown on the image below. |
| {{si:slobase:manual:c_modules:ticketdetail.png?450}} | {{si:slobase:manual:c_modules:ticketdetail.png?450}} | ||
| - | Zahtevo lahko urejate s klikom na gumb //Uredi//. Tako lahko vi in vaši sodelavci dopolnjujete opis zahteve dokler se ta ne reši, vpisujete komentarje in njeno rešitev. Prav tako, lahko na zadevo pripenjate razne dokumente ali v zvezi z njo planirate dogodke oz. naloge. | + | The Ticket can be edited by clicking the //Edit// button. You and your co-workers can supplement the Ticket's description untill it is resolved, enter comments and its solution. You can also attach documents and plan events and tasks related to the subject. |
| - | Zgodovina sprememb | + | History of changes |
| + | |||
| + | Every change can go through different phases untill it is resolved. With managing changes it is possible to see the course of its resolution. | ||
| - | Vsaka zahteva lahko potuje skozi različne faze preden je rešena. S pomočjo vodenja sprememb, lahko vidite potek njenega reševanja. | ||
| ===== FAQ ===== | ===== FAQ ===== | ||
| - | "Frequently Asked Questions" ali pogosto postavljena vprašanja se lahko uporabljajo kot baza znanja, tako za vaše stranke kot tudi zaposlene v podjetju. Vanjo lahko beležite pogosta vprašanja in odgovore (FAQ), ki nastajajo iz rešenih zahtevkov. Na ta način, lahko vaše podjetje zniža število podanih vprašanj za posamezne izdelke in olajša delo klicnemu centru s standardnimi postopki in že pripravljenimi odgovori na pogosto postavljena vprašanja. | + | Frequently Asked Questions can be used as a knowledge database for your Accounts and the employees of the company. You can enter frequently asked questions and answers to them, originating from the resolved Tickets. It is a way for your company to lower the number of asked questions about different products and easen the work of the helpdesk with standard procedures and already prepared answers to frequently asked questions. |
| - | Nov FAQ lahko vpišete s klikom na //Nov FAQ// na [[../../../b_usage:d_loginpage#podrocja| področju vnosa]]. | + | The new FAQ can be entered by clicking the //New FAQ// at the [[../../../b_usage:d_loginpage#podrocja| field of entry]]. |
| - | Odprla se vam bo nova stran, kot je prikazano na spodnji sliki. | + | A new page will open, as seen on the picture below. |
| {{si:slobase:manual:c_modules:newFAQ.png?450}} | {{si:slobase:manual:c_modules:newFAQ.png?450}} | ||
| - | Obrazec za vnos novega FAQ-a vam omogoča vpis vprašanja in odgovora. Poleg tega lahko naredite povezavo na izdelek oz. storitev o kateri je govora in določite primerno kategorijo. | + | The new FAQ form enables you to enter the question and the answer. You can also make a link to the product or service and set the appropriate category. |
| + | |||
| + | ~~ODT~~ | ||