Zendesk (Help Desk Platform)

Zendesk Suite includes several integrated products: Ticket Support — the core ticketing system managing inbound contacts from email, chat, voice, and social. Guide — the knowledge base platform (Help Center) where public-facing documentation and internal articles are authored, published, and maintained. Explore — the analytics and dashboards layer for reporting on support metrics. Sell — an optional CRM layer for smaller companies. Chat — live chat widget for the product or website. The most important operational architecture decisions for a SaaS company: how tickets arrive (email, API, Intercom integration, native web form), the ticket form structure (which fields are required for reporting), the trigger and automation logic, and the tagging taxonomy. Product Ops and Support Ops jointly own Zendesk's configuration as a platform requiring continuous maintenance as the product and team scale.

Zendesk distinguishes between Triggers (fire instantly when conditions are met, e.g., when a ticket is created) and Automations (fire after a time delay, e.g., after 7 days with no reply from the customer). High-value trigger configurations: auto-assign to the correct team based on ticket form or subject line keywords, notify the agent when an SLA breach is approaching (2-hour warning), send an acknowledgment email to the customer with expected response time, tag tickets with "VIP" when the requester's organization ARR exceeds a threshold. High-value automations: close tickets after 7 days of no customer reply (with a closure notification), re-open if the customer replies after closure, escalate tickets that have been in a specific status for 24+ hours beyond their SLA target.

Zendesk Explore provides a SQL-like query builder and pre-built datasets for building support reports. Foundational reports every support team should maintain: (1) Inbound Volume Trend — tickets created per day/week by channel, allowing visual identification of volume spikes and channel shift. (2) SLA Performance — tickets meeting vs. breaching first response and resolution SLAs, filterable by team and ticket type. (3) Agent Performance — tickets resolved, CSAT score, and average handle time per agent per period (used for QA and coaching). (4) CSAT Analysis — CSAT scores by agent, team, channel, and ticket type, with open-text response aggregation. (5) Ticket Age Report — distribution of open tickets by how long they have been open, identifying chronic backlog patterns. Product Ops and Support Ops jointly maintain the Explore dashboard library and ensure metrics are consistent with leadership reporting definitions.