Marketing teams typically plan campaigns in external tools while execution happens in Xtremepush. Work Trafficking brings both sides into one place: a ticket carries the brief, content, QA checklist, and delivery record, so the team works in the same system as the Xperts and campaigns that do the work.
A ticket is the container for a single piece of work. It moves through a shared pipeline from first idea through to deployment. Xperts can be assigned at any stage with an instruction: they carry out the work, post their outcome as a comment, and advance the ticket where the stage allows. The result is an end-to-end record of the work: who did what, how long each stage took, and what was delivered.
Work Trafficking is an optional feature. Contact your account manager to have it enabled for your account.
Ticket types
Three ticket types are available:
Type | Reference | Use for |
|---|---|---|
Campaign | CAMP-# | Planning and executing a campaign through to deployment |
Analysis | ANL-# | Structured research or reporting work with a defined scope and deliverable |
Investigation | INV-# | Exploratory work where the question is still being formed and the output is a conclusion or recommendation |
The pipeline
All ticket types share a single pipeline: Backlog → Planning → Content → QA → Approved → Assembly → Done / Cancelled.
The pipeline is fixed; stages cannot be renamed, reordered, added, or removed.
In this section
Campaign tickets: the full campaign workflow from brief to deployment, including Assembly, QA, and drift detection
Xpert runs: assigning Xperts, how runs work, and what happens when a run completes or fails
Investigation tickets: exploratory research tickets with no Content section or deployment step
Analysis tickets: structured research tickets with a defined scope and sign-off at completion
Metrics: board-level and per-ticket performance data
Configuring Work Trafficking: WIP limits, QA checklist, and permissions