A concept AI assistant for a medical equipment maker. It answers customer and staff product questions in about 2 seconds, using only the company's own manuals, and shows the exact page each answer came from. Anything tricky goes to a real person along with the full chat. It cuts support time and gives customers answers around the clock. Concept project by Ascalify.
Getting the exact manual page in two seconds cuts the back and forth of searching. When a question trips up the bot, handing the whole chat to a human keeps context intact.
Exactly! The handoff was the part I cared about most. Nobody wants to repeat their question to a human after the bot gets stuck. The other side I'd love to add is automation: when a chat is handed off, it automatically creates a support ticket, alerts the team on Slack and follows up with the customer.
As a product designer, I’ve never felt like our field was changing as rapidly as it is right now. Tools emerge, you adapt, they disappear. Processes that took hours can now be largely automated, and overall, I feel like a big part of the fun gets lost because of a communication issue: I struggle to tell the tools exactly what I want in enough detail.
I recently stumbled across a few interesting and promising startups that might bring some of that joy back and take the pain out of parts of our work.
Proto is building an IDE specifically for product designers, bringing design and AI workflows closer together. 👩🏻💻
Simulithic uses AI agents to test your app across devices, browsers, and account types, automating test creation and maintenance. 🤳🏼
Composal uses swarms of AI agents to explore product flows and edge cases, finding what breaks before release. 🕵🏻♂️
Native helps marketers decide what to create by ranking ideas based on brand context, performance, trends, and creative feedback. 🦖
An AI customer support chatbot for a fictional Nigerian food delivery business, Lagos Fresh Kitchen. It runs on n8n Cloud and uses Claude Haiku 5.5 as the AI model. The workflow is three nodes: a chat trigger receives the customer’s message, an AI Agent processes it, and the Anthropic Chat Model writes the answer.
How it behaves
The AI Agent has a system message that sets the rules. It must answer only from the business information, never invent prices, areas, hours or policies, and use a fixed fallback line when the answer isn’t there: “I don’t have enough information to answer that accurately. Please contact our support team.”
The business information it knows
Open Monday to Saturday, 9 AM to 8 PM, closed Sundays
Delivers to Lagos Mainland (Ikeja, Yaba, Surulere, Maryland, Ojota, Gbagada) and Island areas (Victoria Island, Ikoyi, Lekki), not outside Lagos
Delivery takes 30 to 60 minutes, with fees from ₦1,000
Menu of jollof rice, fried rice, rice and stew, pounded yam with egusi, grilled chicken, suya and soft drinks
Payments by card, transfer and cash on delivery
Cancellation allowed before cooking starts
No Sunday orders or Sunday delivery, and no event catering
Refunds, complaints and order status go to support
Logging every cleaning action is the part I like most: when a number in the report looks strange, you can follow it back to the fix that changed it. With 585 issues, how did you decide which ones the script fixes alone and which ones it only reports?