How it works
1
Describe what you want
In natural language: “Update our refund policy,” “Build a Linear bug-report flow,” “Connect our internal admin panel so the agent can look up customers.”
2
The Internal Agent builds it
It asks clarifying questions where needed, then builds the flow: the policies, knowledge, and tool connections the agent needs.
3
Review the draft
Every change is staged as a pending action for your approval. See Release.
What you build
- Configurations: everything you build lives in your Customer Agent’s configurations - channels, tools, memory, knowledge snippets, and web pages. See Customer agent.
- Guardrails: when the agent escalates to a human, deterministic checks before a tool can run, and human approval behind sensitive actions. See Guardrails.
- Connections: the tools your agents act in - the Customer Agent through the scoped tools built on them, the Internal Agent directly in tasks. If a tool has an API, you can connect it just by chatting. See Connections.
- Channels: where customers reach you - email, live chat, and Slack through your ticketing system, or the API. See Channels.
Next: test the change before it ships. See Test.