Skip to main content

​
Catalogue Overview

The Catalogue lists use cases that are ready to hand over to Neural Factory: processes a team runs by hand today, each specified end to end and built in advance. Instead of describing an agent or a workflow from scratch, you pick the use case that matches your process and activate it. You find the Catalogue under Workforce, after Agents and Workflows. It is available to administrators and members.

​
Browsing

Every card names a use case, states its outcome in one sentence, and tells you how close it is to running in your organization. The use cases most teams ask for, and the ones closest to usable for you, come first.
  • Search looks through the name, the outcome, the problem a use case solves and its team.
  • Filters narrow the list by readiness, by team, and by what the use case is. The number beside each filter is what you would get by ticking it. Filters within a group widen the list; filters from different groups narrow it.
  • The address of a filtered view is a link. Send it to a colleague and they see the same list.
A use case is one of four things:

​
Readiness

Readiness is worked out for your organization, from what the use case uses and what you have connected. The documents a use case reads, such as a policy or a methodology, never hold it back: you point it at them when you activate it.

​
A use case page

Click a card to read the use case before you commit to it. On the left, the page says what the use case is:
  • Who it is for and the problem it takes off their hands
  • What it does and how it runs, step by step, starting with what sets it off: a person, one of your systems, a schedule, or a conversation
  • Human in the loop — where a person decides, when the use case has an approval
  • Outcomes and how they are measured
  • What it does not do — stated before you start. If one of these is the reason your process exists, this is the wrong use case
On the right, Readiness lists everything the use case needs from your organization:
  • Each toolkit it uses, connected or not. An administrator (or any member on a cloud plan) gets a Connect button that opens the connection form in a new tab; when you come back, readiness is already up to date. Where your deployment cannot offer a toolkit yet, the row says With us: we set it up together
  • Each of your own systems it works with, marked Activation
  • Each document set it reads: either already among your knowledge bases, or marked You provide
Below that you find what the use case is better with (optional systems), what we put in place for you, what to have ready before you start, and the time to value. Activate starts the use case’s set-up. Once you have activated it, the button becomes Open in Workflows or Open in Agents and takes you to what was created.

​
Describe your own

If nothing in the Catalogue matches your process, Describe your own takes you to the builder, where you describe what you need in your own words.

​
Where activated use cases show up

An activated use case is an ordinary agent or workflow in Agents or Workflows, and the use case’s own page offers Open once one exists. The builder’s “What do you want to build?” page shows a few use cases of the kind you are building under From the catalogue, with a link to browse all of them.