Agents

An agent for every workflow you want to delegate

An agent is a persona of DeepEngine with its own instructions, room and memory. In the product it is called a bot. Provision one per workflow and define its reach, its autonomy and its audience.

DeepEngine ships with the workspace. You provision the rest.

  • DeepEngine

    The agent every workspace starts with. It answers in channels and in private, and delegates work to your agents.

    Built in
  • Scout

    Researches and completes work on websites.

    BrowserAsk first
  • Atlas

    Answers from the team’s docs and keeps them current.

    DocsAccept edits
  • Frontdesk

    Triages new tickets, finds the likely cause and drafts the reply.

    ZendeskAsk first
  • Nightwatch

    Investigates monitoring alerts and remediates what policy allows.

    WorkersAuto
  • Digest

    Compiles last week’s decisions and open items every Monday.

    LinearSchedule

Five examples. The product has no ready-made agents: you define each one in a few sentences.

The anatomy of an agent

Purpose and instructions

One sentence states what the agent is for. Its instructions define how it works, and they apply on top of your organization’s system prompt in every run.

A dedicated room

Every message in an agent’s room goes to the agent, mentioned or not, and each request is a thread of its own. Anywhere else you address it with @, and DeepEngine can delegate work to it.

Persistent memory

An agent retains facts from its conversations, isolated from every other room. You can inspect what it remembers. Switch learning on, and what recurs across its threads becomes a page of its own.

Autonomy levels

Ask first, accept edits, or auto. The level covers what no rule decides. Reading never waits, your rules always apply, and full access is not on offer.

Access control

Everyone in the organization, or only the people you pick. With chosen members the room is private and nobody else sees the agent.

Connected capabilities

A dedicated browser, the services you connect for it, and the workers you grant it. Switch on alerts for a worker, and its monitoring alerts open a thread in the agent’s room.

Four ways to engage an agent

Write in its room

The agent answers every message there. Each request becomes a thread, so ten people can ask at once.

Address it with @

In any channel or thread it can see. It reads the conversation so far and answers where the work is.

Call itBeta

Talk instead of typing, on the web or on mobile. Each agent can have its own language for calls.

Trigger it automatically

An automation, an alert from a worker or a ticket assigned to it starts the work. You hear about it when it matters.

Put your first agent into production

Book a demo and follow an agent from the first request to completed, audited work.