ResponseCX Platform
The AI Workforce platform. Outcome-priced AI agents that resolve customer work end to end across commerce and CX — cancel orders, process returns, update subscriptions, issue refunds — with audit trails and human escalation. The platform ships as a multi-tenant Next.js app hosted on GKE. ResponseCX is the customer-facing product surface; StateSet is the company and category brand.Architecture
Primary surfaces
Outcome model
The platform sells outcomes, not seats. Each outcome is a verified, end-to-end resolution priced against BPO labor. The canonical contract is the SKU catalog inlib/outcomes/sku-catalog.js.
Two SKUs are live today — Triage Outcome (2.00) — with
the rest in development. See
StateSet Billing for the catalog.
High-Value Actions, by default anything at or above $100, require human approval before the
engine executes them. This is configured per brand in Workflow Studio’s Review Gate phase.
Disputes are persisted in Stripe customer balance transactions, where a negative amount is a
credit on the next invoice. Customers can flag an outcome within 14 days from the Outcome
Accounting Dashboard.
Workflow Studio
The Studio configures a 15-phase Temporal pipeline per brand. New brands can start from a template that pre-fills 14+ phases:
The editor supports a List ↔ Graph view toggle, a
⌘K phase jumper, ⌘S save, per-phase ?
explainers, and a pending-changes diff against the last saved config — so you can see what
you’re about to change before saving.
Org provisioning
Creating an org runs all of this in one request:- WorkOS org created, creator set as
org:admin - Hasura
organizationsandaccess_tokensrows created - Qdrant KB collection created (
{slug}_customer_support) - Default AI agent created
- Stripe customer created
- Workflow engine tenant registered
- Default workflow brand created, from a template if one is specified
- All IDs written back to
access_tokens
API conventions
There are roughly 600 API routes, all behindapplyApiGuards. Every route follows the same
shape:
auth: true (user required), auth: { requireOrg: true },
auth: { requireAdmin: true } (implies requireOrg), and auth: { allowInternal: true }.
Security rules
These are enforced project-wide:Deployment
Auto-deploys on push tomaster. The workflow builds via Cloud Build, runs kubectl set image,
watches the rollout, smoke-checks /api/health, then commits the new tag back to the
deployment manifest so git tracks live state.
Required GitHub secrets: GCP_SA_KEY, GCP_PROJECT_ID, GKE_CLUSTER, GKE_REGION,
GKE_NAMESPACE, GKE_DEPLOYMENT, GAR_IMAGE_PATH.
Related
Public API (v1)
Build and tune agents programmatically.
MCP servers
Agent-building and analytics over MCP.
Onsite chat
Embed the chat widget.
Billing
Outcome SKUs, plans, and disputes.