Bally chohan support


Published on

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Bally chohan support

  1. 1. To Ensure Your Business Success Working Effectively with Bally Chohan Support Services Bally Chohan Technology Service Desk                                                              
  2. 2. S ervice R equest Severity Definitions Use Help Desk to log SRs for all Severities No loss of service or resources (Problems that can be rectified on Phone) Minor loss of service or resources (PC / Thin Client / Printer problem] <ul><ul><li>Severe loss of service or resources w/o acceptable workaround (Server/Network problem) </li></ul></ul><ul><ul><li>Complete loss of service or resources regardless of environment and work cannot reasonably continue - the work is considered “mission critical” (data corruption, critical documented function unavailable, indefinite system hangs and repeated system crashes causing unacceptable/indefinite delays for resources/responses) </li></ul></ul>
  3. 3. SR Status Codes <ul><li>NEW New SR </li></ul><ul><li>ASG Assigned to a Support Engineer </li></ul><ul><li>WIP Work In Progress </li></ul><ul><li>RVW Review </li></ul><ul><li>1CB 1st Callback </li></ul><ul><li>2CB 2nd Callback </li></ul><ul><li>IRR Immediate Response Required </li></ul><ul><li>INT Awaiting Internal Response </li></ul><ul><li>WCP Waiting for User to apply Patch </li></ul><ul><li>CUS Waiting on User </li></ul><ul><li>SLP Sleep until User Available </li></ul><ul><li>LMS Left Message </li></ul><ul><li>SCL Soft Close </li></ul><ul><li>HCL Hard Close </li></ul><ul><li>3LV Call transferred to 3 rd Level </li></ul>Support: User: Third Level:
  4. 4. Working Effectively with Bally Chohan Global IT Support
  5. 5. What Does a Support Engineer Do? <ul><li>Works a queue of current user issues in a variety of statuses </li></ul><ul><li>Provides resolutions and / or workarounds </li></ul><ul><li>Responds to new incoming SRs. </li></ul><ul><li>Acts as liaison between user and Infrastructure team </li></ul><ul><li>Contributes to Knowledge base content </li></ul>
  6. 6. Best Practices Lessons learned from our users… <ul><li>Shared ownership in resolving the issue </li></ul><ul><li>Quality and quantity of communication </li></ul><ul><li>Joint planning on problem resolution </li></ul>
  7. 7. Each Environment is Unique! <ul><li>Always test solutions BEFORE introducing them into live environment. </li></ul><ul><li>The data, software and hardware configurations, patch combinations, and integration points are different for every location. </li></ul><ul><li>We depend on our users to manage their environments and help us understand them. </li></ul><ul><li>Users control the quality and quantity of information about their environment </li></ul>
  8. 8. Communicating the Issue <ul><li>Clear problem statement: Cause & Effect </li></ul><ul><ul><li>All known facts </li></ul></ul><ul><ul><li>Is the issue reproducible? </li></ul></ul><ul><ul><li>Detailed history of environment and changes </li></ul></ul><ul><li>Answer all Template questions </li></ul><ul><li>Review our knowledge base on HELP DESK </li></ul><ul><ul><li>Top Tech Docs </li></ul></ul><ul><ul><li>Forums </li></ul></ul><ul><li>Contact Support – Service Desk </li></ul>A problem well stated is a problem half solved
  9. 9. UKLII SERVICE DESK <ul><li>Problem / Solution SR </li></ul><ul><li>Standard Approach to problem solving </li></ul><ul><ul><li>Identify the Issue </li></ul></ul><ul><ul><li>Determine a Cause </li></ul></ul><ul><ul><li>Identify Effective Solutions </li></ul></ul><ul><ul><li>Identify the Best Solution </li></ul></ul><ul><li>Provides a single consistent approach to solving reported problems </li></ul><ul><li>Service Desk: +91 11 xxx xxxx </li></ul>
  10. 10. Benefits of SERVICE DESK
  11. 11. Successful Communication <ul><li>Minimize SR ‘tag’ or ‘pinging’ </li></ul><ul><li>Documentation is essential </li></ul><ul><ul><li>Answer all questions </li></ul></ul><ul><ul><li>Action plans after each update and define who owns each action </li></ul></ul><ul><li>Monitor changes in SR status and severity </li></ul><ul><li>Escalate concerns via the Escalation process </li></ul>
  12. 12. Escalations Bringing Management Attention to your Service Request
  13. 13. Raising Severity vs. Escalations <ul><ul><li>Escalating an issue brings more management attention to it, and when appropriate, more resources. This does not automatically mean that the severity level of the SR will be changed. </li></ul></ul>If the severity level of the SR becomes inappropriate over time, it may be raised by mutual agreement between the Support Engineer and the User.
  14. 14. Escalations <ul><li>Encounter critical roadblocks </li></ul><ul><li>Communicate business issues to managers within IT Support   </li></ul><ul><li>Dissatisfied with resolution or response </li></ul><ul><li>Escalate issues in a timely manner </li></ul><ul><li>Quality of escalation criteria is key: </li></ul><ul><ul><li>Project deadlines? </li></ul></ul><ul><ul><li>Lost Revenue? </li></ul></ul><ul><ul><li>Government reporting? </li></ul></ul><ul><ul><li>Users at your door </li></ul></ul>
  15. 15. Escalation Process Support Representative Second Level Third Level CIO User Call US: +91 11 xxx xxxx Other Global Support Hot Lines:
  16. 16. Summary <ul><li>Understand Support Terminology </li></ul><ul><li>Know Severity Level Definitions </li></ul><ul><li>Access HELP DESK!! </li></ul><ul><li>Run Diagnostic Tests </li></ul><ul><li>Use Bally Chohan Service Desk Support </li></ul><ul><li>Communicate the issue effectively </li></ul><ul><li>Implement the Escalation Process when necessary </li></ul>