Skip to content
All posts

October 16, 2026 · 4 min read

Ask your fleet a question: how Vince works, and why nothing changes until you say so

Vince is the assistant inside VendGogh. Ask which machines went quiet or what sold last week, in your own words. Ask for a change, and Vince shows a plan first. Here is how it works, what it reads, and where it stops.

Monday morning, before the first drive, every operator asks the same questions. Which machines went quiet over the weekend? Which coils are low on the Tuesday route? What sold at the hospital last week? Today you answer them by opening three screens and reading three lists.

Vince answers them when you ask.

What Vince is

Vince is the assistant inside the VendGogh portal. It opens from one button on every screen, in a panel beside the screen you are on. You type a question in your own words. Vince looks it up in your fleet and answers in a sentence or a short list.

Vince reads your data, and no one else’s.

What you can ask

Vince answers from six kinds of record. Each one is a question you already ask:

  • Machines. “Which of my machines are not reporting? List them worst first.” Vince uses the same status as the Operations screen: a machine is not reporting when it misses three expected reads, or, for a machine that reports only when it sells, when its card reader last reported offline.
  • Stock. “Which coils are low at Nine15?”
  • Sales. “What sold most last week, and where?” Vince reads the ledger for the period you name.
  • Alerts. “Which alerts are open?” Vince lists them the way the Alerts screen does: worst first, with the dollars at stake each week.
  • Pick lists. “What do I pull for the library stop?” Vince reads the pick list, item by item.
  • Items. “What is in coil B2 at the gym?”

Above each answer, Vince shows the lookups it made, by name, with the time each one took. You can see where an answer came from before you act on it.

Ask for a change

Vince also makes changes: a new item, a machine set-up, a route, a tag, a restock. It does the typing. You make the decision.

  1. Vince writes a plan. Each step is one line: what it creates, what it changes. A dry run checks the plan against your fleet before you see it.
  2. You select Apply, or Reject. A plan that deletes data also asks you to type a phrase. Vince cannot select Apply for itself. It is built so that it cannot.
  3. VendGogh keeps the record. Who approved the change, and when, stays with the conversation.

When Vince needs something from you, it asks with a short form in the chat: the location, the machine, the route. Fill it in and select Run, and the plan continues.

Your prompts, one slash away

portal.vendgogh.io/fleet/machines

The questions you ask every week should not need typing every week.

  • Type / at the start of the message box, and your saved prompts slide up from it, most used first. Keep typing to narrow them.
  • Type // for every prompt, including the starters that come with Vince: Onboard a location, Plan a restock, Find silent machines, Plan a cash run, and more, grouped by the job.
  • Under any question you asked, select Save as a prompt. The question becomes the form: give it a name, and it is in your list the next time you type a slash.

The keys in the list are buttons too, so a phone has the same controls as a keyboard.

What it costs

Vince AI chat is an add-on to your plan: $9.95 a month for your operator, and everyone on your team can use it. VendGogh runs it for you on an Anthropic model, with a monthly spending ceiling we set with you. Every turn is on the record with its cost, and the AI usage page shows your month against the ceiling. At the ceiling, Vince pauses until we raise it or the month ends. See pricing.

Have an Anthropic key of your own? Vince can run on it instead: you pay Anthropic directly, and VendGogh sets no ceiling. Only your Anthropic account’s limits apply. Ask us.

Either way, Vince reads only the data of the operator you are working as. If you run sub-operators and act as one of them, that turn reads that sub-operator and nothing else.

Where Vince stops

An assistant is only useful if you know what it will not do.

  • Vince does not link a card reader or set an alert aside. Those stay on their own screens, and a Vince prompt that touches them says so.
  • Vince cannot see how much cash a machine holds. It can plan a cash run and propose to record a pickup, and the record waits on your Apply.
  • Vince does not act on its own. It answers your question, or it waits on your Apply.
  • Vince does not read anyone else’s fleet.

See Vince on your own fleet

Book a 30-minute demo. We open Vince on your own machines, ask it the questions you ask every Monday, and show a change from plan to record.

How many machines do you manage?

We reply within one business day.

See everything VendGogh does on the features page.

ai assistantvending management softwarefleet observabilityroute planning