Your ticketing system, your customer history and your help articles are connected once in the gateway. After that the team asks in its own words, and nothing reaches a customer without a human saying yes.
One account is fine for one person. The difference shows up when a whole team uses AI, and when somebody asks what it cost or where the data went.
Everyone signs up separately. Nobody knows what it costs, who has access, or what has been shared.
One way in to every model. One login, one invoice, and you can see what is actually happening.
Claude today, something else next year. With Walma you use all of them and switch when it suits you, without redoing the work.
We have done the groundwork: ready-made connections to the tools you already use, with proven skills and instructions, so the team actually gets going instead of just trying it out.
If you want visibility, you get it: everything the agent does is visible, you get feedback on how the work could be better, and you can put a stop to things it should not do.
Walma AI Hub is a layer between your tools and the models. Here is what that means in practice.
IT approves an MCP server once. After that the tool appears for the people who should have it, with the right permissions. Nobody on the team touches an API key.
Claude, GPT, Gemini and the open models all reach the same connections. You pick the model per task instead of locking yourself in, and if you switch next year the tools come along.
When the off-the-shelf tools run out, we build. RAG over your own material, bespoke agent flows, and narrow MCP servers for systems the vendor has not covered, all running inside the same gateway and the same log.
This category is moving fast. Freshdesk and Help Scout ship their own servers, Zendesk chose to build a client instead, and for the rest we build the connection.
The vendor's own server. Switched on and running the same day.
Community-built. We review the tool descriptions and pin the version before approving.
These we build ourselves, as narrow read-only servers in your tenant. Tell us which you need first.
Included in every rollout.
Questions support already asks, minus building a report first.
The gateway runs in your own Azure tenant in an EU region. Every call is logged with user, tool and arguments. That is the answer when your data protection officer asks where the data goes.
Built for European requirements from day one. Details, subprocessors and policies live in our Trust Center.
Open the Trust CenterNot with us by default. Connections are set read-only, so the agent reads tickets, finds the history and drafts replies, but a human sends. If you want automatic replies on simple tickets that can be opened up, as an active decision per tool with approval and a log. A wrong answer to a customer cannot be taken back.
Not through a server of Zendesk's own, because they chose a different route: they are building an MCP client instead, so their product consumes other servers rather than exposing one. Access the other way therefore goes through an app or a community-built server, which we review before approving.
Freshdesk has an official Freshworks server, generally available since 10 September 2026, and Help Scout and Intercom have their own. Gorgias is in open beta. Zoho Desk and LiveAgent are available through community and aggregator routes. For Front, Kustomer and Dixa we build the connection ourselves.
Yes, and it works. Intercom runs a separate server for EU-hosted workspaces, apart from the US one, so tickets are read where they already live. The server is mostly read-only; its write tools add internal notes and update help articles, and nothing is sent to the customer. The gateway runs in your own Azure tenant in an EU region. Australian-hosted workspaces are not supported by Intercom yet.
Only what you open up, and only for the people who should see it. Permissions are set per role in the gateway. Bear in mind that ticket text is content written by someone outside your organisation, which makes it a possible route in for prompt injection. That is why we run read-only sessions for that kind of data and inspect tool results at the gateway.
Twenty minutes with an engineer. We connect your ticketing system, read-only, and show what the team can ask the next day.
