Set the project scope
Keep approved facts and source files together. Select the relevant record, Knowledge or reference for each request.
Keep a campaign brief in one project, make separate writing and visual requests, then package only the versions you choose.
Start creating in Chat ↗Illustrative coffee launch: the project holds the source material; each draft or visual is still its own reviewed request.
Keep approved facts and source files together. Select the relevant record, Knowledge or reference for each request.
Draft an introduction, make a product image and consider a short clip. Review each result, branch promising work and compare saved versions.
Order the approved pieces, add captions and download the delivery set with its manifest.
The set is a file handoff; it does not post or schedule a campaign. Explore projects for the working space and content sets for the final package.
An illustrative example. Review current inputs, settings and the quote in your workspace.
Write a concise launch introduction using only the approved blend name, origin and launch date. Do not invent an offer.
A fictional unmarked coffee bag on a stone counter in soft morning light, clean product composition, no readable label.
Replace sample facts with approved details. Source selection and later review, comparison or packaging happen in the workspace, outside the prompt text.
Record the audience, required wording, launch date and approved product details. Use current records or Knowledge for recurring facts and decide which visuals need an exact product source. Bring references or a reviewed Taste Profile only for the direction relevant to this request.
Organize campaign projectsCheck every claim and visible product detail before selecting a version. Develop supported native Studio layouts when the work needs editable text. Collect accepted files in an ordered set with captions, reopen it and inspect the download; scheduling, media buying and reporting remain separate steps.
Keep brand guidanceSaving keeps the output in the workspace. Download, content-set delivery and activation of an eligible public release are separate supported actions.
The public boards are labeled layout placeholders. They explain the story and review decisions, not live-provider quality. Inspect the actual saved result in your workspace.