Demo: architecture of the Larkspur customer-service assistant
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
design the assistant as a C4 container view with data flows and handover; prepares ARC-045-LAB1.
Draft outline details
Step by step
- Collect the use cases: order status, return start, product questions, and "talk to a person".
- Draw containers: chat widget, assistant service, policy and product index, order and customer APIs (backed by ERP and CRM), model endpoint, and the agent-desk handover.
- Mark data flows and what each carries; the model receives only the question, retrieved text, and selected order fields.
- Planned mistake: give the assistant read access to the CRM database "for speed". Fix: replace it with a customer-summary API scoped to the signed-in customer, with audit logging.
- Design handover: triggers (low confidence, angry customer, refund request, customer asks) pass the transcript and summary to the human queue.
- Choose a deployment option with reasons and note the open provider-term checks.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.