Understand the Incident and the diagnostic/resolution actions attempted already by the Service Desk and any other technology. 2. Indept knowledge on CUCM and Unity connection. 3. Basic knowledge on RTMT 4. Indept knowledge on MACD which includes phone, partiton CSS, transformation mask, translation pattern. 5. Voice mail addition and deletion. Use the designated or allotted communication bridge, monitoring facilities and on-call schedule from Technology tracks to facilitate immediate attention from all required parties Work with all stakeholders to identify the workaround or resolution for the Incident Set expectations of all stakeholders about the timelines and permissions required for the resolution Send Periodic updates to the stakeholders (and if required, to the customers) through Service Desk, until the Incident is resolved Initiate Emergency Changes if required, mobilize cross functional teams, External Vendors and obtain approvals for the mitigation actions from all stakeholders Retain the Tec+B1hnical Observation Post (certain ad-hoc individuals who observe the service after the Incident is resolved) in order to insure that the resolution has actually resolved the Incident and that the Services have returned to their normal state Open Problem Tickets as per Problem Management Policy and Procedures Document in retrospect, the actions taken, learning and approvals in the service Management tools Document the new knowledge learning and any other recommendations in a Critical Incident Report and submit the report to the audience in line with the Critical Incident Management procedures. Periodically audit Incident records and coach the Incident Management staff to Insure that ''ticket hops'' are reduced to the minimum Enforce the use of available knowledgebase, Configuration Management Database and Known Error Database for quicker resolution of Incidents 16. Quality of updates being made into the Incident Records 17. Devise, measure, report, monitor and improve the internally designed KPIs to improve the efficiency of Incident Management process. Example: Ticket hops, Incidents per staff, Incidents resolved using KEDB 16. Working exposure in ServiceNow ticketing tool. 17. Willing to work under 24/7 operations (Night shift mandatory) Key Skills: Incident Management Location: MUM Required Experience: Min 1 yrs Positions: 1 
0 to 3 Years 
Salary not disclosed 
Mumbai
Safety Tips
How to get a Job early? Follow these tips
Jobs By Roles
Jobs By Cities
