Request EvaluationWorkflow evaluation intake

Tell us which AI workflow you want to control.

The form captures only the context needed to route an initial evaluation request. Deeper security, provider, data-class, and production questions can be handled after fit is established.

Start Evaluation Request →
Starter Profiles

Choose the path closest to your workflow.

A starter profile is not a final contract. It is a routing choice that tells Clariva what kind of demo and evaluation will be most useful.

API / SDK Starter

Direct product integration

Choose this if your product or platform needs to call AI providers through a controlled request layer.

  • API request shape.
  • SDK or gateway-style flow.
  • Policy and provider route fit.
See API contract details →
CRM Starter

Sales and account workflows

Choose this if the workflow involves CRM notes, customer summaries, sales calls, or account context.

  • CRM-style workflow path.
  • Customer text and account data.
  • Reviewable AI assistance.
See API contract details →
Support Workflow Starter

Support tickets and conversations

Choose this if the workflow involves ticket summaries, support triage, response drafting, or conversation analysis.

  • Support workflow, webhook, or API path.
  • Customer-message handling.
  • Approved and rejected examples.
See API contract details →
Signed Webhook Starter

Event-based workflows

Choose this if another system will route structured workflow events through the deployed Clariva control layer.

  • Signed request path.
  • Event payload review.
  • Replay and audit behavior.
See API contract details →
Enterprise Control

Stricter review needs

Choose this if you expect custom policy, SSO, deployment-model review, procurement review, or expanded audit requirements.

  • Security review planning.
  • Custom control scope.
  • Production-readiness items.
See API contract details →
Not Sure

Use when the path is unclear

Choose this if you have an AI workflow in mind but are not sure which entry path applies. Share what the workflow does at a high level, and Clariva can help identify the right starter profile during the first review.

Review sample request details →
Evaluation Request

Request a Clariva evaluation.

Use this form when you want Clariva to review a workflow for evaluation fit. Share enough context to route the evaluation request. Keep the request high-level and do not include regulated, confidential, or production-sensitive data.

1

Evaluation request

Share only high-level context about the workflow. Do not include regulated, confidential, production-sensitive, or customer payload data.

Not sure? Select “Not sure yet” and we’ll clarify the workflow during evaluation.

Optional context
2

What happens after you request evaluation

  1. Clariva reviews the workflow category, source system, and AI task.
  2. You receive the closest starter path: API/SDK, CRM/support, signed webhook, or Enterprise Control.
  3. The first review focuses on one workflow, one provider-route pattern, and approved/rejected request examples.
  4. Production scope is discussed only after the control path appears relevant.

Do not include regulated, confidential, customer-sensitive, production, or credential data in this form.

Submission details are used to route the evaluation. Keep the request high-level and do not include regulated, confidential, production-sensitive, or customer payload data. By submitting this form, you agree that Clariva may use the information you provide to respond to your inquiry and process your request as described in our Privacy Policy and Terms of Use.

If this form does not submit correctly, email admin@clarivaprivacy.com directly. Do not include sensitive, regulated, production, credential, or customer payload data.

Evaluation Outcome

What the evaluation clarifies.

Best-fit profile

The closest Clariva path for your workflow: API/SDK, CRM, support, webhook, or Enterprise Control.

Control model

How Clariva checks policy, proof, replay risk, provider route, rejection behavior, and audit evidence.

Production questions

Which items are standard onboarding and which require security, integration, or enterprise review.