---
title: "Work Trafficking"
slug: "work-trafficking"
updated: 2026-10-21T08:45:00Z
published: 2026-10-21T08:45:00Z
canonical: "docs.xtremepush.com/work-trafficking"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xtremepush.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Work Trafficking

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.

> [!NOTE]
> 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](/documentation/docs/campaign-tickets): the full campaign workflow from brief to deployment, including Assembly, QA, and drift detection
- [Xpert runs](/documentation/docs/xpert-runs): assigning Xperts, how runs work, and what happens when a run completes or fails
- [Investigation tickets](/documentation/docs/investigation-tickets): exploratory research tickets with no Content section or deployment step
- [Analysis tickets](/documentation/docs/analysis-tickets): structured research tickets with a defined scope and sign-off at completion
- [Metrics](/documentation/docs/work-trafficking-metrics): board-level and per-ticket performance data
- [Configuring Work Trafficking](/documentation/docs/configuring-work-trafficking): WIP limits, QA checklist, and permissions