# Vic AI assistant

> Vic AI is the Voltmasters assistant inside the platform: it answers questions about the documentation, reads your own projects, devices and incidents, links you straight to the right screen, and hands

Source: https://voltmasters.io/en/docs/voltmasters-platform/vic-ai-assistant/

**Vic AI** is the Voltmasters support assistant, built into the platform. Vic answers questions about the Voltmasters platform and the energy topics around it (storage, solar, grid connection, EV charging, device integrations), looks up the state of *your own* projects, and points you to the screen where you can act.

Vic is not a search box over the documentation. It combines three sources in one answer:

| Source | What it delivers |
| --- | --- |
| **Documentation** | The pages of this documentation site, searched per question. Relevant pages are shown as clickable **Sources** under the answer. |
| **Your platform data** | Live, read-only access to the projects, devices, incidents and project configuration that *your account* is allowed to see. |
| **Where you are** | The project you currently have open. Ask "are there open incidents" and Vic understands you mean this project. |

## Where to find Vic

| Surface | How to open it | Notes |
| --- | --- | --- |
| **Web portal** | The chat button in the bottom-right corner, on every page inside a project. | Full width or fullscreen, deep links open in the same window. |
| **Mobile app** | The Vic entry in the app. | Vic links to app screens, and to the browser for tasks that only exist in the web portal (device parameters, imbalance trading, API keys, subscription). |

![Voltmasters EMS: the Vic AI chat window in the web portal, answering a question about today's consumption](https://voltmasters.io/assets/docs/vic-ai-conversation.webp)

*Vic in the web portal.*

![Voltmasters EMS: Vic AI in the mobile app, reporting the health of the installation](https://voltmasters.io/assets/docs/vic-ai-mobile.webp)

*Vic in the mobile app.*

> **Note**
>
> In the web portal the assistant appears once you have a project open. On pages outside a project context the button is not shown.

## Asking a question

Type the question the way you would ask a colleague. A few things worth knowing:

-   **Your language.** Ask in Dutch, French or English and Vic answers in the same language.
-   **Context is kept.** Vic remembers the earlier turns of the conversation, so "and on my other project?" works as a follow-up.

> **Tip**
>
> Be concrete. "Which devices are on this project?" gets a better answer than "info about devices". Naming the project, the device or the page you mean saves a round trip.

## Example questions

### Your own projects, devices and incidents

Vic reads these live from the platform, limited to what your account may see.

-   Which projects do I have access to?
-   Give me all devices on this project, grouped by type.
-   Are there any active incidents right now?
-   Which incidents are still open on project *Site Antwerp*?
-   Do I have a Huawei inverter on any of my projects?
-   Which energy meters are installed on this site, and what brand are they?
-   Which strategy is active on this project?
-   What is the grid connection limit configured here?
-   Is imbalance trading enabled on this project?
-   Show me the full controller configuration of this project.

### Finding your way in the platform

Vic answers with a direct link to the screen, adapted to your role. Pages you may not access are not offered.

-   Where do I find the activity log?
-   Where can I manage the API keys of this project?
-   I want to look at the consumption report.
-   Where do I add a colleague to this project?
-   Where do I configure which incidents send a notification?
-   Take me to the battery dashboard.
-   Where do I see my subscription?

### How the platform works

These answers are grounded in this documentation, with the relevant pages attached as sources.

-   What is the difference between cost optimization and self-supply?
-   How does the peak shaving reserve work?
-   When exactly do I get an email about an incident?
-   How do I mute an incident type for one device only?
-   Which battery brands does Voltmasters support?
-   What does the EMS controller need in terms of network and internet access?
-   How do I add a new device to an existing project?
-   What does a data mandate with Fluvius give me?
-   What is the difference between the project dashboard and the Pro dashboard?

### Troubleshooting

-   My PV inverter has been showing no data since yesterday, where do I start?
-   I get a "device offline" incident on my energy meter, what are the usual causes?
-   The battery is not charging even though prices are low, what should I check?
-   An EV charger stays on "waiting", what does that mean?
-   Why does the consumption report show less than the energy meter?

### Questions Vic will hand over

Vic says so plainly when a question falls outside what it can do, and offers the ticket route:

-   I want an invoice for last month. *(billing, goes to a ticket)*
-   Can you change the grid limit of my project to 250 kW? *(Vic reads, it never writes)*
-   My controller has to be replaced. *(hardware, goes to a ticket)*
-   Can you connect the cabinet for me? *(physical electrical work, certified installer)*

## Sources under the answer

When documentation was used, the pages are shown as buttons under the answer. Vic keeps the links out of the running text on purpose, so the answer stays readable and the sources stay verifiable.

For questions about your own projects there are usually no sources: the answer comes from the platform itself, not from a document.

![Voltmasters EMS: the documentation pages an answer is based on, shown as buttons under the answer](https://voltmasters.io/assets/docs/vic-ai-sources.webp)

*The documentation an answer is based on, one button per page.*

## Links to the platform

Ask where something is and Vic answers with a clickable breadcrumb, for example **Configuration → Activity**. In the web portal the click opens the page in the same window, so the conversation stays open beside it. In the mobile app the link opens the app screen, or the browser for a task that only exists in the web portal.

![Voltmasters EMS: an answer from Vic in which the destination Subscription to Billing history is a clickable link](https://voltmasters.io/assets/docs/vic-ai-platform-link.webp)

*A destination named in an answer is always a link, never a path you have to walk yourself.*

The list of destinations is built per user. A page your role does not allow is never offered, so a link Vic gives you is a link that works.

## Handing over to support

Vic does not solve everything, and says so instead of guessing on. In two situations the route to a support ticket appears:

1.  **Immediately**, when the question needs something Vic cannot do: an account action, billing, a hardware swap, or data it has no access to.
2.  **After a few turns**, when a problem is not getting solved. Vic then asks whether a Voltmasters engineer should pick it up, and waits for your answer.

A button appears under the answer. **Only your click creates the ticket.** Vic never opens a ticket by itself and never claims it did.

![Voltmasters EMS: Vic points at the support ticket button under its answer, with the button below it](https://voltmasters.io/assets/docs/vic-ai-ticket-button.webp)

*Vic points at the button, you decide. Nothing is filed until you click it.*

What ends up in the ticket:

-   An AI-written summary of the conversation.
-   The full conversation history, question by question.
-   The project you had open, with a link to its dashboard.
-   Your name and email address, so support can follow up.

A Voltmasters engineer picks the ticket up with that context already in place, so you do not have to tell the story again.

## What Vic cannot do

| Limitation | Why |
| --- | --- |
| **Vic only reads** | Changing settings, device parameters, strategies or users is never done through the chat. Vic points you to the screen where you do it yourself, under your own name, with the change recorded in the activity log. |
| **Vic can be wrong** | Answers are generated. For an important decision, verify against the documentation page in the sources or against the platform itself. |
| **Only your own data** | Access is enforced server-side per project. Vic cannot see a project your account is not authorised for. |
| **No credentials** | Passwords, API keys and tokens are out of scope. Never paste them into the chat. |
| **No pricing or roadmap** | Commercial questions go to the sales team, unreleased features get no answer. |
| **Fair-use limit** | After a burst of questions in a short window Vic asks you to wait a moment. |

## Frequently asked questions

**Does Vic see the data of my project live?**

Yes, for projects, devices, incidents and the controller configuration of a project. Vic queries the platform at the moment you ask, with your own access rights. That is why "are there open incidents" gives the current answer rather than yesterday's.

Vic does not read time-series measurement data, graphs or reports. For those, use the dashboards, which Vic will link you to.

**Which project does Vic assume?**

The project you have open. Ask about "the devices" or "open incidents" without naming a project and Vic uses the current one.

Name another project and Vic switches to it. Ask about "all my projects" or "any incidents anywhere" and Vic looks across every project you can see.

**Are my conversations stored?**

Yes. Conversations are stored linked to your account and the project, so that a ticket can be picked up with full context and so that Voltmasters can monitor the quality of the assistant. Do not paste credentials or data that has no business being in a support conversation.

**Vic gives an answer I doubt. Now what?**

Check the sources under the answer: they are the documentation pages the answer is based on. If there are no sources, Vic answered from general knowledge or from your platform data, and says which.

Still not right? Ask the question again with more detail, or open a support ticket. A wrong answer is useful feedback: the ticket contains the whole conversation, so we can see where it went off.

**Can Vic change something for me?**

No. Vic reads, it never writes. Every change stays a deliberate action by a person, in the platform, recorded in the [activity log](https://voltmasters.io/en/docs/voltmasters-platform/project-settings/activity/) with the name of whoever made it. Vic does take you to the right screen.

**Is Vic available in the mobile app?**

Yes. Vic knows it is running in the app and links to app screens where it can. For a task that only exists in the web portal, such as configuring device parameters or imbalance trading, Vic says so and gives a browser link.

**Which technology is behind Vic?**

Vic runs on Anthropic's Claude models. Per question the documentation is searched with a combination of semantic and keyword search, the relevant fragments go to the model along with your question, and the model calls read-only platform tools when the question is about your own data. The whole exchange runs over the Voltmasters platform, no data goes to third parties beyond the model provider processing the question.