Loading...
Release, inspection and repair for AI agents
Is the agent running today the one you approved?
We check each agent against what you signed, on a schedule and on every change. A fix drafted when one fails. Your team releases. Salesforce and Agentforce first.
Your approvals, your Git, your release.
Inspection reportIllustrative sample
- Discount stays within the approved limitPassed
- Escalates to a human on refund requestsPassed
- Acts only on the approved objectsPassed
- Tone of voice on outbound repliesNot inspected
- Never promises a delivery dateFailed
Issued on a configuration change. Readable without Huscribe.
Register
Order desk assistantInside
Lead responseOutside
Quote builderInside
Model swapped by vendor, 20 Oct
Inspections
AugRe-inspected on changeToday
Fix drafted, awaiting your owner
Three questions nobody in the room can answer today.
Another team widens a permission. Someone edits a knowledge article. The vendor swaps the model. Nobody tells the agent’s owner. Then a customer asks why it promised a delivery date.
What does it actually do?
Not what the deck said. What it did on Tuesday.
When did it break?
The change that broke it was never a ticket.
Why did its answer change?
The model moved. Nobody was told.
| Agent | Owner | Approved to | Today | Last material change |
|---|---|---|---|---|
| Order desk assistant | R. Mensah, Sales Operations | v3, signed 14 Aug | Inside approval | Model swapped by vendor, 20 Oct |
| Lead response | L. Ortega, Sales Development | v2, signed 2 Jul | Outside approval | Knowledge article edited, 3 Sep |
| Quote builder | P. Achebe, Revenue Operations | v1, signed 30 May | Inside approval | Flow changed upstream, 28 Aug |
| Renewal outreach | Unassigned | Not yet approved | Not inspected | Permission widened, 12 Sep |
| Field scheduling | Unassigned | Not yet approved | Not inspected | Found by the readiness check, 1 Sep |
Knowledge article edited, 3 Sep
Illustrative sample. Private pilot. Rows change on events. Nobody has to sit and watch it.
One view of every agent you are accountable for.
Who owns it, what it was approved to do, whether it still does, what changed last. Nothing green by default.
- Who owns it
A named business owner and a named platform owner. No owner is the first finding.
- What it was approved to do
What your people signed, by version: outcomes, prohibited actions, escalations, limits.
- Whether it still does that
Inside approval, outside approval, or not inspected. We say when we have not looked.
- What changed last
The last material change and its source: model, prompt, permission, knowledge article, flow.
- Where the evidence is
Every answer links to its report, in your Git, readable without us.
Start from wherever your agent is.
Builders monitor their own agents. Huscribe checks them for the owner, whoever built them. The release stays yours.
Not live yet
Need it built, or built it and cannot get it released? We take it to a release candidate in your sandbox, your approval attached and the checks written from it. Your team releases it.
Release candidate Order desk assistant, v3
Approval signed by the business owner
Checks compiled from the approval
Tested in your sandbox
Security pack assembled
Your team releases
Built in your sandbox, never in production
Live today
We write down what it is approved to do and check it against that, on a schedule and on every change. You see what held and what moved.
Inspection log Lead response
Scheduled inspectionPassed
Permission widened by another teamRe-inspected
Model swapped by vendorRe-inspected
Knowledge article edited1 check failed
Inspected on every material change
Outside approval
A check fails. We find the cause and draft the smallest change that would pass, evidence quoted. Your owner decides. Your team ships it. We check again.
Finding Failed
CheckNever promises a delivery date
EvidenceTwo replies on 4 Sep, quoted in the report
Proposed causeKnowledge article edited, 3 Sep
Smallest changeRestore the delivery-date rule in the article
Approve the fixReject
Your owner decides. Your team ships it.
Built for Salesforce agents, whoever built them.
One use case today. Agents that act on your Salesforce org, whether Huscribe built them, someone else did, or both.
- Internal agents
- Agents Huscribe designs and builds for your Salesforce org, in your sandbox, with the plans and checks attached from the start. Your team releases them, and they enter the register already inspected.
- External agents
- Agents your team or a vendor built, whether they live in Salesforce or on another platform that reads or writes the CRM. You register them, we inspect them against what you approved, and the evidence lands in the same register.
- Internal and external
- A workflow where an agent Huscribe built hands off to one you already run, or the reverse. The approval describes the whole path, and the inspection follows it across the handoff.
Approve. Release. Inspect. Fix.
01
Approve
Your people write down what the agent may and may not do, and sign it.
02
Release
Not live? We build the candidate in your sandbox. Live? We start from what is running. Your team releases. We never deploy.
03
Inspect
Checks run against what the agent actually did, on a schedule and on every material change.
04
Fix
A failure becomes a finding with the smallest change that would pass. Your owner decides. Your team ships it. We check again.
Security that was audited, not asserted.
SOC 2 Type II
Independent service auditor’s report, available under NDA
ISO/IEC 27001:2022
Certified information security management
Data, access & delivery
Encryption
TLS 1.3 in transit, AES-256 at rest
Data residency
Storage region agreed at onboarding
Separated access
A non-mutating inspection connection, plus dedicated discovery and sandbox identities, each approved by you
Customer-controlled release
We do not deploy to production
Traceable delivery
Requirements, approvals, tests, versions and release evidence, recorded and available to you
Security documentation
DPA, subprocessor list, retention, and deletion details, available during security review
Name one agent. We come back with what it was approved to do and whether it still does.
Show us one agent ↗Prefer to see it first? Book a demo.