Track 02 · Growth

Improve support quality
with SLAs and CSAT

Set clear response targets and start measuring support quality. By the end of this track you will have SLAs, support hours, and CSAT surveys set up and running.

CSAT trending upward SLA compliance above 90% Every negative CSAT gets a follow-up
01

Configure SLAs

SLAs define how quickly your team should respond and resolve issues. Even simple targets help teams stay consistent and prevent tickets from slipping through the cracks.

  • Urgent: 1hr first response, 4hr resolution
  • High: 4hr first response, 24hr resolution
  • Normal: 8 business hours / 48 business hours
Read the docs
Why configure SLAs?

SLAs give every issue a deadline. Without them, tickets sit open until someone notices — with them, a breached timer automatically surfaces the issue so nothing slips silently. Each priority tier (Urgent, High, Normal) can have its own response and resolution window.

SLA data also feeds directly into Analytics dashboards, so you can see which teams or channels consistently miss targets and make data-driven decisions about staffing and coverage.

02

Set Support Hours

Define when your team is actually available so SLA timers only run during working hours.

  • Set your timezone and weekly schedule
  • Add holidays and exceptions
  • SLA timers automatically pause outside these hours
Read the docs
Why does this matter?

Without support hours configured, SLA timers run 24/7. A ticket arriving at 11pm on Friday could show as breached by Monday morning, even if your team responded within minutes of starting work.

Support hours tell Pylon exactly when timers should run. You can configure multiple schedules and assign them to different SLA policies — stricter coverage for enterprise accounts, standard hours for everyone else.

03

Enable CSAT Surveys

CSAT surveys show whether customers are actually happy with the support they receive. They are one of the fastest ways to detect unhappy customers and follow up quickly.

  • Enable automatic surveys after issue resolution
  • Send within 1 hour while the experience is fresh
  • Create a "Negative CSAT" View to catch unhappy customers
Read the docs
With AI Issue QA, Pylon can auto-score reply quality before you even send a CSAT survey Add-on

AI Issue QA reviews every resolved conversation and flags issues where the response may have missed the mark — wrong tone, incomplete answer, or slow follow-up. Catch quality problems before your customer tells you about them in a CSAT survey.

Learn more about AI Issue QA
How CSAT data flows through Pylon

CSAT surveys are sent automatically after an issue resolves. The response data flows straight into Pylon — you can filter your issue list by score, build a dedicated "Negative CSAT" Saved View to prioritize follow-ups, and track satisfaction trends over time in Analytics.

The single most impactful setting is the send delay. Sending within 1 hour of resolution, while the experience is fresh, gets response rates significantly higher than waiting until the next day.

Your Portal

Track your onboarding progress

Log in with your Pylon email address to see your recommended onboarding tasks in the customer portal.

Reference

Related setup topics

Docs for everything in this track.

SLAs

Response & resolution targets

Support Hours

When SLA timers run

CSAT Surveys

Measure customer satisfaction

Custom Fields

Enrich issues with context

Continue your journey
Track 01

Foundation

Centralize, filter, and clear the noise

Learn More
Track 03

Scale

Automate triage, enforce SLA compliance, and eliminate manual routing

Learn More

Not the right track?

Retake the quiz for a different recommendation.

Retake the quiz