Where your data runs, who approves what, and what we don't have yet.
This page is written for the person who has to sign off on Settl. It says where conversations and order data live, which outside services see them, how money is gated, what is recorded, and — plainly — which certifications and controls Settl does not have today.
Your infrastructure, or ours. Either way, one network.
Settl is a set of services — the inbox, the agent, the database, the voice worker — that run together on a single host or cluster. We can run them for you, or deploy them inside your own cloud account or data centre, where conversations, order lookups and the knowledge base never leave your network. The inbox is the open-source Chatwoot helpdesk; the database is Postgres. There is no shared multi-tenant store of your customers' conversations on our side when you self-host.
Traffic to the web app and the inbox is over TLS; the app host sits behind a single signed login, and the only path outside it is the voice signalling socket, which is authenticated by a per-call token.
Exactly one kind of outside call: the model.
The agent sends the text it needs answered — the customer's message, the retrieved policy passages, the live record it read — to the AI model provider you choose. That provider is a setting: Gemini, Anthropic or OpenAI, under your own account and your own data-processing terms with them. Switching provider is a configuration change; the retrieval, the actions and the scoring are the same whichever is behind it. For voice, the speech provider is likewise your choice. Nothing else about a conversation is sent to any third party.
Nothing moves money without a person — and your backend has the last word.
Every action is either a read or a write. Reads — order status, rider position, vehicle telemetry, a payment record — run automatically. Writes — refunds, credits, cancellations, reschedules, remote vehicle commands — go through a policy with a cap you set, and an identity check first: the contact on the conversation must match the customer on the order. Below the cap the agent acts; above it the action waits in an approval queue for a named person. Your own system then enforces its rules on top, so a delivered order cannot be cancelled and a refund cannot exceed the order, whatever the agent proposed.
Answers cite their source, and an unsure agent says so.
Replies are built from passages retrieved from your own policy documents and carry those citations. Below a confidence threshold the agent does not guess; it hands the conversation to a person with a written briefing. Every conversation is then scored by an independent judge against your scorecard — identity verified, policy applied, escalation correct — and a regression in simulation blocks a release.
Who did what, when, on whose approval — the AI included.
Each case carries a timeline of every message, lookup, action and approval. CRM records keep field history, score history and dealer-assignment history with the user who made each change, and changes made by the AI are recorded the same way. Setup changes — rules, caps, policies — are logged with who changed them. Calls are filed with their transcript.
What Settl does not have today.
A security review should know these before the first call.
- No SOC 2, ISO 27001 or similar certification. Settl is a small company; a formal audit is planned, not done.
- No automatic PII redaction before text goes to the model provider. The provider sees the customer's message as written; choose the provider and terms accordingly.
- Encryption at rest is your infrastructure's. When self-hosted, disk and database encryption are whatever your cloud or data centre provides; we configure to it, we do not replace it.
- No published penetration test yet. We will share the results of the first one with customers under NDA.
- Single sign-on is not yet supported for the agent workspace; access is by individual login.
Self-hosted or managed
Docker services on your cloud account or ours; Postgres and Chatwoot underneath.
One signed login per workspace
Agent, customer-demo and inbox surfaces behind sign-in; voice joins by per-call token.
Checked before every write
The conversation's contact must match the order's customer before anything changes.
A named person above the cap
Refunds, credits, cancellations and vehicle commands wait in a queue with the evidence.
Timelines and field history
Every case step, every CRM change and every setup change, with who did it.
Your data in a standard database
Conversations in Chatwoot's Postgres and cases in Settl's, exportable with ordinary tools.
Frequently asked
Can Settl run entirely inside our network?
Yes. All services — inbox, agent, database, voice — can be deployed in your own cloud account or data centre. The only outside call is to the AI model provider you choose, under your own account with them.
Which AI providers see our customers' messages?
Exactly one, the one you configure: Gemini, Anthropic or OpenAI. The agent sends the message, the retrieved policy passages and the live record it read. There is no automatic redaction today, so the provider's data terms matter; we will help you pick.
Who can approve a refund?
Anyone you give the agent workspace login to; the approval is recorded with their name on the case timeline. Caps and the list of actions that need approval are edited in Setup, and those changes are logged too.
Is Settl SOC 2 certified?
No, and this page says so rather than implying otherwise. If a certification is a hard requirement for procurement, Settl does not meet it today.
How do we leave?
Your conversations are in Chatwoot's Postgres database and your cases and CRM records in Settl's; both export with standard database tools. Policy documents and adapters are yours.