What agents can produce
When you give an agent a job, you can steer the shape of what comes back. The deliverable format picker in the composer offers the formats the team uses every day, including:
Weekly update, MTD report, and Monthly report
QBR outline and quarterly narratives and plans
Summary email and Action items
Handoff documents (strategist, AD, AM) and Client 101 briefs
Leave the picker on Auto and the agent chooses the most natural format for the ask. Agents also produce slide decks and spreadsheets — see "Slide decks and styles" for deck specifics.
Tip: You can set a personal default format in Settings → My preferences, so every new request starts from the format you use most.
Where deliverables land
Every deliverable lands in Files, the library in the Agents product's left rail:
Outputs from a chat save alongside the conversation and appear in Files.
Scheduled runs file each client's deliverables into that client's own folder automatically.
Content deliverables (briefs, outlines, articles) also file into the content team's shared Drive folder, in a subfolder per production month.
You'll get a notification when a deliverable is ready — watch the bell in the top bar.
Open any deliverable for a full-page preview, with download, share, and rename at the top. Downloads hand you the real file, properly named — a Word deliverable downloads as the Word document itself, not a PDF preview of it.
Review before it goes out
Agent output is a strong first draft — treat it like one. A quick review flow that works:
Read it in Files. The preview renders the real document, so what you see is what the client gets.
Ask for revisions. Use the composer at the bottom of the document page to request changes — "shorten the intro," "add a slide on Q3 ROAS." The revision comes back as a new version for you to review.
Push to Workbench for anything client-facing. That moves it into the review ladder — In Progress → Awaiting Review → Approved — where a teammate can sign off and you can mark it Client Ready.
Share it with the account team so everyone's looking at the same version.
Note: Numbers deserve a second look. Agents pull from the client's connected data, but promo periods, restatements, or a data source that's mid-sync can skew a figure — you know the account best, and your name is on the deliverable.
Sources you can verify
Deliverables carry their receipts. When an agent pulls a claim from a client document, it cites that specific document right at the claim — as a link that opens the source. Use those links during review: a cited claim can be verified in seconds; anything uncited deserves a harder look before it ships.
Publishing HTML deliverables
Some deliverables are interactive HTML pages — dashboards, audits, visual reports. To share one beyond Omega, use Add to Artifact Portal on its preview: it opens the company's Artifact Portal with the upload form prefilled, and you publish there as the owner, setting visibility or a password. The portal is the supported home for hosted HTML work — use it rather than ad-hoc hosting, so links stay permanent and access stays controlled.
Making deliverables better over time
The more context a client has, the better their deliverables get. Standing instructions, memories, goals, and calendars (all under Settings → Client settings) feed directly into what agents write — set them once and every future report benefits. See "Client setup" for the full tour.