[ 01 ]
A product story buyers can actually demo.
Customer web, governed runtime, and reviewer workspace appear together instead of being split across slides and promises.
[ CUSTOMER SUPPORT ACCELERATOR ]
Ship agentic customer
support with real code.
Compass Support Blueprint is the closest thing to training material and production-shaped implementation: a live customer surface, a governed runtime, reviewer operations, seeded knowledge, and clean seams for the buyer team to adapt.
Use it as the sales story, the architecture walkthrough, and the implementation starter all at once.
CUSTOMER WEB + REVIEWER OPS/
RUNTIME + RAG + HITL/
CONFIGURABLE BLUEPRINT/
REAL CODE TEAMS LEARN FROM
[ 01 ]
OPEN SANDBOX
Run the customer-facing support experience and show the live product loop.
[ 02 ]
READ ARCHITECTURE
Walk through the runtime, retrieval, policy layer, and reviewer path.
[ 03 ]
INSPECT MODULES
Point buyers to the exact app, runtime, reviewer, and data surfaces they inherit.
[ 04 ]
REVIEW PACKAGE
Frame the repo as both a sellable accelerator and a practical implementation starter.
[ 01 ]WHY IT SELLS
Closer to a
real implementation.
This is not positioned like a generic chatbot demo. It shows the full support system buyers care about, with enough technical clarity to earn trust.
[ 02 ]
The control points are visible.
Knowledge, policy, workflow routing, human review, and adapters are presented as real seams in the implementation.
[ 03 ]
The training surface is the codebase.
Teams learn from the same repo they later adapt, so there is no handoff gap between the story and the work.
[ 02 ]SYSTEMS: CONNECTED
A support system
buyers can trace.
The landing page maps directly to the codebase: customer UI, runtime orchestration, retrieval, policy checks, adapters, control plane, and reviewer workspace.
NEXT.JSREADY
FASTAPIREADY
LANGGRAPHREADY
LITELLMREADY
QDRANTREADY
OPAREADY
REVIEW QUEUEREADY
OBSERVABILITYREADY
CUSTOMER CHAT WEBENTRY
CX AGENT RUNTIMEROUTE + GROUND + DECIDE
KNOWLEDGE LAYER
POLICY LAYER
PROVIDER ADAPTERS
REVIEW QUEUE
CONTROL PLANE API
REVIEWER CONSOLE
[ 03 ]CODE SURFACES
The pages, services, and
assets buyers inherit.
apps/customer-chat-web/
Customer web
Landing, support sandbox, and branded support experience.
NEXT.JS / TAILWIND
apps/cx-agent-runtime/
Governed runtime
Routing, retrieval, policies, adapters, and traceable generation.
FASTAPI / LANGGRAPH
apps/reviewer-console/
Reviewer ops
Inbox, transcript, evidence pack, and human decision path.
NEXT.JS / LIVE API
data/, docs/, tests/
Training assets
Seed data, evals, docs, and contracts that explain the system.
JSONL / GUIDES / EVALS
[ 04 ]WHAT SHIPS
Everything needed to
show the full loop.
CUSTOMER APP / SUPPORT SANDBOX
GOVERNED CX RUNTIME
REVIEWER QUEUE + CONSOLE
SEED KNOWLEDGE + GOLDEN EVALS
ADAPTATION DOCS + DEMO SCRIPT
DOCKER + LOCAL DEV FLOW
WHY TEAMS LEARN FROM IT
A blueprint is only useful if teams can understand and modify it fast.
blueprint.config.yaml
apps/customer-chat-web/
apps/cx-agent-runtime/
apps/reviewer-console/
data/eval/golden/
docs/adaptation-guide.md
CONCEPTS STAY ATTACHED TO CODE
BUYERS CAN TRACE A REAL SUPPORT REQUEST
HANDOFF IS PRACTICAL, NOT ABSTRACT
[ 05 ]LEARN BY ADAPTING
Closer to real training
than a generic AI course.
[ 01 ]
Run the loop.
Teams can start with the live customer and reviewer surfaces before they ever open the runtime code.
[ 02 ]
Trace the decisions.
The architecture, citations, workflow traces, and reviewer queue make the support path legible.
[ 03 ]
Modify real seams.
Config, workflows, prompts, data, and provider adapters are all visible and ready for buyer-specific implementation.
[ READY? ]
Use the same asset as the sales story, the technical walkthrough, and the implementation handoff.
COMPASS SUPPORT BLUEPRINT · REAL CODE · BUYER-READY
The point is not just to impress a buyer. It is to give their team a believable starting point they can actually study and implement.