Connecting the Chrome extension to AI: the assistant works along in the employee's browser
Yes. The IntraGPT Agent Connector is a Chrome extension that links an employee's browser to the assistant. The assistant can then open a page, click through, fill something in and read along on that employee's behalf, inside the sessions they are already signed in to. That puts it in places behind a login where a browser on our own server never gets.
What the extension makes possible
Linking with a personal token
The employee installs the extension and links it with a token that belongs to them. From then on their browser reports itself as a connected device and the assistant can work along in it.
Working in existing sessions
The assistant uses the browser the employee is already signed in to. Systems behind a login that would otherwise stay out of reach come within reach, without a password being stored anywhere.
Working along in the right tab
Opening a page, clicking through, filling in a form, making a choice, submitting and going back if it went wrong. The assistant works in the tab that belongs to the task, not in everything that happens to be open.
Reading what only exists on screen
An overview that cannot be exported, the assistant can simply read and summarise. Capturing what is on screen at that moment is possible too, for instance to pass it on.
Seeing whether the browser is still there
The admin shows which devices are connected and when they were last seen, and the extension icon is supposed to be green. If the browser does not respond, the assistant is told that it is probably closed or that the extension is offline.
Daily work the extension takes over
Customer service
- Situation
- An agent has to look up a shipment status mid-call in the carrier's portal, where only they have an account.
- What the agent does
- The assistant works in their own tab, looks up the tracking number and reads the status.
- Result
- The customer hears the answer in the same call, without the agent having to drop out of it.
E-commerce
- Situation
- Stock levels from a dropship supplier only exist in that supplier's own back office, behind a personal login.
- What the agent does
- The assistant opens that screen in the employee's tab and reads the quantities per article.
- Result
- An up-to-date overview in the chat, without an extra account and without a request to the supplier.
Back office
- Situation
- Every Monday the same five screens in an ageing intranet have to be checked.
- What the agent does
- The assistant walks through them in order, takes the requested lines from each screen and lists them together.
- Result
- A quarter of an hour of work becomes a minute, with the employee reading along in their own browser.
Purchasing
- Situation
- A quote has to be submitted in a client's portal where the fields are the same every time.
- What the agent does
- The assistant fills in the form in the employee's tab and leaves it ready; the employee submits it.
- Result
- Less retyping and a final check by the person who is accountable for it.
Installing, linking and working
-
1
Install and link
The employee installs the extension in their own Chrome and links it with their personal token. Nothing more is needed to get going.
-
2
Switch it on per organisation
This channel is on or off per organisation. If it is off, no device can connect at all and the option simply does not exist.
-
3
What the assistant sees
Only the tab it is working in, and within it only what the employee is allowed to see. Its permissions are that employee's permissions.
-
4
What gets recorded
What is opened and done on request appears in the conversation and is recorded. The admin also shows which devices are connected.
Permissions, visibility and where it stops
The extension gives the assistant no new permissions. It works inside one employee's browser and therefore gets exactly as far as that employee does.
Where the data lives: Nederland of de EU
No more than the employee may
The assistant works in the signed-in employee's sessions. A system that employee has no access to stays closed to the assistant as well, because nothing is bypassed.
A token you withdraw
The device reports itself with a personal token. Withdraw it and the link is gone and the extension does nothing more. Useful when an employee leaves or a laptop goes missing.
Enabled per organisation
If an organisation does not want this way of working, the channel stays off and nobody can connect. It is a deliberate choice, not a default setting.
Visible to the person it concerns
The employee sees on their own screen what is happening, because it is their browser and their tab. Nothing runs in the background that they cannot follow, and what happens is recorded.
Practical questions about the Chrome extension
Does the assistant get onto sites behind a login?
Yes, that is what this channel is for. The assistant works in the employee's browser and therefore in the sessions they are already signed in to. No password is stored and nothing is bypassed: if the employee cannot get in, neither can the assistant.
Does IntraGPT work with a Chrome extension?
Yes. You install the IntraGPT Agent Connector in Chrome and link it with a personal token. After that the assistant can work along in the matching tab. The channel is on or off per organisation, so you decide yourself whether it is available.
What if I close Chrome?
Then there is no browser left to work in. If the extension does not respond, the assistant is told the browser is probably closed or the extension is offline, and it does not keep pushing blindly. The admin shows when the device was last seen, so an administrator can see straight away what is going on.
Does the assistant see all my tabs?
No. It works in the tab that belongs to the task, not in everything that happens to be open. What it reads, it reads on request, and it ends up in the conversation the employee is sitting in themselves. That also makes it easy for that employee to follow.
When do I choose the extension and when the browser agent?
Take the extension when the work sits in systems the employee is personally signed in to and where nobody wants a password kept centrally. Take the browser agent for the public web or for a portal whose sign-in details may be stored, because that one runs its own browser and starts every session blank.
Can I connect the Chrome extension to ChatGPT?
ChatGPT does not work along in your employee's browser and knows nothing of the systems they are signed in to. With IntraGPT the extension is a channel you enable per organisation, it works with a personal token per employee, and its use is recorded. On top of that the model runs on our own server in the Netherlands.
Does it also work in Edge or Firefox?
The extension is built and tested for Chrome. If your organisation works with a different browser as standard, mention it in the call and we will look at what that needs before anything is rolled out. What stays true in any case is that the assistant gets no further than the employee does.
What does the Chrome extension cost?
The extension is part of the project we run together. What drives the work is how many employees will use it, which systems are involved and whether things may be filled in and submitted as well. A thirty minute call makes that concrete.
How long does setup take?
Enabling the channel and linking a first employee takes half an hour. After that it is a matter of installing and pasting the token per employee. The real time goes into agreeing which systems may be used this way and who decides that.