Answering wrong is embarrassing. Acting wrong costs money and trust. So Inflection is built the other way round from a chatbot: every capability starts closed, and the rules that keep it closed are yours to write.
Inflection proposes; a person decides. When Inflection is about to click or type, it stops and surfaces exactly what it intends to do — the action, the target, and the value — and waits.
Name the actions Inflection may only explain, never perform. Closing accounts, deleting data, anything irreversible.
Mark inputs Inflection must never fill, even when a customer asks it to.
Cap what an action may be worth. Above the line, it goes to a human.
When an escalation reveals a rule, Inflection proposes it — and it stays a proposal until someone accepts it.
The safest way to handle a card number is never to receive one. Payment-card and identity-number patterns are refused at the input, not filtered afterwards, and training a login captures the shape of the form rather than what was typed into it.
Because Inflection resolves a specific element rather than clicking a coordinate, every action has a name. That is the difference between a log you can defend and a video you have to interpret. Every entry is attributed too: account-specific actions require the customer's own authenticated session, so Inflection never holds a master key to your customer base and cannot reach one account from another's conversation.
What ran, on which control, with what value, and who confirmed it.
Step through any conversation exactly as it happened.
What was attempted before a human took over.
Who verified a flow, who accepted a boundary, and when.
Deployments are provisioned to a chosen region; conversation history and customer data stay in it.
Encrypted in transit, and at rest on managed storage.
Each workspace's knowledge, memories, flows, and credentials are scoped to that workspace.
Public keys for the browser, secret keys for the server. Rotatable, scoped, revocable.
If none of the above is enough, run the whole stack yourself.
Inflection is early, and we would rather tell you that than imply a badge we haven't earned. Here is the honest status.
If your procurement process needs something specific, ask — we will tell you plainly whether we have it today.
Fully managed. Fastest path to a live resolution, with region selection at provisioning.
Deployed into your own account and region. Your infrastructure boundary, your network rules.
The whole stack — agent runtime, worker, storage, crawler — runs on infrastructure you control.
Pin the deployment to a region so customer data and conversation history never leave it.