# Fields you collect: the details the agent captures, and everything that reads them

> Fields are the details the agent captures about each customer. Goals ask for them, and rules, scoring, pipeline stages and workflows all read them.

Source: https://www.linkubit.com/docs/fields-you-collect  
Section: Linkubit help centre › How the AI agent works  
Updated: 2026-10-09

## In short

Settings › Fields you collect holds three lists: About each customer, Company fields and Product fields. The agent fills customer fields from the conversation after every reply. Goals require them, rules and stages can wait for them, and scoring rules and workflow conditions test them. Saving publishes a new version; conversations already underway keep the version they started with.

## The three lists

| List | Filled by | Used by |
| --- | --- | --- |
| **About each customer** | The agent, from the conversation; a person on the contact; an import; a workflow's `set_attribute`. | Goals, agent rules, scoring, pipeline stages, workflow conditions, audiences. |
| **Company fields** | A person, an import, enrichment. | Scoring and workflow conditions (the company's value is used when the contact has none of its own). |
| **Product fields** | You, on each catalogue product. | The catalogue screens and the agent's product lookups. |

## Each field

- **Key** — what goals, rules and workflows refer to (`group_size`). Do not rename a key that is in use; add a new field instead.
- **Label** — what people and the agent read ("Number of guests").
- **Type** — text, number, enum (a fixed list of values), bool, range or money. An enum's values are what the agent must map the answer to, so write them as customers would recognise them.
- **Help text** — sent to the agent with the field. Use it to say what counts: "Total adults and children; a range like 10–15 is fine".
- **Required** — marks the field as important on forms. What the agent asks for is decided by goals, not by this switch.

## How a value gets captured

1. After each reply, one extraction call reads the recent conversation for every field in **About each customer**.
2. A value it finds is written to the contact. The agent can also write a value directly while it works, through its record tool, if its role allows writing contacts.
3. Goals see the new value: the next missing required field becomes the next question.
4. The score is recomputed, and rules waiting on that field stop waiting.

## Ask order

A goal's required fields are asked one at a time, in the order the fields are listed on Fields you collect. Put what you need first at the top — usually what the customer wants, then quantity or size, then date, then budget.

## Versions

Saving publishes a new version and never edits the old one. A conversation keeps the version it started with, so a field you add today is asked in new conversations, not ones already halfway through.

> **A scoring rule on a field fires as soon as the field has a value.** "Group size is present: +15" adds points the moment any value is captured, including an answer you would not count as qualifying. If points should depend on the value, test the value ("group size ≥ 20"), not its presence.

## Related
- [Conversation goals and stance](https://www.linkubit.com/docs/conversation-goals-and-stance)
- [Lead scoring, explained](https://www.linkubit.com/docs/lead-scoring-explained)
- [Agent roles and rules, explained](https://www.linkubit.com/docs/agent-rules-explained)