Pharmacies
Do you have this in stock is the question of the day.
In a pharmacy the phone rings while there is a queue at the counter, and the question is almost always the same: do you have this medicine. The pharmacist leaves the person in front of them, checks, comes back. The call takes a minute and costs two.
The assistant takes the stock question, looks it up in your system through an HTTP tool, says whether the product is available, records the reservation with a name and phone number, and answers hours and address. It recommends nothing and discusses no prescription.
What rings on the pharmacy line
The list is short and stops abruptly before anything to do with pharmaceutical advice, which is precisely the job the pharmacist exists for.
Product availability
The product name, checked in your system if you give it a tool, with a yes or no answer.
A reservation
The name, the phone number and how long the product is held aside.
Hours and address
Including the duty rota, which is the most common night-time question.
The status of a special order
If there is somewhere to read it, otherwise it takes the question and hands it on.
Anything about treatment
Passed to the pharmacist, without exception and with no attempt at a partial answer.
From the question to a product put aside
The flow depends entirely on whether your stock system has an endpoint that can be asked about availability. Without one, the assistant is still useful for hours and for taking the request.
- 01 Check whether this is an advice question The first check, not the last. Anything that sounds like a symptom, a dose or an interaction goes to the pharmacist at once.
- 02 Take the product name and read it back Brand names carry badly on a phone line and resemble each other. The read-back is not optional here.
- 03 Look it up in stock Through an HTTP tool written over your system, with a JSON schema. There is no ready-made connector for pharmacy stock systems.
- 04 Record the reservation Name, number and deadline, as a row in a sheet or a ticket, plus an SMS confirmation if you want one.
- 05 Say plainly what it cannot do When the product is missing, it suggests no substitute. It says the pharmacist can discuss alternatives, and offers the transfer.
What stays at the counter
A reservation that is not written somewhere visible is a product sold to somebody else within ten minutes.
| The reservation | A row in a sheet or a ticket, with the product, the name, the number and the deadline. |
|---|---|
| The confirmation | An SMS to the customer with the product held and until when. |
| The stock query | What the assistant asked and what your system answered, as a tool event on the call. |
| On the call record | The transcript, plus the transfer if the call reached the pharmacist. |
What it does not do for a pharmacy
Nothing on this list is negotiable, because at the other end of the line somebody may make a decision about a medicine.
- It gives no pharmaceutical advice It recommends no products, discusses no doses, explains no interactions and suggests no equivalent. Never, not even for products sold without prescription.
- It does not discuss prescriptions It does not check a prescription, does not confirm whether a medicine requires one, and takes no prescription-based orders.
- No link to your stock system There is no ready-made connector for pharmacy stock systems. A stock check requires an HTTP tool written over your API.
- It takes no money and holds nothing against payment A reservation is a note, not a transaction.
- It does not handle medical emergencies It is configured to recognise emergency phrasing, tell the caller to ring the emergency number, and end. It does not keep somebody on the line during an emergency.
What pharmacies ask us
Can it actually check live stock?
Only if your stock system exposes an endpoint and a tool is written for it. We have no ready-made connector for any pharmacy system. Without one, the assistant is still useful for hours, address and taking the request, which is most of the night-time calls anyway.
What does it do if somebody describes a symptom?
It does not answer at all and transfers to the pharmacist, or, out of hours, says plainly that it cannot help with that and points to the emergency number. That is the only acceptable behaviour, and an assistant trying to be helpful here is a hazard.
Does it work for a duty pharmacy?
Yes, and that is where it is most useful, because at night most calls are about hours and availability. What has to be configured carefully is exactly what it says when the call is a real emergency.
What happens to customer data?
You collect as little as possible: a reservation needs a name and a number, and nothing else. Transcripts can be written straight into your own storage, with a configured retention period and scheduled deletion.
Where to go next
Integrations
25 business connectors, 18 selectable providers, eight storage destinations.
Tools and MCP
Discovery, per-tool permissions, per-server namespacing, and a tool of your own.
Telephony
Numbers, trunks, dial plan, queues, operators and campaigns, in one system.
Pricing
Components at their published price, the platform on top, and what we cannot price yet.
Notes
-
1
The tools named on this page are the ones in
App\Services\Integrations\ConnectorRegistrycarryingimplemented. Anything that is only in the catalogue, without that flag, is not named here as though it worked. - 2 The stock check is your own HTTP tool, with a JSON schema and versioning. No connector in the registry covers pharmacy stock systems.