Configuring Work Trafficking

Work Trafficking is an optional feature. Contact your account manager to have it enabled for your account.

The pipeline

All ticket types share a single pipeline: Backlog, Planning, Content, QA, Approved, Assembly, Done, and Cancelled. The stages cannot be renamed, reordered, added, or removed. The only pipeline setting you can change is the WIP limit for each stage.

A WIP limit sets the number of tickets the stage is designed to hold at once. When the count reaches that limit, the board highlights the stage as a prompt to move work through before adding more. The limit is a signal, not a gate: tickets can still move into a full stage. Three to five is a practical starting point for Planning and Content; QA often needs a lower limit because reviews take longer than drafting. Start conservative and adjust once you can see where work tends to accumulate.

QA checklist

The QA checklist template sets the standard every campaign must meet before it can be signed off. The default template covers the most common pre-send checks: subject lines, links, merge fields, audience, schedule, and whether content covers the channels on the plan. Admins can edit the template at any time to add, remove, or rename items.

Start with the default and add items that reflect checks your team has actually failed before. A checklist built from real incidents is more useful than one built from theory.

To add or edit a QA checklist item navigate to: Tickets > Settings > Campaign > QA checklist

For each item you can set two pieces of information:

• Label - to identify the checklist item in the list

• Help text - to describe what the reviewer should check

Changes to the template apply to tickets that enter QA after the change. Tickets already in QA keep the checklist they had when they arrived at that stage.

Connecting Xtremepush

The Audience field in the Planning section pulls live segments from a connected Xtremepush instance. Connect your instance from Settings > My Integrations > Xtremepush to enable the segment picker. Without a connected instance, the Audience field will be empty.

Saved views

Save any board or list configuration (filter set, column arrangement, type selection) as a view. Private views are visible only to you; shared views are available to the whole team. Shared views are useful for standing workflows: a QA-only view, a view filtered to a specific campaign type, or a personal view for tracking your own tickets.

Permissions

Any team member can create, edit, move, assign, link, and comment on tickets. Only tenant admins can configure the board. Only the comment author or an admin can delete a comment.