Agent actions
Review, approve, or reject every change Arketa Agent proposes for your studio
Agent actions is where every change Arketa Agent proposes waits for a person. Nothing runs until someone with the right permission approves it. Go to Arketa Agent → Approvals in the sidebar. Arketa Agent appears once Agent is on for your studio, or when something is waiting for you.
Agent actions is rolling out to studios gradually. If you don't see Approvals or the digest, it isn't on for your studio yet.
The three tabs
| Tab | What it shows |
|---|---|
| Needs approval | Proposals waiting for a decision, with a count badge. Rows are sorted soonest-to-expire. Columns are Action, Requested by, Client / Target, Risk, and Expires, with a Review button on each row. |
| Proposed by me | The proposals you asked Agent for. |
| History | Approved, rejected, and expired actions from the last 90 days. Details are removed after 90 days. |
Click Ask the Agent in the page header to request something new. The Arketa Agent item in the sidebar shows a count of approvals waiting for you. A dot instead of a count means you have an unread money digest. See Money on the table →
Review a proposal
Open the proposal
On the Needs approval tab, click Review on the row.
Check what will happen
The drawer shows What will happen in plain words, plus an activity timeline of the proposal so far.
Approve or reject
Approve it the way its risk level asks (see below), or click Reject. If you can't approve it, the drawer says Needs approval by someone with … and names the permission.
A sent message cannot be recalled. Check the recipients and the copy before you approve anything that reaches clients.
Risk levels
| Risk | How you approve |
|---|---|
| Low | Click approve. |
| Medium | Click approve. For memberships (pause, resume, cancel at renewal), first tick the checkbox that restates the effect that can't be undone. |
| High | Type the confirmation the prompt asks for, such as the recipient count or the client's full name. High-risk actions can only be approved from this page, not from the chat card. |
Expiry
Low-risk proposals expire after 24 hours. Everything else expires after 4 hours. If the action has a sooner natural deadline, that deadline wins. An expired proposal moves to History, and you can ask Agent for it again.
Withdraw or reject
- Withdraw is for the person who asked for the action. Use it when you no longer want it.
- Reject is for anyone who could approve the action. You can add an optional reason.
Statuses
| Status | What it means |
|---|---|
| Awaiting approval | Waiting for someone with the right permission. |
| Working | Approved and running now. |
| Done | Finished. |
| Failed | It didn't complete. Click Try again or Propose again. |
| Rejected | Someone who could approve it said no. |
| Withdrawn | The person who asked for it canceled it. |
| Expired | Nobody decided before it expired. |
| Replaced | Agent proposed a newer version. Click Review the new version. |
| No longer valid | Something changed since the proposal, so it can't run as written. |
What the Agent can do
On the Agent's Overview tab, click What the Agent can do › to open a catalog of every action, grouped, each with a risk badge. Click Try on any action to fill the composer with an example.
Reach clients
| Action | What it does | Risk |
|---|---|---|
| Message a client | Text or email one person. | Medium |
| Message up to 100 clients | One text or email to a named list. Unreachable clients are skipped and counted. Above 10 recipients, the approver types the count. | Medium |
| Draft a broadcast | Email or text copy saved as a draft. | Low |
| Schedule or unschedule a broadcast | Up to 30 days out. | Medium |
| Send a broadcast now | The approver types the recipient count. | High |
| Email a payment link | Up to 10 products. | Medium |
Automate
| Action | What it does | Risk |
|---|---|---|
| Create a draft automation | Saved switched off. | Low |
| Turn an automation on or off | Switching one on is the riskier step. | Medium |
| Enroll clients in an automation | Up to 100 named clients. | Medium |
| Enroll a whole segment | The approver types the client count. | High |
Organize clients
| Action | What it does | Risk |
|---|---|---|
| Build a segment | A saved client filter. | Low |
| Tag clients | Up to 100 clients, 10 tags. Medium risk if the tag triggers an automation. | Low |
| Add a client note | Saved to the client's profile. | Low |
| Add a client | A new client record from a name and contact. | Low |
| Create a staff task | A to-do for someone on your team. | Low |
Bookings & memberships
| Action | What it does | Risk |
|---|---|---|
| Book a client into a class | Any class on your schedule. | Medium |
| Cancel a reservation | Frees the spot for someone else. | Medium |
| Pause a membership | Up to 24 billing cycles. | Medium |
| Resume a membership | Ends a pause early. | Medium |
| Cancel a membership | Ends at the next renewal. Ending it today is high risk and needs a typed confirmation. | Medium |
Permissions
Anyone can ask Agent for something. Approving an action needs the same permission the action needs when you do it by hand. For example, sending a broadcast needs permission to edit broadcasts, and canceling a membership needs the permission to cancel memberships.