Zendesk / Intercom / Front / Pylon
Where the customer conversation lives — the ticket, the thread, and the SLA clock.
Lesson 6 of 10
Support & GTM Toolbelt
A single ticket rarely stays in one tool. Following it across the stack — fast — is most of what "getting productive in week one" actually means.
The stack a ticket actually touches
Five categories of tool cover most of what you'll need to move between.
Jira / Linear
Where an escalated bug becomes an engineering ticket, with its own status separate from the support ticket.
Metabase
Where you go to answer "how many customers hit this" without waiting on a data engineer.
LaunchDarkly
Feature flags — often the real explanation for why one customer's experience differs from the docs.
Billing tools (Stripe, etc.)
Where "my invoice is wrong" actually gets resolved — subscription state, proration, and payment failures.
Exercises
Look at the sanitized ticket trace below, then work through both exercises.
Zendesk #48213 — "Export button missing for one user"
→ Linked to Jira ENG-1092 (status: In Progress)
→ LaunchDarkly flag: new-export-ui — 20% rollout
→ Customer's account: NOT in rollout cohort
→ Root cause: feature flag targeting, not a bugConcept check
Answer in your head first, then click a question to reveal the answer.
Scenario checklist
Work through the sample ticket trace and check each item off. Progress is saved in your browser.
Go deeper
These primers are a starting point. Read the primary sources to build real fluency.
Zendesk: What is Zendesk?The conversation/ticketing layer most support orgs are built onAtlassian: Getting started with JiraHow an engineering ticket tracks a fix, separate from the customer-facing oneLaunchDarkly: What are feature flags?Why "it works for me but not them" is often a rollout state, not a bugMetabase: Learn MetabaseSelf-serve querying, for when you need an answer faster than a data engineer can give it
Training Notes
What building this project taught me.
This module is the practical front door, not a flagged gap
None of these tools are individually hard to learn. The value is recognizing the pattern fast — conversation tool ↔ engineering tracker ↔ flag/rollout state ↔ billing system — on day one at a new company.
The trace below is illustrative, not a real ticket
Real tool integrations vary — some companies link tickets automatically, others rely on someone pasting a URL into a comment. The shape of the trace matters more than any specific tool's UI.