TARGET RESPONSE TIME Clause Samples
The TARGET RESPONSE TIME clause sets a specific timeframe within which one party must respond to communications, requests, or actions from the other party. Typically, this clause outlines the maximum number of hours or business days allowed for a reply, and may apply to issues such as support requests, approval processes, or incident notifications. Its core practical function is to ensure timely communication and accountability, reducing delays and misunderstandings between the parties.
POPULAR SAMPLE Copied 7 times
TARGET RESPONSE TIME. A response to a request for Support Services shall consist of receipt of and acknowledgement by Azul of Customer’s request for Support Services (the “First Response”). Azul will use commercially reasonable efforts to provide a First Response within the target SLA response time set forth in the table below. Customer acknowledges that a First Response may not include resolution for all requests for Support Services. However, Customer acknowledges and understands that no software is perfect or error free and that, despite Azul’s commercially reasonable efforts, Azul may not be able to provide answers to or resolve some or all requests for Support Services. Azul makes no promises, guarantees, or assurances of any kind that it will be able to resolve all of Customer’s Support Services requests. Error Type TARGET RESPONSE TIME Priority 1 1 Business Day 1 hour Priority 2 2 Business Days 4 hours Priority 3 2 Business Days 1 Business Day Priority 4 2 Business Days 2 Business Days
TARGET RESPONSE TIME. If there is a Target Response Time, Provider will use commercially reasonable efforts to respond to support requests sent to the Support Channel within the Target Response Time.
TARGET RESPONSE TIME. The target response time for all IT requests is 1 hour. i.e. we aim to ensure that every request is categorised and allocated to a member of the IT team within 1 hour, at which point a confirmation email is automatically sent to the user. The process of categorising a request also ensures that an appropriate “due date” is calculated.
TARGET RESPONSE TIME. RelyMD’s support team strives to respond to all support requests, regardless of severity, within one (1) to two (2) hours of receiving notice (if notice is received during the support hours set forth in Section 2.5 above). Response time is defined as the time between receipt of the support request and the time that a RelyMD support team member begins working on the request. Due to the diversity of issues that might occur, and the methods needed to resolve them, response time is not defined as the time between the receipt of the request and problem resolution. Under all circumstances, the Customer’s timely cooperation with the RelyMD support team will be a determinant of how quickly RelyMD can achieve problem resolution.
TARGET RESPONSE TIME. The Target Response Time is the time in which the Service Desk must respond to your ticket. There are specific targets set within this Service Level Agreement, which relate to response times to Incidents, based upon priority.
TARGET RESPONSE TIME. 5.1 AMCS aims to provide the Customer with a response within a specific time limit, as stated below, based on the agreed Priority Code of the Support Case (“Target Response Time”). Target Response Times are measured within the Hours of Coverage. P3 Medium 16 Hours P4 Low 72 Hours
TARGET RESPONSE TIME. Poppulo categorizes issues into four Severity levels. Our target response time is directly related to the severity categorization of each issue:
TARGET RESPONSE TIME. The Supplier categorises issues into four severity levels. Target response time is directly related to the severity categorisation of each issue, as follows: Severity Description Targeted Response Severity 1 A critical Initial response Critical production issue time* affecting all users Initial response that severely shall be posted on impacts use of the Supplier’s website software, within 1 hour including ▇▇▇.▇▇▇▇▇▇▇.▇▇ unavailability of m/status Ongoing microsites and/or response time administration Updates shall be platform with no posted every 30 workaround minutes available. at Systems are ▇▇▇.▇▇▇▇▇▇▇.▇▇ monitored 24/7 for m/status. If issue Severity 1 issues. has not been resolved with 1 hour it shall be notified of the issue by 2 hours the issue is resolved an update will be posted on ▇▇▇.▇▇▇▇▇▇▇.▇▇ m/s Poppulo shall communicate a report stating the reason for the outage. Severity 2 Major functionality Initial response Urgent is impacted or time* performance is Initial response significantly shall be posted on reduced. An issue Supplier’s website that is persistent within 1 hour and affects many ▇▇▇.▇▇▇▇▇▇▇.▇▇ users and/or m/status and as major functionality an with no alert to all workaround affected users. available. Ongoing Systems are response time monitored 24/7 for Updates shall be Severity 2 posted every hour issues. ▇▇▇.▇▇▇▇▇▇▇.▇▇ m/status. If the issue has not been resolved with 6 hours users shall be notified of the issue. Once the issue is resolved an up be posted on ▇▇▇.▇▇▇▇▇▇▇.▇▇ m/ Severity 3 High System performance issue or bug affecting noncore functionality but not preventing access to microsites or Initial response time** Initial response shall be communicated affected users by email within 4 hours. Depending administration platform. on users affected Severity 3 issues can be reported through Poppulo phone or email support. alerts may also be posted within 4 hours. Ongoing response time Once a solution to the issue confirmed, affected users shall by email within 4 business hours when the solution shall be important. Once the issue has been resolved affected users shall be notified by email within 1 business day Severity 4 Low Routine technical issues, bugs affecting a small number of users where a reasonable workaround is available and all other customer queries channelled through Poppulo customer support. Severity 4 issues can be reported through Poppulo phone or email support. Initial and ongoing response time** Initial and ongoi...