Skip to main content

Asking Iris better questions

A few small habits — naming the timeframe, channel, and metric — turn vague answers into sharp, client-ready analysis.

Written by Schae Lilley

Be specific about three things

The fastest way to a great answer is to spell out:

  1. The timeframe. "Last 30 days," "June vs. May," "Q2 to date." Without it, Iris has to guess what period you mean.

  2. The channel. "Paid search," "Meta," "email," "organic" — or "blended" if you truly want everything combined.

  3. The metric. "ROAS," "CPA," "revenue," "leads." Name the number you actually care about.

Compare these:

  • Vague: "How are ads doing?"

  • Specific: "What was Meta ROAS for the last 30 days, and how does it compare to the 30 days before?"

The second question gets you an answer you can paste into a client update.

Ask for comparisons

Numbers mean more with context, and Iris is built for it:

  • "Compare paid search and paid social CPA for June."

  • "How does this month's revenue compare to the same month last year?"

  • "Which campaign improved the most week over week?"

Follow up instead of starting over

Each chat keeps its context, so refine rather than re-ask. If an answer is too high-level, say "break that down by campaign." If it's too detailed, say "give me the three takeaways." You can keep steering until the answer is exactly what you need.

Ask for the format you want

Iris can do more than write paragraphs:

  • "Chart it." Get an interactive chart you can open in the preview pane.

  • "Put that in a table." Ideal for campaign-by-campaign breakdowns.

  • "Turn this into a slide deck." Great for QBR prep or client updates.

  • "Export that as a spreadsheet." For anything you want to work with outside Omega.

Add your own context

You can attach files to a chat — drag and drop them onto the message box or use the attach button. A media plan, a client brief, or an export from another tool gives Iris context it can't get from connected data alone.

Tip: If Iris's answer seems off, check the Sources side of the left rail to confirm which data is connected for the pinned client. Iris can only analyze what's connected.

Did this answer your question?