EN
Contact
office@version2.hr+385 99 561 7706For AI

AI Integration

We put AI to work inside the software you already run.

We connect an assistant or an automation to your documents, enquiries and business software. Together we agree what it may read and do, who reviews its work and how it passes a question to a person, and then we test it on your own cases.

It’s a reply desk we built, working from our own documents. It reads only what its role may open, drafts the reply to a client’s question and shows where the answer came from, so the person who sends it can check it first.

Reply desk

Role: client support

Built by Version2

1. A client asks
2. It reads only what this role may read

Draft, ready for review

3. Draft reply

Your Basic plan covers security updates, uptime monitoring and a monthly health check, with two hours of support a month. The monitoring is what tells us the site is down, and putting it back up comes out of those hours.

Basic care includes security updates, uptime monitoring and a monthly health check, with two hours of support a month. Standard care adds content updates, bug fixes and performance monitoring, with five hours a month.

SourceCare plans, what each one covers, section 2.1
Where a person steps in
Support reads the draft and sends it.

Read 3 of 3 permitted documents, matched section 2.1 of Care plans, what each one covers.

What we connect

A first one is usually one of these four jobs.

Each one reads something you already have and prepares one thing, and it only acts on its own where you’ve decided it may.

A support queue with six conversations, two with a prepared draft, one waiting for approval and one passed to a person.
Support replies prepared from approved documents

01

Answers from your own documents

Questions from customers or from your own team, answered out of approved documents, as a draft a person reads and sends.

  • Reads documents
  • Writes a draft
  • A person sends

When a job should run end to end, with a person handling only the exceptions, that’s what an agent does. See AI agents

Limits

Most of the risk is in what it reads.

The system needs an agreed answer for each of these, and we settle them with you before the build starts.

  1. The documents don’t answer the question.

    Who owns the website once the project is finished?

    Project terms and handoverOperations, updated 28 August 2026

    Passed to a person

    The documents this role may read don’t answer this question.

    Where a person steps in
    A person answers the client.

  2. The answer sits outside this person’s access.

    What do you pay for the server our site runs on?

    What we pay for hosting and licencesFinance only, Outside this role’s access

    Passed to a person

    The documents this role may read don’t answer this question.

    Where a person steps in
    A person answers the client.

  3. A document is out of date.

    Are care plan prices changing in January?

    Care plans, what each one coversSupport, updated 3 September 2026

    Held for the document owner

    The matching section is being updated by its owner, so no reply quotes it.

    Where a person steps in
    The document owner answers the client.

The work isn’t written down anywhere.

If the rule only lives in one person’s head, there’s nothing to connect to yet. Writing it down is the first job, and now and then it turns out a form or a rule in the software you already have does what you were after.

Responsibility

Each step of a reply has someone responsible for it.

  1. Your document owner

    The source

    Keeps the approved information current and marks a section for review when it changes.

    Support, updated 3 September 2026

    Care plans, what each one covers

    2.1Basic care includes security updates, uptime monitoring and a monthly health check, with two hours of support a month. Standard care adds content updates, bug fixes and performance monitoring, with five hours a month.

  2. Version2

    The checks

    Tests the agreed cases before the connection is used, and again after every change.

    Agreed cases

    • Our site went down on a Sunday. What does our care plan cover?Draft, ready for review
    • Can we split the invoice, or do we pay it all up front?Draft, needs approval
    • Who owns the website once the project is finished?Draft, ready for review
    • What do you pay for the server our site runs on?Passed to a person
    • Are care plan prices changing in January?Held for the document owner

  3. The assistant

    The draft

    Prepares the reply from permitted documents, or passes the question on.

    Draft, ready for review

    Your Basic plan covers security updates, uptime monitoring and a monthly health check, with two hours of support a month. The monitoring is what tells us the site is down, and putting it back up comes out of those hours.

    SourceCare plans, what each one covers, section 2.1

  4. Your reviewer

    The approval

    Reads what needs approval before it reaches a customer.

    Support reads the draft and sends it.

Questions

What people ask before they connect anything.

Do you need access to everything we have?

No. One source to begin with, read-only wherever that’s possible, and only what the job needs. Access grows when the job grows, and you agree to it each time.

Our documents are a mess. Is that a problem?

It’s the usual starting point, and tidying them is worth doing whether or not you connect anything. We look at what exists in the first week and say plainly what has to be sorted before a connection is worth building.

Will it send anything to a customer on its own?

Only when you’ve decided it should. The default is a draft that a person reads and sends, and case by case you tell us which replies can go out on their own and which wait for approval.

Can it work with the software we already use?

Usually. Anything with a documented way in, and quite a lot without one. When a system has no way in at all, you’ll hear it from us in the first week.

Where does our information go?

The model runs as a service, so a question and the passages it needs are sent to it. We agree with you which provider that is and what it may keep before anything is connected. If the information can’t leave your systems at all, it needs a private build that runs where you decide. Private AI

What does it cost to run?

Model usage, billed at what it costs, and care if you want it. We work the usage out from your own volumes and put the figure in the written recommendation, before you commit to anything.

Scope and price

We start by looking at one workflow.

We examine one workflow and the data it depends on, then write down the proposed connection, its limits and the next step. That week costs €490 and comes off the build if you go ahead.

The same written recommendation can conclude that the connection isn’t ready to build.

Get an integration quote Free 10-minute call

Workflow IntegrationRecommended first step

One data source and one assistant or automation, with permissions set by role. We test it on your real cases before handover.

from €1,900per project, 2 to 3 weeks

Multi-System Integration

Up to three connected systems, roles and an audit trail, monitoring, and a monthly review for the first three months.

from €4,900per project, 4 to 6 weeks

The build is a one-off. Model usage is billed at cost, and care after handover is €190 a month when you want it.

ContactWhatsApp