Developer Support

Build effective support systems that help developers succeed and scale.

Skill Contract

Parameters

parameters:
  required:
    - support_type: enum[question, bug, feature, escalation]
    - context: string
  optional:
    - urgency: enum[low, medium, high, critical]
    - channel: enum[forum, discord, ticket, office_hours]

Output

output:
  response:
    answer: string
    resources: array[Link]
    follow_up: array[Action]

Support Channels

Support Tier Model

Tier 0: Self-Service
├── Documentation
├── FAQ
├── Knowledge Base
└── Search

Tier 1: Community
├── Forums
├── Discord/Slack
└── Stack Overflow

Tier 2: DevRel Team
├── Office Hours
├── Direct Outreach
└── Webinars

Tier 3: Engineering
├── Bug Reports
├── Feature Requests
└── Architecture Reviews

Office Hours Best Practices

Format

• Weekly or bi-weekly
• 30-60 minutes
• Open Q&A or themed topics
• Record for those who can't attend

Running Sessions

1. Start on time - Respect schedules
2. Screen share - Show, don't just tell
3. Take notes - Action items to follow up
4. Be honest - "I'll find out" is OK

FAQ Management

Creating Effective FAQs

Q: How do I authenticate with the API?

A: You can authenticate using API keys or OAuth 2.0:

**API Keys** (simplest)
curl -H "Authorization: Bearer YOUR_API_KEY" ...

**OAuth 2.0** (for user data)
[See our OAuth guide →](/docs/oauth)

Related: [Authentication errors](/docs/errors#auth)

FAQ Sources

• Support tickets (recurring issues)
• Community questions
• Search queries
• User feedback

Retry Logic

retry_patterns:
  unresolved_question:
    strategy: "Escalate to specialist"

  user_frustrated:
    strategy: "Personal outreach, expedite"

  recurring_issue:
    strategy: "Create FAQ, update docs"

Failure Modes & Recovery

Debug Checklist

□ Problem clearly understood?
□ Docs checked first?
□ Similar issues in history?
□ Reproducible steps?
□ Workaround available?
□ Escalation path clear?

Test Template

test_developer_support:
  unit_tests:
    - test_response_time:
        assert: "<24h for community"
    - test_answer_accuracy:
        assert: "Solves problem"

  integration_tests:
    - test_escalation_flow:
        assert: "Reaches specialist"

Support Metrics

Observability

metrics:
  - tickets_resolved: integer
  - response_time_avg: duration
  - csat_score: float
  - deflection_rate: float

See assets/ for support templates.