Help
HomeFeaturesPricingBlog
  • What is Keeping?
  • Getting Started
    • Quick start for admins
    • Quick start for agents
    • Using Keeping in Gmail
    • Keeping and your customer
    • Keeping for Chrome
    • Keeping for Safari
  • Fundamentals
    • Mobile & web access
    • Converting an email to a ticket
    • Using Templates
    • Changing ticket status
    • Assigning a ticket
    • Editing ticket recipients
    • Moving a ticket
    • Sharing a ticket
    • Using tags
    • Enable an autoreply
    • Creating a new ticket
    • Collision detection
    • Email signatures
    • Private notes
    • Activity log
    • Managing spam
    • Shared drafts
    • Agent Availability
  • Setup
    • Installing the Chrome Extension
    • Installing the Safari Extension
    • Integrations
      • Asana
      • ClickUp
      • HubSpot
      • Jira
      • Linear
      • Shortcut
      • Shopify
      • Zapier
    • Connecting a mailbox
      • Sign in with Google
      • Connect a Google Group
      • Connect a Gmail Alias
      • Forwarding your mailbox
      • Custom domains
      • Connect a web form
      • Disconnecting a mailbox
    • Inviting users
    • Admin & agent roles
    • Manually updating the Extension
  • Workflows
    • What are Workflows?
    • Creating Workflows
    • Workflow conditions
    • Workflow actions
    • Round Robin assignment
  • Service Level Agreements
    • What are SLAs?
    • Creating an SLA
    • SLA conditions
    • SLA actions
  • Satisfaction Ratings (CSAT)
    • What are CSAT Ratings?
    • Enabling Satisfaction Ratings
    • Customizing the CSAT widget
    • CSAT Reports
  • Reporting & Analytics
    • What are Reports?
    • Classic Reports
      • Setting work schedules
      • First response time
    • Advanced Reports
      • Team performance
      • Agent performance
      • Ticket statistics
      • Message statistics
      • Export to CSV
  • Preferences
    • Reversing conversation order
    • Pushing tickets into inbox
    • Hiding the Keeping toolbar
    • Close & Next
    • Personal Inbox Signature
    • Notifications
      • Desktop Notifications
      • Browser permissions
      • Inside Gmail
    • Set your business hours
  • Account & Plans
    • Adding and removing paid seats
    • Changing billing plans
    • Changing organization name
    • Updating your billing information
    • Pausing your subscription
    • Cancelling your subscription
  • Troubleshooting & FAQs
    • Toolbar Not Refreshing
  • Security and Privacy
    • Security & Privacy Practices
    • Google Permissions
Powered by GitBook
On this page
  • What are SLA conditions?
  • First Response Time and Resolution Time
  • Business Time vs Calendar Time
  • Additional Conditions
  1. Service Level Agreements

SLA conditions

How to set conditions to trigger your SLA in Keeping.

PreviousCreating an SLANextSLA actions

Last updated 1 year ago

Every SLA must include a single time-based condition. You may also include one (or more) other conditions to further refine your SLA.

What are SLA conditions?

First Response Time and Resolution Time

Every SLA contains a single time-based condition that starts running when a new ticket arrives into your support mailbox.

  • First Response Time measures how long it takes for an agent to first reply to your support customer. Auto replies are NOT included in this calculation, and replies after the first reply have no effect.

  • Resolution Time measures how long a support ticket stays in an "open" state. When a ticket is moved to a "closed" or "pending" state, the resolution time "clock" is paused. The "clock" reactivates as soon as the ticket moves back into the "open" state. Resolution time is cumulative, meaning as a ticket moves from "open" to "closed" and back to "open" (and so on), the resolution time increases whenever the ticket is in an "open" state.

Business Time vs Calendar Time

Every time-based condition can be calculated on business time or calendar time. When you choose a condition based on business time, the "clock" is only running during your business hours. For example, if your business hours are 9:00am to 5:00pm (17:00), and a new ticket arrives at 4:00pm (16:00), and your agent replies at 10:00am the next day, your agent's business time response is 2 hours. Conversely, this would have a calendar time response of 18 hours.

Additional Conditions

In addition to at least a single time-based condition, you may add one or more other conditions that must match before the Violation is triggered. For further detail on how these conditions work, see the reference inside Workflows.

Workflow conditions