Connect Loket.nl to AI: staff questions answered and leave actually requested
Loket.nl can be connected to AI. The assistant answers questions about employees, departments and payslips from your own Loket environment, and it can file a leave request that lands with the manager for approval in the usual way. That last part makes this connector special: it is the only HR connector in the catalogue that writes anything back. So it happens only on an explicit request, and only once the dates and the type of leave have been confirmed.
What the assistant can draw from Loket.nl
Questions about employees
The assistant looks up employees as they appear in Loket and can limit itself to the people currently employed. Questions such as who has just joined or who belongs to a team are handled in the conversation, without anyone opening the administration.
How the departments are set out
The departments come through exactly as they are recorded in Loket. That lets the assistant answer a question about a team without anyone having to dig out the org chart first.
Payslips per period
A payslip is always requested for one employee and one period. That is deliberately narrow: there is no way to pull the slips for the whole organisation in one go.
Filing a leave request
The assistant can file a leave request with the type of leave, the first and last day and a short note. That is a genuine request that reaches a manager, so it has the details confirmed first.
Tied to your own environment
The connector hangs on the Loket environment you point it at. If an accounting office serves several employers, those environments stay strictly apart.
Where payroll administration gets some breathing room
HR
- Situation
- The HR adviser gets short questions all day: who works where, who has just started, who has left.
- What the agent does
- The assistant looks it up in Loket and links the employee to the right department.
- Result
- Those loose questions get settled in the conversation and time is left for the work that needs a human.
Payroll
- Situation
- An employee wonders whether the payslip for a given month is ready and whether the travel allowance is on it.
- What the agent does
- The assistant looks at the slip for that period for that one employee and describes what it shows.
- Result
- No email to payroll and no waiting, while the data never leaves your own environment.
Team leadership
- Situation
- Someone wants two weeks off in the summer and can never remember where the request has to be filed.
- What the agent does
- The assistant first confirms the type of leave and the first and last day, then files the request.
- Result
- The request sits in the usual approval flow with the manager, without anything being arranged outside Loket.
Healthcare
- Situation
- A scheduler needs to know quickly who is employed at a location before the staffing is finalised.
- What the agent does
- The assistant lists the people currently employed, grouped by department.
- Result
- The roster is finished sooner and nobody calls a colleague who left last month.
Accounting office
- Situation
- An office runs payroll for several employers and gets the same standard questions from every client.
- What the agent does
- Each employer has its own connector pointing at the matching Loket environment.
- Result
- Every client gets an answer from their own administration, with no way for another employer's data to slip in.
From switching on to the first question
-
1
Switching the connector on
Loket.nl is ready and waiting in IntraGPT. You authorise the access inside Loket itself and point out the environment the assistant may work with.
-
2
Rights and roles
You decide which roles see the HR assistant. Filing leave requests is a separate choice you can enable on its own or leave switched off.
-
3
What the assistant does and does not see
It works per employee and per period and shares only what the person asking may view. It does not start talking about colleagues on its own initiative.
-
4
What gets recorded
Every question and every filed request goes into the log. Afterwards you can see when something was submitted and at whose request.
Pay and absence are special categories of data
A payroll administration holds data not everyone should be able to reach, and sometimes absence information as well. The connector is arranged tightly around that.
Where the data lives: Nederland of de EU
Access stays yours
You grant the access yourself and can withdraw it at any moment. From then on the assistant sees nothing from Loket any more.
Only what the person asking may see
The assistant answers personal questions about the user's own details. Colleagues' payslips do not come up unasked, not even when the question is put in general terms.
Requests stay traceable
Because this is the only HR connector that can submit something, the log counts double here. For each leave request you can see which employee and which days it concerned.
On a dedicated server
The model runs on our own server in the Netherlands. Names, contracts and pay details are not sent to an American model provider and are never used for training.
Questions about the Loket.nl connector
Can I connect Loket.nl to ChatGPT?
ChatGPT has no connection to Loket.nl, and putting pay data into a public chatbot is exactly what you want to avoid. IntraGPT works like a chat, but with a connector fixed to your own environment that fetches only what the question needs and records everything.
Does IntraGPT work with Loket.nl?
Yes. Loket.nl is one of the connectors ready to go in IntraGPT, covering questions about employees, departments and payslips and the filing of a leave request. It is a working integration already in use at clients.
Can the assistant really request leave, or does it only make a draft?
It files a genuine request. It enters the same approval flow as a request someone fills in inside Loket themselves and is assessed by the manager. That is why the assistant first confirms the type of leave and the days, and never acts on its own initiative. This is the only HR connector in the catalogue that writes anything back; the other HR connectors only read.
Does the assistant see a colleague's payslip?
No. A payslip is always requested for one employee and one period, and the assistant shares only what the person asking may view. There is no way to obtain an overview of the entire payroll administration, and the roles in IntraGPT decide who can use the HR assistant at all.
Our payroll runs through an accounting office, does it still work?
Yes, and with Loket.nl that is the rule rather than the exception. The employer or the office authorises access to the environment in question. If the office serves several employers, each employer gets its own connector, so the administrations stay separated.
Can we withdraw the connector again?
Yes, at any moment and without consulting us. You remove the permission inside Loket and the assistant can no longer retrieve anything from it. Ongoing conversations lose nothing, but new personnel questions simply go unanswered from then on.
What does a Loket.nl connector cost?
Connecting is part of the project we run together. What drives the work is the number of Loket environments, whether filing leave requests is allowed and how finely the roles have to be arranged. We make that concrete in a short call.
How long does setup take?
Once the access has been authorised, the connection stands within minutes. The lead time usually sits elsewhere: agreeing internally who may use the HR assistant, and establishing with the works council or the privacy officer which details may be shown.