Platform

Runtime + control plane for policy decisions.

decide is integration-first for support teams. Keep execution inside Zendesk or Intercom via API, then use a lightweight control plane for keys, limits, usage, audit exports, and rollout visibility.

Open live demo Start sprint intake

What ships now

Phase 1 is a thin control plane. Support teams do not need another daily workspace; they need predictable runtime behavior and evidence when procurement or QA asks for it.

Integration runtime

Policy routing stays in your existing helpdesk workflow.

/api/decide for yes/no/tie routing plus request_id.
Policy checks through refund/cancel/return/trial notaries.
Deterministic output fields mapped into ticket macros or automations.

Control plane essentials

Visibility and governance for paid rollout and production operations.

API keys, plan limits, and usage metering.
Audit search by request_id with CSV export.
KPI baseline vs current snapshot for pilot readouts.

Zendesk flow in production

Workflow stage	System action	Stored evidence
Route decision	Workflow posts ticket context to `/api/decide`.	`request_id`, decision, ticket id.
Execute policy	Workflow calls the matching notary endpoint with vendor + policy args.	Policy verdict, code, latency, req/resp hashes.
Apply action	Macro/automation issues refund, partial credit, or escalation.	Final action + deterministic rationale.
4. Review + export	Ops lead reviews runs and exports audit CSV for QA/disputes.	Run history linked by `request_id`.

Access model by tier

Tier	Access	Primary use
Evaluate ($0)	Public eval limits, no SLA, short retention.	Validate payloads and deterministic behavior.
Onboarding Sprint (2 weeks)	Scoped private key, KPI baseline/target, weekly readout.	One queue rollout and measured ROI proof.
Core	Higher limits, SLA/support, longer retention, audit exports.	Commercial deployment across support operations.

Public docs and marketing stay on decide.fyi. Authenticated controls expand at app.decide.fyi during sprint and Core onboarding.