Skip to content
Vectis
Book a demo

AI Connector

Ask Claude, ChatGPT or Microsoft Copilot Studio about your fleet, and propose changes, with your own Vectis permissions.

The Vectis AI Connector lets you ask Claude, ChatGPT or Microsoft Copilot Studio questions about your fleet and, if your organisation allows it, propose changes, without leaving the AI app you already use. It uses the same tools, permissions and safety rules as the AI Assistant built into Vectis.

How it works

The connector is a server your AI app talks to using MCP (Model Context Protocol), a standard way for AI apps to connect to other services. You give the AI app one URL, sign in to Vectis as yourself, and approve the connection. From then on, the AI app can ask Vectis questions on your behalf and, if your organisation allows it, propose changes for you to confirm.

What it can do

  • Answer questions using live Vectis data, such as vehicles, bookings, trips, compliance status, fuel, faults and RUC status, limited to what you are allowed to see.
  • Search and open Vectis guides and documents.
  • Propose changes, for example updating a vehicle's status or creating a booking, if your organisation has turned proposals on.

What it can't do

  • See more than your Vectis role and pool assignments allow. A pool-scoped person only sees their own pools' vehicles, bookings and trips, over the connector as well as in Vectis. Nobody can see another organisation's data through it.
  • Apply a change straight away. Every change is a proposal first, and nothing in Vectis changes until a person confirms it.
  • Cancel a booking or make any other destructive change. Those can only be approved inside Vectis.
  • Connect without a person. Connecting is always done by someone signing in as themselves; there is no API key or service-account option.

The safety model

  1. You sign in as you. The AI app never gets its own Vectis account. It acts with your permissions, checked on every call. If your role changes or your account is deactivated, the connector follows straight away.
  2. Reading happens straight away, limited to your role and pools.
  3. Changes are off by default. An administrator has to turn on Allow AI apps to propose changes before any AI app can propose anything.
  4. Changes are proposed, not applied. Where it can, the AI app asks you to confirm; accepting applies the change, declining leaves it pending. If it can't ask you, it gives you a link to approve the change in Vectis.
  5. Destructive changes, such as cancelling a booking, only ever give you an approval link. They can't be confirmed from inside the AI app.
  6. You can disconnect at any time. You can see and disconnect every AI app connected to your account, and administrators can do the same for every connection in the organisation.

What data goes where

  • Vectis keeps no extra copy of your fleet data for the connector. It records audit details for each call (which tool, which AI app, which person, the outcome, how many rows and how long it took) and a usage count, the same way the built-in assistant is audited.
  • The AI vendor sees the data in its answers, while it answers your question, under that vendor's own terms, not Vectis's. The consent screen, and for organisations with Australian data residency the data residency notice, say so before you connect.
  • Free text that people typed into Vectis, such as vehicle notes, booking notes and document text, is passed to the AI app marked as data, not instructions, so a note written by someone else can't be mistaken for a command from you.
  • Nothing changes in Vectis until a person applies it. Even with proposals on, the connector never writes to your fleet data directly.
  • Disconnecting, or an administrator turning the connector off, stops data reaching the AI app straight away.

In this guide