---
title: "Using reports with the Assistant, Flows and tickets"
slug: "using-reports-with-the-assistant-flows-and-tickets"
updated: 2026-10-29T13:02:39Z
published: 2026-10-29T13:02:39Z
canonical: "docs.xtremepush.com/using-reports-with-the-assistant-flows-and-tickets"
---

> ## 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.

# Using reports with the Assistant, Flows and tickets

Make reports from Assistant conversations and HTML artefacts, ask the Assistant about reports, and use reports in flows and on Analysis tickets.

## Before you begin

Analysis tickets need Work Trafficking as well as Reports. See [Work Trafficking](/documentation/docs/work-trafficking).

## Make a report from a conversation

When a conversation in the Assistant has turned into analysis you want every week, make it a report.

1. In the Assistant, open the conversation.
2. Click **Make a report** in the conversation header. (The button appears once the conversation has a question in it).
3. In the design workspace, check the draft the Xpert builds from the questions you asked and the queries it ran.
4. When the preview is right, save v1. See [Creating and designing a report](/documentation/docs/creating-and-designing-a-report).

You can also ask the Assistant, for example *Make this a weekly report*. It replies with a card; click **Open report** to continue in the design workspace.

## Ask the Assistant about reports

| You can ask it to | Example |
| --- | --- |
| Find a report | *Which reports cover push performance?* |
| Summarise an edition | *What did last week's campaign report say?* |
| Run a published report | *Run the weekly digest for last week* |
| Create a draft report | *Create a report on journey drop-off from the journey funnel template* |
| Rename or tag a report | *Rename the weekly digest to Monday CRM digest* or *Tag the weekly digest with CRM* |
| Suggest a change | *Add opens by channel to the weekly digest*. On a report with takes, this becomes a proposal on the latest take for you to accept. On a new report with no takes yet, it edits the draft. |

The Assistant never publishes a version, sends or shares a take, accepts a change, or changes a report's schedule, delivery or Xpert. Those stay with you.

## Convert an HTML artefact to a report

If an Xpert has produced an HTML report you want to keep producing, turn it into a report.

1. Go to **Content** > **Xpert Artefacts** and open an HTML artefact you own.
2. Click **Convert to report**.
3. In the design workspace, check the page. The Xpert rebuilds it in your house style, with each figure linked to a query. Any figure it cannot get from your data yet is marked **static**.
4. When the preview is right, save v1.

> [!NOTE]
> The artefact itself does not change.

## Add a report to a flow

The **Report** block, in the Output group, produces an edition of a report as a step in a flow.

1. In a flow, add a **Report** block.
2. Choose the **Report**. Only published reports are listed. The report's own Xpert writes the edition.
3. Choose the **Period**:
  - **The report's period rule (latest period)**, for example yesterday for a daily report.
  - **A specific period**, then choose it in **Which period**.
4. Optionally, select:
  - **Give the Xpert the previous steps' output as context**.
  - **Send to the report's delivery targets**, to send the take to the report's own email and Slack recipients with its designed message. The report must have recipients.
5. Save the flow.

After a run, click the Report block to see the result: the report name, period and status, **Open this take**, and the delivery to each recipient. If every recipient fails, the block fails.

## Pin a report to an Analysis ticket

An Analysis ticket's Launch section has a **Report** slot for the take that answers the ticket.

1. Open the Analysis ticket and go to its Launch section.
2. Click **Pin a take**.
3. Choose a report, then one of its finished takes.
4. Click **Pin**.

The slot then shows the report, period, take and status, with **Open report**. When the report has a newer take, click **Update to take N**. To change the take, click **Pin another take** or **Unpin**.

When an Xpert assigned to the ticket runs a report, it pins the take itself.

> [!NOTE]
> A pinned take is needed for sign-off
> 
> With Reports switched on, you cannot sign off an Analysis ticket, or move it to Approved or Done, without a pinned take. The sign-off check names what is missing, for example *No report pinned*. Changing the pinned report withdraws an existing sign-off.

## Raise a ticket from a take

If a take shows something worth looking into, click **Raise a ticket** above it. XpertOS creates an Investigation ticket in Backlog, linked to any ticket that has the take pinned. The report's timeline records the ticket. **Raise a ticket** needs Work Trafficking.