One line added to your website puts the Adoomi chat window in front of every visitor: answers 24/7 in the customer's own language, drawn only from the pages and FAQs you approved, and a handover to your team the moment a question goes past them. The chat window adds under 32 KB to a page and sets no tracking cookies.
The assistant replies 24/7, in the customer's own language, drawing only on the website pages, FAQs and approved content you gave it. Where that content does not settle a question, it says so and passes the question to a person rather than filling the gap itself.
A question that needs a human becomes a structured enquiry — contact details, what the customer wants, the context around it — routed by email to whoever owns that kind of question. The customer then picks the route: carry on with your team on WhatsApp with everything already said carried across, or take a booking link when a call is the obvious next step. Lead capture, WhatsApp handoff and Calendly bookings each have their own page.
The chat window carries your branding, and its styling is sealed off from the page around it, so it will not fight your site's design and your own stylesheets will not distort it. It adds under 32 KB to a page — a budget the build is held to, not a marketing figure.
Every conversation is there to read, visitors can rate an answer as helpful or not, and the questions your content could not cover collect as knowledge gaps. That list is the honest brief for what to publish next; the knowledge sync page covers feeding it back in.
Point Adoomi at your web address and it reads your public pages — services, prices, policies, opening hours, contact routes — and builds the assistant's knowledge out of what you have already published. There is no knowledge base to write from scratch.
The chat window carries your branding, not ours — and the opening line is yours to set. You review both, and everything it may say, before going live.
Before a customer sees anything, you review what the assistant intends to say and approve it. This is the step worth real time: it is where an answer that is technically drawn from your site, but reads badly or emphasises the wrong thing, gets fixed.
Adoomi gives you one line to paste into your site and the chat window is live. Any website or content management system takes it — WordPress, Shopify, Wix or hand-built alike. Connecting the site, reviewing the answers and adding that line runs to ~10 min in total.
Collects the visitor's contact details, what they need and the context around it, and files one structured enquiry rather than handing your team a chat transcript. Limit: details arrive only when the visitor chooses to give them, because no form stands in front of the answer — someone who gets what they came for and leaves stays anonymous.
Moves the conversation to your team on a WhatsApp number you set, carrying the original question and the captured details across so nobody restarts from a blank chat. Limit: WhatsApp is a handoff destination, not a second channel — no Adoomi assistant answers inside WhatsApp, and you cannot push a chat there from your side.
Shares your public Calendly link at the point where a call becomes the obvious next step, after the questions standing in front of the booking have been answered. Limit: Adoomi never reads your calendar, so the assistant cannot say which slots are free; the visitor picks a slot on Calendly's page and Calendly sends the confirmation.
Keeps the answers current by re-crawling your public pages on a schedule and again when a source changes, and takes PDF, Word and plain-text uploads for facts that never reached a page. Limit: public pages only, and no live feeds — anything behind a login has to be uploaded, and stock or prices are as current as the last sync rather than as current as your till.
CustomerDo you fit them as well, or is it supply only? And do you come out as far as Bath?
AdoomiFitting is included — the site lists supply and fit as standard on every made-to-measure build — and Bath sits inside the coverage area published on our service page. Anything else you would like me to check?
CustomerGood. What would a garden studio with insulation and electrics come to, and could it be finished before Christmas?
AdoomiPrice and lead time both depend on a site survey, so I will not guess at either — that is the team's call, not mine. I can put the question in front of them tonight. What is your name and the best email, and roughly where are you?
CustomerRob Ferris, and I will leave my work email. We are just outside Bath, and access down the side of the house is tight.
AdoomiThanks Rob. That is with the team now and will be waiting when the office opens. If you would rather carry on from your phone, I can move us over to WhatsApp and they will pick it up there with everything you have already told me.
Your teamEmail alert, first thing Monday: Rob Ferris, just outside Bath, garden studio with insulation and electrics, tight side access, asking about a pre-Christmas finish. Asked on a Sunday evening, with nobody at a desk.
The two questions the website already answered were answered. The two it could not settle, the price and the date, became an enquiry rather than a guess — the rule the whole page runs on. Nothing was installed for any of it beyond the one line on the site, no cookie was set, and the office found a complete enquiry on Monday morning instead of a missed visitor.
The chat window on your own site is the single channel. The AI phone agent is waitlist only and cannot be switched on today, and there is no social-messaging or in-app version. WhatsApp is where a conversation is handed to your team, not somewhere the assistant answers.
The assistant is designed for the pages any visitor can reach. It has no view of a signed-in customer's account, order or booking, so it can explain your returns policy from a published page but cannot look up one person's order, and it cannot act inside a logged-in area on their behalf.
A thin website gives thin answers. Where your pages do not cover something customers keep asking, the assistant hands the question over instead of inventing a reply, and it will keep doing so until someone publishes the fact or uploads it. The knowledge sync page covers fixing that.
The assistant will not quote a price, a lead time or a guarantee your content does not support, and sensitive enquiries route to a named person. Some conversations therefore end with the team confirming rather than with an answer — deliberately, because the alternative is a confident wrong one.
Nothing is stored persistently in the visitor's browser and no tracking cookies are set, so someone who comes back next week starts a fresh conversation rather than being recognised. That is the deliberate trade for a chat window that does not follow people around.
Adoomi gives you one line to paste into your site, and the chat window appears. Any website or content management system takes it — WordPress, Shopify, Wix or hand-built alike. Connecting your site, reviewing the answers and adding that line runs to ~10 min in total.
The chat window adds under 32 KB to a page, a budget the build is held to rather than a claim made for a brochure. Its styling is sealed off from the page around it as well, so it will not fight your site's design and your own stylesheets will not distort it.
Adoomi answers only from the website, FAQ and approved content you gave it, and you review what it may say before go-live. A question your content does not cover becomes a handover: the assistant says it cannot confirm, captures the enquiry and passes it to a person.
The assistant replies in the customer's own language, 24/7, from the same approved content — a visitor who opens the chat in Polish or Spanish is answered in it, with no translated copy of your site to maintain. The multilingual setup page covers how that is reviewed.
The chat window sets no tracking cookies and keeps nothing in the visitor's browser between sessions, so a conversation does not follow anyone around your site. Everything sits on EU-hosted infrastructure, with GDPR data export and deletion built in.
Plans start free: £0 a month for 50 message credits, then Local £8 for 200, Growth £20 for 500 and Scale £75 for 4,000. One credit is one AI answer, so a conversation of several questions spends several credits. A credit is one AI answer — handovers, email alerts and booking links are part of how an answer ends.
A scripted chatbot walks visitors down pre-written flows and dead-ends the moment a question isn't in the tree. Adoomi answers from your approved website content in the customer's own words, and when it can't answer it hands over to your team — a person, not a dead end.
Adoomi starts with your public business knowledge and routes the moments that need a person to your team.