{"id":267,"date":"2024-03-11T04:18:22","date_gmt":"2024-03-11T04:18:22","guid":{"rendered":"http:\/\/34.142.164.87\/?p=267"},"modified":"2024-03-11T04:18:22","modified_gmt":"2024-03-11T04:18:22","slug":"escalation-policy","status":"publish","type":"post","link":"https:\/\/ops-docs.eezee.co\/?p=267","title":{"rendered":"Escalation Policy"},"content":{"rendered":"<p><strong>Escalation Policy for Eezee Operations<\/strong><\/p>\n<p><strong>Objective:<\/strong> The escalation policy is designed to efficiently address and resolve issues that arise within the Eezee e-commerce marketplace, particularly focusing on scenarios involving out-of-stock items, long lead times, and end-of-life products.<\/p>\n<p><strong>Escalation Procedure:<\/strong><\/p>\n<ol>\n<li><strong>Initial Notification:<\/strong>\n<ul>\n<li>Upon identification of an issue related to an order, the team lead responsible for order management will be immediately notified through the appropriate communication channel (e.g., email, instant messaging).<\/li>\n<li>The team lead is responsible for assessing the issue and initiating preliminary steps to resolve it.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Escalation to Assistant Manager (After 24 hours):<\/strong>\n<ul>\n<li>If the issue persists beyond 24 hours without resolution, the team lead will escalate the matter to the Assistant Manager.<\/li>\n<li>The Assistant Manager will review the situation, provide necessary guidance, and collaborate with relevant teams to expedite the resolution process.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Escalation to Manager (After 48 hours):<\/strong>\n<ul>\n<li>If the issue remains unresolved after 48 hours from the initial notification, it will be further escalated to the Manager.<\/li>\n<li>The Manager will conduct a thorough assessment of the situation, engage with cross-functional teams if required, and implement strategic measures to address the issue promptly.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Escalation to Head of Operations (After 72 hours):<\/strong>\n<ul>\n<li>In the rare event that the issue persists beyond 72 hours without resolution, the matter will be escalated to the Head of Operations.<\/li>\n<li>The Head of Operations will take decisive action to resolve the issue, including coordination with executive-level stakeholders, if necessary, to ensure a swift and satisfactory resolution.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<p><strong>Responsibilities:<\/strong><\/p>\n<ul>\n<li><strong>Team Lead:<\/strong>\n<ul>\n<li>Promptly assess and address the initial notification of the issue.<\/li>\n<li>Collaborate with relevant teams to troubleshoot and resolve the problem within the stipulated timeframe.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Assistant Manager:<\/strong>\n<ul>\n<li>Review escalated issues after 24 hours and provide guidance to facilitate resolution.<\/li>\n<li>Coordinate with teams to expedite the resolution process and escalate to the Manager if necessary.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Manager:<\/strong>\n<ul>\n<li>Conduct a thorough assessment of escalated issues after 48 hours.<\/li>\n<li>Implement strategic measures and allocate resources to address the issue promptly.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Head of Operations:<\/strong>\n<ul>\n<li>Oversee escalated issues that remain unresolved after 72 hours.<\/li>\n<li>Take decisive action, including engaging executive stakeholders if required, to ensure a satisfactory resolution and prevent recurrence.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><strong>Communication Protocol:<\/strong><\/p>\n<ul>\n<li>All escalations must be documented and communicated through official channels to ensure transparency and accountability.<\/li>\n<li>Regular updates regarding the status and progress of escalated issues should be provided to relevant stakeholders at each stage of escalation.<\/li>\n<\/ul>\n<p><strong>Conclusion:<\/strong> The escalation policy outlined above aims to streamline the resolution process for issues encountered within the Eezee e-commerce marketplace, thereby ensuring a seamless and satisfactory experience for customers and stakeholders alike. Continuous monitoring, collaboration, and timely intervention are key principles guiding the effective implementation of this escalation framework.<\/p>\n<table>\n<tbody>\n<tr>\n<td width=\"150\">Initial Notification<\/td>\n<td width=\"150\">Immediate<\/td>\n<td width=\"150\">Team Lead informed<\/td>\n<td width=\"150\">Teams<\/td>\n<\/tr>\n<tr>\n<td width=\"150\">Escalation to Team Lead<\/td>\n<td width=\"150\">&lt;24hrs<\/td>\n<td width=\"150\">Assistant Manager Informed<\/td>\n<td width=\"150\">CS Agent<\/td>\n<\/tr>\n<tr>\n<td width=\"150\">Escalation to Assistant Manager<\/td>\n<td width=\"150\">&gt;24 hrs<\/td>\n<td width=\"150\">Manager Informed<\/td>\n<td width=\"150\">CS Lead \/ BD<\/td>\n<\/tr>\n<tr>\n<td width=\"150\">Escalation to Manager<\/td>\n<td width=\"150\">&gt;48hrs<\/td>\n<td width=\"150\">Head of ops informed<\/td>\n<td width=\"150\">Head of CS \/ Head of Sales<\/td>\n<\/tr>\n<tr>\n<td width=\"150\">Escalation to HOO<\/td>\n<td width=\"150\">&gt;72hrs<\/td>\n<td width=\"150\">&nbsp;<\/td>\n<td width=\"150\">&nbsp;<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Escalation Policy for Eezee Operations Objective: The escalation policy is designed to efficiently address and resolve issues that arise within the Eezee e-commerce marketplace, particularly focusing on scenarios involving out-of-stock items, long lead times, and end-of-life products. Escalation Procedure: Initial Notification: Upon identification of an issue related to an order, the team lead responsible for&#8230;<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"categories":[4],"tags":[9],"class_list":["post-267","post","type-post","status-publish","format-standard","hentry","category-policies","tag-om"],"_links":{"self":[{"href":"https:\/\/ops-docs.eezee.co\/index.php?rest_route=\/wp\/v2\/posts\/267","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ops-docs.eezee.co\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ops-docs.eezee.co\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ops-docs.eezee.co\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/ops-docs.eezee.co\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=267"}],"version-history":[{"count":1,"href":"https:\/\/ops-docs.eezee.co\/index.php?rest_route=\/wp\/v2\/posts\/267\/revisions"}],"predecessor-version":[{"id":268,"href":"https:\/\/ops-docs.eezee.co\/index.php?rest_route=\/wp\/v2\/posts\/267\/revisions\/268"}],"wp:attachment":[{"href":"https:\/\/ops-docs.eezee.co\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=267"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ops-docs.eezee.co\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=267"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ops-docs.eezee.co\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=267"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}