Pylon
Knowledge BaseWebsiteChangelogBook a DemoLogin
  • Getting Started
    • Introduction
    • Quick Start
    • Slack Setup
    • Channel Configuration
    • User Guide
  • Support Workflows
    • Omnichannel Support
    • Issues
      • Views
      • Statuses
      • Message Editor
      • Copilot
      • Internal Threads
      • Proactive Issues
      • Translation
      • Bulk actions
      • Issue Groups
    • SLAs
    • Support Hours
    • CSAT
    • Ticket Forms
    • Assignment Rules
      • User Status
    • Email
  • Platform
    • Custom Fields
    • Required and Conditional Fields
    • Tags
    • Teams
    • Triggers
      • Logs & History
    • Macros
    • Command Search
    • Roles & User Management
    • Training Data
    • Ask AI
  • AI Agents
    • Overview
    • Build
      • Resources
    • Test
  • Knowledge Base
    • Overview
    • Articles & Collections
      • Editor
      • Copilot
      • Templates
      • Collaboration
    • Knowledge Gaps
    • Styling & Customization
    • Custom Authentication
    • Search
    • Translation
  • Customer Portal
    • Overview
    • Styling & Customization
    • Access Control
    • Portal Experience
    • Custom Authentication
  • In-App Chat
    • Overview
    • Styling
    • Functionality
    • Chat Experience
    • Chat Setup
    • Identity Verification
    • JavaScript API
  • Account Management
    • Accounts
    • Views
    • Notebooks
      • Blocks
    • Highlights
    • Fields
    • Copilot
    • Activities
      • Custom Activities
  • Reporting & Analytics
    • Analytics
    • Default Dashboards
    • Custom Dashboards
  • Broadcasts
    • Overview
    • Create a Broadcast
    • Analytics
  • Integrations
    • CRM
      • Salesforce
      • Hubspot
      • Attio
      • Pipedrive
    • Ticketing
      • Linear
      • GitHub Issues
      • Asana
      • Jira
    • Alerting
      • PagerDuty
      • Opsgenie
    • Chat
      • Slack
        • Internal Threads
        • Collect Data
        • Support Ticket Flow
        • Welcome Message
        • Bookmarks
        • Onboard Employees
        • Left Company
        • Slack Community
      • Microsoft Teams
      • Discord
    • Incident Management
      • incident.io
    • Call Recording
      • Gong
      • Fathom
      • Grain
      • Fireflies
  • Data Warehouse
    • Snowflake
    • BigQuery
  • Developer
    • API
      • Authentication
      • Errors
      • API reference
        • Attachments
        • Accounts
          • Activities
          • Highlights
        • Contacts
        • Custom Fields
        • Issues
        • Knowledge Base
        • Me
        • Messages
        • Tags
        • Teams
        • Ticket Forms
        • User roles
        • Users
      • External IDs
    • Custom Apps
    • Embedded Iframes
    • Webhooks
Powered by GitBook
On this page
  • ​Setup
  • Notification
  • Support Hours

Was this helpful?

  1. Support Workflows

SLAs

Set differentiated service level agreement timers on customer issues.

PreviousIssue GroupsNextSupport Hours

Last updated 1 month ago

Was this helpful?

SLAs (AKA Service Level Agreements) are rules for how quickly you want to respond to and resolve customer issues.

Pylon supports three types of SLAs:

  1. First Response Time: how quickly someone on your team should respond to an initial message or request from the customer.

  2. Next Response Time: how quickly someone on your team should respond to each subsequent message in a customer request after the first.

  3. Resolution Time: how long it takes to resolve a request after it’s been started (more often called Time to Resolution).

Setup

  1. Visit the and hit Create

  2. Select from one of the available templates for common SLA configurations for a good starting point

  1. Modify the trigger with the conditions and values that make sense for your business. SLAs can be applied based on many factors, including the priority of the issue, the type of customer who raised it, etc.

Notification

To setup notifications for SLAs, choose the "Send Slack notification on SLA breaches" template. Update the channel to your preferred one, or the action to a different notification type (such as email).

When an issue violates an SLA

  1. The configured action will be taken, for example notifying a Slack channel

Support Hours

Users can also subscribe to notifications for SLA breaches on issues they are assigned to on the .

If you want SLAs to only increment during your working hours, you can configure Support Hours on the . This makes sure that weekends and evenings will not inflate your count of SLA breaches.

notifications page
Settings Page
​
SLAs page