Working prototype
Web chatbot with RAG
Answering from a controlled document base rather than with a generic reply.
Ready to simulate
Dossier · Project 05 / 13 · Applied AI & automation
An automation is not a row of logos. Each demonstration states the problem, the steps, the output, the human control and its real level of maturity.
Each demonstration runs in your browser, on fictitious data, and contacts no external service. Four of the seven flows stop and wait for your decision: that is how they work in real life. The status on each card also states its origin: what I built, and what I deployed and adapted from a training programme.
Working prototype
Answering from a controlled document base rather than with a generic reply.
Ready to simulate
Working prototype
Qualifying a request and offering a slot, with a human taking over whenever the framework is not enough.
Ready to simulate
Working prototype
Identifying the priority and proposing a reply, without ever sending on the user’s behalf.
Ready to simulate
Experiment
Keeping the link between angle, format, draft, approval and publication date.
Ready to simulate
Deployed flow · adapted from a training programme
Answering a WhatsApp voice message by querying real stock, then replying by voice.
Ready to simulate
Deployed flow · adapted from a training programme
Booking an appointment by phone and, above all, being able to move it afterwards, because the reference is kept.
Ready to simulate
Deployed flow · adapted from a training programme
From a monitored source to a structured article, with sourced research, internal linking and metadata.
Ready to simulate
Where these flows come from
The first four are mine, designed for my own needs or for a client’s. The last three come from an automation training programme (La Tribu Divisual): I deployed them on my own instance, connected them to my own services, fixed them where they broke and adapted them to my cases. The real work is there, in the commissioning and the debugging, not in the authorship of the diagram. I would rather say so than let you guess.
Prototype, experiment and deployed flow are never blurred together, and the origin of each flow is stated.
The demonstration uses no real client, conversation or document.
Sensitive decisions and outward actions require a confirmation.