When a chat answer includes a table you want to keep or share, it appears as a Report draft card. The card shows a title (the question you asked), how many rows and columns the result has, the columns by name, and the table itself. The actions sit at the top of the card, and they belong to that card alone — so if you open other tables from the same answer, you can save or email the one you actually need.
If the result has a date column, the card also shows a Coverage line: the earliest and latest day in the rows, and any days in between that have no rows (for example "missing: 10 Oct, 12 Oct, 13 Oct"). Check it before you save — a missing day usually means the figures for that day have not arrived yet. When the table is long and only the first rows were fetched, the line says the coverage is for the rows shown, because the rest cannot be checked.
How the answer was checked is folded under How this was checked. Open it when you want the detail; nothing is hidden.
The exception is a table labelled Sample preview: that's a peek at what a source holds, not a finished answer, so it is not a report draft and carries no report actions. Ask for the figures you want and use that result instead.
Save as a draft report
Save as draft report files the exact result as a draft report — same numbers, same columns, re-runnable any time. A box asks you to name it (your question is filled in for you) and to pick a category. It is saved to My reports as a draft; only you and your administrators can see it until an administrator publishes it. It also keeps the governed method that will run the report again, so the draft and its method are created together.
If the button is greyed out, the question behind that table can't be saved as it stands. Run the question again and save the new result.
You can also just ask in the chat — "save this as a report" works. The assistant gives the report a name and a category, and the report is built from the query behind the result you were looking at, exactly as the button would build it. The assistant never writes the report itself, so what is saved is always the checked result. It tells you the name it used, and the report waits in My reports as a draft. If nothing has been checked in the chat yet, it says so and asks you to run the question first.
You are taken straight to the saved report, so you never have to go looking for it. At the top of it you'll find a short panel explaining that it is a draft and what you can do next: publish it into the catalogue, re-file it under a different category, put it on a schedule, ask for a change, or drop it. Publishing is what turns it into something the whole team can find and run — and it also puts the method behind it on the skills shelf. If you don't have admin rights, the panel says so and tells you to ask an administrator to publish it.
Until it's published, a draft is a private working copy: it appears under the Drafts view on the Reports page, not in the main catalogue. See Drafts: publish, archive, amend.
The grid on a saved report is a live re-run of the query, so it's always current — it isn't a frozen snapshot of the day you saved it.
Download the table
Excel and CSV above a chat table give you the whole result, not the rows on screen. A chat answer deliberately shows only the first few rows, so your file will usually be longer than the table you were looking at. See Export to Excel.
Email it
Email report (also at the top of the card) composes a draft email — it does not send anything. The draft lands in your Outbox (sidebar) with the answer summarised in the body and the full table attached as a spreadsheet — the same complete result you'd get from the download button, not just the rows shown in the chat.
To actually send: open the Outbox, review the draft, edit anything that needs changing, and click Send. You'll be asked to confirm. Nothing ever leaves the system without that deliberate click.
This two-step design is intentional: an email with your company's numbers in it should never be one accidental click away.