How it works
Support TTFR (time to first response) measures how long it takes your team to first respond to a support ticket, from ticket creation to the first response your support platform records. This metric is critical for understanding how responsive your team is to customer issues. Lower TTFR indicates:- Responsive engineering team
- Good support escalation processes
- Clear on-call or support rotation
- Adequate engineering capacity for support
Calculation
TTFR is measured from when a support ticket is created until the first response your support platform records for it. Formula:What counts as first response
Weave uses the first response time your support platform records for each ticket:- Pylon: The first response time Pylon reports for the issue
- Zendesk: The first public comment from an agent or admin
What doesn’t count
Weave doesn’t check who sent the first response or what it says. A reply from a support team member who isn’t an engineer, or a short acknowledgment (“I’ll look into this”), counts as the first response. For Zendesk, internal notes and comments from end users don’t count.Median vs. average
This metric uses median (not average) because:- Outliers (e.g., tickets created over weekends) don’t skew results
- Median represents typical response time better than average
- More actionable for setting SLAs
Industry benchmarks
Support response time expectations vary by industry and customer segment:These benchmarks are general targets. Weave’s TTFR uses the first response your support platform records, which often comes from your support team rather than an engineer.
Why it matters
Fast engineering response time is crucial for:- Customer satisfaction: Quick responses build trust and reduce churn
- Revenue protection: Enterprise customers expect fast resolution
- Product reputation: Response time affects reviews and referrals
- Support team morale: Reduces pressure when engineers respond quickly
- Unclear escalation processes
- Engineers overwhelmed with support
- No dedicated support rotation
- Time zone coverage gaps
Common patterns
Business hours coverage
- Fast TTFR during work hours (< 2 hours)
- Slower TTFR outside business hours (4-8 hours)
- Solution: Consider follow-the-sun coverage or on-call rotation
Priority-based response
- P0/P1 tickets: < 1 hour
- P2/P3 tickets: 4-24 hours
- Solution: Clear escalation criteria and automated routing
Expertise-based delays
- Generic issues: Fast response
- Specialized issues: Slow response (waiting for expert availability)
- Solution: Better documentation and knowledge sharing
Improving TTFR
To reduce time to first response:-
Establish clear processes:
- Define what requires engineering escalation
- Create escalation paths by issue type
- Set explicit TTFR targets by priority
-
Implement support rotation:
- Dedicate engineers to support duty
- Create rotation schedule
- Protect support time from meetings
- Provide on-call compensation
-
Improve visibility:
- Set up Slack alerts for escalated tickets
- Create support dashboard for engineers
- Send daily digests of pending tickets
-
Empower support team:
- Expand technical knowledge
- Provide better debugging tools
- Create playbooks for common issues
- Reduce unnecessary escalations
-
Leverage automation:
- Auto-route tickets by type
- Provide self-service diagnostic tools
- Use AI to suggest solutions
- Create triage automation
Integration requirements
To track support TTFR:- Connect support platform: Currently supports Pylon and Zendesk
- Map engineer accounts: Link Weave accounts to support platform users
Technical details
How is response time calculated?
How is response time calculated?
Response time is measured as:If a ticket is reassigned later, only the first response is counted, and the ticket is attributed to its current assignee.
Which tickets are included?
Which tickets are included?
Included:
- Tickets created in the selected period that have a first response, whoever sent it
- In organization-wide views, tickets that are unassigned or whose assignee isn’t linked to a Weave account
- Tickets without a first response yet, including tickets auto-closed without one
- Tickets assigned to someone whose Weave account isn’t an engineer account
- In engineer and team views, tickets not assigned to those engineers
How are tickets attributed to engineers?
How are tickets attributed to engineers?
Weave doesn’t identify who sent the first response or check what it says. It uses the first response time your support platform records.Engineer and team views attribute each ticket to its current assignee, using the link between the assignee’s support platform user and their Weave account. Tickets assigned to someone whose Weave account isn’t an engineer account are excluded.
How is TTFR aggregated?
How is TTFR aggregated?
TTFR uses median across all tickets in the time period:
- Daily view: Median TTFR for tickets created that day
- Weekly view: Median TTFR for tickets created that week
- Monthly view: Median TTFR for tickets created that month
What data sources are used?
What data sources are used?
Support TTFR uses data from:
- Pylon and Zendesk: Ticket creation and first response timestamps, and each ticket’s assignee
- Weave accounts: Engineer identification and mapping
Related metrics
- Support contributions: Count of engineer contributions to support tickets, one per engineer per ticket
- Slack thread response time: Response times in Slack