Skip to main content

Design a customer support assistant for an Indian bank.

System design · Pro 3

Short answer

Clarify goals and limits first: languages, channels, which questions it may answer, and what must go to a human. Then: RAG over approved policy documents, read-only tools for account information behind strong authentication, strict guardrails against advice and data leaks, handoff to agents, evaluation before launch, and monitoring of quality, cost and escalations.

Deeper answer

Requirements: users ask in English, Hindi and other languages; answers must follow current policy; no account changes without verification; regulators expect privacy and auditability. Success metrics: resolution rate, correct escalation, customer satisfaction, cost per conversation.

Components: an intent router; retrieval over versioned policy documents with citations; tools for balance or transaction status with the user's verified identity, least privilege and full logging; a response check for forbidden content such as investment advice; human handoff with the conversation summary.

Risks: hallucinated policy, prompt injection through user messages, leaking another customer's data, and wrong answers in regional languages. Address each with grounding, permission checks in code (not in the prompt), and an eval set per language. Roll out to a small share of users, watch metrics, then expand.

What a strong answer covers

Answer it out loud in the mock interview about 2 min

Follow-ups to expect

Common mistakes

Learn it

Design an AI system

Today's AI turns are used

Lessons, roadmaps, videos, practice cards and the code playground stay free with your account, with no limit.