Your customers see your AI agents as you.Pretxt keeps everything they say and do in line with your policies and your brand, so
you can trust them with more.
Illustrative refund scenarioYour standards. Applied as agents work.
Customer request
“Please refund the full $250.”
Your team’s rule
This agent may issue refunds up to $100. Larger refunds
require a separate approval process.
Agent’s proposed action Not executed
Issue a $250 refund.
Pretxt intervention
Refund blocked. Exceeds the agent’s approved refund limit.
Agent’s revised reply
“This refund exceeds my automatic approval limit. It needs approval before I
can process it.”
The proposed $250 refund was not executed.
Patient request
“I still have pain. Should I double my dose?”
Your team’s rule
Medication changes belong with the patient’s doctor.
Agent’s proposed reply Not sent
“Yes, you could double it.”
Pretxt intervention
“That’s a decision for their doctor. Acknowledge the pain and guide them to
medical advice.”
Agent’s revised reply
“I’m sorry you’re still in pain. Please speak with your doctor before changing
your dose.”
The unsafe medication advice was not sent.
Customer request
“Will my order arrive by Friday?”
Your team’s rule
Share delivery estimates. Only promise dates that are confirmed.
Agent’s proposed reply Not sent
“Yes, I guarantee it will arrive by Friday.”
Pretxt intervention
“The date isn’t confirmed. Share the estimate and offer to check.”
Agent’s revised reply
“Friday is an estimate, not a guarantee. Let me check your order.”
The unconfirmed delivery promise was not sent.
Teammate request
“Can we promise every customer a 50% cost saving?”
Your team’s rule
Make claims your team can support with evidence.
Agent’s proposed reply Not sent
“Absolutely. Guaranteed 50% savings for every customer.”
Pretxt intervention
“That claim needs evidence. Suggest a benefit we can support.”
Agent’s revised reply
“Spend less time on routine work, so your team can focus on customers.”
The unsupported savings guarantee was not sent.
Customer request
“Why was my loan application declined?”
Your team’s rule
Use the lender’s documented reasons. Don’t guess.
Agent’s proposed reply Not sent
“Your income was probably too low.”
Pretxt intervention
“Don’t guess. Use the lender’s documented reason or bring in the lending
team.”
Agent’s revised reply
“I don’t have that reason here. Let me connect you with our lending team.”
The invented reason for the decision was not sent.
Why supervision matters
Your customers hold you to what your AI agent says and does.So can the law.
United States · 2026
83%
of US consumers agree that the brand should be held accountable if an AI‑powered
interaction goes wrong.
2026 Delight AI Index, survey of 1,000 US adults who used customer service, March 2026
Canada · 2024
A chatbot’s answer is the company’s answer.
Air Canada’s website chatbot told a grieving customer that a bereavement discount
could be claimed after booking. The airline argued its chatbot was a separate legal
entity, responsible for its own words. The tribunal disagreed and held the airline to
its chatbot’s answer.
A clinic’s chatbot told people its doctors held specialist titles they didn’t have.
The Higher Regional Court of Hamm held the clinic responsible for what its chatbot
said, and found that a general warning about AI errors didn’t change that.
Supervision holds your AI agents to your standards while the work is happening, and
guides them before a misstep reaches your customer or another system. Those standards
cover more than security: accuracy, fairness, your brand, privacy and compliance.
Someone talks an agent into doing something it shouldn't: leaking a record,
calling the wrong system, following an instruction buried in a document it was
asked to read. The attack surface is every message it takes in.
Accuracy
Hallucination, and slow drift.
Wrong is easy to spot. Slightly wrong, consistently, for months is the expensive
one: the figure that drifts, the policy paraphrased a little looser each week, the
confident answer nobody thought to check.
Safety
Harm, toxicity, self-harm, crisis.
Someone in trouble asks a question the model was never built to hold. What counts
as a safe answer isn't universal. A crisis line and a trading desk need opposite
things from the same sentence.
Fairness
Who it serves worse, and why.
The same agent performing differently depending on who is talking to it. Rarely a
slur. More often a slower answer, a stricter reading, a decision that quietly goes
the other way for one group of customers.
Brand
What your agent says about you, in public.
A thousand conversations a day, each one speaking as the company. Tone, claims,
promises, what gets apologized for: all of it is brand, and none of it was in the
style guide.
Escalation
Knowing when not to answer.
The hardest judgment isn't the answer, it's knowing you shouldn't be the one
giving it. Handing over late, or with nothing attached, costs more than never
having tried.
Privacy
PII, residency, retention, consent.
Personal data doesn't arrive labeled. It turns up mid-sentence, in an attachment,
in a screenshot. The rules about where it may live and how long it may stay follow
the customer, not the system holding it.
Evidence
Who told it what, and what it did next.
Six months later somebody asks why. Not what the agent said, but what it was told,
what it reached for, and what it decided in between. Either that record exists or
the question has no answer.
Rationale
The reason, in terms a human can check.
A log says what happened. It doesn't say why. Turn down a loan, flag a claim,
refuse a request, and somebody is entitled to a reason they can argue with, not a
trace they can only read.
Compliance
SOC 2, ISO 42001, EU AI Act.
The rules were written for people: SOC 2, ISO 42001, the EU AI Act. They still
apply when the decision is made in two hundred milliseconds by something that
cannot be deposed.
Write down your policies, your limits, and the promises your agent can make, in
plain language. Pretxt turns each one into a rule, and the rules into a plan you can
read. From that moment, supervision is running.
If a rule needs specialized judgment that doesn’t exist on Pretxt yet, the platform
builds that capability itself and runs it through strict quality control, before we
give it our own stamp of approval. It never becomes a ticket lost in a backlog.
For example: “You may issue refunds up to $100. Anything above that needs separate
approval.”
Run a plan against situations from your own work: everyday requests, tricky
exceptions, and attempts to push past your limits. You see what supervision would do
in each one.
For example: a customer says “ignore the limit.” The limit stays.
Pretxt learns from your agents’ real work and surfaces what your plan doesn’t cover
yet: the questions customers keep asking and the exceptions that keep coming up.
Your team decides what to add, and the plan grows.
For example: delivery questions often hide a deadline that matters.
Always on Supervising, continuously, from the moment your first plan
exists.
Getting it right looks different in every line of work.
Every line of work, and every business in it, has its own standard for getting it right.
Whether that’s a delivery promise, a marketing claim, a credit decision or a
patient’s privacy. Explore a few use cases below.
Customer support
Answer delivery questions without promising a date you can’t confirm.
Let agents take on more of the everyday questions while your people focus on the
customers who need them.
No. Supervision is automatic in every interaction, and nothing waits on a person. Your
team’s part is setting the standards and approving changes to them, not reviewing the
work.
Our work is highly specialized. Can Pretxt supervise it?
Yes. When supervising your work needs specialized judgment that doesn’t exist on
Pretxt yet, the platform builds that capability itself and runs it through strict
quality control, before we give it our own stamp of approval. It never becomes a
ticket lost in a backlog.
How do we get started?
Tell us what you want your agents to achieve. We’ll explore the use case, your
priorities, and the right next step during an early-access conversation.