Trained on your content
Your pages, your documents, your price list. The answers are yours rather than a model's best guess about your industry - which is the difference between helpful and embarrassing.
A chatbot trained on your own pages, documents and price list - answering customers in Latvian and English around the clock, and handing the real enquiries to a human. Built into your site rather than bolted onto it.
Most of the questions arriving in your inbox have already been answered somewhere on your website. Opening hours. Delivery times. Whether you do that particular thing. Roughly what it costs. They arrive anyway, because asking is faster than reading and because the answer was on page four.
A chatbot trained on your own content answers those the moment they're asked - at eleven at night, on a Sunday, in Latvian or English depending on who's asking. Not a general-purpose assistant with your logo on it, but one that has read your pages, your price list and whatever documents you hand it, and that says "I don't know - here's a human" when it doesn't.
That last part matters more than the clever answers. A bot that guesses is worse than no bot at all: it costs you the enquiry and the trust in the same message, and you never find out it happened. We tune it to hand over rather than improvise, and to hand over with the conversation attached, so nobody has to explain themselves twice.
And it lives inside your site rather than in a third-party window. It carries your design, loads with your pages, and doesn't put someone else's branding in front of your customer at the exact moment they're deciding whether to trust you.
Your pages, your documents, your price list. The answers are yours rather than a model's best guess about your industry - which is the difference between helpful and embarrassing.
It answers in the language it was asked in. For a Latvian business with customers abroad that's the difference between a reply and a bounce.
Tuned to admit it doesn't know rather than to improvise, and to pass the conversation to you with the context attached so the customer doesn't start again.
The question that arrives at eleven at night gets answered at eleven at night. The ones actually worth your attention still reach you - that's the point of the handover.
Built into the pages rather than dropped in as a vendor's floating window, so it carries your typography and your colours and not a logo you're paying to advertise.
When your prices or services change, so does what it tells people. A chatbot quoting last year's price is worse than no chatbot, so keeping it current is part of the work rather than an afterthought.
The number depends on how much content it has to learn, how many languages it answers in, and what should happen when it can't answer. Scoped into one fixed offer like everything else here.
quoted
If it's part of a new site or a redesign, it's quoted inside the same offer rather than sold to you afterwards as a second project.
quoted together
A bot whose answers went stale is a liability. We agree how it stays current - and what that costs - before it goes live, not after.
agreed up front
"Quoted per project" isn't evasion here. A bot answering six questions about opening hours and a bot reading a two-hundred-page price list are different jobs with an order of magnitude between them. Tell us which one you need and you get one fixed number before anything starts.
That's the failure mode worth engineering against, and most of the work goes into it. It answers from your content rather than from general knowledge, and it's tuned to hand over rather than fill a gap. Before it goes live we test it against the questions you actually get, not the ones we hope it handles.
Whichever fits the job and the budget, and we name it in the offer rather than keeping it vague. What matters more than the model is what it's allowed to read and what it does when it doesn't know - those are decisions, not defaults.
They come to you, and they're worth reading: a month of them is the clearest list you will ever get of what your website fails to explain. Where they're stored and what the provider does with them is something we put in writing before you agree to anything.
It can be wired to, and whether it should is a real question rather than a feature request. Answering is low-risk; transacting is not. We'd rather it qualified an enquiry well and handed over cleanly than took a booking it half-understood.
No. It can go into a site we didn't build, as long as we can reach the content it needs to learn. If the website itself is the reason people are asking in the first place, we'll tell you that too - sometimes the honest answer is a clearer page, not a bot.
No site yet? Send your business name and a few words about what you sell. We agree the structure with you, then give you one fixed price that doesn't change mid-project.