Ask your first question

Start with the outcome

Tell Vega what you want to understand or decide. A useful question usually includes a subject, a time period, and the kind of answer you need.

For example:

Summarize electricity consumption for the main site over the last seven days and point out the largest daily change.

Before asking, check the active account. Vega searches only the sites, components, measurements, invoices, and documents available in that account.

Start a conversation

1. Select New Chat in the left navigation.
2. Review the suggestions under Try asking. Select one to place it in the message box, or use the refresh button to show a different set.
3. If a suggested question ends with an asset placeholder, choose the site and component requested by the picker.
4. Edit the question so it states your intended outcome and period.
5. Select Send.
6. Wait while Vega reports that it is checking information and preparing the answer.

Suggestions are starting points, not fixed commands. Always replace broad wording such as “this year” or “all sites” when the decision requires an exact scope.

Use a reliable question pattern

Build the question from four parts:

1. Objective — summarize, compare, explain, verify, or identify.
2. Scope — the site or component selected with an @ reference.
3. Period — an explicit date range or an unambiguous relative period.
4. Output — a concise explanation, values, table, chart, or ranked list.

For example:

Compare daily consumption for @Main Warehouse / Grid Meter from 1 August through 31 August 2026 with the previous complete month. Show a table and identify the three largest daily increases.

Vega resolves natural-language periods such as “yesterday,” “last month,” and “year to date.” Explicit dates are safer when billing boundaries, time zones, or partial days matter.

Add context

If the first answer is too broad, add the details that matter. You can specify:

• a site, building, meter, or connected asset,
• a date range or comparison period,
• the metric or unit you care about, and
• whether you want a summary, comparison, chart, or recommendation.

You can add this context in a follow-up message. Vega uses the conversation to understand what your next question refers to.

When an account has more than one plausible site or similarly named component, use the picker instead of relying on a typed name. If you want every component at one site, choose All components at site.

Refine the answer

Treat the first response as a starting point. Ask Vega to narrow the period, compare another asset, explain an anomaly, or present the information differently.

Try follow-ups such as:

• “Compare that with the previous week.”
• “Which day contributed most to the increase?”
• “Show only business hours.”
• “Explain the result in plain language.”
• “State the exact components, dates, units, and data coverage used.”

Be precise when it matters

Use explicit dates and asset names for decisions that depend on an exact scope. If Vega interprets a name or period differently than you intended, correct it in your next message and ask it to recalculate.

If the response is taking the wrong direction

While Vega is generating, the send button becomes Stop response. Select it to end the active response. Vega keeps the stopped turn in the conversation and labels it Response stopped. If stopping is not acknowledged, the control offers Retry stop.

Then send a corrected question. Do not treat the incomplete response as a finished analysis.

Before relying on the result

Ask Vega to state the scope and data coverage, especially for numerical answers. Then use Verify Vega’s answers before acting to check measurements, invoice periods, source documents, and assumptions.