Kognitos | FAQ - Answers to your business automation questions

How does Kognitos use Generative AI?

Generative AI is the core of Kognitos and used throughout the user experience. At its core, Kognitos uses its own LLM to translate “English Code” into API based automation. When errors or exceptions occur, Kognitos utilizes both its own LLM and outside LLMs like GPT-3 to provide “Conversational Exception Handling”, presenting users with a problem statement in English and giving users the ability to address the exception and even teach the process logic for exceptions in the future, all in English. Kognitos is also using Generative AI in its Koncierge part of the product, currently in Beta. Koncierge uses its experience seeing other automations to suggest to users how to automate a wish of theirs.

How are runs in Kognitos triggered?

Process runs are triggered in three different ways:

Scheduled: For processes that need to run on-time, at the same time every hour, day, week or month, use Kognitos’s scheduling function.
Event Driven: The most common form of trigger used by Kognitos customers is event-driven runs. Kognitos automations can be triggered by receiving emails, files, or by monitoring various software. (Ex. Insurance claim received by Kognitos inbox triggers the automation run). This is particularly an advantage for high-volume, high-frequency processes, and/or processes where it would be beneficial for processes to run 24/7.
Manual Trigger: Often called “Attended Automation” by legacy systems, Kognitos processes can also be triggered manually by clicking the “Run” button from the process list or in the actual process page.

How is Kognitos Organized?

Kognitos is organized by Organizations, Departments and Processes

Organization: A customer is listed as an “Organization” within Kognitos. Customer data sits within this organization and can be further segmented down to the department or process level. Administrators and those with the highest levels of privileges within the customer are able to see Organization wide views, manage permissions for other users, and create/delete departments as needed. Credentials that are needed organization wide are stored and managed at the organization level.
Department: A Kognitos department is a sub-unit of the organization housing the various processes needed by that department. A common example of a department is “Accounts Receivable”, though an organization may also wish to segment their automations based on region or country as well. At the department level, organizations can manage and view processes and users within that department, manage exceptions and apply learnings.
Process: A process is the basic unit within Kognitos, where automations are built and run in English. The process page details the current process flow, facts that are found and used in previous process runs, and any runs that currently require human intervention/exception handling. Previous runs can be reviewed and audited all in English.

Is there a test environment?

Kognitos has simplified the testing process, eliminating the need for automation tools like RPA to have multiple environments deployed. Instead, Kognitos provides users with two testing environments, each integrated within a department for easy use/toggle as needed.

Playground: The playground is the primary testing environment where users can build and experiment with Kognitos. It checks for syntax errors, and other potential problems before a user “publishes” the process into production.
Mini Playground: When users encounter exceptions from a process in production, they may wish to test different remedies to that problem or exception without the actual applications in the process being affected. Mini-Playground enables a user to run these different remedies to exception handling prior to handling the actual exception in production, and can also decide if the remedy should be learned for future use using “Teach a Technique”.

Where are the bots?

Kognitos does not have “Bots”. Bots have traditionally been used in RPA and other automation technologies as run-times, but quickly become a nightmare to manage needing complex orchestration and scheduling. This often results in un-used bots or “Software on the Shelf”. It also creates capacity constraints during moments when a process needs to run more than normal (ex. Holiday season for retailers). Instead, Kognitos scales on demand as needed, no extra configuration, orchestration or extra charges required.

How does Kognitos manage permissions?

Permissions are governed at the Organization and department level. Various roles can be given to users within an organization including:

Organization Admin: Access to all departments and organization views and can add/delete users or credentials as needed.

Department Head: Department heads have the same rights as an organization admin but only for a single department. They can add or delete users from a department, make changes to processes and control department-wide credentials.

Process Manager: A process manager can handle build, change and delete processes. Additionally, they can save “Learnings” or route exceptions to other people to assist.

User: Users have the lowest level of permissions within Kognitos and can only trigger automation runs and handle exceptions. They are not able to use the “Teach a Technique” function in exception handling.

Kognitos FAQ

Introduction to Kognitos

In-App Functionality

Architecture

Security and Governance

Kognitos has achieved the SOC 2 Type II certification for our best-in-class security controls and compliance with the AICPA’s Trust Services Criteria.
Unlock the Power of AI for Your Business Today