Grupo Nova Blanca

Three languages on one site

Nova Blanca looks after gardens, pools and palms on the Costa Blanca and does landscape design. Its clients are Russian-, English- and Spanish-speaking. A site in one language simply does not work for half of them.

So the landing page was built in three languages from the start: Russian, English and Spanish. Switching is instant, with no page reload. It is not just the headings that change: buttons, statuses, captions and the AI chat's replies change too.

The chosen language is remembered. Someone comes back a week later and the site opens the way they left it. A small thing that people only notice when it is missing.

A window in the corner

Two or three seconds after the page loads, a small window with a greeting appears in the bottom right corner. Not a full-screen popup, no dimmed background, no countdown timer. It is simply clear that you can write here and get an answer now.

A window in the corner is easy to ignore, and that is a deliberate choice: the visitor is free to scroll through the page in peace. Behind the window is not a scripted bot with buttons and canned options. It is an AI staff member called Alex, trained on the company's services and the specifics of the region.

The height of a palm

Garden care does not fit neatly into a price list. The cost of pruning depends on the height of the palm, the cost of cleaning tiles on the type of dirt, and a pool is better serviced twice a month rather than once the water has turned green.

Alex keeps these reference points in mind. He explains the difference between a one-off clean and a contract not as a list of packages, but the way a manager who has worked a few seasons in the region would. That is the main job at first contact: not to send a price list, but to explain why the price is what it is.

One or two questions

A form kills the conversation. So Alex does not roll out a list of fields; he asks as he goes, one or two questions at a time, at the moment it makes sense.

The client thinks they are just checking a price. By the end of the conversation Alex already has:

• what is needed and how much of it
• the property's parameters: area, pool volume, number and height of palms
• name, phone number and exact address
• the format: one-off or ongoing
• the details that matter to pass on to the manager

He detects the language himself, from the first message. If the client has a pool, he will ask about the garden too. Once, without pushing.

Every visitor gets their own Session ID. Someone closes the tab, comes back in the evening, and Alex remembers what they discussed during the day. Not a set of separate messages but one continuous thread.

A lead in Telegram

Once the details are collected, the conversation ends and a complete lead lands in the manager's Telegram. Name, contact, address, the request itself, the details and the language of the conversation.

The manager does not exchange messages, does not ask for the address again and does not pick through screenshots of someone else's chat. He steps in at the call and site-visit stage, when everything is already known. From the client's message to the notification on the phone takes a few seconds.

What Alex does not do

He does not quote an exact figure. He knows the reference points and explains what the price depends on, but the final number is worked out by a person, after a call and an inspection. You cannot prune a palm blind, and you cannot quote an exact price for it blind either.

The second limitation is worth stating plainly. Leads here go to Telegram, not to a CRM. While the volume is small, that is enough: the manager sees the message and calls. But a chat is a notification channel, not a funnel. It keeps no client history and tracks no deal status, and at scale that needs a separate module.

And we are not giving figures for this project. We do not have consolidated statistics for a period, so this case is about the mechanics, not about growth percentages.

The keys to the content

The owner changes the text and photos himself. The site has a CMS panel with a login: sign in, tweak a service description, swap a photo after the season. No developer and no technical knowledge needed.

The rest is under the hood: meta tags, Open Graph, semantic markup, load speed, a full mobile version. Most people open a site like this on a phone, standing in the yard next to those very palms.

The site greets the client, answers questions, collects the details and passes on the lead. The manager arrives to a conversation that is already done.