The action queue

Introduction

The action queue is how Helix proposes changes to a client file. Nothing Helix writes ever changes your data on its own. Every add, update, or delete shows up in the queue first, and nothing runs until you approve it.

When the action queue appears

The queue appears only on client-scoped Helix, because global Helix does not have access to client files. It shows up in a bar at the bottom of the chat the moment Helix proposes its first change. If Helix proposes more than one action, they all queue up together so you can handle them in a batch.

Reviewing an action

Each action in the queue shows:

• What it would do: add, update, or delete.

• What it would change: an asset, debt, beneficiary, coverage record, or note.

• Why Helix proposed it: a short reason based on the conversation.

• The field values Helix is suggesting.

Use the navigation arrows to move between actions when there is more than one.

Editing, approving, or denying

You have three options on any action:

• Approve: accept Helix's proposal as is.

• Edit: open the action in a modal to adjust the field values before approving.

• Deny: discard the proposal. Helix does not try again unless you ask.

Once every action has been approved or denied, submit the batch. Approved actions run immediately against the client file. Denied actions disappear.

After approval

Approved actions write to the client file the same way you would write by hand. The results show up on the relevant pages (Financials, Beneficiaries, Coverage, or Notes). They also appear in the recent activity feed on the client overview. If something landed wrong, you can undo it by editing or deleting the entity directly on its page.