
24/7
Cover that no longer depends on someone being available to answer.
70+
The range the assistant has to answer questions about.
20+
Markets the client sells into, which is why multilingual handling mattered.

A heating systems producer with a portfolio of more than 70 products and exports to over 20 countries.
Its customer support ran on manual processes, which is where this project started.
Support leaned on manual work, which drove costs up and response times down, while the information people needed sat scattered across systems.
Every response was written by hand, which pushed operational costs up and reaction times down, with nothing covering customers outside working hours.
Dispersed information made accurate answers hard to reach, and standard systems could not adapt to a user’s context.
Insight into query handling and the effectiveness of support was limited.

What we did
The platform runs on an LLM with retrieval-augmented generation, with a dynamic knowledge base and an administration panel that keep content in the client’s hands.
A responsive full-screen interface for desktop and mobile, with wireframes and mockups covering new chats, resumed ones, error states and animations, and user journeys mapped so navigation stays obvious.
The backend manages sessions and conversations, pulls data from the CMS through agent tool calls, handles multilingual queries and exposes API endpoints to the frontend, with the knowledge base updated straight from the CMS.
Responsive layouts, conversations updating in real time, and interactive touches such as an “AI is typing…” notice and a history of past chats.
Pipelines, environment setup and automated tests carried each release, with QA spanning functionality, security, performance and user testing on a range of devices and browsers. Going live on a dedicated subdomain helps scalability, branding and SEO.
01
The architecture behind the platform, keeping answers tied to the client’s own content.
02
The dynamic knowledge base runs through the CMS already in place, so updating content needs no developer.
03
Pipelines, environment setup and automated tests behind every deployment.
What’s next