Service Level Agreement

Use the service level page as an operational reference, then compare it with the executed agreement, order form, and incorporated schedules that apply to the engagement. Before deciding that a commitment applies, identify the covered service, customer workspace, approved support channel, measurement period, business-hours rule, and stated exclusions. Check whether the language describes a service objective, a response target, a restoration expectation, or a contractual remedy, because those concepts can be governed differently and should not be treated as interchangeable.

Evaluate severity from the documented definition and the impact that can be shown at the time of the incident. Capture when the issue began, when it was submitted through the supported reporting channel, which users or functions were affected, whether a workaround existed, and what evidence supports the reported scope. Keep the ticket reference, relevant timestamps, status information, material replies, and actions already attempted together in a single incident record. A shared record gives both sides a consistent basis for determining classification and timing without relying on recollection or scattered messages.

Escalate when the documented path calls for additional ownership, review, or a decision about an apparently missed commitment. Reference the customer workspace and existing ticket, summarize the current impact, identify the commitment you believe is relevant, and note the response already received. Avoid creating duplicate incident reports unless the service team directs you to do so, since separate records can split the evidence and timeline. After the incident is resolved, reconcile the final severity, the applicable timing calculation, any exclusions that were applied, the corrective action communicated, and any remedy that the governing terms actually provide.