What is Aisera?
Aisera is an enterprise Agentic AI and service management platform designed for large organizations, covering IT, employee services, customer support, operations, and voice-related tasks. It leverages domain-specific agents, large language models, corporate knowledge, and automated processes to enable users to resolve issues on their own and carry out system operations.
In November 2025, Aisera announced that it had been acquired by Automation Anywhere; its products, customer support services, and the automation ecosystem are being integrated further. Existing customers should pay attention to the brand transition and any changes in product names when reviewing relevant documentation and support resources.
Main product areas
| Product direction | Primary users | Primary use |
|---|---|---|
| AI Service Desk | Company employees and IT team | Self-service, request processing, and IT workflows |
| AI Customer Service | Customers and customer service team | Customer Q&A, problem resolution, and manual assistance |
| Next-Gen ITSM | IT Service Management Team | Event, issue, change, asset, and knowledge management |
| Ops Experience | IT Operations Team | Proactive detection, root cause analysis, and automatic repair |
| AI Voice Bot | Phone and Voice Services Team | Voice self-service, routing, and process execution |
| BYO Bot/LLM | Companies that already have models or robots | Unified orchestration of self-built and third-party capabilities |
Core functions
- Multi-agent orchestration and task routing.
- Enterprise knowledge retrieval and access control.
- Natural language self-service.
- IT requests and events are resolved automatically.
- Real-time assistance from customer service agents.
- Low-code and no-code workflows.
- Proactive event detection and root cause analysis.
- Multilingual and multi-channel dialogue.
- Enterprise search, summarization, and answer generation.
- It includes built-in models, robots, and integration with third-party systems.
AiseraGPT
AiseraGPT combines enterprise-scale large models with search and action capabilities to create customizable generative AI solutions. Enterprises can use these models to answer questions based on their own knowledge, service catalogs, historical tickets, and business data, thereby triggering automated processes.
Multi-agent architecture
The platform uses Universal Agent to coordinate domain agents with task agents. Domain agents are responsible for areas such as IT, HR, or customer service, while task agents carry out specific actions like querying, updating data, approving requests, and handling failures.
- The Universal Agent identifies the request and selects the domain.
- The Domain Agent understands specific business contexts.
- The Task Agent carries out the specific processes and actions.
- The system adjusts the path based on real-time feedback.
- Manual verification should be retained for decisions or high-risk operations.
Universal Bot
Universal Bot provides a unified interface for communicating with employees or customers, intelligently routing requests to the appropriate robot or department. It helps to reduce the effort required by users to find the right entry point among various portals and service desks.
Agent Studio
Agent Studio enables administrators to create agents using natural language and a guided interface; it also provides access to a pre-existing library of agents. This reduces the barriers to getting started, but complex applications still require clear definitions regarding permissions, data, actions, and testing standards.
LLM Studio
LLM Studio is used to select, configure, and evaluate models and prompts, as well as to connect corporate data with specific applications. Companies can purchase, develop, or integrate their own models; the actual scope of support depends on the deployment method and the contract terms.
Workflow Studio and Hyperflows
Workflow Studio and Hyperflows are used to orchestrate multi-step business processes, interface calls, and automated actions. Hyperflows also supports interfaces such as MCP, which enable agents to discover and utilize the capabilities of external systems.
Event Studio
Event Studio allows external events to trigger agents or workflows, such as monitoring alerts, changes in system status, and business events. For event-driven processes, it is necessary to set rules for deduplication, thresholds, timeouts, and rollback to prevent repeated executions.
AI Service Desk
- Answer employees' IT questions.
- Service requests are created and updated automatically.
- Execute password, access, and software processes.
- Recommend personalized knowledge articles.
- Generate new knowledge from historical solutions.
- Leave complex tasks to the IT support staff.
- Analyze request trends and service quality.
Next-Gen ITSM
Aisera utilizes AI agents for managing events, issues, changes, assets, releases, and knowledge, and it offers capabilities for managing AI-native services. Companies can integrate this solution with their existing ITSM systems or evaluate its next-generation ITSM modules; the extent of the migration will depend on the specifics of each project.
Event and Issue Management
- Automatic classification and completion of events.
- Link similar tickets to known issues.
- Identify significant events from monitoring data.
- Analyze the root causes of repeated failures.
- Recommended repair steps and next actions.
- Perform automatic repair within the allowed range.
- Document solutions and update knowledge.
Change management
The platform can utilize CMDB, environmental data, and historical records to assess the impact of changes, schedule their implementation, and monitor the results. Automatic approval, execution, and rollback are functions associated with high risks; therefore, separation of responsibilities and manual authorization must be maintained.
CMDB and configuration analysis
Aisera can link monitored traffic with ServiceNow CMDB, identify missing relationships or configuration drifts, and provide suggestions for corrections. The documentation emphasizes updating the CMDB after manual verification, in order to prevent the model from directly altering critical configurations.
Asset and Release Management
- Identify and track hardware and software assets.
- Identify anomalies and lifecycle risks.
- Manage maintenance and renewal information.
- Predict release impacts and dependencies.
- Schedule and deploy tasks before and after.
- Monitor the performance of the service after it is released.
Proactive prediction and major events
The platform utilizes service desk tickets and observability data to identify anomalies, predict failures, and reduce the time required to detect and resolve them. The early detection times and customer benefits mentioned on the official website are specific examples and should not be considered as guarantees for all environments.
Customer service agent
- Handle common and complex customer issues.
- Read the context from the CRM and order systems.
- Handle refund, modification, and account-related processes.
- Supports Web, messaging, email, and voice channels.
- Per the policy, escalate the issue to a human agent.
- Summarize the conversation and record the processing results.
- Analyze customer intentions, emotions, and feedback.
Agent Assist – Agent assistant
Agent Assist can be integrated into customer service systems such as ServiceNow and Jira, providing summaries, recommended knowledge, draft responses, and next steps. The outputs must be confirmed by the agent, especially in cases related to refunds, account changes, and regulated transactions.
Voice robot
The AI Voice Bot is designed for telephone and voice-based self-service applications; it can understand natural language, retrieve information, and initiate business processes. When deploying it, it is necessary to take into account factors such as language, accent, telephone infrastructure, recording permissions, emergency routing, and latency.
Enterprise neural search
Neural Search understands natural language queries by taking into account databases, discussions, tickets, knowledge bases, and business applications, and it returns results related to the user’s permissions based on their identity. The answers may include links to additional materials for further review, but the key conclusions still need to be checked in the original source.
Enterprise knowledge generation
Deep Research for Knowledge Generation allows for the search of external information, comparison of various sources to create knowledge articles, and the extraction of solution patterns from resolved tickets and agent records. The content generated must be approved by the person in charge of knowledge management before it can be published.
Domain ontology
The platform can identify entities, synonyms, and relationships from tickets, knowledge articles, service catalogs, and session logs to create an ontology suitable for the specific industry. This helps in understanding internal terminology, but ongoing correction by business experts is required.
Multilingual and multi-channel
- Web chat.
- Mobile and messaging channels.
- Email.
- Text message.
- Microsoft Teams and Slack.
- Telephony and voice.
- Customize the dialogue interface.
- Multilingual staff and customer service.
Enterprise integration
Aisera claims to be able to connect to over 100 different enterprise applications, covering ITSM, HR, CRM, collaboration tools, knowledge management systems, monitoring solutions, and business systems. It is necessary to determine within the scope of the project whether the specific connectors are included in the package, whether two-way data synchronization is supported, or if custom development is required.
| Integration type | Common systems or methods | Uses |
|---|---|---|
| ITSM and tickets | ServiceNow, Jira, etc. | Requests, events, and agent collaboration |
| Collaboration channels | Slack, Microsoft Teams | Employee self-service and notifications |
| Knowledge and content | Confluence and enterprise knowledge bases | Permission-based retrieval and answer generation |
| Observability | AppDynamics, New Relic, and others | Anomaly detection and root cause analysis |
| Custom system | API, WebSocket, and event channels | Dialogue, data ingestion, and business actions |
Developer API
The platform offers Conversation and Workflows APIs, WebSocket, data ingestion APIs, ingestion monitoring APIs, and Event Studio trigger interfaces. Administrators need to create API Channels within the tenant and securely store one-time access tokens.
- Create a custom chat interface.
- Receive real-time conversations via WebSocket.
- Push external data to tenants.
- Check the status of the data ingestion task.
- AI workflows are initiated by external events.
- Connect to systems that do not have pre-installed adapters.
Content permission control
Aisera can perform content permission checks based on the metadata of knowledge articles, user attributes, and APIs from external systems. For complex permissions such as those found in ServiceNow and Confluence, the platform can call the underlying systems to verify whether a user has access rights before providing a response.
Deployment method
| Deployment method | Applicable scenarios | Precautions |
|---|---|---|
| Public cloud | Companies that wish to go live quickly | Confirmation area, tenant isolation, and data policies |
| AWS, Azure, or GCP | Organizations that already use major cloud platforms | Verify the boundaries of responsibilities regarding networking and hosting. |
| VPC | Enterprises that require stronger network isolation | Confirm the access paths for model and data services. |
| Hybrid cloud | Use both local and cloud systems simultaneously | Design identity, network, and audit pathways |
| Local deployment | Strict data or regulatory requirements | Confirm hardware, upgrade, and support costs |
Tutorial on creating agents
- Select IT, HR, customer service, or other specific business scenarios.
- Determine the questions that can be answered and the actions that are permitted to be carried out.
- Create or select a preset agent in Agent Studio.
- Connects to organized knowledge and service catalogs.
- Configure identities, permissions, and rules for manual transfer.
- Use historical issues to test accuracy and security boundaries.
- Real users will be gradually enabled after approval.
Tutorial on integrating corporate knowledge
- Inventory the knowledge base, tickets, catalogs, and sources of discussions.
- Delete expired, conflicting, and ownerless content.
- Retain department, region, and role metadata for the document.
- Configure data sources and regular ingestion schedules.
- Enable content access control and user synchronization.
- Test the same issue using accounts with different permissions.
- Establish processes for knowledge approval, feedback, and updating.
API Integration Tutorial
- Create an API Channel in the tenant settings.
- Name the channel and securely save the token immediately.
- Associate the Channel with the target Agent Application.
- Record the Channel ID and application configuration.
- Call the dialog or ingestion interfaces with the minimum required permissions.
- Implement rate limiting, error handling, and key rotation.
- Connect to the production system only after verification in the testing environment.
Corporate procurement tutorial
- Define the service scenarios, channels, languages, and user base.
- Compile a list of existing ITSM, CRM, and knowledge systems.
- Apply for a demonstration and request a customized quote.
- Confirm deployment, models, data retention, and support scope.
- Use historical tickets to complete controlled proof of concept.
- Measure the resolution rate, accuracy, latency, and overall cost.
- The contract is signed after passing security, legal, and operational approvals.
Which users are it suitable for
- Medium and large enterprises with a high number of IT requests.
- Inter-departmental organizations that require employee self-service.
- Teams that need automation for complex customer service.
- Companies that wish to integrate ITSM with proactive operations management.
- Organizations that need unified services for voice, messaging, and collaboration.
- Companies that already have their own models or robots.
- Regulated agencies with strict permission and deployment requirements.
Typical use cases
- Automatically completes password and software access requests.
- Significant events are identified from monitoring data.
- Analyze CMDB relationships and configuration drift.
- Assists with risk assessment and rollback for changes.
- Provide real-time knowledge and response suggestions for customer service.
- Automatically handles orders, bills, and account issues.
- Provide voice self-service over the phone.
- Perform permission-based enterprise searches across knowledge bases.
- Integrate self-built LLMs into corporate business processes.
It’s not very suitable for which situations
- Only users who need a general personal chat assistant.
- Small teams that wish to view the fixed public prices immediately.
- Organizations without a data governance and process owner.
- Websites that only need a simple FAQ plugin.
- Companies that are unable to provide system integration and identity management capabilities.
- Teams that need to maintain a completely open-source platform on their own.
- Purchasing that proceeds directly to large-scale deployment without conducting a concept validation.
Pricing method
The Aisera official website does not disclose the prices of standard packages, the cost per seat, or the price per request; customized quotes are provided through demonstrations, RFPs, and sales consultations. The total cost is generally influenced by factors such as product modules, the number of users, the distribution channel, language, integration options, deployment methods, and level of support.
| Price items | Public status | It needs to be confirmed at the time of purchase. |
|---|---|---|
| Platform subscription | Standard price not disclosed | Number of product modules and environments included |
| User or session quota | Not disclosed | Billing units, excess and peak limits |
| Implementation and integration | Quotation by project | Pre-set connectors and customized scope of work |
| VPC, hybrid cloud, or on-premises deployment | Request for quote | Responsibilities for infrastructure, upgrades, and operation and maintenance |
| Corporate support | Determined in accordance with the contract | SLA, service duration, and dedicated resources |
| Concept validation | Contact sales | Test scope, timeline, and data processing conditions |
Acquisition and support for migration
In November 2025, Aisera announced its merger with Automation Anywhere; the two companies plan to combine enterprise agents with large-scale automation. In 2026, the original Aisera support portal was also migrated to Automation Anywhere’s A-People Portal, and existing customers need to update their support processes.
Security and TRAPS framework
TRAPS stands for Trusted, Responsible, Auditable, Private, and Secure; it addresses risks such as prompt injection, data poisoning, permission issues, privacy concerns, and audit problems. The platform emphasizes input cleaning, content filtering, manual data selection, model validation, and continuous monitoring.
- WAF and internal input validation for services.
- Verified system prompt.
- Training data cleaning and anomaly detection.
- Manual review can be applied to the data used for model training.
- Continuous monitoring of model performance and abnormal behavior.
- Anonymization of PII, PCI, and PHI.
- Adhere to the company’s existing permission structure.
- Generating answers can provide citation support.
Safety and Compliance Statement
The official website states that Aisera holds ISO/IEC 27001 and CSA STAR Level 1 certifications, and is in compliance with SOC 2, GDPR, HIPAA/BAA, and CCPA requirements. Companies should request the current valid reports, scope of application, and data processing agreements from the Trust Center.
Data and model training
Aisera states that customer data belongs to the customers themselves and is not used to train models for other customers; moreover, customers have control over external data sources. Specific details regarding data retention, etc., are governed by the enterprise contracts, deployment structures, and lists of sub-processors.
Encryption and infrastructure
- TLS 1.2 or a higher version is used for transmitting data.
- Static data is encrypted using AES-256.
- It supports mainstream public clouds as well as isolated deployments.
- The control network can be managed via VPC and hybrid cloud.
- Content access is governed by the permissions of the user and the source system.
- Enterprises should ensure key management and log retention.
Product advantages
- It covers IT, employees, customers, operations, and voice use cases.
- Combines enterprise search, generation, and action execution.
- Multi-agent systems are suitable for complex service processes.
- It provides development tools for Agents, LLMs, Events, and Workflows.
- It supports the promotion of integration with over 100 enterprise applications.
- It can be connected to custom models and robots.
- Offers public cloud, VPC, hybrid cloud, and on-premises deployment.
- Integration with the Automation Anywhere automation ecosystem.
Usage restrictions
- The official website does not disclose standard prices.
- Deployment and integration require enterprise-level implementation capabilities.
- Automated execution of high-risk actions requires strict governance.
- The learning and configuration costs for multi-module products are high.
- The results achieved in client cases cannot be directly applied to all organizations.
- Some of the support and product entry points are being migrated following the acquisition.
- The underlying platform is not an open-source project.
- The compliance statement needs to be verified in accordance with the scope of procurement.
Is it open source?
Aisera is enterprise software for commercial use, and its official website does not make the source code of its core platform available. Its open architecture, APIs, MCP support, and BYO LLM capabilities emphasize interoperability, but this does not mean that it is possible to download the source code and deploy it oneself.
Basic information
| Project | Content |
|---|---|
| Tool name | Aisera |
| Current affiliation | Automation Anywhere |
| Tool type | Enterprise Agentic AI and service management platform |
| Main scenarios | IT, employee services, customer support, operations, and voice |
| Key technologies | AiseraGPT, multi-agent systems, enterprise search, and automation |
| Deployment method | Cloud, VPC, hybrid cloud, and on-premises deployment |
| Price pattern | Custom quotes for businesses |
| Whether API is provided | Yes |
| Is it open source? | No |
Recommendation score
The comprehensive recommendation score is 4.4 out of 5 points. Aisera is suitable for large organizations that need to integrate corporate knowledge, service management, and automation; however, its procurement process, customized pricing, and implementation costs are significantly higher than those of simpler chatbots.
Frequently Asked Questions
Was Aisera acquired?
Yes, Aisera was announced to be acquired by Automation Anywhere in November 2025, and its products and support services are currently being integrated further.
How much is Aisera?
The official website does not specify standard prices; a quote must be obtained by contacting sales, taking into account factors such as the modules used, the scale of the project, integration requirements, and deployment needs.
Is Aisera an ITSM product?
It offers Next-Gen ITSM, and can also be used as an agent layer that is added on top of existing service management systems such as ServiceNow and Jira.
Can I use my own large model?
The BYO LLM and BYO Bot options can be evaluated; the specific models supported and the methods of deployment must be confirmed according to the contract.
Does Aisera offer voice robots?
An AI Voice Bot is provided for voice-based self-service and business processes; language support, latency, and compatibility with telephone systems need to be tested in practice.
Is local deployment supported?
Options include cloud, VPC, hybrid cloud, and on-premises deployment; the specific architecture and prices require a quote.
Does Aisera provide APIs?
It provides interfaces for dialogue, workflows, WebSocket, data ingestion, monitoring, and event triggering.
Are customer data used to train other customer models?
Official statements say no, but companies should verify the specific data pathways through contracts, deployment architectures, and terms with sub-processors.
Is Aisera open source?
Not being open source; an open architecture, API, and MCP interoperability do not equate to open core source code.
Guigong Network Security Registration No. 45132202000164