Connections

Three ways to connect to your systems

Our agents complete requests in your own systems: your CRM, ERP, case management or sector software. To do that, they connect in one of three ways, always in this order.

Book a demo See the three ways

The standard

MCP: the same standard as Claude and ChatGPT

Our agents work with systems through MCP, the Model Context Protocol. It is the open standard AI assistants such as Claude and ChatGPT use to connect to tools and data. What works for them works for your agents.

What is MCP?

An MCP server describes what a system can do: which data you can look up and which actions you can perform. An AI agent that connects to that server uses the system safely and under control, without custom work for every action.

“Through the API where possible, through the screen where necessary.”

1 · First choice

Your vendor's MCP server

More and more vendors offer a ready-made MCP server for their software. If one exists for your system, we connect to it right away: the fastest route to a reliable connection.

How it works

The vendor maintains the server, so it keeps up with updates of the system.
The same server Claude or ChatGPT use to work with the system.
Konversaitional connects to it and decides per agent which actions are allowed.
No development work on your side.

Ask your vendor whether the MCP server exists, whether it is a paid service and whether it needs to be activated.

2 · On request

A custom MCP server for your own back end

If your system has no MCP server, Konversaitional builds one: on the system's APIs, or through direct access, for example to the database. That makes your own back-end systems safely accessible to our AI agents.

What you get

A server that exposes exactly the data and actions your agents need, and nothing more.
Read and write: look up, register, change, follow up.
Access and permissions are fixed in the server, so an agent never steps outside its limits.
One server serves all your agents, for Contact and for Employees.

A custom MCP server is quoted per project. The price depends on what your system allows and on how reusable the server is.

3 · Fallback

A virtual browser session

If there is no API and no direct access, the agent works in the application the way your own employees do: through the screen, in a virtual browser session.

How it works

The agent logs in, navigates and performs the same actions as an employee.
Suited to older packages and sector software without a usable API.
This connection also runs through MCP, so your agents work with it in the same way.
Only when nothing else is possible: an API stays faster and more robust.

A connection through a browser session is quoted per project, like a custom MCP server.

In every case

MCP stays the standard

Whichever way we choose, your agents work with every system in the same, controlled way.

One way of working
Whether the connection comes from your vendor, is built to measure or runs through the screen: for your agents it is always an MCP server. Roles, permissions and the audit trail work the same everywhere.
Connect once, use twice
The systems you use to help customers are usually the same ones your employees work in. One connection serves both Konversaitional Contact and Konversaitional Employees.

Which way fits your systems is something we look at together in the demo. And how Konversaitional fits the rest of your organisation: your brand, your telephony and your own APIs.

Integration in your organisation