CSA Batch 19|| Day 13 || SLA Definitions

SLA Definitions (ServiceNow) This session focused on Service Level Agreements (SLAs) in ServiceNow, covering their purpose, components, configuration, and practical implementation. 1. What is an SLA? An SLA is an agreement between a service provider and a customer that defines expected service delivery timelines and performance standards. For example, if a course is promised to be completed in 30 days with daily 1-hour classes, that commitment acts as an SLA. Failure to meet the agreed timeline can result in penalties. 2. Four Key Components of an SLA A. Definition Defines when and how the SLA operates: Business hours (e.g., 8 AM–5 PM) Weekdays only or 24×7 Holiday exclusions Applicable schedules Example: Support responses may be faster on weekdays than weekends. B. Start Condition Determines when the SLA begins. Examples: Product delivery SLA starts when an order is placed. Incident SLA starts when specified conditions are met. C. Stop Condition Determines when the SLA is considered complete. Example: A delivery ticket stops once the product has been delivered and no further action is required. D. Cancel Condition Used when the SLA becomes invalid and must be terminated. Example: A project or batch is cancelled and restarted later, requiring the old SLA to be cancelled. 3. Response SLA vs Resolution SLA Response SLA Measures the time taken to acknowledge a request or incident. Example: User sends a message. Support acknowledges it. Resolution SLA Measures the time taken to fully resolve the issue. Example: Support investigates and provides a solution after several hours. 4. Creating an SLA in ServiceNow Important recommendations: Use the Incident table for practice. Give SLAs meaningful names that indicate: Priority SLA type Duration Example naming: P1 Resolution – 1 Hour Batch19 P3 – 15 Minutes 5. SLA Duration Types ServiceNow supports: Standard durations User-specified durations (most commonly used) Examples: 15 minutes 1 hour 2 business days The system automatically calculates breach times based on the configured duration. 6. Schedule Configuration Schedules determine when SLA time counts. No Schedule (24×7) Runs continuously No holidays or weekends considered Common for Priority 1 incidents Business Schedule Examples: 8 AM–5 PM Monday–Friday Excluding holidays SLA countdown only occurs during scheduled working hours. 7. Holidays and Child Schedules Organizations can create child schedules to define holidays. Examples: Christmas New Year National holidays When holidays are configured: SLA timers pause during those dates. Breach calculations skip holiday periods. 8. Time Zone Handling Schedules and SLAs can use: Caller Time Zone (recommended) System Time Zone CI Time Zone Fixed Time Zone Common practice: Use Caller Time Zone so SLA calculations match the user's location. 9. SLA Pause Logic SLAs can be paused when waiting on external input. Example: Support requests information from a user. User takes 2 hours to respond. SLA timer pauses during that waiting period. Pause conditions vary by organization and business requirements. 10. SLA Conditions An SLA only attaches when configured conditions are met. Examples: Priority = P1 Assignment Group is not empty Short Description contains specific text Without matching conditions, the SLA will not start. 11. SLA Engine Information Once attached, ServiceNow automatically tracks: Start Time End/Breach Time Business Time Left Current State (In Progress, Paused, Breached) These values are managed by the ServiceNow SLA Engine. 12. Task Table Relationship The instructor explained that: Incident extends the Task table. SLA records are associated with Task-based records. SLA configurations often reference Task fields (such as Caller and Time Zone). This allows SLAs to work consistently across: Incidents Changes Problems Requests Knowledge-related tasks Homework Open existing SLA Definitions in ServiceNow. Review: Schedule Time Zone Start Conditions Pause Conditions Stop Conditions Cancel Conditions Understand how each SLA is configured and attached to records. Key Takeaway An SLA in ServiceNow is built around conditions, duration, schedules, time zones, and lifecycle controls (start, pause, stop, cancel). Proper SLA design ensures accurate tracking of service commitments and performance against agreed service targets.