Answers the counter list
Opening times and the bank-holiday rota, the delivery area and days, how prescriptions reach you from the surgery, which vaccinations and services you run, and how to book one.
A pharmacy gets the same counter questions all day: what time do you close, do you deliver to my postcode, has my repeat come through, do you do travel jabs, is the flu clinic bookable, do you make up blister packs. That list comes back off pages you approved — at whatever hour, in the customer's language, while the dispensary works. It says nothing about a medicine — no dosing, no interactions, no symptoms, no view on whether it can wait — and hands those to the pharmacist you name.
Fig. 01.A · Pharmacies
Fig. 02.A · pain quotesA dispensary cannot be paused. The phone goes while a script is being checked, somebody is waiting at the counter and the delivery round needs sorting — and most of what is ringing is are you open Sunday, do you deliver to my road, is my repeat in yet. The ones that arrive after the shutters are down get nothing until morning, and that customer walks into the pharmacy that answered instead.
Opening times and the bank-holiday rota, the delivery area and days, how prescriptions reach you from the surgery, which vaccinations and services you run, and how to book one.
Which service, who it is for, when they could come and how to reach them — captured for the counter to confirm, with no symptom and no list of tablets asked for along the way.
Dosing, interactions, side effects, Pharmacy First and "is this safe with mine" each stop the assistant, surface your out-of-hours wording and reach the pharmacist you named.
Everything on this list already has an answer on your website — the rota, the delivery postcodes, the services, the travel-clinic process — and the assistant repeats that answer at the hour it is asked. What is not on the list, and never will be, is anything about a medicine.
Half the counter's time goes on enquiries that arrive half-formed. Adoomi asks the practical things instead: which service — flu, travel, blood pressure, a blister-pack review — who it is for, when they could come, whether they are already a customer, and how to reach them. What it never asks for is a symptom or a list of what somebody is taking, because none of that belongs in a chat window at all. The pharmacist gets a complete enquiry and does the clinical part in person.
With Adoomi
Fig. 06.A · after-hoursPharmacy questions cluster around the shutters: late evening, Sunday, the bank holiday. Adoomi keeps answering the published list — opening times and rota, the delivery area and days, how prescriptions reach you from the surgery, the services you run and how to book one. A medicines question gets no answer. It repeats what your own page tells customers out of hours — ring the pharmacy in opening times, 111 for urgent NHS advice, 999 in an emergency — then flags it for the pharmacist.
Opening times, the bank-holiday rota, delivery postcodes, how a repeat reaches you from the surgery, the vaccinations you run and what a travel appointment involves are on your site already. Answering from there stops the counter reciting the postcode list, and frees the phone for calls that need the pharmacist. What still reaches your team always did need them — a medicines question, a Pharmacy First conversation, a prescription to chase — by email alert, or into a WhatsApp handoff.
Fig. 08.A · controlsTwo lines hold. The clinical one: no dosing, no interactions, no symptoms, no over-the-counter suggestion, no Pharmacy First assessment, no view on whether it can wait. Each one emails the pharmacist you name. The factual one: no dispensing system, no stock file — nothing is called ready or in. Sensitive and safeguarding messages reach one person, not the counter inbox. Chats stay in the EU, are wiped on GDPR request, with no message content in logs. None of this makes you compliant.
Hours, rota, delivery, the prescription process and your services are drawn from content you approved. Whatever those pages miss is handed over, not answered plausibly.
Dosing, interactions, side effects, product suggestions, Pharmacy First and symptoms are all outside it. Each one ends the assistant's turn and reaches the pharmacist you named.
The assistant is connected to neither, so it never says a prescription is ready or an item is in. It explains your published process and passes the specific question on.
Emergency contraception, supervised consumption and safeguarding enquiries reach a named individual, not the counter inbox. Chats are EU-hosted, erasable under GDPR, with no content in logs.
Opening times, the bank-holiday rota, your delivery postcodes and days, the services you run and how to book one are all answered straight from your own pages — including late on a Saturday night, long after the shutters are down and the question still gets asked.
Medicines questions are never answered here. Dosing, interactions, side effects, whether something is safe alongside an existing prescription, and anything that sounds like a symptom all stop the assistant and reach the pharmacist you named, with your out-of-hours wording shown.
Prescription status is not something the assistant can see. It has no link to your dispensing system, so it explains your published process — how a repeat reaches you from the surgery, and what your page says about collection — then passes the specific enquiry to the counter.
Travel and vaccination answers come from your own service pages: what a travel appointment covers, how far ahead to book it, which clinics you run and who they are open to. Which vaccines one itinerary needs is a pharmacist consultation, so the trip and dates are captured and handed on.
Sensitive messages go to the person you nominate, never the shared counter inbox — emergency contraception, supervised consumption, anything about a vulnerable customer. Chats themselves are EU-hosted, exportable or deletable under GDPR, with no message content in logs, and set no tracking cookies.
Credits are what you pay for: 50 come with the £0 Free plan, then £8 buys 200, £20 buys 500 and £75 buys 4,000. Setup is connecting your site, reading the answers it drafts and putting one line on your website — ~10 min in total. Nothing is visible to a customer until the pharmacy approves it.
There is no measured claim here, only what is structurally true. The assistant is wired to your published pages and nothing else — no dispensing system, no stock file, no ordering system — so "is mine ready" and "have you got it in" get an honest handover, not a confident wrong answer. Because it holds no clinical view, no dosing or interaction question ever gets one. What it does runs at every hour, in the customer's language: hours and rota, delivery, services and how to book one.
Hours and rota, delivery area, the prescription process and service bookings come back in the customer's own language, at whatever hour the question lands, straight from pages you approved.
The assistant sees no dispensing system and no stock. "Is mine ready" and "have you got it in" get your published process and a handover, not a guess.
Dosing, interactions, side effects and Pharmacy First are never answered. Your out-of-hours wording is shown and the pharmacist you named is flagged.
Connect your opening-times, delivery, services and travel-clinic pages, say which pharmacist takes medicines and who takes anything sensitive, then ask it "is my prescription ready, and can I take this with my other tablets" before a customer does. Nothing reaches a customer until you have approved it. Point it at the site, read what it drafts, paste one line into your website — ~10 min all in. The Free plan is £0 a month and carries 50 message credits.
Fig. 12.A · Pharmacies