Deploy a working chatbot, embedded as a chat bubble on a live test web page, for a real business you chose in task 1. It must answer that business's five real FAQs, greet visitors on its own brand, fall back gracefully instead of guessing when it doesn't know, and capture a visitor's name and email. Then prove it works: submit a 60-second screen recording of the live bot in action plus your written support-hours-saved estimate. This is the first real asset in your portfolio, built end to end with no code.
Reuse the five FAQs and the cost math you already produced in tasks 1 and 2 — this project assembles work you've mostly done, it doesn't ask for new material. If the bot invents answers, the fix is almost always in the system-prompt/instructions ('do not guess; if unsure, use the fallback line'), not in the FAQ text. When embedding, always use the page builder's Embed/Code block, never a text block, or you'll see raw code instead of a bubble. Keep the recording plain and under 60 seconds; owners trust a real, unedited screen capture far more than a polished one.
A shareable link like https://flowroom-demo.carrd.co showing a chat bubble in the corner. Clicking it opens: 'Hi! Welcome to Flow Room. I can help with class timings, passes, beginner classes, location, and freezing your membership. What would you like to know?' Asking 'u open sundays?' returns 'We're closed on Sundays.' Asking 'do you sell mats?' returns the fallback handoff. After a pricing question the bot offers the schedule and captures Test Visitor / test@example.com, which appears in the Leads tab. Caption: 'This bot handles ~68 questions/week — about 11 hours and 3,200 rupees of staff time a month at a 75% deflection rate — and captures every interested visitor.'