A digital assistant that welcomes every visitor.
A trained digital assistant right on your website that guides the customer from the first question all the way to a booking, inquiry or contact — and when they come back, it recognises them and picks up where you left off. Works around the clock, talks and types, and looks like part of your site.
It's not a chat widget. It's not an FAQ search.
It's a digital assistant on your website.
A website assistant isn't a box in the bottom-right corner. It's a digital assistant that's first in contact with the customer and leads them from the first question to a booking, enquiry or contact.
What the assistant actually does.
Actions it can perform on its own.
- 01Answers a question from your knowledge base (opening hours, pricing, terms)
- 02Navigates the visitor directly to a specific page, product or service
- 03Books an appointment, viewing or meeting in the connected calendar
- 04Checks the availability of a product, service or time slot in real time
- 05Creates a contact in the CRM with the full conversation history and UTM attribution
- 06Sends documents (a quote, PDF, photos, a syllabus)
- 07Handles a query about order, delivery or appointment status
- 08Qualifies an enquiry through 3–5 questions and hands it to sales
- 09Sends a link to pay the balance, fill in a form or complete an action
The customer asks. The assistant checks and answers.
A real conversation on the website. No forms, no waiting.
You don't have to choose. Typing and talking in one window.
Same brain, same knowledge, same actions — only how the visitor communicates changes. They type, or say it out loud. They can switch anytime, mid-conversation, with one tap.
Trained once, speaks two ways
Your products, pricing, rules and integrations are shared. Whether the visitor types or talks, the same assistant answers from the same data.
Chat and voice, switch anytime
The visitor picks what suits them — and switches mid-sentence. The most natural experience: type, or say it out loud.
Start with one, add the other
Launch just typing and add voice later — no new deployment. It's the same assistant, just a new mode.
And whichever combination you choose, you run it from one dashboard — history, stats and escalations in one place, free with every solution.
Looking for a mode where the visitor speaks instead of typing? See the Voice assistant →
Want the visitor to be able to type as well? See the Website assistant →
The customer never has to repeat themselves.
They start typing on the web, finish by phone or e-mail — and the assistant recognises them there too. No "please send it to us again", no filling in the same thing twice. For the customer it means the company has them covered, wherever they reach out from.
Remembers the context
It knows who the customer is and what they dealt with. It never starts from zero.
Picks up the last conversation
It continues where you left off — even a day or a week later.
We connect it to assistants elsewhere
Also have phone or email? We connect the assistants, they share context — and the customer repeats nothing.
Five contexts in which it communicates on the web.
Web traffic isn't homogeneous. A visitor arrives from different sources, with different intent, at a different stage of deciding. The assistant recognizes the context and adapts the conversation accordingly.
A cold visitor from search
Someone who just landed from Google. The assistant welcomes them, finds out their intent, navigates to relevant content — without pushing.
A return from an ad or newsletter
The visitor arrived with a specific expectation. The assistant knows the source (UTM) and picks up on what the ad or email promised.
An existing customer
If they're logged in or identified, the assistant finds their history in the CRM and communicates with the full context of orders or services.
A visitor with a specific transactional need
Booking, availability, a return, an invoice. The assistant performs the action or escalates to a human with the full history.
An aimless browser
Someone who's just looking around. The assistant stays quiet and opens a conversation only on an explicit signal — it doesn't overload.
What you customize on this assistant.
We don't build templates. We build the website assistant individually based on how your company and your website work.
Style and tone
How the assistant welcomes and guides a visitor — from formal to friendly, brief or detailed. All in your brand's tone.
What it can do
Welcoming, website navigation, qualifying enquiries, bookings, recommendations, performing actions — you define the scope.
What it knows
Your services, catalog, pricing, availability, FAQs and internal rules. Trained on the reality of your company.
Connections
CRM, booking system, inventory, calendar, helpdesk and internal software — it works with live data.
In your brand's design
Colors, the assistant's name, window appearance, message style and a strategic pop-up — notification bubble, message preview, proactive greeting and its timing.
Handover to a human
When and to whom to hand over — with the full conversation context. You set the rules to fit your team.
Every solution bespoke
Plus anything else — it's up to you what the assistant should know, do and which features it has.
With every assistant you also get a free dashboard — conversation history, statistics, escalation overview and live conversations where your team can take over the chat directly from the overview.
How the assistant is trained on your company.
The web is often the customer's first contact with you. Training therefore focuses mainly on the first impression and page context.
Tone of the first message
How the assistant starts a conversation — formal, welcoming, playful. We calibrate it from your existing website copy.
Knowledge base
Services, pricing, terms, opening hours, availability. The assistant draws only from approved sources.
Context-based responses per page
The assistant knows which page the customer is on. It reacts differently on the contact page than on a product page.
Rules for proactive outreach
When to offer help, when to stay quiet. It can't be overloaded, it doesn't pop up every 3 seconds.
Escalation logic
Rules for when to hand over to sales, when to technical support, when to customer service.
Which systems it connects to.
The assistant works with your company's real data in real time. It's not an isolated widget.
CRM system
Raynet, Anabix, eWay-CRM or a custom API. Creating contacts, history lookup, conversion attribution.
Booking system
Reservio, Reenio, Bookio, Rezervace.com extranet or your own calendars. Booking right in the dialogue.
E-commerce platform
Shoptet, Upgates, WooCommerce. Availability, prices, order status, returns.
Inventory / ERP
Pohoda, Money S3, Helios, ABRA, iDoklad. Live data on inventory, delivery times, prices.
Helpdesk
Daktela or your own helpdesk. Escalation continues in the ticketing system with the full history. When a system has no API, we solve the connection another way too.
Analytics
Google Analytics 4, Meta Pixel, Hotjar. Matching the conversation with the visitor's overall journey.
When it hands over to a human.
Escalation is a first-class feature. The assistant knows when to stop handling and hand over.
Customer request
“I want to talk to a specific person” → immediate transfer based on CRM assignment or region.
Complex price calculation
When the standard price list isn't enough, the assistant hands over with a summary of the requirements.
Sensitive topic
Refunds, legal or health questions and other more sensitive situations — a human by default, or a digital assistant by arrangement.
A high-value opportunity
If the qualification score exceeds a threshold or it's a big opportunity, escalation to a senior.
Outside training
A question outside the knowledge base → escalation with a suggestion of what to add.
Operational impact we measure from the first week.
Four layers of reporting — from visitor behavior to impact on revenue.
How the assistant responds
How the assistant responds — what's actually measured.
- Conversation volume, share of proactive vs. reactive
- Response time, conversation length
- Resolved autonomously vs. escalated
What came out of the dialogue
What came out of the dialogue — what's actually measured.
- Bookings / enquiries / orders created
- Conversion rate before vs. after deployment
- Lifetime value of customers acquired via the assistant
What moved off the team
What moved off the team — what's actually measured.
- Reduction in contact-form volume
- Fewer email queries about basic information
- Shifting the team to complex cases
What you learn from the data
What you learn from the data — what's actually measured.
- Top questions → suggested website changes
- Places where visitors hesitate
- Trends by period, campaign, source
What deployment looks like.
Seven steps from the first consultation to production — 7–10 days.
Consultation
Mapping visitor traffic, goals, links to other channels.
Website audit
Analysis of heatmaps, analytics, top pages, the contact form.
Configuration
Tone, context-based responses per page, escalation rules.
Training
Filling the knowledge base, approved answers, examples of good conversations.
Integration
CRM, booking system, e-commerce platform, inventory.
Test operation
Test conversations with the team, A/B on live visitors.
Live operation
Launch across the whole website, weekly reviews for the first 4 weeks.
Thirty minutes to know whether a website assistant makes sense for you.
No presentation. We'll discuss your communication volume, typical customer situations and how the assistant would fit into your processes.
30 minutes. Online. No commitment.