Enquiries arrive when nobody's online
Evenings and weekends are peak browsing time. By Monday morning that visitor has already bought from whoever replied first.
A chatbot trained on your own pricing, policies and product content — it answers visitors, qualifies leads and books calls while your team sleeps.
68% resolved without a human
2.4s median first reply
5 days from content to live
30+ languages answered
The answer they wanted was already on your site. They just weren't going to hunt for it.
Evenings and weekends are peak browsing time. By Monday morning that visitor has already bought from whoever replied first.
Lead times, pricing, coverage areas, returns. Hours a week restating things that are already written down somewhere on your site.
People want an answer now, not a reply within two working days. Most will not fill the form in at all.
An AI website chatbot is an assistant embedded in your site that answers visitors' questions from your own content — pricing, policies, specifications — rather than from a scripted menu, and hands over to a person when it reaches the edge of what it knows.
The distinction that matters is retrieval. A menu-based bot matches a visitor to a branch somebody drew in advance; an AI chatbot reads the question, retrieves the relevant passages from your material, and answers in your own wording — including for phrasings nobody anticipated. Digital Otters builds, trains and runs them as a managed service. It usually runs alongside AI lead qualification and marketing automation, so a captured conversation becomes a scored, routed lead rather than another inbox item — and alongside AI search visibility work, which is the same problem one step earlier: being answerable to assistants that never reach your site at all.
No procurement cycle, no developer sprint. Three touchpoints and it is answering.
Day 1
Your site, PDFs, price lists and past support tickets. It learns your actual answers — not generic ones scraped off the internet.
Day 3
Tone of voice, topics it must not touch, when to hand over to a person, and what counts as a lead worth passing on.
Day 5
One line of code on your site. Conversations, captured leads and every question it could not answer land in your dashboard.
It quotes your pricing and your policies. If the answer is not in your material it says so, rather than inventing one.
Asks your qualifying questions in conversation, then pushes the contact and the full transcript into your CRM.
Reads your live calendar, offers real slots, and confirms the booking inside the chat window.
When it hits its limit it routes to a human — with the transcript attached, so nobody starts from scratch.
Detects the visitor's language automatically and replies in it, using the same source content.
Every unanswered question is logged, so you can see exactly which gap to fill next.
Set it up on the left, talk to it on the right. This is the same configuration screen you get on day one — the sector, the tone and the permissions all change what it says.
otters init --name="Northwind Blinds" --sector=retail --tone=friendly --capture-leads --booking --handover
It reads order status live, explains your returns window in your own wording, and walks shoppers to the right size or spec before they bounce.
It runs your intake questions, filters out the work you don't take, and books the ones worth your time straight into a slot.
Trained on your docs and changelog, it handles the setup questions your support team answers fifty times a week.
Availability, eligibility and directions answered instantly, with the appointment confirmed before the visitor leaves the page.
Most website "chatbots" are branching menus with a search box bolted on. Here's where the difference actually shows up.
| Menu-based chatbot | Live chat only | A Digital Otters bot | |
|---|---|---|---|
| Unusual wording | Falls back to "I didn't understand that" | Handled well, if somebody is online | Understood and answered |
| Nights and weekends | Answers, but only the scripted paths | Offline form | Full coverage, leads still captured |
| Getting your pricing right | Whatever was hard-coded last year | Depends who is on shift | Pulled from your live source content |
| When it doesn't know | Loops you back to the main menu | A person picks it up | Says so, then hands over with the transcript |
| Changing an answer | Rebuild the flow | Retrain the team | Edit the page, or pin an override |
| Cost at 3,000 conversations | Low, and it shows | Roughly two full-time salaries | One managed plan |
“We were losing every weekend enquiry. Now they're in the CRM by Monday, already qualified.”
Head of Growth · retail client, UAE
If it isn't on this list, tell us — the connection gets built as part of setup.
Move the sliders to match your month. Nothing is sent anywhere — the arithmetic runs in your browser.
$657
Saved per month, after the Growth plan
Conversations handled without a human408
Team hours returned each month41 hrs
After-hours enquiries answered270
Cost of the Growth plan−$649
Assumes a 68% resolution rate without escalation — the median across the deployments Digital Otters runs. Your own rate depends on how much source material the bot is given.
Managed plans include the build, the retraining and the monthly report. Conversation volumes are soft limits — nobody gets cut off mid-sentence.
One site, one bot, the essentials.
$249
per month
For teams treating chat as a sales channel.
$649
per month
Multi-brand, multi-market, with support.
Custom
scoped to markets & systems
Fees exclude third-party tooling and any content work needed where the answers don't yet exist in writing. A one-off build without a managed plan is possible — ask.
It captures the conversation. These are the services that qualify it, route it and make sure people find you in the first place.
It only answers from the content you give it, and every answer is checked against a confidence threshold. Below that line it stops guessing, tells the visitor it does not have that answer, and offers a human instead. Those moments are logged so Digital Otters can close the gap in your source content.
It hands over. Depending on your setup that is a live agent in your inbox, a callback request or a ticket — always with the full transcript attached, so the visitor never repeats themselves.
Your content and conversations are stored in the region you choose and are never used to train shared models. You can delete any single conversation or the whole knowledge base at any time.
Your website URL, any PDFs or price lists you want included, and about thirty minutes to agree tone and handover rules. Digital Otters does the rest and shows you a working bot before it goes anywhere near your live site.
Yes. You can override any response, pin an exact answer to a specific question, and block topics entirely. Changes take effect immediately — no rebuild, no redeploy.
Anything that lets you paste a script tag: WordPress, Shopify, Webflow, Squarespace, HubSpot CMS or a custom build. There is a React component for app-like sites, and a WhatsApp channel if you want the same bot answering there.
Helpdesk bots are usually decision trees with a search box bolted on. This is retrieval over your own content: it handles wording it has never seen, quotes the live version of your pricing page, and escalates with context instead of looping you back to a menu.
We ingest what exists and tell you what is missing. If the answers people ask for are not written down anywhere, that becomes a short content job — and it usually improves the site for humans and search engines at the same time.
Resolution rate without escalation, leads captured, after-hours coverage, and the unanswered-question log. Those four go in a monthly report alongside the conversations themselves, so you can read what people actually asked.
Instantly, from your dashboard, and you keep an export of every conversation and captured lead. There is no lock-in period on the managed plans.
Send Digital Otters your URL and the ten questions your team is tired of answering. We'll come back with what a bot trained on your own pages would say to each of them — and what it would take to put it live.