Engagements & scoping
You want to know whether your agent is in scope, what a Baseline Assurance Sprint would cover, or what the readiness review involves.
Response: one business day. target You will get either a readiness-review slot or a written decline with the reason — see scope & exclusions.
A run in flight
An assurance run is executing, a result is disputed, or you need a bundle re-issued. Existing customers only.
Response: four business hours. target A suspected false finding triggers the recall protocol — an automated hold within four hours, notice within 24 business hours, root-cause analysis within five business days.
Billing & contracts
Invoices, purchase orders, tax documentation, DPA execution, vendor onboarding questionnaires.
Response: two business days. target Most vendor questionnaires are already answered at the trust centre; sending that link first is usually faster than waiting for us.
Security disclosure
You have found a vulnerability in eval.qa, the qabit adapter, the CLI, or a signed bundle.
Acknowledgement: one business day. target Machine-readable policy at security.txt. Please do not open a public issue before we have replied.
What we will not do on a call
We will not quote a price we have not scoped, estimate a defect count for an agent we have not seen, or agree to evaluate a system where the conflict rules in the Independence Charter apply. If one of those is what you need, the honest answer arrives faster by email.
Before you write
- Scoping — it helps to know your warehouse, roughly how many models are in the semantic layer, and whether a named Business Definition Owner exists. Why that last one matters.
- Procurement — the DPA, subprocessor list and security & data handling pages are the current versions; there is no newer pack behind a form.
- Evaluating us — a full sample report and the bundle verifier are public and need no conversation.