Prompt examples

Every prompt below maps to something the assistant can genuinely do. Say it in your own words; specifics (folder names, markets, template names) make the first answer the right one. Prompts marked approval card change nothing until you approve the card.

Finding things#

• "Do we have any vertical video of the trainers on a running track?": searches the whole library, looks at the files when tags don't settle it, and attaches clickable thumbnails of the matches.
• "Which templates could run a Demand Gen video?": checks placement fit per composition and links the templates that qualify.
• "What is in the Autumn campaign folder?": resolves the folder by name and lists its contents, with links.
• "What are our competitors saying about waterproof jackets right now?": searches the live web through your own provider key and answers with cited sources.

Reports and status#

• "How many renders completed last week compared with the week before?": a workspace report over both periods, comparison included.
• "Why did yesterday's build fail?": reads the build's creatives and reports each failure with its reason.
• "Did the DE creatives deliver to Google successfully?": reads each creative's delivery outcome and reports any failure with its reason.
• "How much storage are we using, and which folders are heaviest?": organisation storage totals, broken down by folder.

Library upkeep#

• "Tag everything in the Product folder with subject and season tags": looks at each file first, then writes the tags directly. Tags only ever add; nothing is replaced.
• "Set up a folder for each of our twelve markets under Campaigns": creates the whole folder tree directly, in one pass.
• "Rename the January shoot assets to match our new naming convention": approval card listing every rename before anything changes.
• "Block the old logo files so nothing renders with them": approval card; blocked assets stay in the library but can never render.

Campaign building#

• "Draft an autumn sale campaign for the waterproof shell range, UK, Germany and France, Meta and Google, using the summer launch template": a campaign approval card, then a validated flow approval card showing the expected creative count and the full matrix of what a build would produce.
• "Add a Black Friday version for Germany only": a flow edit approval card with a diff of the creative combinations it adds and removes.
• "Which markets and languages do our flows already use?": reads the market and language pairings across your existing flows.
• "Upload the approved German renders to Meta": an approval card naming each creative and its destination. Everything arrives paused.

Copy and brand#

• "Check every written value in the Spring flow against the glossary": an advisory check of the whole flow, flagging prohibited claims, claims missing their required qualifier, and forbidden words.
• "What claims are approved for the French market?": lists the live claims for that market, with qualifiers and expiry dates.
• "Does this headline break any German glossary rules?": checks the exact copy you give it against that market's rule set.

Generating media#

• "Generate a square hero image of oak furniture in morning light": confirms the brief and model before generating anything; the image lands as a tagged asset in the AI Generated folder and appears in the chat. Up to 4 images per turn.
• "Make the background warmer and lose the clutter": edits the image it just generated; every pass lands as a new asset, so nothing is overwritten.
• "Create a short clip of rain hitting a tent canvas": starts a video generation; clips take a few minutes and land in AI Generated automatically, even if you move on. Up to 2 videos per turn.

Phrasing tips#

• Name the market, language, template or folder you mean: "the DE creatives from the summer launch template" beats "those ads from before".
• The assistant reads before it asks: it searches the library, checks placement fit and counts combinations itself rather than asking for details it can look up.
• You can leave mid-turn: answers, generations and approval follow-ups carry on in the background and are waiting when you come back, even after closing the tab.