The purpose
Goal, tone, instructions and handoff criteria guide how it works.
Define each agent's role and connect information and tools. Automate customer service, system queries and tasks, with team approval when needed.
Explore an agent's roles ↓An agent uses the available context to interpret a request and decide how to respond. When it has the necessary tools and access, it can take part in the actions that move the journey forward.
Design starts with the work: who it supports, what information it can access and how far it can go. Its actions make sense within that responsibility.
Goal, tone, instructions and handoff criteria guide how it works.
The conversation and authorized information help understand the request.
Defined actions and access connect the agent to what the operation allows.
Explore the contexts and access level.
The same agent concept meets different kinds of work.
Understand the request, look up the permitted context and help the person move forward.
I need to reschedule my appointment. Is there any time available this week?
I can check availability so you can choose a new time.
Continuity can reuse the conversation history within the configured period. Information from one message helps interpret the next.
This context has limits: session length, available data, and the person's access. The design needs to define when to resume, when to ask, and when to hand off.
A tool provides access to an operation.
Your use must respect your role and permissions.
Find the contact and continue the service with the available data.
Check availability and prepare the next meeting.
Join the conversation through the official channel connected to the operation.
Access the files that the journey makes available and authorizes.
Support summaries, classification and reading of information.
Query and update information according to the composition and access permissions.
Text guidance helps define behavior. Access to actions needs its own controls, configured in the platform and in the journey.
Explore governance in depthRole and access context determine what can be viewed or done.
Select tools and configure the applicable controls. Naming an action should not mean unrestricted access.
Approvals and sensitive actions need a review experience defined by the operations team.
Missing information, uncertainty and failures should be routed onward instead of met with a made-up answer.
A view of agent management
and the start of its setup.
An overview of configured agents, with their tools and configuration status.
Catalisa showcase material · original date not providedConfiguration brings the intent closer to the skills and instructions chosen for the agent. Studio helps structure how it's built.
Discover StudioReference for the agent creation interface, with identity, skills, security, instructions and review steps.
Interface baseline from 07/30/2026 · demo dataScreenshots preserved in the repository. They are interface references, not evidence of performance or of a running conversation. Click to enlarge.
Building a complete experience takes more than configuring a conversation. Capabilities and business rules need to come together in the same design.
No. Choose the tools the agent's role requires and configure the applicable access and controls. A well-defined responsibility makes it easier to observe and validate behavior.
No. Continuity depends on the session configuration and the allowed inactivity period. Conversation history also does not amount to unrestricted access to company data.
These are different roles. A copilot can support the professional during a conversation and prepare records for review. Automated service interacts directly with the customer, within the defined rules and permissions.
Rules need to be explicit and live in the responsible capabilities. The agent can interpret the request and use tools, but the design must preserve the operation's policies, authorizations and reviews.
Tools and integrations can connect the agent to information and actions in existing systems. This depends on the available interfaces and the required credentials, contracts and permissions.
Choose one role and a short journey. Define the goal, permitted data, tools, and handoff points. Validate the behavior before expanding its scope.