> ## Documentation Index
> Fetch the complete documentation index at: https://docs.raum.am/llms.txt
> Use this file to discover all available pages before exploring further.

# Action and Edit

> Use Action for ticket-aware support instructions and Edit for targeted refinement of existing Zendesk composer text.

Email Mode includes **Action** and **Edit** for work that does not fit a single preset button.

They look similar because both accept an instruction, but they operate on different things.

## Action

Use **Action** to give RAUM a ticket-aware support instruction.

Action can use:

* the ticket conversation and Zendesk context;
* procedures;
* organization knowledge;
* SOURCE tools; and
* ACTION tools according to their configured approval rules.

Examples:

* check the customer's current order and explain the status;
* follow the cancellation procedure for this ticket;
* determine whether the customer qualifies for a refund;
* prepare the appropriate ticket changes; or
* perform an approved external operation and write the resulting response.

### Run an Action

1. Click **Action**.
2. Enter the instruction.
3. Execute it.
4. Respond to any procedure/tool decision or ticket-change approval prompt.
5. Review the resulting composer text and Zendesk changes.

Action can run even when there is no existing composer draft because the instruction is about the ticket/workflow rather than only editing text.

## Decision-first workflows

An Action can discover that the relevant procedure or tool requires an agent choice.

The app pauses and presents the available options. The agent can choose one and optionally add notes. RAUM then resumes the workflow with that decision rather than guessing.

Multiple decisions can be collected sequentially when the workflow requires them.

[Approvals and decisions →](https://docs.raum.am/using-the-app/approvals.md)

## Edit

Use **Edit** to transform the text already present in the composer with a specific instruction.

Examples:

* shorten this response;
* make the explanation clearer;
* lead with the resolution;
* preserve the first paragraph but rewrite the rest;
* remove repetition; or
* add a specific detail from the ticket.

Edit is disabled when there is no composer text to modify.

## Action versus Edit

| | Action | Edit |
| - | - | - |
| Needs existing composer text | No | Yes |
| Primary subject | Ticket/workflow | Current draft |
| Can use procedures/tools | Yes | Uses Assistant context but is primarily a text-refinement operation |
| Can require agent decisions | Yes | Normally no workflow decision tree |
| Typical result | Support work + response | Revised composer text |

## Zendesk ticket-change approvals

A generated workflow can also recommend Zendesk changes such as permitted status, tag, group, assignee, or field operations.

When explicit agent authorization is required, the app presents a separate ticket-change approval prompt instead of silently applying the suggestions.

If applying or recording approved changes fails, the draft can remain usable while the app warns the agent to review the ticket before submission.

## Cached Action/Edit results

Where response caching applies, the app can ask whether to use the cached result or regenerate a fresh one.

> **[Approvals and decisions](https://docs.raum.am/using-the-app/approvals.md)**
>
> Understand procedure choices, ACTION approvals, and Zendesk changes.

> **[Connections](https://docs.raum.am/configuration/integrations.md)**
>
> See how SOURCE and ACTION tools are configured.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.