Sales
“Delete the record” cannot be a robot's click
Looking up a customer's history is one thing; deleting a record changes the system, and someone has to answer for it.
Confirmation first
Platform · Approvals
The AI stops before a sensitive action. A person decides.
It is the brake that lets the company connect AI to its systems: the agent shows the action and waits for Approve or Deny. Here you approve an action, not a text.
See how it worksSkyller · Company CRM · approval
Skyller - AI AssistantCompany CRM · approvalReply to Aurora about the September collection and send the email.
…
Skyller is an AI and can make mistakes. Remember to check.
Demonstration · illustrative data
SAFE · MEDIUM RISK · HIGH RISK · CRITICAL
high risk and critical ask for confirmation by default
ALWAYS · INHERIT · NEVER
company, agent and conversation adjust the rule
APPROVALS INBOX
in the bell and on its own page, only what waits for you
SLACK · TELEGRAM
people on those channels decide there
Where this shows up in your day
Giving AI autonomy is scary until a reliable brake exists.
Customer service
The email that goes out under the company's name
A draft helps; a send makes a commitment. The person wants to read it first, without copying it elsewhere.
Read, approve, send
Management
“Who authorized this?”
When something goes wrong, that is the question. A text “confirm?” in the chat does not survive an audit.
Record of who and when
How it works
From request to action, with a person in the middle.
01
Every function has a risk
Each function gets a level: Safe, Medium risk, High risk or Critical. Delete, remove, archive and send ask for confirmation; change and create go through, unless the company tightens the rule.
02
The company adjusts the rule
The administrator requires or waives approval per function and can lock the choice. The agent and the conversation have their own layer: inherit, always or never.
03
The agent stops and shows
At the moment of action, the agent opens a card with the action and its parameters and stops there, with no text “confirm?”.
04
A person decides
Approve or Deny on the card, in the bell, on the Approvals page or through Slack and Telegram. Read-only viewers do not decide, and the administrator decides for no one.
05
It gets recorded
The decision applies to that call, in that company, with who asked, what it was, who decided and when. With no decision, the pending item expires.
Live proof
Nobody at the screen. The automation stopped anyway.
Starting point
The “Weekly collection” automation, created by the manager, runs at 7 a.m. with the finance agent; “send email to the customer” always asks for approval.
What happens
- 01On reaching “send the collection email to Aurora”, the run stops and waits for approval.
- 02The pending item appears in the manager's Approvals inbox, with the action and its parameters, and the notice arrives in the bell.
- 03The manager approves, the run resumes where it stopped and the item moves to Approved.
Result
The email went out because a person said yes, and the record shows who authorised it and when.
Skyller · Weekly collection · paused run
Weekly collection · paused runMonday 7am routine: check customers with overdue invoices and prepare collection emails for review.
…
Skyller is an AI and can make mistakes. Remember to check.
Demonstration · illustrative data
Good to know
- Only sensitive actions stop; looking things up and writing text go straight through, and the company can reclassify a function.
- The inbox gathers only agent action pauses; invitations and document review have their own screens.
- A pending item with no decision expires, and the run ends without acting.
To evaluate calmly
Where the rule is set, and where the decision happens.
Select a topic to see its capabilities, conditions, and limits.
- Risk per function
- Safe, Medium risk, High risk or Critical on each connected function; high risk and critical ask for confirmation by default, and the company can reclassify.
- Company policy, with a lock
- The administrator requires or waives approval per function and can lock the choice. Once locked, it overrides anyone's preference, in both directions.
- Policy per agent
- Each of the agent's tools has “inherit”, “always ask” or “never ask”: that is how an agent that only read things starts acting with a brake.
- Adjustment per conversation and per person
- The conversation can tighten the rule for the session, and each person can set “always ask” or “always accept” where the company did not lock it.
- Card with action and parameters
- It shows what will be done and with which data. Approve resumes where it stopped; Deny ends that action, and the agent carries on with what it has.
- Approvals inbox
- In the bell and on a page with Pending, Approved, Rejected and All; each person decides their own. Pauses with several actions are decided in the conversation.
- Off screen: Slack and Telegram
- People who use Skyller through a connected channel get the card there, with Approve and Deny, and decide in one click; the inbox shows the same result.
- Automations stop too
- A sensitive action pauses the run; owner and collaborators are notified, and the pending item, which belongs to the owner, shows which automation it came from.
- Record and validity
- The decision is tied to that call and that company, with who decided and when. Every tool call also goes to the activity trail: which one, in which system, by whom and which rule applied.
Real application
Two functions enabled. One of them waits for the manager.
- 01Administrator
In the CRM, releases “look up customer history” with no approval and marks “send email to the customer” to always ask, locked.
- 02Finance analyst
Asks in the chat: “Reply to Aurora about the September collection”. The lookup comes back at once; sending the email stops at the card.
- 03Finance analyst
Reads the card and denies it: the amount quoted in the text does not match what was agreed. The agent answers without sending anything.
- 04Finance analyst
Corrects the amount, asks again and approves. The email is sent, and each attempt has its own record.
- 05Manager
Sees the sequence in the company trail: request, denial, new request and approval. The chat itself stays the person's.
Questions from whoever decides
What people ask before enabling a real action.
Next step
Enable the function you do not let anyone automate today.
Mark the function to always ask for approval, request the action in the chat and see the card before anything happens.