How to save a HERO data question as a reusable query, where to find your saved queries, and how to refine, delete, approve, or quarantine them.
Last updated
Requires: Access to HERO chat. Saved queries follow you personally, they are not tied to a single property.
Once HERO gives you an analytical answer (one with numbers or a chart, not just a chat reply), you can save the question so you do not have to type it out again next time.
Ask HERO a data question, either in the HERO chat panel or from the command palette (Cmd/Ctrl-K).
Once HERO answers, hover over the answer (or tap it on mobile) to reveal the action row below it, then click Save query.
A confirm window opens showing the question as asked and a plain-language summary of what this saves, along with a note that it will be available across all your properties. This is a read-only confirmation, not an editor: there is nothing to type or adjust here.
Click Save query to confirm.
A toast confirms Query saved, along with its status. Saved · active means it is ready to use right away. Saved · pending review means URBI is double-checking it before it is used in future answers.
To see your saved queries, click the bookmark icon in the HERO chat header, labeled My saved queries.
From the list, each saved query shows its status and when you last used it. You can refine it in chat (opens the question back in HERO chat so you can adjust it, since saved queries cannot be edited directly, only refined by asking again), or delete it for good (you will be asked to confirm, since this cannot be undone).
If a saved query gets flagged (this happens after repeated "Bad answer" feedback on answers that used it), you can Approve it to restore normal use, or Remove it.
Saved queries follow you, the person, across every property you have access to. They are not shared with other staff.
If URBI tells you a saved query can no longer run because something it depends on changed, you can choose Store anyway (quarantined) to keep it for later review, or cancel instead. A quarantined query is not used again until it is re-checked.
HERO never shows or requires any code or technical query syntax anywhere in this flow.