Skip to main content
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. The Agentic Fields Center is available to every organization. Find it under Administration > Company Settings > Agentic Fields Center. 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.

​
Setting up a field

The Agentic Fields Center sets up extractions only. A prompt tells the agent what value to pull out of the source document or email — it can’t perform calculations, apply transformations, or look up values in other fields to derive an answer. For logic like that, you still need a calculated field, which is fixed, deterministic logic built into the platform rather than something you can prompt for. If you need an additional calculated field, reach out to the integration team to set it up.
Everything starts in the Field Manager. From there, the path depends on what kind of field you’re working with and whether you want AI to capture it.
1

Create or pick the field in Field Manager

Add a field from the pre-written standard list, or create a custom field. Standard fields already have either standard capturing or calculated logic built in; custom fields start out with no capturing at all.
2

Decide whether AI should capture it

  • Standard field, and you don’t want AI to capture it — toggle Ignore AI Capture on the field in Field Manager. That’s the whole setup; no need to visit the Agentic Fields Center.
  • Custom field you want captured, or a standard field whose capturing you want to refine — head to the Agentic Fields Center to write a prompt. This is also where you go if you want to override or narrow down what a standard field captures by default.
3

Turn on self-learning (optional)

In Field Manager, toggle Self-Learning on for the field if you’d rather the agent build its own capturing rules over time from confirmed requests, instead of (or alongside) a rule you write yourself. See Self-learning below for where the rules it learns show up.
4

Set up the prompt in the Agentic Fields Center

Open the field in the Agentic Fields Center and write a prompt describing what to capture and when — see Creating a new rule below. 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

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. When you click the back button on a field’s configuration page, you return to the landing page with your search and filters still applied. This shows:
  • A header with the field’s name, description (if set), and the intent and areas it’s configured for.
  • An Agent Capture Instructions 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.

​
Standard Global Default

Standard capturing fields come with a built-in description that the agent already uses to capture the value. When your organization hasn’t written its own Global Default rule for one of these fields, the rule list shows that built-in description as a Global Default card with a Standard badge. This lets you see the baseline prompt the agent follows before you add more specific rules. The standard card only appears on the All filter. It also matches the search box against the description text. To customize the baseline prompt:
1

Expand the standard card

Click the Global Default card marked Standard to see its prompt.
2

Edit the prompt and examples

Change the prompt text and add any Examples. A Draft badge appears on the card while you have unsaved changes.
3

Save the prompt

Click Save Prompt. The Agentic Fields Center saves your edit as your organization’s own Global Default (P0) rule, with the area set to Default, the source set to Any, and All Customers. Your rule then replaces the standard card. Click Cancel to discard the draft.
If you aren’t allowed to create default rules, for example because of your area access, the card shows the reason and Save Prompt stays disabled.

​
Self-learning

Instead of (or alongside) writing a rule yourself, you can let the agent learn a field’s capturing rules on its own from confirmed requests.
  • Turn it on. In Field Manager, open the field and toggle Self-Learning on.
  • Where it shows up. Rules the agent learns appear back in the Agentic Fields Center like any other rule, but with a Self-Learned badge on the card. They’re shown as a read-only overlay first — click Override with Manual Prompt if you want to take control and edit one yourself. See Opening a field above for more on reading rule cards.
Writing a manual prompt at a sender domain or sender email level stops self-learning for that field at that level — your manual prompt takes over there, even if self-learning is still on elsewhere for the field. See Rule hierarchy.

​
Creating a new rule

1

Click Add rule

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

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.
3

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.
4

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.
5

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

1

Open the rule

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

Click the trash icon

Click the trash icon on the rule card.
3

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:
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.

​
FAQ

Not today. Prompts can only tell the agent what value to extract — they can’t perform math, transformations, or reference other fields to derive a result. This is in Beta, and we’ll be expanding what you can do here over time — see Rollout plan and what’s next.

​
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.