Support contributions

​

How it works

Support contributions counts the customer support tickets engineers contribute to. Each engineer who posts on a ticket counts once for that ticket, and Weave rates the contribution major, medium, or minor by the effort involved. This metric helps you understand which engineers are helping customers and how support workload is distributed across your team. Higher contributions may indicate:

• Engineers with strong customer empathy
• Product experts who can debug complex issues
• Team members handling escalated support cases
• Potential support burden on engineering resources

​

Calculation

The metric counts one contribution for each engineer who posts on a support ticket. An AI assessment of the conversation rates each contribution major, medium, or minor by effort. What counts as a contribution:

• Responding to a support ticket
• Adding technical investigation details
• Providing a solution or workaround
• Escalating or routing to the right team
• Confirming a fix or resolution in a message

What doesn’t count:

• Automated notifications
• Messages from customers
• Ticket actions without a message, such as assignments, escalations, or marking a ticket as resolved
• Support team members who aren’t linked to a Weave engineer account

Internal notes count, and so do short acknowledgments: an engineer whose only message is “Looking into this” still counts, usually rated minor.

​

Multiple contributions per ticket

If an engineer contributes to the same ticket multiple times:

• The engineer still counts as one contribution for that ticket
• Follow-up messages can change the contribution’s rating, but don’t add contributions
• This reflects how many tickets each engineer helped with and how much effort each took, not how many messages they sent

​

Why it matters

Tracking support contributions helps with:

1. Workload management: Identify engineers spending excessive time on support
2. Knowledge distribution: Find which engineers are product experts
3. Support efficiency: Measure how engineering resources are allocated
4. Team planning: Balance feature development with support needs

​

When support contributions are healthy

• Distributed: Multiple engineers contribute, no single person overwhelmed
• Expertise-based: Complex issues go to engineers with relevant knowledge
• Responsive: Quick first responses with thorough investigation
• Learning opportunity: Junior engineers gain customer insight

​

When support contributions indicate problems

• Concentrated: One engineer handling most support tickets
• High volume: Engineers spending majority of time on support
• Slow response: Long time to first response (see TTFR metric)
• Repeat issues: Same problems requiring engineer intervention

​

Interpreting the numbers

​

By engineer (individual view)

• 0-2 contributions/week: Normal for IC roles focused on development
• 3-5 contributions/week: Balanced mix of development and support
• 5-10 contributions/week: Significant support responsibility
• 10+ contributions/week: Primary support role or product expert

​

By team (organization view)

• Low overall contributions: Support team handles most issues independently
• Moderate contributions: Healthy escalation of complex technical issues
• High contributions: Support team may need more training or tooling

​

Integration with support platforms

Support contributions are tracked through integrations with Pylon and Zendesk:

​

Pylon

• Tracks engineer responses in Pylon support conversations
• Links Weave accounts to Pylon users
• Dates each contribution by the ticket’s creation time and records ticket details

​

Zendesk

• Tracks engineer comments on Zendesk tickets, including internal notes
• Links Weave accounts to Zendesk agents and admins by email

​

Configuration

To track support contributions:

1. Connect your support platform: Connect your Pylon or Zendesk workspace from the Data page
2. Map accounts: Link Weave engineer accounts to Pylon or Zendesk users

​

Improving support efficiency

To optimize engineering support contributions:

1. Empower support team:
   • Create technical runbooks
   • Provide better debugging tools
   • Expand support team’s technical knowledge
2. Reduce escalations:
   • Improve product documentation
   • Add better error messages and logging
   • Fix recurring issues proactively
3. Distribute expertise:
   • Create rotation for complex support
   • Document solutions in knowledge base
   • Pair junior engineers with experts
4. Balance workload:
   • Set clear support SLAs
   • Protect engineering focus time
   • Schedule dedicated support hours
5. Learn from patterns:
   • Track common support issues
   • Prioritize fixes for frequent problems
   • Use support data to inform product roadmap

​

Technical details

​

Related metrics

• Support TTFR: Time to first response for support tickets
• Slack thread response time: Response times in Slack channels