Adoomi answers the shop questions your published content already settles — specifications, delivery options, returns and refunds, sizing and care — and captures the ones that need a person, in the customer's own words. There is no live stock feed and no order lookup, so this page is as much about what it will not answer as what it will.
Specifications, materials, sizing, care, compatibility, what is included in the box — the assistant replies 24/7, in the customer's own language, drawing only on the product pages, policy pages and documents you gave it. Where a detail was never published, it says so and passes the question on rather than filling the gap itself.
Delivery options and timeframes, returns and refunds, and what condition an item has to come back in: the assistant repeats the policy as you wrote it. It quotes the published estimate and never a date of its own invention, and it will not soften a rule to keep a sale moving.
A stock check or an order chase becomes one structured enquiry — contact details, the order context the customer gave, and what they actually asked in their own words rather than a tidied-up paraphrase. Email alerts put it in front of whoever handles orders; the customer can carry on with your team on WhatsApp if a phone suits them better.
Asked to look up an order, confirm a stock level or process a refund, the assistant names the limit and moves straight to capturing the enquiry. That is deliberate: a shopper told "I cannot see your order, but here is what I can do about it" is better served than one given a confident wrong answer about their own money.
Point Adoomi at your web address and it reads your public pages — product pages, delivery information, returns and refunds, contact routes — and builds the assistant's knowledge out of what you have already published. Facts that never reached a page, such as a size chart or a care sheet, go in as PDF, Word or plain-text uploads.
Nothing routes anywhere until you give it a destination: the address of whoever actually handles orders for the email alert, and your WhatsApp number if customers should be able to carry on there. Destinations are set per assistant, so a shop assistant and a general enquiries assistant on the same site can route differently.
Before go-live you read the answers the assistant proposes and change any you would not send yourself. Put the hard ones to it — is this in stock, where is my order, can I return something I have worn once — because how it declines is as much a part of the shopping experience as how it answers.
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.
Feeds the assistant your catalogue pages, delivery information and returns policy from a crawl of your public site, plus PDF, Word and plain-text uploads for the specification or care sheet that never reached a page. Limit: there are no live feeds — stock, prices and product details are as current as the last sync rather than as current as your till, and anything behind a customer login has to be uploaded instead Syncs run on daily and weekly cycles and when a source changes.
Files the questions your content cannot settle as one structured enquiry: contact details, what the shopper wants in their own words, and whatever order context they gave. Limit: everything captured comes from the customer, because nothing is looked up on their behalf — an order number they do not have to hand arrives missing.
Routes each captured order enquiry to whoever actually handles orders, so a stock check or a chase does not wait for someone to open a dashboard. Limit: an alert is a notification, not a ticketing system; no queues, assignments, statuses or reminders sit behind it.
Lets the shopper carry on with your team on WhatsApp, where a photo of the wrong item or a damaged delivery is easier to send from a phone, with the original question and captured details carried across. Limit: WhatsApp is a handoff destination, not a second channel — no Adoomi assistant answers inside WhatsApp, the customer decides whether to go there, and you cannot push a chat across from your side.
CustomerI ordered the wool coat last week and it has turned up too big. Can I still send it back — I have tried it on.
AdoomiYour returns page treats an item tried on for fit as unworn, provided the tags are still attached and it comes back in the original packaging — and it sets out the return window and who covers the postage.
CustomerGood. Do you have it in a small? And where is my other order — the tracking has not moved since Saturday.
AdoomiTwo things I cannot do from here, and I would rather say so than guess. I cannot see live stock, so I will not tell you a small is available when the page may be behind what is actually on the shelf. And I cannot look up an individual order, account or tracking — I have no access to them at all. What I can do is put both in front of the team with everything you have told me. Can I take your name, your email and the order number?
CustomerPriya Raman, and use the email the order confirmation went to. Order number is 40118.
AdoomiThanks Priya. That is with the team now: a small in the wool coat, and the order whose tracking has not moved since Saturday. They will reply to the address on the order. If you would rather carry on from your phone, I can move us to WhatsApp and they will pick it up there with everything you have already said.
Your teamEmail alert to the orders inbox: Priya Raman — wants the wool coat in a smaller size, needs a stock check, plus a chase on an existing order where tracking has not updated since Saturday. Order number supplied, reply to the address on the order. The returns question was already answered from the policy page.
The returns question was answered because the returns page answers it. The two that needed a system Adoomi cannot see — live stock and one customer's order — were named as such and captured instead, order number and all, in Priya's own words. That is the whole pattern of this page: the published policy gets answered, the lookup gets handed over, and nothing is invented in between.
Adoomi does not connect to your till, warehouse or shop platform, so availability and prices are as current as the last sync rather than as current as your shelves. The honest pattern is the one the assistant follows: answer what you have published about availability and restocking, then capture the specific stock question for the team to confirm — syncs run on daily and weekly cycles, and again when a source changes.
The assistant cannot see an individual's order status, account or tracking — there is no account access by design. Asked "where is my order", it says so plainly, takes the order number and contact details and routes the enquiry to your team. What it does hold, the captured enquiry, is EU-hosted with GDPR export and deletion built in.
Money and order state stay in your own shop systems. The assistant can explain from your published policy how a refund works and where to start one, but it cannot issue the refund, take a card payment, change a delivery address, cancel an order or book a courier collection.
The assistant repeats the delivery options and timeframes on your site and will not invent an arrival date. It will not promise next-day for an area you have not published, will not confirm that a particular parcel has shipped, and will not treat an estimate as a commitment on your behalf.
A specification missing from the product page, a care instruction nobody ever wrote down: the assistant hands the question over rather than guessing, and it will keep doing so until the fact is published or uploaded. The questions it could not answer collect as knowledge gaps, which is the honest brief for what to add to the catalogue next.
Stock answers are as current as the last sync and never live, because Adoomi reads no till or warehouse system. The honest pattern is to answer what your pages say about availability and restocking, then capture the specific stock question and route it to whoever handles orders.
Order lookup sits outside what Adoomi does: the assistant has no access to an individual's order, account or tracking, by design. Asked where an order is, it says so plainly, takes the order number and contact details, and routes the enquiry to your team by email or on to WhatsApp.
Product details and specifications, sizing, care and compatibility, delivery options and timeframes, returns and refunds — whatever your product pages, policy pages and uploaded documents actually say. Where the content does not settle a question, the assistant hands it over rather than filling the gap.
Delivery answers are the estimates you have already published, and nothing beyond them. The assistant repeats the options and timeframes on your site; it will not invent an arrival date, promise next-day for an area you have not covered, or confirm that a particular parcel has shipped.
Payments, refunds and order changes stay in your own shop systems. Adoomi explains from your published policy how a refund works and where to start one, but it cannot issue a refund, take a card payment, change a delivery address or cancel an order.
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 shopper asking about sizing, then delivery, then returns spends several. Credits are spent when the assistant answers.
Adoomi starts with your public business knowledge and routes the moments that need a person to your team.