Delivered by our team through its European experience (Evolution Agency, France).
Answers the team corrects itself, without touching the wiring.
For Boly, an event equipment rental company in Haute-Savoie, our team built the website assistant in 2024, then rebuilt it in 2026 on our agent platform so the team keeps control of its answers.
35
questions from the team's FAQ, carried over one per entry
9
buttons from the original menu carried over as they were, with their fixed answers
0
prices invented and no availability confirmed on the team's behalf during testing
Methodology: the results on this page are qualitative. They come from operating the tools and from the testing done before each launch. We publish client-specific percentages only once they are measured and approved.
Context
Boly rents out equipment for events (photo booths, inflatables, DJ gear) and provides DJ services in Haute-Savoie, France. On boly.fr, visitors pick a product, check its availability in the online calendar and book.
The team was losing time answering phone calls about questions already covered on the website. Since 2024, an assistant built by our team has answered them, from the site's information, and sorted each conversation into categories in Airtable. In 2026, the team wanted to edit the content of its answers itself. The starting point:
- A FAQ the team maintains in a table of 35 questions
- A catalog of several hundred products, with their prices, on the online shop
- A welcome menu of nine buttons and its fixed answers, in the first version of the assistant
Challenge
Change tools without the visitor noticing, and without the team losing a single line of what it had written.
Give back control of the content
What the team maintains is a table of questions and answers. It wanted to fix an answer, not redraw a flowchart.
Lose nothing on the way
The menu, the fixed answers, the text the team had reworked and the sending of contact requests all had to move to the new version as they were.
Get prices and emergencies right
Give the price from the online catalog, never confirm availability on the team's behalf, and, when equipment breaks down during an event, give the phone number first.
Solution: the same FAQ, organized differently, and the team in control
The assistant is rebuilt and run by our team on our agent platform. The principle: carry over what exists as it is, and let the team decide when two sources disagree.
- 1
One entry per question
The 35 questions in the team's table become 35 entries, one per question, with a readable title and the original wording kept. An entry that stacks several questions is hard for search to find; one per entry, the right answer comes up. The two questions with no answer become 'To complete' entries the team sees in the console.
- 2
The catalog read from the shop
Each product has its own entry, with its price, read directly from the online shop. When prices change, one command reads the catalog again.
- 3
The same assistant for the visitor
The nine buttons of the original menu and their ten fixed answers are carried over as they were: clicking a button answers without calling the model. The drawn character from the first version stays the avatar, and the colors are taken from the logo.
- 4
The team's work carried over
The text the team had reworked in the first version is set as the new assistant's identity. The practical rules it held (depot, opening hours, deposit, payment, delivery) also become entries in the knowledge base. Where that text and the website disagreed, the team decided.
- 5
Complete contact requests
When a visitor wants to be contacted, the assistant collects last name, first name, email, phone and need, then emails the request to Boly's contact address. It is sent once, when the contact details are given. It replaces the former automation scenario.
- 6
The team in control
The team has its own access to the console, with a role cut for it: it edits the knowledge base entries and the assistant's identity text.
Results
No percentages on this page: we only publish a client rate once it is measured and approved. The results below are observed during testing of the new version.
No price invented and no availability confirmed on the team's behalf during testing
When equipment breaks down during an event, the phone number comes first
A contact request is sent once, with its five fields filled in
The honest framing: the assistant answers with what the team has written. What is missing from the FAQ is not invented: the team adds it itself, in the console.
Stack
Your answers already exist. Keep control of them.
Evaluate your project free with our interactive tools, or book a call: we look at the questions you get on the phone, and tell you what an agent can handle, and what it should leave to your team.