Skip to main content

​
Purpose

An AI Employee is a named role your team works with day to day. It is not a chatbot, not a workflow and not a raw agent. Each one does one kind of work, within your permissions, and brings anything consequential to you before it happens.
Agents are the building blocks. AI Employees are the workforce. Agents are pre-built by Exterview. AI Employees are the roles that put them to work for your organization.

​
The AI Employees in Exterview

Available. Five AI Employees work in Exterview today. You find them in Settings → Setup → Operations → AI Employees, with what each one does and how many tools it can use. You can ask any of them from the Smaya Assistant or from a connected assistant over MCP. Upcoming: asking them from Slack.

​
Handoffs between AI Employees

Available. You do not have to pick the right AI Employee. Ask one, and it hands the work to the colleague whose job it is. The reply names the AI Employee that did the work. A handoff runs as you, with your permissions. Handing work to another AI Employee never widens what can be read or changed.

​
Approval before writes

Available. Creating a role, publishing a job and contacting a candidate always show you an approval card first. Nothing happens until you approve it. Report Specialist and Smaya write nothing at all.
Hiring outcomes stay with people. No AI Employee sets a candidate to hired, rejected or withdrawn. It prepares the evidence and a recommendation. A named person decides.
A handoff runs as you, with your permissions. Report Specialist and Smaya never write.

​
The agent’s role for each job

Available. When you create a job, the Agent Role tab describes the agent’s role for that job and the first message candidates receive. It is the mandate the AI Employees work to for that job, and you edit it like any other part of the job.

​
The ceiling that never moves

Three rules hold for every AI Employee, in every configuration.

Never exceeds its human

An AI Employee can never reach data or take an action the person invoking it could not. Authority is the intersection of the role’s scope and yours, never the sum.

Never decides alone

Outcomes that materially affect a person — hiring, rejection, an offer, a performance judgment — are always made by a named human.

Never acts unrecorded

Every action and every approval is captured and attributed.

​
Where AI Employees are going

Upcoming. Composing your own AI Employees from the Agent Library, each with a full charter:

Mandate and operating window

What the role exists to achieve, the standing goals it is accountable for, and when it is active.

Scope of authority

An explicit allow-list of what it may read and write, bounded by module and data boundary.

Three named owners

A business owner for the outcome, a technical owner for how it runs, and a data steward for what it may see.

A lifecycle, not on and off

Proposed, approved, active, suspended and retired, with the person who drafts a charter never the person who approves it. Suspending one role in one action leaves the others running.
AI Employees that work on a standing goal, without anyone starting the work, come with the agent swarm and are also Upcoming.

​
What this changes commercially

Exterview does not sell headcount subtraction. It sells a supervision ratio: one person oversees a portfolio of AI Employees, each bringing anything outside its remit to the named person responsible. See The Hybrid Workforce.

​
FAQs

No. An agent is a specialized capability, pre-built and reusable. An AI Employee is a named role that puts agents to work. Your teams interact with AI Employees.
It reads and answers freely within your permissions. Creating a role, publishing a job and contacting a candidate always wait for your approval, and nothing adverse is ever decided by an AI Employee.
Not yet. Five AI Employees are Available today. Composing your own from the Agent Library is Upcoming.
Today they work in Exterview. As Gradientflo arrives, post-hire agents become available to AI Employees alongside talent agents.