Skip to main content
Customer-facing agents (called customer agents in Conduit) answer your contacts: guests, leads, customers and anyone else who messages you. Each one listens to one or more inboxes and replies to the messages that arrive there, using its instructions, Knowledge, Skills and tools. Use customer-facing agents for support, sales, guest messaging, lead intake and any other job where the AI talks directly to a contact. For work that happens behind the scenes, use an internal agent instead.

How they differ from internal agents

Create a customer-facing agent

1

Open Agents

Go to Agents in the workspace sidebar.
2

Add a customer agent

Select Add agent > Create customer agent. Conduit also creates an inbox for the agent, so inbound conversations for that contact type can be routed to it.
3

Configure it

Fill in the Persona, Tools, Skills and Settings tabs. See Agents for what each tab holds.

Inbox triggers

A customer-facing agent runs when a message arrives in an inbox it’s attached to. The agent’s sidebar lists them under Inbox triggers, and warns you when another agent already listens to the same inbox. Messages in the Unmapped inbox don’t trigger agents. If an agent is attached to Unmapped, Conduit flags it so you can remove the trigger or route those messages to another inbox. See Triggers.

Autopilot, Copilot and Inactive

Set how the agent responds from the Agent behavior menu in its top bar. Pick a mode, then select Save.
The Agent behavior menu with Autopilot selected, followed by Copilot and Inactive, above a Save button
Most teams start in Copilot, review proposed replies until they trust the agent, then switch to Autopilot. See Road to autopilot.

Settings that only customer-facing agents have

Because they reply to contacts, customer-facing agents have extra sections on the Settings tab:
  • Escalation rules: what happens when the agent escalates a message.
  • Behavior: language, voice, working hours, reply delay, auto mark-as-done and signature.
See Agent settings. For what the agent already knows about a guest’s stay, see Reservation context.

Test and review

  • Before going live, use Sandbox to simulate conversations with realistic contacts and reservations. See Testing agents.
  • After publishing, open the Activity tab. It lists one row per run with its status, contact, start time and disposition, and lets you open the trace to see the instructions, Knowledge and tools the agent used.
The metrics at the top of Activity show the agent’s Runs, Autopilot rate and Escalations. Filter runs by status, by disposition (such as Resolved, Escalated or No op), or to sandbox runs only. See Understand dispositions for what each disposition means.

Voice agents

Voice agents also talk to contacts, but on phone calls. They’re configured separately because they need phone number routing, voice behavior, transfer rules and call-specific guardrails. See Agents.