Skip to main content
Internal agents are AI agents that work for your team instead of talking to your customers by default. They run operational work behind the scenes: checking arrivals, triaging tasks, summarizing escalations, reacting to PMS events, answering teammates in Slack, or calling your other systems. An internal agent doesn’t own an inbox. It starts when one of its triggers fires, reasons about the job you gave it, uses the tools you enabled, and then finishes, posts a result, or hands work to another agent.

Internal agents, customer agents and workflows

Use a workflow when something should happen the same way every time. Use an internal agent when the right action depends on judgment, or when there are too many cases to list in advance. For example, a workflow can react to “cleaning status changed”, but deciding which guest to tell, and whether to tell them at all, is a job for an agent.

What an internal agent can do

  • Read your workspace. Look up reservations, contacts, conversations, tasks, listings and Knowledge through the tools you enable.
  • Act. Send messages, update records, and call connected integrations, MCP servers, custom tools and AI-triggered workflows, depending on the tools you enable.
  • Follow your process. Use Skills for repeatable procedures and guardrails for rules it must always follow.
  • Delegate. Hand parts of a job to subagents that run in parallel.
  • Talk with your team. Answer in a chat in Conduit, or in Slack and Microsoft Teams when you turn those on.

What starts a run

The first four triggers each have a page under Runs on in the agent’s sidebar. Teammates can also start the agent directly. An agent can have several triggers at once. Every run, whatever started it, appears in the agent’s Activity tab.

How a run works

1

A trigger fires

Conduit starts a run and passes the agent what it needs: the message, the event payload, the webhook body, or the task you wrote for the schedule.
2

The agent plans

The agent reads its instructions, guardrails and Skills, then decides what to do with this input.
3

The agent uses tools

The agent looks things up and takes actions with the tools enabled on its Tools tab. It can delegate parts of the job to subagents.
4

The run ends

The agent finishes its work. In a chat, Slack or Teams it answers the person who asked. On a message trigger set to Reply, Conduit sends its answer back in the same conversation.
When AI is paused on a conversation or contact, message triggers set to Reply don’t run there. Listen only agents keep running. Message triggers also skip messages Conduit marks as spam.

Agent status

Each internal agent is either Active or Inactive. Set it under Agent status in the status menu in the agent’s top bar, then select Save. See Turn the agent on or off. Turning a single trigger off, such as one schedule or the webhook, leaves the agent’s other triggers running.

Credits

Internal agent runs consume credits. Each run has a dynamic cost based on the work the agent does, so there is no flat rate per run. Chats with an internal agent are runs too, and they also consume credits. To see what each internal agent has used, go to Settings > Billing and expand Internal Agents for a per-agent breakdown. Open an agent to see its credits and runs for the current billing cycle. See Credits for how credits work across Conduit.

Next steps

Create and configure

Create an internal agent and set its instructions, tools, Skills and settings.

Chat and activity

Talk to the agent, run it on demand, and review what it did.

Use cases

Internal agents other teams have built.

Subagents

Split a large job across specialized agents.