Agentic Fields Center - Go Autonomous

This is in Beta and is in a phased rollout. See Rollout plan and what’s next for what’s available today.

Overview

The Agentic Fields Center gives you control to create your own fields with capturing logic, see the real-time learnings the system has collected on each field, and adjust them — all from your administration settings, without needing to loop in your Engagement Manager. To make it easy to reason about, we’ve categorised every field into four types.

When more than one rule could apply to the same field, the most specific one takes precedence: a sender email rule beats a sender domain rule, which beats an Area / Source rule, which beats the Global Default. See Rule hierarchy for the full breakdown.

The four types of fields

We’re improving how each type is labelled in the Field Manager so it’s obvious at a glance which fields use standard capturing, which are calculated, and which you can override in the Agentic Fields Center.

Type	What it is	Adjustable in Agentic Fields Center?
Standard capturing	A built-in field extracted using our standard model (e.g. product number, quantity).	Yes
Standard, calculated logic	A built-in field derived from a calculation, or driven by special deterministic logic (e.g. total price = quantity × unit price).	No — the logic is fixed
Non-standard, no capturing	A custom field you’ve defined that isn’t being captured automatically.	Yes
Non-standard, enhanced capturing	A custom field with capturing logic you’ve authored in the Agentic Fields Center.	Yes

Setting up a field

Pick standard or custom

In the Field Manager, the pre-written list of fields already has either standard capturing or calculated logic built in — or you can create a custom field instead.

Adjust capturing in the Agentic Fields Center (optional)

If you want to shape how the field is captured, open the Agentic Fields Center and write a prompt describing what to capture and when. Save it, then open a live request to watch the learnings flow in.

Today, field definitions are scoped per intent — a field’s capturing rules apply to the intent you’ve configured them under. In a future release, a single field definition will be able to span multiple intents so you can maintain one source of truth for the same field across similar request types.

Using the Agentic Fields Center

The landing page

Navigate to Administration > Company Settings > Configurations > Agentic Fields Center. The page opens on a searchable table of every agentic field across your organisation. At the top, you can:

Search fields by name.
Filter by area — show only fields included in one or more specific areas.
Filter by intent — show only fields configured for one or more specific intents.

If no fields have been configured yet, the page shows an empty state pointing you to the Field Manager — agentic fields are created through field configurations there, not directly in the Agentic Fields Center.

Table columns

Column	What it shows
Field Name	The field’s display name, plus any status badges: an area-access warning if you can’t fully access the field, Auto-calculated for calculated fields, or Capture off for fields with AI capture disabled in Field Manager.
Included In Area(s)	One badge per area the field is configured for. A field with no area override shows a single Default badge.
Intent	The intent (or intents) this field is configured under.
Prompting Rules Count	How many prompting rules currently exist for this field.

Rows for Auto-calculated and Capture off fields are pushed to the bottom of the table and shown dimmed — they’re not adjustable here, so clicking them does nothing.

Opening a field

Click any interactive row to open its configuration page. This shows:

A header with the field’s name, description (if set), and the intent and areas it’s configured for.
An Agent Prompting Rules section listing every rule for this field, with a count badge.
A priority note reminding you how rules are ranked: Customer Specific > Area + Source > Area / Source > Global Default (see Rule hierarchy below).
A search box and a filter (All / Area / Source / Customer) to narrow down the rule list.

If no rules exist yet, you’ll see an empty state instead — its message differs depending on whether the field already has built-in default extraction (in which case it invites you to add a rule to refine capturing) or has no capturing at all yet. Each rule card shows a Self-Learned badge when the rule was learned automatically, so you can see at a glance which rules are self-learned and which were written manually. Click any rule card to expand it. From there you can edit the prompt and its examples, then Save Prompt. Cards for Self-Learned rules are shown as a read-only overlay first — click Override with Manual Prompt to unlock editing. See Deleting a rule below to remove one.

Creating a new rule

Click Add rule

From a field’s configuration page, click Add rule to open the rule dialog.

Set the Area and Source

Choose which Area the rule applies to (or Default for every area), and which Source the agent should look in — Any, Email, or Attachment. Use Any when the value could appear in either.

Set the rule granularity

Leave it as All Customers for a broad rule, or narrow it to By Sender Domain or By Sender Email to target a specific customer.

Write the prompt and examples

Enter the Prompt rule — describe what to capture, where to find it, and how to format it. Add 3–5 Examples of realistic values the field should contain. Open Tips for writing prompts & examples for guidance and a worked example.

Add rule

A badge in the dialog shows which priority tier the rule will land in as you fill out the form (e.g. Global Default (P0)). Click Add rule to save it.

Best practices for writing prompts

Be as descriptive as possible — the more context you give the agent, the more reliably it finds the right value. A strong prompt tells the agent what to look for, where to find it, and how to format the output, and your examples show it real values to recognise. For example, to capture a port:

Prompt: “Identify the port of loading or discharge. Ports are normally listed near the delivery address, or in a dedicated field labelled ‘Port’, ‘POL’, or ‘POD’. Capture just the port name and country, without the full address.”
Examples: Rotterdam, NL, POL: Shanghai, Hamburg, Port of Long Beach

Open Tips for writing prompts & examples in the Add rule dialog for more guidance, including a full worked example.

Deleting a rule

Open the rule

On the field’s configuration page, find the rule you want to remove.

Click the trash icon

Click the trash icon on the rule card.

Confirm the deletion

Confirm in the dialog that appears. Deleting a rule is permanent and can’t be undone.

Rule hierarchy

When more than one rule could apply to the same field, the most specific rule wins. Rules are ranked, from highest to lowest priority:

Tier	Priority	What sets it
Customer Specific — Sender Email	P4	A specific sender email is set on the rule.
Customer Specific — Sender Domain	P3	A sender domain (not a specific email) is set on the rule.
Area / Source	P1	An area, a source, or both are set (with no customer identifier).
Global Default	P0	No area, source, or customer identifier is set — applies everywhere as a fallback.

The Add rule dialog and priority note distinguish rules scoped to both an area and a source from rules scoped to only one, but both currently rank at the same Area / Source (P1) priority — the difference is in how specifically the rule targets a request, not in which one wins.

If you manually write a prompt at a sender domain or sender email level for a field, self-learning stops for that field at that domain or sender level — your manual prompt takes over and the system won’t keep learning on top of it there, even if self-learning is still on elsewhere for the field.

What’s next

Rollout plan and what’s next — how the Agentic Fields Center is being released, phase by phase, and what’s coming after.
Field Manager — configure which fields appear in each configuration.
Areas — scope Agentic Fields rules to specific areas.

​Overview

​The four types of fields

​Setting up a field

​Using the Agentic Fields Center

​The landing page

​Table columns

​Opening a field

​Creating a new rule

​Best practices for writing prompts

​Deleting a rule

​Rule hierarchy

​What’s next

Overview

The four types of fields

Setting up a field

Using the Agentic Fields Center

The landing page

Table columns

Opening a field

Creating a new rule

Best practices for writing prompts

Deleting a rule

Rule hierarchy

What’s next