​

VH3 AI: Field Service Intelligence

VH3 AI is the intelligence layer that sits alongside your field service management system. It connects the systems your operation already runs on, keeps the operational picture current as jobs, relationships, and accounts change, and makes that intelligence available to your team, automations, agents, and any application you build on top.

​

A new kind of infrastructure

Field service businesses have been generating rich operational data for years. Jobs, engineers, sites, customers, communications, worksheets, compliance records. The problem has never been a lack of data. It has been a lack of infrastructure that connects it, understands it in context, and keeps it reliable for everyone who needs to use it. VH3 AI is that infrastructure: a dedicated intelligence layer built specifically for field service, designed around three principles. Understands the domain. Every record is mapped into a structured model of what actually happens in a field service operation: the jobs, the people, the sites, the outcomes, the relationships between them. The model does not change between integrations. Whether you run one FMS or several, the intelligence layer speaks one language and maintains one consistent picture of the business. Connects structure, meaning, and change. VH3 AI maintains a connected operating picture of the business using four capabilities working together. Relationship mapping links every job to its engineer, site, customer, outcome, and history, traversable in any direction. Meaning-based search indexes fault descriptions, job notes, and worksheet answers so similar history is findable even when engineers described the same fault differently. Structured job enrichment holds the classified record produced once at ingest and read by every downstream agent, report, and automation. Continuous monitoring watches the same layer for repeat visits, SLA drift, dormant customers, stale relationships, and emerging risk. Any question that crosses more than one of these, and most real operational questions do, draws from all four. Keeps the picture current. Data flows in continuously. New jobs are enriched as they arrive. Entity resolution handles inconsistent names, changing site relationships, renamed job types, stale contacts, and source data written by different people at different times. When a customer hierarchy changes, a site relationship is corrected, or a job type is renamed, the intelligence layer updates the shared operating picture rather than forking another stale view. The intelligence compounds with every new record and stays current as the operation changes. The result is a persistent, reliable, always-current picture of the business, context and understanding that every team, tool, and agent in the organisation can draw from simultaneously.

​

Work that moves while you are doing other things

The platform runs continuously, watching for patterns without waiting to be asked. Sentinels watch the operation 24/7 against the graph, with near-zero AI cost at detection. When a pattern crosses a threshold, the platform can open a case, link the relevant jobs and evidence, ask Connie for a draft brief, and route it to the team that owns the customer or region. By the time a coordinator next opens their queue, the work is queued with context. That loop, sentinels, cases, teams, and Connie working together, is how VH3 AI turns continuous intelligence into autonomous follow-through. The operator’s job is to steer and verify, not to chase the platform.

​

Why this architecture matters now

The AI infrastructure market is running into a problem that anyone who has deployed agents at real scale will recognise. Agents built on classic retrieval, semantic search over raw records, answer from the closest chunks, work in a demo. They struggle when they need to do real operational work: cross-referencing history, synthesising patterns across hundreds of thousands of jobs, producing reliable answers under conditions the chatbot era was never designed for. We know this because we lived it. VH3 AI had production AI agents running against real operations by late 2024. Processing hundreds of thousands of jobs across multiple large clients made the limits of that approach visible in ways that a pilot never would. Over that period and into early 2025, it became clear that what field service agents actually need is a maintained operating context: assembled, resolved, current, and scoped to the work at hand. That is what the intelligence layer provides. Four connected capabilities, relationship mapping, meaning-based search, structured records, and continuous monitoring, combined into a synthesis layer that agents read directly. VH3 AI was built for production field service scale, not demos. Read how the intelligence layer works →

​

One foundation. Every consumer.

The line between application and consumer is collapsing. A team might run a shared dashboard today, a custom internal tool next quarter, a lightweight agent-powered interface the quarter after that. Businesses are building more of their own software, spinning up purpose-built surfaces for specific teams, and treating the intelligence layer as the shared foundation underneath all of it. VH3 AI is designed for that world. Whatever your team builds on top of it, they are all drawing from the same foundation. The same enriched, connected, reliable data. Every report, briefing, automation, custom app, and AI agent sees the same operational picture. Nothing diverges. Nothing goes stale. To make building on top of this practical from day one, VH3 AI ships with authentication and user management built in, 100+ workflow automation templates, and detailed guides for connecting AI coding tools and agents directly to the intelligence layer. You do not have to build the scaffolding. You start from working infrastructure.

​

AI costs should work like a utility

Most AI tools in this market hide their costs. The vendor buys tokens from a model provider, marks them up, and buries the difference inside a seat fee or a platform fee. You never see the line item. You never know what you are actually paying for. We take a different position. AI consumption should be transparent, predictable, and proportional to what you actually use, the same way electricity or bandwidth works. The platform fee covers everything the intelligence layer does internally: enrichment, entity resolution, relationship mapping, continuous monitoring, goal and rules management, third-party system context, and all the AI built into the platform’s own tooling. That is included. There are no per-seat licenses. Pricing is based on job volume and a small number of capability tiers, because the value of the platform scales with the operation, not with headcount. The variable part is agentic consumption. When you use Connie or any of the AI agents, those calls pass through your own model provider key. You see the exact cost of every conversation. You choose which model to use. You change it whenever you want. No margin in the middle, no opaque bundle hiding the spend. The platform also gets more efficient as it scales. Advanced caching and pre-computation mean the intelligence is prepared before it is needed. A hundred people asking questions from the same foundation costs less per query than ten people asking questions from a system that rebuilds context on every call. Your costs go down as your team goes up.

​

Freedom, not obligations

The industry has a habit of locking operational data inside long contracts, making it difficult to export, and building switching costs into the product. VH3 AI takes a different position. No long-term contracts after the initial term. No charges for seats that are not being used. No exports gated behind support tickets. If you choose to leave, your enriched operational data comes with you. The intelligence belongs to your organisation. We keep customers because the platform earns it. The intelligence you build is yours: query it via the API, consume it through automations, connect it to your own AI models, or build your own applications directly on top of it. Dedicated, isolated infrastructure is available on Enterprise plans.

​

What the API gives you

The VH3 AI API is the single point of access to everything the intelligence layer produces:

​

How it works

​

The operating knowledge that stays with the business

Field service businesses lose institutional knowledge constantly. An engineer retires and takes thirty years of fault patterns with them. A contracts manager leaves and the context behind every difficult client relationship goes with them. A new joiner spends their first six months trying to piece together how the operation works from conversations, inboxes, and tacit knowledge. VH3 AI changes that equation. Because everything the business does flows into the intelligence layer, every job, every outcome, every pattern, every relationship, that knowledge becomes part of the maintained operational picture. It compounds over time and is available to everyone who needs it, at the moment they need it. A new engineer gets a pre-visit briefing that includes every fault ever seen at that site, what fixed it, and who attended. A new ops manager can ask natural language questions about how the operation has run over the past three years and get cited, data-backed answers. Someone onboarding into an account management role can pull a full history of every customer relationship, communication pattern, and outstanding risk in minutes rather than months. The platform supports onboarding, offboarding, and upskilling as first-class functions of the intelligence layer. People come and go. The operational knowledge stays.

​

Supported FMS platforms

VH3 AI ingests and normalises data regardless of which FMS sits underneath. The intelligence layer speaks one language. The source system does not matter. Live today: BigChange, full ingestion, polling, discovery, enrichment, and entity resolution. Roadmap: Joblogic, Simpro, Jobber, Uptick, ServiceNow, Commusoft, and others. Multi-FMS ingestion into a single intelligence layer is supported for organisations running more than one system.

​

Next steps