Free Starter Pack Before you start using Claude for Excel, apply these best practices
← All Integrations
Zendesk Logo

Zendesk + Go Fig

Customer Success

Integrate Zendesk support data with Go Fig for customer service cost analysis and insights.

Support is a major line item and a leading indicator of churn, but the data lives in Zendesk and rarely makes it into the finance conversation. Go Fig pulls tickets, users, organizations, agents, groups, macros, tags, custom fields, SLA data, satisfaction ratings, and time-tracking records into the Financial Intelligence Graph and joins them to revenue, contract tier, and cost-center payroll from accounting. The result is cost-to-serve by plan and segment, agent productivity anchored on real handle-time data, ticket-volume forecasts that drive staffing decisions, and churn leading indicators tied to ticket patterns like reopen rate, escalations, or bug tag volume. Celeste reasons across Zendesk's ticket and satisfaction data to surface the questions VP Support and CFOs argue about: which customers are margin-destructive, how much would shifting one point of deflection save, and where SLA misses correlate with downgrade. The integration is read-only and respects Zendesk agent-role visibility.

Key facts

API
Zendesk Support REST API v2
Custom fields
Tickets, users, and organizations, fully synced
Satisfaction
CSAT and ratings with comments
SLA data
Policy definitions, breaches, and metrics
Sync cadence
Hourly incremental via incremental export endpoints

SOC 2 Type II ยท All integrations

What you can do with Zendesk data in Go Fig

Cost-to-serve by customer and plan

Join Zendesk ticket volume, handle time, and agent hours to MRR, plan, and segment from billing. Surface which customers and which plan tiers are margin-destructive at current support load, and model the margin impact of plan repricing or tier reshuffling.

Churn leading indicators

Model ticket volume trends, reopen rate, escalation frequency, and tag patterns (cancellation_intent, bug, integration_issue) against actual downgrade and churn events to produce a churn risk score that runs 60 to 90 days ahead of billing signals.

Support staffing and headcount planning

Forecast ticket volume from customer growth and release cadence, layer in agent capacity and seasonality, and flag where headcount adds are needed before SLA misses start driving CSAT down.

Data available from Zendesk

Go Fig extracts and normalizes the following data from your Zendesk account:

Tickets
Ticket metrics (first response, full resolution, replies)
Users (end users)
Organizations
Agents and admins
Groups
Macros
Tags
Custom fields on tickets, users, and organizations
Satisfaction ratings and comments
SLA policies, targets, and breaches
Time tracking and views

How to connect Zendesk

1

Generate the Zendesk API token

In the Zendesk admin center, create an API token against a dedicated admin user (finance-integration@ is a common convention). Go Fig uses the incremental export endpoints for tickets and users, which require admin-level access and are rate-limited generously compared to the standard search API.

2

Inventory tag taxonomy and ticket custom fields

Zendesk tag taxonomies sprawl over time. Go Fig surfaces your current tag usage, flags low-volume or near-duplicate tags (cancel vs cancellation vs churn), and lets you group tags into categories for analysis. Ticket custom fields (priority_override, billing_issue, segment) sync as native columns so Celeste can reason over them.

3

Map agent groups to cost centers

Agent groups (Tier 1, Tier 2, Escalations, Onboarding) map to cost centers in your accounting system. This is the join that produces true fully loaded cost-to-serve once Go Fig combines Zendesk handle time and agent hours with payroll expense from accounting.

4

Connect billing and CRM for segment context

If Stripe, Chargebee, NetSuite, or Salesforce is connected, Go Fig joins Zendesk organizations to billing accounts on external_id, domain, or organization name. Once joined, every support metric can be sliced by MRR, ARR, contract tier, renewal date, and CSM owner.

Authentication: Zendesk API token tied to a dedicated admin user, or OAuth 2.0 for multi-brand accounts. Tokens are scoped read-only to tickets, users, organizations, ticket metrics, satisfaction ratings, and SLA policies. Zendesk Suite, Support Professional, and Enterprise plans are supported, Team plan works with reduced metric coverage.

Common Questions About Zendesk Integration

How does Go Fig handle Zendesk's tag taxonomy and tag drift?

Tags sync as raw categorical values and as a normalized, grouped view you define during setup. Because Zendesk tags have no strict schema, drift is inevitable, the starter flow highlights near-duplicates and near-empty tags, and lets you group them into analysis categories (cancellation_signals, bug_categories, billing_issues) that Celeste uses for cross-period reporting. The raw tag view stays available when you need fidelity to a specific agent's tagging.

What satisfaction data is available, and can it be joined to revenue?

Good / bad ratings and any open-text comments sync per satisfaction request. Once Zendesk organizations are joined to billing accounts, Celeste can segment CSAT by ARR tier, show how satisfaction trends for soon-to-renew accounts, and correlate low ratings with downgrade events. CSAT by product area is also easy once tickets are tagged by product.

Does Go Fig support Zendesk multi-brand and multi-help-center setups?

Yes. Brand is a native dimension in the ingested data, so multi-brand Zendesk accounts can report by brand, help-center, or rollup without re-configuring. Help center article and view data also sync per brand when that content is part of your deflection strategy.

How are SLA policies and breaches modeled?

SLA policy definitions sync alongside per-ticket SLA metrics (first response, full resolution, next reply) and breach events. Breach rate by priority, by brand, and by agent group is available out of the box, and Celeste can model the revenue exposure of SLA misses once organization-to-revenue joins are in place.

What about Zendesk API rate limits and historical backfill?

Zendesk enforces per-minute rate limits that vary by plan (400 requests per minute on Enterprise). Go Fig uses the incremental export endpoints for tickets and users, which have dedicated higher limits and are designed exactly for this use case. Historical backfill is supported for the full ticket history your account retains, and steady-state hourly incrementals stay well under the rate ceiling.

Ready to connect Zendesk?

See how your Zendesk data looks in Go Fig with a personalized demo.

Book a Demo