Business case and benefits
- Customer service director
- A · Accountable
- Responsible Person
- C · Consulted
- Solutions architect
- C · Consulted
- Technical PM
- R · Responsible
- Engineers
- I · Informed
- Compliance & DPO
- I · Informed
- Security
- I · Informed
Pharmacies get straight answers on stock, alternatives, delivery times and credits at any hour, by phone, email or portal. Clear limits keep clinical advice and controlled drugs with people.
At a glance
An illustrative scenario. Linked to a real, anonymised case study below; the numbers here are still typical examples. The cloud services and UK rules were checked on 9 November 2026.
Most routine orders reach a wholesaler electronically, straight from the pharmacy's ordering system. The order desk handles everything else: a pharmacist asking whether a short line will come in tomorrow, a dispenser chasing a missing tote, a dispensing practice asking for a different pack size, a branch wanting a credit for a damaged item, and the steady questions about cut-off times and delivery slots.
When medicines are short, calls rise sharply and the questions get harder. Is it out everywhere or just here? Is there another manufacturer's version of the same product? Is it on a manufacturer's quota? Customer service staff look across the ERP, the warehouse system and supplier notices to answer, while the queue grows. Pharmacy teams, who are already stretched, wait on hold to hear an answer that's often 'not until Thursday'.
Some of these conversations carry real risk. A pharmacist may ask what they could use instead, which is a clinical question the wholesaler shouldn't answer. A caller may want to add a Schedule 2 controlled drug to an order, which has its own legal requirements. Unusually large orders may need checking before they're supplied. Any automation has to know exactly where those lines are.
Agree these, and measure the baseline, before anything is built. Example targets are typical, not promises.
How long a pharmacy waits for a first useful answer, by channel.
ExamplePhone under 30 seconds; email under 15 minutes
Stock, alternative and delivery queries answered fully by the agent. Measured on queries it should handle, not all contacts.
Example50–60% of those queries
How often staff can act on a handed-off query without asking the pharmacy again.
ExampleOver 90%
Answers found wrong in a weekly sample, such as stock promised that wasn't available.
ExampleBelow 1%, reviewed weekly
Any clinical advice or controlled drug action by the agent, found in sampling or testing.
ExampleZero, with every case investigated
Time from a pharmacy reporting a damaged or missing item to the credit being issued.
ExampleFrom 5 days to 1–2 days
Cross-sector rules are on the UK regulation map.
A wholesaler may only supply customers entitled to receive medicines, and the Responsible Person expects unusually large orders to be checked. The agent works only on verified, qualified accounts, and orders above each account's normal pattern for a line go to a person before they're confirmed.
For Schedule 2 and 3 drugs, a supplier must hold a signed requisition on the approved form, the FP10CDF in England, before delivering to the people listed in regulation 14, such as doctors. That includes dispensing practices. The agent never adds, changes or cancels a Schedule 2 or 3 line. It routes the caller to the CD team with the details.
Choosing a different medicine is a decision for the prescriber or pharmacist. The agent offers only the same active ingredient, strength and form, and says when a Serious Shortage Protocol is in force, linking to the NHSBSA notice. Clinical questions go to the manufacturer's medical information service or a person.
Returned stock can only go back to saleable stock if conditions are met, including proof of proper storage for fridge lines. The agent logs the request and issues a reference, but whether stock is credited or returned to stock is decided by people, under the Responsible Person's procedures.
Order confirmations and delivery updates are service messages. Promotions are marketing, and many pharmacies are sole traders or partnerships, which PECR treats like individuals, so marketing emails need consent or the soft opt-in. Since February 2026, PECR fines can reach UK GDPR levels. The agent only sends service messages.
Recording and transcribing calls relies on the Investigatory Powers Act 2016 business regulations and a UK GDPR lawful basis. Callers are told they're speaking to an automated assistant and that calls are recorded. Patient details sometimes come up on calls, so transcripts are minimised and redacted, processed in UK regions, and kept for a set period.
Showing AWSAzuresovereign / on-prem services. Switch with the toggle; every diagram and table on this page follows it.
01Channels
02Intake
03Intelligence
04Orchestration
05Systems of record
06People
| Layer | AWS | Azure | Sovereign / on-prem |
|---|---|---|---|
| Phone and contact centreOr keep your existing contact-centre platform and connect the agent to it. | Amazon Connect | Azure Communication Services (Call Automation), or Dynamics 365 Contact Center | Your existing phone system, connected over SIP |
| SpeechTest on real calls: dispensary noise, drug names, strengths and pack sizes. | Amazon Transcribe | Azure Speech in Foundry Tools | Open-weight speech models (e.g. Whisper) on your own GPUs |
| Email and portal intake | Amazon SES, API Gateway | Logic Apps connectors, API Management | Your existing mail server; Kong, or your existing API gateway |
| Reading attachmentsPhotos of damaged items, delivery notes and scanned requisitions. | Amazon Textract | Azure Content Understanding (includes Document Intelligence) | Open-source parsing (e.g. Docling) plus an open-weight vision model |
| Reasoning and repliesEach offers a choice of models. | Amazon Bedrock | Microsoft Foundry | Open-weight models served with vLLM on your own GPUs, or IONOS AI Model Hub |
| Product and policy knowledge (retrieval)Product data, cut-off times, returns policy and current Serious Shortage Protocols, each with a named owner. | Bedrock Knowledge Bases | Foundry IQ, built on Azure AI Search | OpenSearch, or PostgreSQL with pgvector |
| Agent runtimeThe original Bedrock Agents closed to new customers on 30 July 2026; new builds use AgentCore. | Amazon Bedrock AgentCore | Foundry Agent Service | An open-source agent framework (e.g. LangGraph) on Kubernetes |
| Workflow and events | Step Functions, EventBridge, SQS | Logic Apps or Durable Functions, Event Grid, Service Bus | Temporal or n8n; Apache Kafka or RabbitMQ |
| Link to ERP, WMS and transportThe agent calls the same APIs as the portal, with the same limits. | API Gateway, plus your existing integration platform if you have one | API Management, plus your existing integration platform if you have one | Kong, or your existing API gateway |
| Platform | Managed AWS services, Amazon EKS where containers are needed | Managed Azure services, AKS where containers are needed | Kubernetes on-prem (e.g. OpenShift, Rancher), or IONOS Managed Kubernetes |
| Human hand-offSummary, transcript and suggested next step arrive with the call or case. | In the team's existing agent desktop or CRM | In the team's existing agent desktop or CRM | In the team's existing agent desktop or CRM |
| GuardrailsTopic filters catch clinical questions, but the hard limits sit in the tool permissions. | Bedrock Guardrails | Foundry guardrails (Azure AI Content Safety) | Open-source guardrails (e.g. NeMo Guardrails, Llama Guard) |
| Identity, keys, data protection | IAM Identity Center, KMS, Macie | Entra ID, Key Vault, Purview | Keycloak or your existing Active Directory; OpenBao or HashiCorp Vault; an HSM |
| Monitoring and auditEvery answer, tool call and hand-off logged, so any conversation can be replayed. | CloudWatch, CloudTrail | Azure Monitor, Log Analytics | Prometheus, Grafana, OpenTelemetry |
| UK data residencyAzure Communication Services stores data by geography, chosen when the resource is created. | eu-west-2 (London) | UK South / UK West | Your own UK data centre, or a UK/EU provider (IONOS AI Model Hub runs in Germany) |
On a phone, the table shows the platform you pick. Sovereign / on-prem means open, portable components you can run in your own data centre or with a UK or European provider; IONOS is shown as one example, and others exist. What sovereign cloud means →
Many organisations keep core systems and sensitive data on their own servers. This is how the same design works across both.
Stays on-prem
The ERP, WMS, transport system and phone system usually stay where they are, often in your own data centre. Pharmacies' electronic orders keep flowing straight into the ERP, and call recordings can stay on-prem if your policy requires it.
Uses cloud AI
Speech-to-text, the order desk agent and the knowledge index run in the cloud, or on your own sovereign stack. Voice needs a fast round trip, so they sit in the same UK region as the contact-centre platform, or next to your own phone system.
How they connect
The agent calls the ERP and WMS through your API gateway across a private link, such as AWS Direct Connect, Azure ExpressRoute or a site-to-site VPN, with the same account checks as the portal. Calls reach a cloud contact centre over SIP trunks; Azure Arc or AWS Outposts can host parts of the stack on-prem if needed.
If the link drops
The agent can't check stock, so it doesn't answer stock or delivery questions. Calls route straight to the team as they do today, emails wait safely in the queue, and orders from pharmacies' own ordering systems are unaffected.
What each agent may do through its tools, what it may not, and where a person signs off. The limits are enforced by the platform, not the prompt.
Order desk agent
Where a person signs offPeople decide every controlled drug order, every held or unusual order, every return to stock, and every credit above the limit. The agent's tools enforce these limits in the platform's identity and policy controls, not in its instructions: it simply has no tool that can touch a Schedule 2 or 3 line or release a held order.
The agent reaches the ERP, WMS and transport system only through the same API layer the customer portal uses, with the same account checks and quantity limits. If you already run an integration platform, the agent uses it like any other channel.
Stock answers come from available-to-promise, not raw stock. Stock that's quarantined, allocated to other customers or held back under a manufacturer's quota isn't offered, so the agent can't promise what the warehouse won't pick.
Every order change carries a unique ID, so a dropped call or a repeated email never creates a duplicate order. Changes are confirmed back to the pharmacy in writing.
If the ERP or the agent is down, nothing is guessed. Calls route straight to the team as they do today, and emails wait safely in the queue.
Sample a month of calls and emails to see why pharmacies contact you, measure the baseline, and check API access to the ERP, WMS and transport systems.
Gate · must be true to passContact reasons and baseline agreed, data access confirmed, DPIA started, Responsible Person and compliance involved.
Email and portal first, for stock, alternative and delivery queries. The agent drafts, staff send, and the drafts are compared with what staff would have written.
Gate · must be true to passAccuracy and hand-off quality within agreed limits, zero boundary breaches in testing, and compliance sign-off.
Email and portal answers go live, then voice for the same query types, out of hours first, with monitoring, support and a rollback plan.
Gate · must be true to passMonitoring, support model, rollback plan and staff training in place.
Add credits and returns, then proactive service messages such as a short line arriving early, one at a time.
Gate · must be true to passEach new capability passes the same pilot gate.
| Activity | Customer service director | Responsible Person | Solutions architectI can fill this | Technical PMI can fill this | EngineersI can fill this | Compliance & DPO | SecurityI can fill this |
|---|---|---|---|---|---|---|---|
| Business case and benefits | Accountable | Consulted | Consulted | Responsible | Informed | Informed | Informed |
| Target architecture | Informed | Consulted | Accountable and Responsible | Consulted | Consulted | Consulted | Consulted |
| Hand-off rules and agent limits | Accountable | Responsible | Consulted | Consulted | Informed | Consulted | Consulted |
| DPIA, PECR and call recording review | Accountable | Consulted | Consulted | Informed | Informed | Responsible | Consulted |
| Build and integration | Informed | Informed | Accountable | Responsible | Responsible | Informed | Consulted |
| Accuracy and boundary testing | Informed | Consulted | Accountable | Consulted | Responsible | Consulted | Responsible |
| Go-live decision | Accountable | Responsible | Consulted | Responsible | Informed | Consulted | Consulted |
| Run, monitor and improve | Accountable | Consulted | Consulted | Informed | Responsible | Consulted | Consulted |
R ResponsibleA AccountableC ConsultedI Informed· not involved
Option A
If there's no architect on the programme, I'd own the design end to end: the contact channels, the agent and its limits, the integration with your ERP, warehouse and transport systems, and the gates. I'd report to your programme board and agree the hand-off rules with your Responsible Person early.
Option B
If your partner or your own team already has an architect, I'd take on the agent's tools and permissions and the integration with your ERP and warehouse system under their lead, which is where order desk projects usually get stuck, and give them a second senior opinion on the rest.
Goes wrong
The agent says a line is in stock, but it's allocated, quarantined or on quota.
How the design avoids it
Answers come from available-to-promise and quota rules through the API layer, never from a raw stock figure.
Goes wrong
A pharmacist asks what they could use instead, and the agent drifts into clinical advice.
How the design avoids it
Alternatives come only from a same-ingredient, same-strength list, clinical questions hand off, and every release is tested with questions designed to push it over the line.
Goes wrong
A drug name or strength is misheard on a noisy call.
How the design avoids it
The agent reads back product, strength, pack size and quantity, matches on product code, and confirms every change in writing.
Goes wrong
Hand-offs lose the context, so the pharmacy explains everything twice.
How the design avoids it
The summary, transcript and account details arrive on the person's screen with the call or case.
Goes wrong
Helpful 'back in stock' messages slowly turn into promotions sent without consent.
How the design avoids it
Service messages and marketing are separate flows. The agent sends service messages only, and marketing goes through PECR checks owned by the marketing team.
Changes already announced or under way that affect this design. More in the UK horizon scan.
The national analogue phone (PSTN) switch-off has no further extension. Some pharmacies still phone or fax orders over analogue lines. Make sure your own lines and any fax-to-email route are on IP, and expect some of that traffic to move to email and the portal, where the agent can pick it up.
Most newly registered pharmacists are now independent prescribers, and prescribing is being added to community pharmacy services. Expect more varied and more urgent orders. Keep the clinical line sharp, and check with your CD lead how requisition rules apply as prescribing grows.
NHSBSA's July 2026 guidance describes an electronic FP10CDF that can be completed online, though it's still printed and signed in ink. Design the requisition check so a scanned form can be matched to an order now, and a fully electronic one later.
The main data protection changes took effect on 5 February 2026, including higher PECR fines and new rules on automated decisions. The ICO is reviewing its marketing guidance. Keep service and marketing messages apart in the design, and track the ICO's updates.
Amazon Connect was relaunched in April 2026 with agentic self-service, and Bedrock Agents closed to new customers in July 2026. Keep the agent's tools behind your own APIs, so the contact platform or agent runtime can change without rewriting the integration.
Good answers are specific. Vague answers to any of these are worth following up.
Whether you need someone to lead the design or to support the architect you already have, let's talk it through.