Stage Checklist

  • ✓ Research (.md file)
  • ✓ POC App
  • ✓ POC UI (templates)
  • ✓ Microservice
  • ✓ Containerized (Dockerfile)
  • ✓ Helm Chart
  • ✓ CI/CD Pipeline
  • ✓ Frontend Page
Download Research Download Implementation Guide

AI Research

Last researched: 2026-03-05

Refund Rules

Zendesk typically operates on a no-refund policy for mid-cycle cancellations or downgrades, with charges applying for the full billing period. However, they may provide pro-rated refunds for billing errors or service outages that exceed SLA thresholds. Annual plans generally have no refund provisions except in cases of material breach by Zendesk.

Credit Policies

Zendesk offers service credits for downtime that exceeds their 99.9% uptime SLA commitment. Credits are typically calculated as a percentage of monthly fees based on downtime duration. They may also provide credits for acknowledged service disruptions or performance issues. Credits must usually be requested within 30 days of the incident and are applied to future invoices rather than cash refunds.

Contractual Terms

Auto-renewal clauses are standard with 30-day notice required for cancellation. Price increases are typically limited to once per year with 30-60 days advance notice. Contracts often include usage-based overage charges for exceeding included limits (storage, API calls). Enterprise contracts may have more favorable terms including price protection periods and longer notice requirements for changes.

Integration Complexity

★★☆☆☆

Technical Notes

Zendesk uses OAuth 2.0 or API token authentication. Rate limit is 700 requests/minute for most endpoints. Key endpoints: /api/v2/users for agent data with native last_login_at field, /api/v2/incremental/ticket_events for activity tracking. Subdomain-based URLs ({subdomain}.zendesk.com). Good documentation and RESTful design. May need to handle pagination for large user bases. Consider filtering by role (agent/admin) to exclude free end-users from seat analysis.