AI chatbots for your website and your company knowledge — answers with sources, not guesses
Visitors ask the chatbot on your site in their own words, in Hebrew, English or Russian, and get an answer from your pages, price lists and documents, with a link to where it came from. When the answer isn't there, the bot says so and takes their details for your team.
- Answers from your content, with a link to the source
- Hebrew, English and Russian, right to left done properly
- Says “I don't know” and hands over to a person
What is an AI website chatbot, and what do we build?
An AI website chatbot is a chat window on your site that understands questions in plain language and answers from content you approve: your pages, FAQ, price lists and documents. DDreamLab, a software company in Netanya, builds chatbots that reply in Hebrew, English or Russian, link each answer to its source, send leads to your CRM and hand the chat to a person. We also build internal assistants that answer staff questions from company documents (RAG).
What happens when answers are hard to find?
The answer is on your site, but nobody finds it
Delivery times sit on one page, the cancellation policy in the terms, the price list in a PDF. Visitors don't dig. They close the tab, or they call and ask you what's already written there, in the middle of your working day.
“Leave your details and we'll get back to you”
A contact form filled in at 23:00 on a Thursday means an answer on Sunday at best. Many visitors never fill it in: they have one quick question, want the answer now, and move on to the competitor whose site gave them one.
A generic AI widget that makes things up
Plug-and-play chat widgets on a general-purpose model sound fluent and confident, including when they're wrong. They invent a discount, commit to a delivery date or quote a price you changed last month, and your team is left explaining it to an unhappy customer.
Company knowledge lives in one person's head
Procedures are scattered across Google Drive, old emails, PDFs and the team's WhatsApp group. New employees keep interrupting the one colleague who knows, and when that colleague is on vacation or called up for reserve duty, everyone waits.
How we build your website chatbot
We pick one job and collect the sources
Answering site visitors, capturing leads or helping staff find procedures: we start with one. You point us to the sources, such as site pages, FAQ, price lists, terms and Drive folders. This is often where outdated or contradictory documents turn up, and we flag them so you can fix them before they go into the knowledge base.
We set the rules
Together we define what the chatbot answers, what it never answers (special prices, legal or medical advice, promised dates) and when it passes the conversation to a person. The bot introduces itself as a bot, and you approve its tone and key wording.
We build the knowledge base and the chat
We turn your content into a searchable knowledge base, connect a language model and build the chat window in your brand, right to left in Hebrew and comfortable on a phone. Leads go to your CRM, email or WhatsApp.
We test on your real questions
You give us questions that customers or staff actually ask, awkward ones included. We run them through the bot, and your team reviews every answer and its source. A wrong or weak answer gets fixed in the content or the rules, not hidden.
We launch in stages and keep it current
The chat starts on a few pages or with one team. We read the conversation logs, and the “unanswered questions” report shows which information is missing. When your site or documents change, the knowledge base updates, and we tune the bot as your business changes.
What you get
- A chat window on your site in your brand, right to left in Hebrew and easy to use on a phone
- A knowledge base built from your pages, FAQ, price lists and documents, updated when the sources change
- Answers that link to the page or document they came from, so anyone can check them
- Clear rules: topics the bot answers, topics it declines and when it hands the chat to a person
- Lead capture: name, phone and the question itself go to your CRM, email or WhatsApp together with the conversation
- An optional internal assistant for staff, with login and access rights by role
- A conversation log and an “unanswered questions” report that shows which content is missing
Where a website chatbot or knowledge assistant makes sense
Accounting office or insurance agency
Visitors ask whether you handle annual reports for an osek patur (exempt small business), which documents to bring, how to file a claim. The chatbot answers from your service pages and guides, and when someone is ready, it takes their name, phone and topic and sends the lead to the right person in the office. Anything that calls for professional advice goes to a human.
Importer or supplier with a technical catalog
“Does this pump fit a 2-inch pipe?” “Is there a Hebrew manual?” The chatbot searches your catalog and spec sheets, answers in the customer's language and links to the right product sheet. When a question needs an engineer, it collects the model and the intended use and passes a complete request to sales.
Chain or franchise with several branches
Branch staff ask the internal assistant how to handle a return, what's on the opening checklist or which supplier to call. It answers from the procedures head office maintains, with a link to the current version, so branches stop working from a printout that's two years old.
Service company with technicians in the field
A technician at a customer's home asks about an error code or an installation step for a specific model. The assistant finds the answer in the manufacturer's manuals and your internal notes, in Hebrew or English, and shows the page it came from.
Knowledge assistant: ask your company documents in plain words
This is the internal side of the same technology: a RAG chatbot, where RAG stands for retrieval-augmented generation. Before answering, the assistant searches your documents, finds the relevant passages and writes an answer based only on them, with links to the sources. If the documents don't contain the answer, it says it doesn't know instead of inventing one. That matters more than style: a confident wrong answer about a procedure costs more than no answer at all.
- Sources such as Google Drive, Notion, PDF and Word files, your website and internal FAQ, in Hebrew, English or Russian
- Every answer links to the document and section it came from, so staff can check before they act
- Access rights: each employee gets answers only from documents they're allowed to see
- Ask in Russian about a procedure written in Hebrew, and get the answer in Russian with a link to the Hebrew original
- Scanned documents go through text recognition (OCR) first, and we check tables and figures by hand, since that's where recognition errors tend to hide
- An “unanswered questions” report shows which documents are missing or out of date
- Available where your team already works: a web page, an internal portal or WhatsApp
The chat window on your site: what visitors see
The chatbot sits on your existing site as a small window, on most platforms, including WordPress and custom-built sites. It opens in the visitor's language, keeps the whole conversation in view and never pretends to be a person. You decide what it does outside working hours and on Shabbat and holidays: answer questions, take details for a call back after Shabbat, or simply show a short message.
- Right to left in Hebrew, left to right in English and Russian, with mixed Hebrew-English text displayed correctly
- Suggested questions for the first click, so visitors don't face an empty box
- A short form inside the chat when the visitor is ready: name, phone and a summary of the chat reach your team in the language they prefer
- Marketing consent asked separately, and only if you plan to send offers, as Israel's anti-spam law requires
- A privacy notice in the chat, with what's stored and for how long agreed in advance, with Privacy Protection Law Amendment 13 in mind
- Built with the Israeli accessibility standard IS 5568 in mind: keyboard navigation and labels for screen readers
- Loads after your page content, so the chat doesn't hold up your site
Send us a link to your site and the 10 questions visitors ask most. We'll show you how the chatbot would answer them, and where it would say it doesn't know.
Sources and tools it works with
- Website widget
- WordPress
- Google Drive
- Notion
- PDF and Word files
- Google Sheets
- CRM via API
- WhatsApp Business API
- n8n
- Claude API
- OpenAI API
If a system has an API, we can usually connect it. If it doesn't, we'll tell you upfront.
How a project with us runs
The same four steps, whether it's a bot, an integration or a whole system.
Short call
You tell us what's slowing you down and how you work today. We ask questions — and if a ready-made tool fits, we'll say so.
Your partDescribe the task in your own words
Written proposal
Scope, stages and a cost estimate in writing, including who owns the code, the accounts and the data.
Your partReview, ask questions, decide
Build in stages
You see working parts early and try them on real cases. Your feedback goes straight into the next stage.
Your partTest and give feedback
Launch and support
We launch, watch how it behaves in real use and stay on for fixes and improvements.
Your partUse it and tell us what to improve
What the cost depends on
- Where the chatbot works: your website only, or also WhatsApp and an internal assistant for staff
- How much content there is and what state it's in: a tidy FAQ, or hundreds of PDFs, scans and outdated versions
- How the content stays current: a one-time load, or automatic updates from your site, Drive or catalog
- What the bot does beyond answering, such as capturing leads, checking order status or booking, and whether those systems have an API
- Access rights: one public knowledge base, or different permissions for different teams
- Languages: Hebrew only, or also Russian, English and others
- Conversation volume, which drives running costs such as AI model usage and hosting, kept separate from development
We don't publish prices: a chat that answers from twenty pages and an assistant over thousands of internal documents are different projects. After a short call you get a written estimate, with development and monthly running costs listed separately. If a ready-made chat tool covers what you need, we'll tell you that too. Call or message us on 050-854-2579.
Ownership, privacy and accessibility
Your code and data
Ownership of the code and data is agreed in writing before we start: who owns the source code, the accounts and the information is in the agreement — not something you find out at the end.
Privacy by design
We build with Israel's Privacy Protection Law and Amendment 13 in mind: we collect only what's needed, keep secrets on the server and agree with you where the data is stored.
Accessibility built in
Interfaces built with IS 5568 and WCAG AA in mind: keyboard navigation, contrast, screen-reader labels and right-to-left layouts.
Questions about AI chatbots for websites
How much does an AI chatbot for a website cost?
It depends on how much content the bot works from, which systems it connects to, how many languages it speaks and whether your staff also get an internal assistant. There are two parts: building it, and monthly running costs for AI usage and hosting, which grow with the number of conversations. After a short call we send a written estimate with both parts listed separately.
Why not just install a ready-made chat widget?
Sometimes that's the right call, and if it is, we'll say so. A ready-made widget is fine for a simple FAQ. A custom chatbot makes sense when answers must come strictly from your approved content with a source, when leads must land in your CRM with the full conversation, when Hebrew and right-to-left have to work properly, or when staff need internal documents with access rights.
What happens when the bot doesn't know the answer or gets it wrong?
Any AI can be wrong, so we plan for it. The bot answers only from your content; when the answer isn't there, it says so and offers to pass the question to your team. Topics you define, such as special prices, always go to a person. Every conversation is logged, and after launch we review the logs and the unanswered questions and fix the content or the rules.
How well does it handle Hebrew, including our PDFs?
Current language models handle everyday Hebrew well, including typos and Hebrew mixed with English, but not perfectly. Hebrew PDFs and Word files that contain real text work well. Scans need text recognition first, and complex tables need checking, so we test on your real documents before launch. A visitor can also ask in Russian or English and get an answer drawn from Hebrew content.
Where is our data stored, and is it used to train AI models?
We connect to language models through their business APIs and choose plans whose terms say your data isn't used to train the models, and we show you those terms before we start. Your documents, the knowledge base and conversation logs can live in your own cloud account. We agree in advance what is stored and for how long, with Israel's Privacy Protection Law (Amendment 13) in mind.
How long does it take to launch, and what happens afterwards?
The timeline depends mostly on your content: how much there is, how organised it is and how quickly your team reviews the test answers. Connecting a CRM or several document sources adds time. We usually start with one clear job and widen it later. After launch we keep the knowledge base current, review the unanswered questions and update the bot when your services, prices or procedures change.
Show us where your visitors get stuck
Message us on 050-854-2579 or leave your details. Send a link to your site, or tell us which documents your team keeps searching through, and on a short call we'll tell you honestly what a chatbot can answer, what should stay with a person and what it would take to build.
Send us a link to your site and the 10 questions visitors ask most. We'll show you how the chatbot would answer them, and where it would say it doesn't know.
Prefer to talk? Call050-854-2579