CX Agent by Conxt

Ask CX-Agent

Describe the case. The agent will find the governed path.

ADVISE

Agent role

Ticket source

Example scenarios

Ticket or scenario155 chars

Read-only in Advise mode. No action runs without authorization.

Identity & evidenceGuardrail inputs

Customer / tenant ID

Invoice / reference

Customer identity verifiedTier-1 authentication passedPayment gateway settledSettled charge rather than pending

Playbook matching, guardrail gates, signed execution

Ready when you are

Choose an example or paste a real scenario. CX-Agent finds the approved playbook, applies its guardrails, and explains exactly what can happen next.

Account context, simulated adapter boundaries, and the append-only session trace

Conxt governed

Customer contexttenant 9482

Customer IDcust_acme_8921

AccountSarah Chen (Acme Labs)

SSO authVerified

Billing stateSettled

Policy enginestandard-governance-v1

Authority conxt_team_memory. Execution requires cryptographically validated short-lived tokens within restricted server-side adapter boundaries.

Simulated adapters3 demo fixtures

Stripe gatewayadapter.stripe.v2

Restricted

Okta directoryadapter.okta.iam

SSO & sessions

Conxt memory storeconxt.memory.governed

Governed memory

Session traceAppend-only