Bring a model provider
Use an available provider, or connect one already in use. Configure models around the agents’ work.
Explore agent setupFrom a first request toa shared way of working.
Work with agents connected to business information and tools. Develop applications, schedule recurring tasks, and share useful capabilities across the team.
Customer operationsAgentAR
Alex RuizCustomer Success
Review the customer feedback and flag the issues that need attention.
Support feedback agentFindings ready
Customer insights agentFindings ready
Feedback reviewApplicationA working view of the findings
Themes6
Comments42
To review8
Explore themes and inspect original comments.
Feedback reviewRecurring taskEvery Monday09:00 UTC
ScheduledGive an agent a role in the business.
Describe what the team needs help with and how the work should be done. Configure the agent through conversation, or adjust its instructions, skills, and model in settings.
Instructions that reflect the work
Define the requirements and checks that should guide the agent.
Reusable skills
Choose from available skills. Selected skills stay attached to the agent.
Choice of model provider
Use an available provider, or connect one the team already uses.
More about skills and configuration
Skills can be installed and updated from a Git-based catalog. Provider connection details and model settings belong in the configuration guide.
Support feedback agentSkills and modelSkills
Model
OpenRouterSuggested
Connect the tools the team uses. Bring the ones already built.
Start with the integration catalog, or connect internal systems and services. Give each agent the information and actions relevant to its work.
Available integrations
Connect business services from the catalog.
Internal and custom connections
Bring internal services through MCP, APIs, and custom tools.
Tools for each agent
Choose which capabilities are available to the agent.
MCP, APIs, and custom connections
MCP connects agents to compatible tool servers. APIs and custom tools can support additional services. Authentication and setup requirements vary by connection.
Connections for this agentCatalogSlackGoogle DocsGmailNotionShopifyZendeskSalesforceLinearGitHubGoogle SheetsJiraCalendarInternal system · MCP
Illustrative catalog marks · connection methods depend on configuration
One conversation. Several ways to get the work done.
Agents can use tools, delegate to specialists, and work in a browser or computer environment. Follow the activity and review the resulting work.
Customer operationsTool activityPrepare a brief using the latest account notes.
Search account recordsComplete
Read recent discussionsComplete
Account brief
Recent changes, open issues, and questions to confirm.
From a request to an observable action.
See which tools the agent uses and what they return. Review the work with its supporting information.
Customer operationsSpecialistsSFSupport feedbackRecurring issuesComplete
CICustomer insightsAccount contextComplete
Brought together
The support evidence and account context come together here.
Bring in specialists without starting over.
A coordinating agent can delegate parts of a task to other agents and bring their contributions together. Independent work can run in parallel.
BrowserObservable workexample.com / product / pricing
Business plan
Published termsBilling details
Check scope before comparingSource captured for review
Return to the conversation and supporting evidence.
Work beyond the conversation.
Agents can interact with web pages and computer tools. Observe the work and return to the conversation it supports.
Execution environments and observation
Browser and computer tools operate within configured execution environments. Sandbox lifecycle, persistence, and isolation details should be checked for the deployment. Enterprise documentation covers these choices.
When an answer is not enough, create something usable.
Agents can develop custom tools and lightweight applications to support the work, with an interface and the logic behind it. Describe what is needed and refine it through conversation.
Tools that extend the agent
Reusable ways to retrieve information, perform actions, and follow a process.
Applications people can use
Controls and interfaces for exploring information and carrying out tasks.
Refinement through conversation
Adjust the application when requirements change.
Make this an application. Let the team explore themes and open the original comments.
Feedback reviewApplicationSetup instructions need clarificationSupport
Additional administrator neededAccount notes
Read-only role requestedSurvey
Original customer comment
The email names a different screen.
Set the work to run again.
Turn a request into a one-time or recurring task. For more involved work, combine tool actions and agents in a multi-step pipeline.
Scheduled tasks
Specify when the work runs and which agent handles it.
Task pipelines
Coordinate tools, agents, and conditional steps.
Run history
Inspect status, timing, and the conversation produced by each run.
How a multi-step task can fit together
Collect records, prepare context, ask an agent to review, then save the result. Pipelines can include tool steps, other agents, and conditional logic. Scheduling and external actions require the relevant configuration.
Run this review every Monday morning.
Customer feedback reviewScheduled taskEvery Monday09:00 UTC · Customer operations
ScheduledWeekly reviewCompletedWeekly reviewCompleted
Give the next person a working starting point.
Share useful agents and applications with the team. People can use what is already available rather than recreate the original instructions, tools, and interface.
Share an agentCustomer operationsCOCustomer operationsAgent
JHJordan HaleUse the existing agent for a new task.
The same capability. A different person’s task.
The next person can begin with an established agent, rather than reconstructing its setup in a separate conversation.
Share an applicationFeedback reviewFRFeedback reviewApplication
JHJordan HaleOpen the application and use its existing controls.
The original conversation is not required.
The team can use an application’s interface directly. The available data and actions depend on the sharing and connection configuration.
Shared capability is not the same as shared personal memory. Exact access, credential, and sharing boundaries depend on configuration.
Models, integrations, and environment stay under the team’s control.
Bring integrations
Start with the catalog, or connect internal systems, services, and specialist tools.
Explore connectionsChoose the environment
Explore deployment, isolation, access, and support options for the organization.
Enterprise optionsSee how the pieces fit the work.
Bring a task or process the team already handles. We will walk through the agents, connections, applications, and recurring tasks that could support it.