Who this is for. Super Admins setting up or maintaining an Agent Co-worker. See the Roles and Access.
The control that opens this wizard reads Create Agent, at the foot of the Running Instances popup.
The setup wizard configures an Agent Co-worker in six steps, whether you are creating one or editing a live one. This article covers what each step asks for and the order to work in. For the step-by-step procedure, see Create an Agent Co-worker.
Figure 1. The setup wizard on the Work scope step, with the six-step rail across the top.
Open the wizard
You reach the wizard from the Agent Co-workers page rather than from a settings menu, by one of two routes. Create Agent, at the foot of the Running Instances popup, opens New AI agent co-worker on an empty form. Edit on an instance row opens Edit AI agent co-worker against that live instance. The steps below are the second route.
Open Agent Co-workers and select the Agent Co-worker you want to configure. To create a new instance instead, select Create Agent at the foot of the popup.
In the Running Instances popup, select Edit on the instance.
The Edit AI agent co-worker page opens on Work scope.
Six steps
Steps 1, 2, and 6 take about a minute each; step 3 is where nearly all the configuration work sits. Steps 4 and 5 are placeholders in the current release and are skipped, so in practice you work four.
Table 1. Agent Co-worker setup steps
Step |
Name |
What you do |
Effort |
|---|---|---|---|
1 |
Work scope |
Name the agent and select the system of record and connected mailbox it operates against. A description is optional. |
Four fields, three of them required |
2 |
Choose functions |
Select which AP functions the Agent Co-worker handles, before any detailed configuration. |
Checkboxes |
3 |
Define capabilities |
Configure each selected function on its own tab. Each tab has its own inner rail of capability sections. |
This is where nearly all the work is. |
4 |
Exception treatment |
The wizard skips this step when you continue from Define capabilities. |
None |
5 |
Try out coworker |
The wizard skips this step when you continue from Define capabilities. |
None |
6 |
Activate |
Activate the configured Agent Co-worker. |
One action |
There is no pre-activation test run, so the configuration review at step 6 is your only check before the Agent Co-worker starts working live traffic.
How Define capabilities is organized
Step 3 is not one screen. Each function you selected at step 2 gets its own tab, and each tab carries its own inner rail of capability sections. Selecting two functions means configuring two tabs.
Table 2. Capability sections by function
AP Invoices tab |
AP Helpdesk tab (Governed Autonomy) |
|---|---|
Autonomy level |
Autonomy Level |
Document intake |
Contact Management |
Field extraction |
Email Categories |
Business rules |
Vendor Categories |
Write to SOR |
Processing & Automation |
None |
Processing Rules |
None |
Assignee Hold |
None |
Email Archiving |
None |
Task SLA |
The AP Helpdesk rail above assumes Governed Autonomy. Selecting Collaborative Mode presents a different set of sections. For more information, see AP Helpdesk Autonomy Level.
Move through the steps
The work scope, function and capability form settings are written when you select Run on the final step. Four panels are the exception: Email Categories, Processing Rules, Internal Contacts and System Senders save through their own buttons as soon as you use them, so a change there takes effect even if you leave without selecting Run.
Each step has Back and Next at the bottom of the page, and the step indicator at the top shows your position.
Within Define capabilities, the inner rail on the left lists the capability sections for the current function tab. You can select a section directly rather than stepping through in order, which matters when you return later to change one setting.
The capability rail collapses using the toggle at its top, giving the main panel more horizontal space. That helps on the wider sections such as Processing Rules, Email Categories, and Field extraction. The collapsed state applies to the current session only and is not retained across page loads.
Configuring in the right order
Within step 3, order matters in the same way on both tabs: the autonomy setting comes first, because it determines what else exists or how much the rest of the configuration has to carry.
On the AP Helpdesk tab:
Autonomy Level, because it determines which of the remaining sections exist.
Contact Management, because sender classification sets the authorization scope every later section operates inside.
The remaining sections can be configured in the order presented.
On the AP Invoices tab: work the inner rail top to bottom. The sections form a pipeline: intake decides what is accepted, extraction decides how fields are filled, business rules adjust the result, and Write to SOR decides what may post. Configuring out of order means making decisions about later stages before you have settled the earlier ones.
Settings reached from elsewhere
Not everything lives in the wizard. Plain-language policy rules live in the Rulebook rather than in any capability section, so a setting you cannot find in Define capabilities is usually there.