MLSD-022 · DESIGN PRACTICE
Practice: Customer-support RAG
Draft the complete decision system before revealing the guidance. Use a 45-minute rehearsal budget and adapt it to the interviewer’s direction.
Preserve eligibility, available-at-decision inputs, mature labels, bounded work and compatible releases. Explain alternatives and test a normal, boundary and failure case.
Your practice draft
Design customer-support RAG for web chat and agent copilot under the synthetic 100-tenant, 50,000-article, 80-turn/s workload. Draw ingestion, identity, knowledge/live-data boundaries, retrieval, grounding, action confirmation, handoff, evaluation and rollout. Then change one constraint: session expires mid-tool call, article is withdrawn during generation or ticketing is unavailable.
Saved locally on this device. The worked answer does not score your draft. Existing lesson notes and completion are separate.
Progressive hints
Hint 1
Separate customer and agent channels, identity, audience visibility and allowed tools.
Hint 2
Keep reusable approved knowledge in RAG; fetch customer-specific state from source-of-truth APIs after object authorization.
Hint 3
Trace a normal answer, live lookup, sensitive action and escalation; include idempotency and safe failure.
Self-review evidence
For each criterion, record Missing, Prompted, Independent or Adaptive reasoning. No automated scoring or offer prediction is provided.
- Channel-specific identity and disclosure policy.
- Immutable article versions, attributed conversation events and evidence provenance.
- Object-level authorization and least-privilege tools.
- Hybrid retrieval, citation validation, grounding and abstention.
- Confirmed idempotent actions and durable handoff.
- Held-out evaluation and mature customer outcomes.
- Bounded capacity, safe fallback, rollout and honest synthetic assumptions.
Reveal worked design guidance
Use governed versioned knowledge ingestion with channel-specific retrieval policy. Derive actor, tenant and scope from verified identity; load bounded attributed context; route to knowledge, live-data or handoff. Retrieve only authorized evidence, fetch customer facts from authoritative APIs after object-level authorization, and validate structured claims/citations before responding. Sensitive actions require confirmation, reauthorization, idempotency and post-write verification. Persist handoff intent and report success only after ticket/queue confirmation. Evaluate retrieval, grounding, policy and mature resolution separately; launch agent copilot before customer automation.
Open the complete worked design in a new tab →The new tab keeps this draft visible. Save it on this device before closing the page.