Skip to main content
Every Ask Z agent has two controls, and you decide both.
  • Approval policy sets which actions the agent must ask you about before it takes them.
  • Intelligence sets how much reasoning the agent puts into a task, and what that costs.
The choices are the same everywhere in Z360. What changes from place to place is where you set them and where the starting values come from. This page explains the choices first, then each place.

The two controls at a glance

On a Work pipeline, the Intelligence control is labelled Reasoning mode. It is the same control with the same three choices.

Approval policy

The approval policy sets how often the agent stops and waits for a person.

What an approval covers

Approvals apply to actions in Z360 and in your connected apps: creating, changing, sending, and deleting. Searching the web, reading a file you attached, and searching your knowledge base never need approval under any policy.

How Auto decides

Think of Auto as a safer version of Full access. The agent keeps working without stopping to ask you all the time. Before a serious action that you did not ask for, it pauses and asks you to review. Runs on its own, which is almost everything:
  • Looking things up: searching, listing, checking availability, reading a record
  • Creating and updating records as part of your request: contacts, tickets, notes, reminders, tags, assignments, stage changes, booking or rescheduling an appointment
  • A normal one-to-one email, text, chat message, or call that is part of the task you gave it
  • Any other action that does not clearly match one of the reasons below
Asks first, when the agent is about to do one of these without being asked:
  • It cannot be undone. Deleting, cancelling, archiving, or overwriting a record. This is the most common reason.
  • It moves money. A purchase, a refund, or a change to a plan or payment details.
  • It changes who has access. Team roles, security settings, or sharing a file with people outside your organization.
  • It changes something live. Publishing or changing a live agent, pipeline, Expert, or Automation, or submitting an insurance claim or a carrier registration. Creating a new one does not need approval.
  • It reaches many people or shares sensitive details. A bulk send, a public post, sending personal, financial, or health details to someone they are not about, or making a new legal or financial commitment for your business.
  • It is not what you asked for. Acting on a different person or record than the task is about, or going far beyond the request.
Two things to know about Auto:
  • When no strong reason applies, the action runs. Auto does not stop “just in case”, and it does not ask because an action is new to it.
  • What you ask for explicitly runs too. If you tell the agent to “delete the duplicate contact”, it does not stop to ask again. Auto pauses only for serious actions the agent decides on by itself.

Ask for approval

The agent asks before nearly everything it does in Z360, including reading a record it needs. Expect several requests for one task. This is the right setting while you are learning what an agent does. It is tiring for everyday work.

Full access

Nothing waits for approval, including deletions. Choose it only for work you already trust. The agent can still stop to ask you a question when it is missing something. A question is not an approval request, and Full access does not turn questions off.

Respond to an approval request

When the agent needs approval, a card titled Approval required takes the place of the message box. The agent is paused until you answer.
1

Read what the agent wants to do

The card shows the action as a question, such as “Update contact?”, with the details underneath. Check the target record and the values.
2

Approve or reject

Click Approve to let the action run.Click Reject to stop it. Type what the agent should do instead, then click Confirm reject. The agent reads your reason and adjusts.
3

Answer every request

If several actions are waiting, the card shows a count such as 1/3 with arrows to move between them. The agent continues only after you have answered all of them.
For a deletion, the button is red and reads Approve deletion. Approving lets the agent permanently delete the item. Rejecting keeps it.

Change the policy from the card

The approval card has its own approval policy selector, at the bottom left. Use it when you are tired of approving one action after another, or when you want tighter review from here on. The new policy applies to the rest of that conversation. Requests that are already waiting still need your answer.

Find requests that are waiting

A paused agent does nothing until someone answers, so it helps to know where to look.

Intelligence

Intelligence chooses the AI model behind the agent. A higher level reasons for longer and handles harder tasks. It also uses many more tokens, so it costs more.

How to choose

Start on Everyday. Z360 recommends it for most work, and it is included with Platform and Managed plans. Move up a level when one of these is true:
  • The task needs a plan with many steps, and the agent skips or repeats some
  • The answer depends on weighing several records or conversations together
  • A mistake would be expensive to undo
Move back down when the task is done. A higher level does not make simple work better, only more expensive.
Raise the level for one hard task, then lower it again. In an Ask Z chat the control is in the message box, so switching takes one click.

What it costs

Everyday usage is included with Platform and Managed plans, within your plan’s fair-use limits. Advanced and Frontier use many more tokens for the same task and are billed as usage. Rates and promotions change, so check the pricing page before you rely on a number.
  • To compare current rates, go to Settings → Billing → Pricing.
  • To see what was used, go to Settings → Billing → Usage Logs.
See Billing settings for how allowances and the wallet work.

Where to set each control

Each kind of agent takes its starting values from a different place. Where to find the full steps:

How the kinds of agents differ

  • Ask Z chat. You are in the conversation, so you set both controls yourself and answer requests as they come.
  • Inbox agent. It works on a customer conversation that your organization assigned to it. In Auto, replying in that conversation and updating that customer’s records count as routine. Acting on a different conversation does not.
  • Automation. It runs without anyone watching. On Ask for approval or Auto, a run can pause and wait until someone opens it, so check the Needs Attention view.
  • Expert. An Expert always works at its own Intelligence level, whatever the chat is set to. Its approval requests appear in the conversation that called it.
  • Work agent. Each Work Item’s agent starts from its pipeline’s settings. The messages it sends to customers go through Inbox conversations, which follow the Inbox defaults.

How your choices are remembered

Each conversation remembers its own approval policy and Intelligence.
  • A change applies to that conversation only. Other chats keep their own settings.
  • A default applies when a conversation starts. If you change the Inbox defaults, a pipeline’s settings, or an Automation’s settings, conversations that already exist keep the values they started with. New ones use the new values.
  • Automations depend on their chat setting. An Automation set to Separate chat for each run picks up new settings on its next run. One set to Continue in the same chat keeps the settings it started with.
To change a conversation that is already running, open it and use the selectors in its message box.

Tips

  • Start tight, then loosen. Use Ask for approval while you learn what an agent does, then move to Auto.
  • Keep Full access for proven routines. It skips every check, including the one before a deletion.
  • Read the details, not only the title. The card shows the exact record and values. Most mistakes are visible there.
  • Say why when you reject. “Use the billing address, not the shipping address” gets a better second attempt than a bare rejection.
  • Check Needs Attention daily. A waiting agent is a stalled task.
  • Leave Intelligence on Everyday unless the task is hard. Step up for one task, then step back down.

Ask Z Expert Modes

Expert modes, previews, and follow-up questions in Ask Z.

Approvals and control in Work

Pipeline defaults, per-Work-Item changes, working hours, and agent questions.

AI Studio Automations

Set an approval policy and Intelligence level for each Automation.

Billing settings

Plans, included usage, and pricing for each Intelligence level.