Limits
You set the limits. Kestrel keeps them.
An agent that can issue refunds needs rules a person can read and a record a person can check. This is how Kestrel handles both.
Rules your support lead can read
A rule is one sentence with one number in it. Change the number and the next ticket follows it. There is no prompt to tune and nothing to deploy.
Approvals where your team already is
When a request goes over a limit, Kestrel asks in Slack or on the ticket and waits. One tap approves it, and the customer never sees the pause.
41sis the typical time to an answer
Nothing happens off the record
Every read, lookup, question and change is written down with the time and who did it. Export the log, or send it to the tools your security team already watches.
Built for a security review
The answers your security team will ask for, before they ask.
Ask for the full security pack and the latest audit report.
SOC 2 Type II
Audited every year. The report is yours to read under NDA.
Your Region
Data stays in the EU or the US, whichever you choose.
No Training
Your tickets are never used to train a shared model.
Single Sign-On
SAML and roles, so only the right people edit a rule.
Delete Any Time
Remove one run or all history. It is gone within a day.
Scoped Access
Each connection can do only the actions you switch on.
Start with one rule and one limit.
Set a refund limit you are comfortable with. Raise it when the first hundred runs give you a reason to.