Running it safely
The parts your security team asks about.
Separate environments, scoped API keys, and credentials that are stored once and referenced by name, never pasted into a flow.
Capability
11 / 11
Projects, secrets & keys
Projects as environments
Keep staging and production apart, with their own agents, tools, numbers, and members. Cloning an agent between projects moves the work without recreating every node and tool by hand.
Secrets, referenced not pasted
API credentials are stored once and referenced by name wherever a tool needs them. They do not live in flow configuration, and they do not end up in a transcript.
Scoped programmatic access
API keys are issued per project so an integration reaches exactly what it needs. Agents, tools, and workflows can all be managed through the API for teams that would rather work in code than in a console.
More capabilities
Connecting your systems
Tools & integrations
Call your own REST endpoints, connect an MCP server, and map responses into the conversation, with per-node overrides and a test run before anything goes live.
Read →After the call
Monitoring & outcomes
Full call history with transcripts and recordings, plus outcome definitions and dashboards built on the results that matter to your business.
Read →Designing the conversation
Flow Builder
Design the call as a graph: conversation, tool, router, transfer, and end-call nodes, connected by conditions you define rather than hope the model infers.
Read →


