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.
Make a report from a conversation
When a conversation in the Assistant has turned into analysis you want every week, make it a report.
In the Assistant, open the conversation.
Click Make a report in the conversation header. (The button appears once the conversation has a question in it).
In the design workspace, check the draft the Xpert builds from the questions you asked and the queries it ran.
When the preview is right, save v1. See 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.
Go to Content > Xpert Artefacts and open an HTML artefact you own.
Click Convert to report.
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.
When the preview is right, save v1.
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.
In a flow, add a Report block.
Choose the Report. Only published reports are listed. The report's own Xpert writes the edition.
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.
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.
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.
Open the Analysis ticket and go to its Launch section.
Click Pin a take.
Choose a report, then one of its finished takes.
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.
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.