Case study · Product UI
The screens people use to talk to an assistant. A support chat that shows its sources, an agent that checks availability and makes a booking, and questions answered from your own documents. The demos run on scripted conversations, so you can try them without an AI account.
Why it exists
An assistant is only as useful as the screen around it. People need to see where an answer came from, what an agent is doing, and when it needs them to step in.
How it was made
01
Chat apps
History, attachments and a composer that handles long messages, in the same components the rest of the catalog uses.
02
Agents that show their work
Tool calls and reasoning appear step by step, so you can watch an agent check availability and make a booking.
03
Answers with sources
Answers from your own documents cite the page they came from, so people can check them.
04
Try it without an account
The demos run on scripted conversations, so they work for anyone, with no AI key and nothing sent to a model.
Where it is now
Live in the catalog's AI chat chapter. In a client build the same screens connect to a real model and the client's own documents.
Built with
- React
- prompt-kit
- shadcn/ui
Services it shows
Get a quote
Tell us what you'd like built and we'll send a written quote with a fixed price and a dated plan.