End-to-end autonomous support-resolution corpus

Name: End-to-end autonomous support-resolution corpus: per ticket, triage decisions, auto-resolution vs drafted-reply vs escalation outcomes, the agent's reasoning traces and audit logs, knowledge-retrieval events across a unified support knowledge layer (help desk, CRM, knowledge base, proprietary APIs, public web/social sources), customer profile and entitlement context, account/order/identity resolution links, voice-agent conversation transcripts, and escalation-policy/human-review interventions.
Creator: Crystol AI

CRYSTOL AIManage supplier listing

End-to-end autonomous support-resolution corpus: per ticket, triage decisions, auto-resolution vs drafted-reply vs escalation outcomes, the agent's reasoning traces and audit logs, knowledge-retrieval events across a unified support knowledge layer (help desk, CRM, knowledge base, proprietary APIs, public web/social sources), customer profile and entitlement context, account/order/identity resolution links, voice-agent conversation transcripts, and escalation-policy/human-review interventions.

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Crystol AI and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Application Software
Instruments: equities
Categories: AlternativeSentiment

Dataset card

Type: not stated
Format: Text (ticket conversations, drafted replies, reasoning traces, knowledge passages) + Tabular (triage/escalation/outcome records, entitlement and identity-resolution links) + Audio/transcript for voice agents
Volume: Small — est. 10^4-10^5 tickets with full reasoning-trace/audit records to date; value per record is high (reasoning + outcome + entitlement context + knowledge attribution) but breadth is early
Users: N/A as consumer metric — B2B platform; est. small enterprise/SMB customer base (demo inbox shows 448 tickets resolved; named customers Spearpay and Anchors; near-zero listed headcount) — tens of tenants at best
History: 1 years
Update frequency: not stated
Growth: Active (very early) — live site with pricing, careers page, demo funnel and case studies published; company footprint (0 listed employees on provider record) indicates a tiny founding team
Launched: ~2025-2026 (recent company/provider record; product surfaces like voice agents and MCP integration reflect the current agent-tooling era; case-study dates in 2026)
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site