Can a KYN agent send an email on its own?

Not to anyone outside the company. It drafts, and a person sends. Internal reminders and reports are sent by the agent. A client can lift the gate for a named workflow in writing after 30 days of reviewed, gated operation.

What stops an agent from spending money?

The money gate: payments, refunds, credit notes and price changes wait for an approver. Spend on the model keys is capped per key, and the client holds a kill switch per agent.

How do we audit what the agent did?

Every action is logged in your own account with input, prompt, model, output, time and, for gated actions, the approver. Reports carry the row references behind each figure.

What happens when the model provider goes down?

The agent stops and the queue holds. People keep working in the same mailbox, CRM and books; nothing is lost and nothing is sent. When the provider returns, the queue resumes from where it stopped.

AI governance: what an agent may do alone.

An agent that sends on its own is the risk, not the feature. Every KYN agent runs under one rule: it may read, draft, sort, remind and report by itself, and anything that leaves the company waits for a named person. This page states the rule, the gates and the controls.

Security principles Personal data protection (PDPA)Vendor security FAQ

The rule

Alone: read the mailbox, the CRM, the books and the chat; classify; draft a reply or a document; file; remind a colleague; produce a report. Never alone: send an email or a WhatsApp message to a customer or supplier; make or approve a payment; submit a filing; change a price; delete a record; post to a third-party system. Those wait in a queue for a person with the role to approve, and the approval is logged with the person’s name.

The four gates

Outbound: every message to someone outside the company. Money: every payment, refund, credit note or price change. Filings: every submission to a regulator, a bank or a platform. Deletion: every removal of a record that another record depends on. Each gate has an approver role; a person can hold more than one role, an agent can hold none.

What the log holds

For every agent action: the input it read, the prompt and model used, the output, the time, and for gated actions the approver and the moment of approval. Reports carry the row references their figures came from. The log is in the client’s account and is readable by the client without KYN.

Limits set in advance

Daily caps on outbound volume (45 emails a day per sender on the sales agents). Spend caps per model key. Rate limits on every public endpoint. A kill switch per agent that stops it in one action, held by the client.

How a client changes the rule

A client can move an action from gated to autonomous, in writing, for a named workflow, after the agent has run gated for at least 30 days with its approval rate reviewed. Reminders to the client’s own staff and internal reports are autonomous from day one. The default stays: anything that leaves the company waits.

Failure modes we design for

A wrong classification files a message in the wrong queue; a person sees it at the next review. A wrong draft is edited or discarded before it is sent. A wrong figure on a report is traced to its rows through the log. A model outage stops the agent, not the business: the queue holds and the people keep working in the same tools.

Checked 13 October 2026. When a practice changes, this page changes with it.

Questions buyers ask

Can a KYN agent send an email on its own?: Not to anyone outside the company. It drafts, and a person sends. Internal reminders and reports are sent by the agent. A client can lift the gate for a named workflow in writing after 30 days of reviewed, gated operation.
What stops an agent from spending money?: The money gate: payments, refunds, credit notes and price changes wait for an approver. Spend on the model keys is capped per key, and the client holds a kill switch per agent.
How do we audit what the agent did?: Every action is logged in your own account with input, prompt, model, output, time and, for gated actions, the approver. Reports carry the row references behind each figure.
What happens when the model provider goes down?: The agent stops and the queue holds. People keep working in the same mailbox, CRM and books; nothing is lost and nothing is sent. When the provider returns, the queue resumes from where it stopped.