An investigation ticket tracks a structured piece of research or investigative work. Use it when the task is about understanding something (a pattern in the data, a hypothesis, a process question) and the output is a conclusion or recommendation rather than a campaign.
Investigation tickets use the reference prefix INV-#.
How investigation tickets differ from other tickets
Investigation tickets follow the same pipeline as all other ticket types. They have two differences from other tickets:
The Planning section contains a free-form plan document only. There are no dedicated fields for channels, audience, or send date: these are not relevant for investigation work.
The Launch section is sign-off only. There is no assembly step and no deploy action. Signing off marks the investigation complete and moves the ticket to Done.
There is no Content section on investigation tickets.
Planning
The plan document is a free-form markdown space. Use it to set out the research question, the approach, any constraints, and what a successful outcome looks like. There are no required fields.
When to use investigation tickets
Use an investigation ticket when the work is exploratory and the question is still being formed: something is wrong or unclear and you need to find out why. If the scope is more defined, with specific metrics, a time period, and a breakdown already clear, use an analysis ticket instead. If the investigation leads to a campaign recommendation, create a campaign ticket for the follow-on work and link them with a relates to link.
Using Xperts on investigation tickets
You can assign an Xpert to an investigation ticket at any stage. The same run rules apply: one run at a time, you cannot cancel a run in progress, and Xperts cannot sign off. See Xpert runs for details.