Technical Claims Verification Agent
Verifies product, SLA, security and client-result claims before publishing.
- Industry
- IT Company
- Department
- Content
- Team
- Content Production
- Kind
- Assistant
- Approver
- Content Lead
- Code
- CON-05
It extracts every checkable claim from a draft (uptime and SLA figures, ISO 27001 and SOC 2 status, benchmark results, client outcomes, feature availability) and verifies each against the certification register, release records and signed client case-study data. It blocks the piece from publishing while a material claim is false or unverified and logs the result on the draft's task.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: the reference and case-study permissions and signed outcome figures for the clients named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Content Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it updates the draft's task with the fact-check result and blocks or clears it for publishing. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The claims register: current certifications with scope and expiry, published SLAs per service tier, approved benchmark results with method, client outcome figures with sign-off, and the feature availability list by release.
Reads from
the CRM: the reference and case-study permissions and signed outcome figures for the clients named.
Acts in
the project management tool: it updates the draft's task with the fact-check result and blocks or clears it for publishing.
Hands back
An object with verdict (clear, blocked), claims (a list, each with text, kind, status true, false, unverified or needs_rewording, evidence and fix) and blocking_count.
Asks a person when
A material claim is false or unverified and the requester wants to publish anyway, or a client outcome lacks sign-off.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Oldest source for a market statistic (months) | 18 | A market statistic from a source older than this is unverified. |
| Check certification scope | On | When on, a certification claim must match the certified scope (services, locations) as well as its validity date. |
| Client results need the client's written sign-off | On | When on, a client outcome figure is verified only when the client signed it off for publication. |
| Benchmarks need a published method | On | When on, a performance or cost figure is verified only when its test method is on record. |
| Block publishing on | material claims | Which claims stop the piece from publishing until resolved. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A certification claim is true only when the register shows it valid on the publish date and, when on is true, covering the service named.
- An SLA or uptime figure must match the published SLA for that service tier exactly; a rounded-up figure is false.
- When on is true, a client result is verified only with the client's written sign-off on record.
- When on is true, a performance or cost-saving figure without a recorded test method is unverified.
- A market statistic from a source older than 18 months is unverified.
- Block publishing on material claims; SLA, certification and client claims are always material.
See the Technical Claims Verification Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.