. IT Magazines (Portugal)
. Bit
. PC Guia
. Redes
. Desenvolvimento
. AskASP
. Cascading Style Sheets (CSS)
. DevASP
. DevGuru
. Perl.com
. PHP.NET
. W3C
. Bases de Dados
. Informix
. Oracle
. Blogs
. Alniyat
. Bitites
. ISMS
. IT-Mania
. lixo@net
. Nerd Tec
. SC Blog
. WebTuga
. IT Jobs (Portugal)
. IT Jobs
. Firewall Grátis
. Comodo
. Guarddog
. Jetico
. Kerio
. PCTools
. Sygate
. WIPFW
. Anti-Vírus Grátis
. PC Tools
. Anti-Spyware Grátis
. a2 Free
. Ad-aware
. Data Recovery Grátis
. Fóruns
. PTCoders
. Speedway
. Portais
. Tutoriais
Resolving tickets might be difficult to assess.
If a user submits a request support ticket just saying something like "I have a problem in Oracle", I must assure I collect all the information needed in order to troubleshoot the problem he is facing. The possible support ticket classifying must be Pending or Suspended. However If the problem presented by the user is somehow known and you can present him with a highly probable solution, I can simply send it to him while classifying the ticket as resolved.
Some might say that I am trying to loose ownership or accountability on the user's request making his customer experience worse. Nevertheless we, as a “Resolver” group must think on our customers as a whole. When I classify the ticket as resolved I am making myself available to another customer that also needs my help. This will improve Customer experience globally.
So, how will differentiate when to resolve or when to suspend? I will resolve whenever I have a highly probable solution, not a possible solution. Possible solutions are troubleshooting ("Please can you try this, can you try that..."). I will resolve when the probability of the solution presented is so high that I am almost sure I just have to wait on the feedback from the user to confirm the resolution or not. If not I will have to return to the troubleshooting.
Ok, now how about Closing Ticket's?
Easy! There are no Grey areas here. Every time you have a resolved case with a confirmed resolution you will close the ticket. And if you have a Standard Problem you will certainly have a standard solution. This is an obvious direct Close.
This must seem of little importance, whenever I suspend a ticket I am adding work to my stack that is pending and requires an action from me. If I resolve the ticket my work is done or not, but at least the next action needed must be from the user. Not you can focus on other issues/tickets. Closing the ticket is the main goal. No pending issues for me or for the user.
Graph below might help you!
O dinheiro é pouco e necessário. Como tal resolvi começar a fazer uns biscates para quem estiver interessado:
Diskcopy Serviços Informáticos
vírus,backup's, recuperação de dados, spy wares, instalações, configurações e todo o tipo de resolução de problemas.
€10 por deslocação
€35 por 4 horas de Trabalho, só pagos se o problema ficar resolvido.
Preços não incluem Hardware que seja necessário comprar
Contactos:
diskcopy.si@gmail.com
965450556
Interessados?
Destroy all enemy units for victory (30+ weapons). |
| Play this free game now!! |
Get the sheep across the road and into a pen. |
| Play this free game now!! |
You have documents that the 'Corporation' want. Can you escape? |
| Play this free game now!! |
The enemy is approaching and you are all that stands in the way. |
| Play this free game now!! |
Your favorite Miniclip friends have challenged each other to race! |
| Play this free game now!! |