Track 03 · Scale

The Automated Engine

Automate triage, enforce compliance, and eliminate manual work. By the end of this track you will have teams organized, triggers routing issues automatically, and dashboards replacing gut feel.

<5% issues need manual routing 95%+ SLA compliance Dashboards over gut feel
01

Organize your Teams

Before automating routing, Pylon needs to know your team structure. Group people by function, segment, or product area.

  • Customer Success, Engineering, Billing
  • Enterprise Support vs SMB Support
  • One person can belong to multiple teams
Read the docs
How Teams power routing and reporting

Teams control routing, views, and reporting. You can be as broad as "Support" or as specific as "Enterprise CS – APAC". Because one person can belong to multiple teams, complex org structures are easy to model — a senior engineer can sit in both Engineering and an Enterprise Escalations team without duplication.

Every team gets its own Saved View, its own round-robin assignment pool, and its own slice of the Analytics dashboard, making it easy for team leads to see exactly how their group is performing.

02

Build routing Triggers

This is where manual triage dies. Triggers auto-route issues to the right team based on AI categorization, keywords, or account tier.

  • Question Type = Bug → assign to Engineering
  • Account Tier = Enterprise → assign to Enterprise CS
  • No assignment after 5 min → round-robin to on-call
Read the docs
With AI Assistants, use AI prompts to route issues to the right team based on topic Add-on

AI Assistants let you write plain-language prompts that classify incoming issues by topic and automatically route them to the relevant team -- no manual triage needed. Set up rules like "if the issue is about billing, assign to Finance" and let the AI handle the rest.

Learn more about AI Assistants
How routing works in Pylon
Manual routing
  • Best for smaller teams or where routing logic isn't well-defined
  • Support team reviews new issues in the kanban or a filtered view
  • Manually assigns to a person or team in Pylon
  • Loop in external teams via Slack internal threads, or push to GitHub / Linear
Automated routing (Triggers)
  • Best when no dedicated triage team and logic is well-defined
  • Route on: Account Tier, Priority, Question Type, Topic, or any account/issue field
  • Route to: an assignee or team in Pylon, or via Slack internal threads
  • Question Type and Topic can be AI-classified automatically
Common examples
  • Account issues → account owner in Pylon
  • Question Type = Bug → Engineering team in Slack
  • Billing@ email → Billing team in Pylon
03

Set up Analytics dashboards

You can't improve what you can't measure. Build dashboards that give team leads real-time visibility into operational health.

  • SLA compliance rate and trends
  • Volume by category, team, and channel
  • Response time and resolution time distributions
Read the docs
How SLA timers are calculated

Response SLAs (first response time and next reply time) only tick during business hours, and only while your customer was the last to respond with the issue in a New or On You status. They pause in all other statuses.

Resolution SLAs tick during business hours while an issue is New, On You, or On Customer — pausing whenever it moves to any other state. Set your hours under Settings > Support Hours, otherwise timers run 24/7.

Terminology

What do p50, p90, and p99 mean in Analytics?

p50

Half your issues resolved faster than this, half slower. Your baseline performance number.

The median
p90

90% of issues resolved within this time. Highlights the worst-case experience most customers encounter.

Near worst-case
p99

Only 1% of issues take longer than this. Focusing on p99 surfaces the outliers that disproportionately hurt satisfaction.

True outliers

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.

Teams

Organize users into groups

Triggers

Automate actions on events

Analytics

Dashboards & reporting

Ask AI

Search KB from any issue

Continue your journey
Track 01

Foundation

Centralize, filter, and clear the noise

Learn More
Track 02

Growth

Set response targets, measure CSAT, and build feedback loops

Learn More

Not the right track?

Retake the quiz for a different recommendation.

Retake the quiz