Pylon
Knowledge BaseWebsiteChangelogBook a DemoLogin
  • Getting Started
    • Introduction
    • Quick Start
    • Slack Setup
    • Channel Configuration
    • User Guide
    • Pylonboarding
      • Issue Views
      • Teams
      • Account Management
      • Knowledge Base
      • Chat Widget
      • SLAs
  • Support Workflows
    • Omnichannel Support
    • Issues
      • Views
      • Statuses
      • Message Editor
      • Copilot
      • Sidebar
      • 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
  • Chat Widget
    • Overview
    • Styling
    • Functionality
    • Chat Experience
    • Chat Setup
    • Identity Verification
    • JavaScript API
  • Account Management
    • Accounts
    • Views
    • Notebooks
      • Blocks
    • Highlights
    • Fields
    • Copilot
    • Activities
      • Custom Activities
    • Sidebar
  • 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
  • Calendar
    • Google Calendar
    • Outlook Calendar
  • 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
  • Overview
  • Setup
  • Use Cases
  • Best Practices

Was this helpful?

  1. Getting Started
  2. Pylonboarding

SLAs

Maintain high service levels on your customer issues.

Last updated 13 hours ago

Was this helpful?

Overview

SLAs (Service Level Agreements) help ensure timely, consistent support by defining how quickly your team should respond to and resolve customer issues. With Pylon, you can customize SLAs to match the expectations of different customer segments, prioritize critical issues, and automate reminders or escalations when targets are missed.

Pylon supports three types of SLAs:

  • First Response Time – The time it takes for your team to respond to the first customer message

  • Next Response Time – The time between a customer’s follow-up and your next reply

  • Resolution Time – The total time it takes to fully resolve an issue

All SLAs can be configured to respect business hours and customized by priority, customer tier, and more.


Setup


Use Cases

  • Tiered Support

    • Set stricter SLAs for enterprise accounts and more flexible targets for standard users

  • Priority-Based Routing

    • Assign faster SLAs to issues marked as “Urgent” or related to critical workflows

  • Proactive Escalations

    • Automatically alert managers or trigger escalation workflows when a deadline is missed

  • Time-Sensitive Channels

    • Create different SLAs for Slack, in-app chat, or email based on the nature of each channel

  • Resolution Reporting

    • Track SLA performance over time to identify trends and improve team efficiency


Best Practices

  • Use Templates to Start

    • Begin with a prebuilt SLA template and customize it to fit your needs

  • Set Support Hours

    • Enable Support Hours to prevent off-hours SLA breaches

  • Enable Notifications

    • Set up breach alerts via Slack or email to keep your team aware and responsive

  • Review SLA Breaches

    • Use Analytics dashboards to analyze performance and fine-tune thresholds and routing over time