> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to use AI agents that fill fields and move cards automatically after replying
- URL: https://blog.jestor.com/ai-agents-fill-fields-move-cards/
- Published: 2026-07-12T00:32:24.000Z
- Updated: 2026-07-12T00:32:24.000Z
- Author: Bruno Bannach

Before, an AI agent would only reply to the ticket — fields like **resolution date** or category remained manual. In **Jestor version 8.0**, the email agent gained permission to edit specific fields and move the card between phases on its own, with a scope defined by the admin.

## What is permissioned field editing, and why does it exist?

Permissioned field editing is **automation governance**: the admin defines exactly which fields the agent can change, instead of giving it unrestricted access to the database.

| Scenario       | Agent scope                                   | Operational impact                           |
| -------------- | --------------------------------------------- | -------------------------------------------- |
| **Before**     | Only replies to the ticket                    | Resolution field filled in by hand           |
| **Jestor 8.0** | Replies, classifies, and edits defined fields | Field filled in and card moved automatically |

## How to use AI agents with field editing in Jestor

- **Scope defined by the admin:** you choose exactly which fields the agent can edit.
- **Automatic filling:** resolution date filled in as soon as the customer confirms satisfaction.
- **Classification by category:** finance, HR, or support, based on the configured documentation.
- **Card movement:** the agent moves the card to "resolved" after replying.

**How to configure it in Jestor:** in the email agent settings, select the editable fields and add the knowledge base — the agent then acts within that scope.

> **Operational tip:** for critical processes, add a manual verification checkbox before the action is confirmed.

## Why choose Jestor for this automation?

The key differentiator is **scope control**: the agent performs real write actions on the database, but only within the fields the admin releases — reducing the risk of unrestricted automation. The feature is already available on the email agent, with expansion planned for the platform's other agents.

## Frequently Asked Questions

**What happens if the agent tries to edit a field outside its allowed scope?** It doesn't happen — the admin defines exactly which fields it can change.

**How do I review what the agent classified before confirming the action?** Add a manual verification checkbox; the action only becomes final after that review.

**Does this feature only work for email tickets?** Today it's available on the email agent, with expansion planned for the other agents.

## Reference video

Check out other practical tutorials on the [Jestor YouTube channel](https://www.youtube.com/@jestorbr?ref=blog.jestor.com).

## Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all with no code and with AI support. Get to know Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.