Support Request Ticketing System User Guide

Transcription

1 Support Request Ticketing System User Guide Prepared by: Last Updated Document Ref: Document Version: Rapid4Cloud March 2016 Support Request Ticketing System User Guide 1.1 Copyright 2016, Rapid4Cloud All Rights reserved. 1 / 14

2 TABLE OF CONTENTS INTENDED AUDIENCE 3 1 INTRODUCTION TO THE SUPPORT REQUEST TICKETING SYSTEM Contacting Support Support Service Hours 4 2 TICKET LIFECYCLE 5 3 TICKET POLICY Ticket Priority and Response Time Ticket Assignment Ticket Escalation 7 4 USING THE SUPPORT REQUEST TICKETING SYSTEM Login to the Ticketing System Obtaining a New Password Creating a Ticket Ticket Closure Ticket Printing 12 2 / 14

3 Intended Audience The intended audience for this Support Request User Guide is customers and support engineers using the Support website. The following contents provide the appropriate channels and proper procedures to open a Support Request Ticket (hereafter referred to as Ticket) and solve issues. Also provided is information on how to escalate a Support Request when an urgent response is needed. 3 / 14

4 1 Introduction to the Support Request Ticketing System Rapid4cloud provides technical assistance for all Rapid products and the Oracle e-business Suite. You can open a Ticket at the Support website ( The web site is available 24/7. It uses a standard web interface to make obtaining information and resolutions quicker and easier. 1.1 Contacting support If for any reason the support website cannot be accessed, please call the following number and leave a message or voice mail: (USA) The phone should be answered by a person 24x7 but just in case voic should be active when no person is available 1.2 Support service hours Electronic support: Personal support: 24 hours per day Refer to your support contract. 4 / 14

5 2 Ticket Lifecycle In general a Ticket has the following lifecycle: New Request Open (Under Investigation Request More Info) Work in Progress Solution Offered Pending Autoclose Closed When a new Ticket is created, an notification is sent to the Customer Care Manager who takes action on assigning appropriately skilled staff as Ticket agents. Upon assignment from the Customer Care Manager, an notification will be automatically sent to the Ticket Owner and Ticket Responsible agents who take responsibility of the Ticket. Updates by the agents will generate an notification to the requester. It is recommended that the requester regularly check the progress of the Ticket via the Support website to ensure that or SPAM filtering is not interfering with delivery of updates or attachments. The process of a hypothetical ticket may be as follows: Scenario: Day 1: New Request Open Under Investigation Day 2: Request for more information Waiting for requester Day 3: Still waiting for requester, support will send notification to the requester. Day 4: If the status remains unchanged, the requester will be notified that the Ticket will be closed by support Pending Autoclose Day 5: Support will close the Ticket Closed unsuccessful The requester may reopen the Ticket by replying to an notification generated under this Ticket or by visiting the Support website and reviewing closed Tickets. 5 / 14

6 3 Ticket Policy All Tickets will be monitored on a daily, weekly and on-demand basis. Daily All outstanding Tickets are reviewed by Rapid4Cloud management. An assessment on the quality of the interaction with requester is undertaken to ensure the information and actions being taken are a value add and professional in manner. Weekly A weekly review by management is conducted to ensure that daily and weekly objectives are met. On-demand Any Ticket open for more than 10 business days is monitored by management to ensure it is being addressed in the most expedient manner. 3.1 Ticket Priority and Response Time A Ticket, after review by Rapid4Cloud support team, will be assigned one of the following priorities: Very-High, High, Medium, Low, or Very Low. Very-HIGH Response according to SLA. Your production use of the supported programs is stopped or so severely impacted that you cannot reasonably continue work. You experience a complete loss of service. The operation is mission critical to the business and the situation is an emergency. A very-high Ticket has one or more of the following characteristics: A Rapid4Cloud product bug causes data becomes corrupted. A critical documented Rapid4Cloud function is not available. The system hangs indefinitely due to Rapid4Cloud, causing unacceptable or indefinite delays for resources or response. The system crashes and crashes repeatedly after restart attempts due to Rapid4Cloud. Reasonable efforts will be made to respond to very-high priority Tickets within the agreed period. Rapid4Cloud will work 24x7 until the issue is resolved or as long as useful progress can be made. You must provide Rapid4Cloud with a contact during this 24x7 period, either on-site or by pager/cell phone, to assist with data gathering, testing and applying fixes. You are requested to propose this severity classification with great care, so that valid very-high Ticket situations obtain the necessary resource allocation. HIGH Response according to SLA. Reasonable efforts will be made to respond to high priority Tickets within the agreed period. MEDIUM Response by next working day within Rapid4Cloud business hours. You experience a severe loss of service. Important features are unavailable with no acceptable workaround, however operations can continue in a restricted fashion. LOW Response within 3 working days within Rapid4Cloud business hours. You experience a minor loss of service. The impact is an inconvenience, which may require a workaround to restore functionality. Very LOW 6 / 14

7 Response within 5 working days within Rapid4Cloud business hours. Enhancement requests to KB or the tool itself. 3.2 Ticket Assignment Once a Ticket is opened, the Customer Care Manager is responsible for taking action or assigning appropriately skilled staff as ticket owners until it is completed. 3.3 Ticket Escalation To escalate a specific Ticket or discuss issues on any Ticket, you can contact the Customer Care Manager. See section 1.1 Contacting Support for details. 7 / 14

8 4 Using the Support Request Ticketing System 4.1 Login to the Ticketing System Use the following steps when logging in to the Ticketing System: 1. Connect to the Support website URL provided: 2. Enter your User Name and Password. See Figure Click Log In button. Figure 4.1 The Ticketing System Login page. 4.2 Obtaining a new password Use the following steps if a user password has been forgotten: 1. Connect to the Support website URL provided: 2. Click on the Forgot password? link. 3. Enter your User name and click the Submit button. An will be sent directly from Support team with a new password to the registered to that User name. See Figure 4.2. Figure 4.2 Request new password page. 4.3 Creating a Ticket After logging in to the Ticketing System, all the previous Tickets that have been created will be shown. See Figure 4.3. Figure 4.3 My Tickets review page. Create a new Ticket by selecting New Ticket from the menu. See Figure / 14

9 Figure 4.4 New Ticket submission form. In order to complete the ticket request detail, fill in the form: Subject: Provide a brief summary of the issue. Text: Provide a detailed explanation of the issue. Include screenshots and version information for all products in use in addition to exhaustive steps to reproduce the issue. Attachment: Upload all necessary supporting attachments to troubleshoot the issue. Include screenshots, injection log files, debug log files, BR100 files, BWP files, etc. You can find a sample Ticket in the Figure / 14

10 Figure 4.5 Submit the new Ticket with extensive details and documentation. To submit the new Ticket, click the Submit button, the system will create a Ticket number as seen in Figure 4.6. Figure 4.6 My Tickets review page. 10 / 14

11 The Ticket has now been submitted to the Ticketing System. Support team members will be automatically notified by . Below are the meanings of the headings shown in Figure 4.7. Age: How long this ticket has been open. Subject: Provide a brief summary of the issue (provided by you). State: The possible Ticket statuses are: New: The Ticket is still new. Support has not yet taken any action. Under Investigation: The Support agent is determining the type of issue and what needs to be accomplished to resolve it. Under Review : The Support agent has escalated the issue to management to decide the course of action for the ticket. Waiting on customer: The Support agent has requested additional information of feedback from the Customer. f no feedback is received within the timeframe communicated by the Support agent, the ticket will be changed to the appropriate Pending auto close status. Work in Progress: The solution is in development; in certain cases an ETA will be provided. Pending auto close+: A solution has been provided or the issue has been determined to be unrelated to the Rapid4Cloud product. If no feedback is received within the timeframe communicated by the Support agent, the ticket will be changed to Closed successful status. Pending auto close-: A solution has not been offered. If no feedback is received within the timeframe communicated by the Support agent, the ticket will be changed to Closed unsuccessful status. Closed successful, A solution has been delivered and the Customer accepted or failed to provide feedback on the success of the solution. Closed unsuccessful, Ticket has been closed even though the issue is not resolved. Queue: Indicates the ticket type. For example, issues related to KB will go in one of the queues KB - Bug or KB - Enhancement. 4.4 Ticket Closure Once the issue is solved the Ticket can be closed. There are two ways to close a Ticket. 1. When a notification is received via that a solution has been provided: reply to that mail and ask Support to close the Ticket. 2. Close the Ticket on the Support website. 2.1 Login as described in 4.1 Login to the Ticketing System. 2.2 Search for the Ticket to be closed. 2.3 Open the ticket. See Sample as shown as Figure Explain why the Ticket is being closed Select next state: Closed successful: The issue is resolved. Closed unsuccessful: The issue is unresolved but no longer requires action by Rapid4Cloud support team Click Submit. 2.4 A notification will be sent to the requester confirming the closure of the Ticket. 11 / 14

12 Figure 4.7 Ticket closure by Customer. 4.5 Ticket Printing If desired, the Ticketing System provides print functionality. The following are steps to print a summary of your tickets: 1. Login as described in 4.1 Login to the Ticketing System. 2. Click Search in the ticket menu and define the criteria. 3. At the output to section, select Print and click Search button. See Figure / 14

13 Figure 4.8 Ticket printing. 4. The results generate a printer-friendly summary of the tickets that fit the search criteria. See Figure / 14

14 Figure 4.9 Ticket search results. ************************************* End of Document ************************************* 14 / 14