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 panel at the bottom of the chat the moment Helix proposes its first change. If Helix proposes more than one action, they all land in one list so you can handle them together.

Reviewing an action

Each row in the list shows:

• What it would do: add, update, or delete.
• What it would change: an asset, debt, policy, beneficiary designation, note, company or trust, household member, profile detail, relationship, stage, or to-do.
• Why Helix proposed it: a short reason based on the conversation.
• The field values Helix is suggesting.

Open a row to see its fields. When there is more than one change, the list groups them under Needs your input and Ready to save.

Adding, editing, or leaving out

On any open row you can:

• Add: accept Helix’s proposal as is. For an update or a delete, the button reads Update record or Delete.
• Change the field values in place before you add the row.
• Leave out: discard the proposal. Helix does not try again unless you ask.

To handle a whole list at once, use Save N changes to add every row that is ready, or Dismiss all to leave them all out. Added changes run immediately against the client file. Changes you leave out 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). Helix also leaves a line in the chat that says what was done, with a View button that opens it. If something landed wrong, you can undo it by editing or deleting the entity directly on its page.