nessie

Agents that use a browser like anyone else

Sign an account in once, and agents work in any website your business uses, connector or not.

Most of the software your business runs on was never built for agents. The booking system, the supplier’s ordering portal, the inventory system, the local government’s bid portal, the property portal, your company’s Facebook and Instagram: none of them has a connector, and most never will. Nessie’s agents do not need one. They use a browser, like anyone else on your team.

A real browser, in the cloud or on your computer

Each team has a browser in the cloud that its agents share, and each agent keeps its own tabs in it. When a job needs something that only works from your office — a system on your own network, a website that only trusts your address — the agent uses a browser on a computer of yours instead, through the Nessie app installed there.

Sign it in once

  • A person signs in, not the agent. You open the team’s browser from your own conversation, sign in to the account the way you always do, and confirm the sign-in is shared with the team. From then on, agents with browser access work in that account.
  • Passwords stay with people. When a page asks for a password or a code, it goes in through a secure entry card. The agent never sees it, and it never appears in a conversation.
  • Personal stays personal. Your own accounts — your personal email, your bank — are a personal sign-in, used only in your private conversation with your own agents. Nobody else on the team can reach them.
  • One switch per agent. Browser access is a switch on the agent’s Access tab. An agent without it never opens the browser.

Watch it, take over, hand it back

You can watch any agent’s browser while it works, take control at any moment, and hand it back. Before it moves to a website it was not asked to use, it asks. Screenshots and files it downloads land in Documents, where the team can see them. The work is in the channel like any other: the agent says what it did, a person corrects it, and it does it that way from then on.

What teams use it for

  • Bookings. Taking, moving and canceling bookings in the booking system you already pay for.
  • Inventory and suppliers. Reading what is left in the inventory system and drafting the order in the supplier’s portal for a person to confirm.
  • Social media. Posting to the company’s Facebook, Instagram or TikTok and answering comments, signed in to the business account.
  • Research. Tell an agent to find every local government in the country and it loads them all, maps each one’s bid portal, and checks them on the schedule you set.
  • Everything with a login and no API. Property portals, government services, accounting websites, the old admin panel nobody wants to touch.

When there is a connector

A browser is slower than a connector, and a website can change under it. Where a system offers a proper connection — Google Workspace, Xero, HubSpot, or any app in the App Store — agents use that instead, and keep the browser for everything else. Inside your own software, a digital employee works on the page beside the person using it.

See it at work in a restaurant, an escape room, an architecture studio or a shop.

Request an invitation