AI Chat Commerce · Tony O'Connell ecom build
← Back to orb
Tony O'Connell ecom build · built for prescription-edge categories

The bot that sells, qualifies, and routes - regulator-aware by design.

A conversational commerce layer that lives on oleo.ie. Patients ask plain-English questions about MCAP, eligibility, conditions, the Panacea device, OleoCare onboarding. Prescribers use the same surface to look up products, request samples, or trigger a Module 1 onboarding flow. Buys (where legally permitted) happen in-bot. Prescription requests get routed, never sold.

Built by Tony O'Connell ASAI-aware Two-track logic Verify-before-checkout
O
Oleo Assistant
Online · ~30s reply
Hi - I'm Oleo's assistant. Are you a patient, a healthcare professional, or just exploring?
I'm a patient. Got MS spasticity, my consultant mentioned MCAP.
Got it. MCAP covers MS spasticity. Three things matter here:
1) eligibility check
2) consultant referral path
3) what your treatment looks like day-to-day.

Want the 60-second eligibility screener, or the consultant pathway?
What's the device I'd use?
For MS spasticity under MCAP it's the Oleo Panacea inhaler. Built for medical use, paired with the OleoCare app for adherence tracking. Available to MCAP patients with a consultant prescription.
📦
Oleo Panacea Inhaler
For MCAP-prescribed patients
Available via prescription
See the device page →
Type a question...
What it does

Three jobs. One conversation surface.

1

Educate (always permitted)

Patient asks about MS spasticity, chemo nausea, refractory epilepsy, MCAP cost, the application path. Bot answers from a regulator-aligned knowledge base. Cites HPRA + gov.ie + named clinical reviewers. Never makes off-label clinical claims.

2

Route (the qualifier)

Eligibility screener (5 questions). If MCAP-eligible, routes to "ask your consultant about a referral" + a draft message they can copy. If a HCP, routes to the prescriber portal + Module 1 onboarding. If neither, gracefully exits with educational links.

3

Sell (where legal)

Panacea device sales (assuming MDR Class IIa confirmed). OleoCare app downloads. CPD module purchases for HCPs. Conference / event tickets. Anything advertisable. Prescription cannabis is NEVER sold in-bot - always routed to prescriber.

How it stays compliant

The two-track guardrails are baked in.

What the bot will do

  • Answer plain-English condition + MCAP questions citing HPRA, gov.ie, HSE
  • Run the eligibility screener (consent-gated, GDPR-aware)
  • Route patients to "talk to your consultant" with a draft referral request
  • Onboard HCPs into Module 1 prescriber flow
  • Sell Panacea device, OleoCare-related extras, CPD modules (advertisable goods)
  • Handover to a human when the question is out of scope

What the bot will not do

  • Sell MCAP-prescription cannabis (never)
  • Make clinical claims beyond MCAP-listed indications
  • Diagnose, recommend specific dosages, or substitute for a prescriber
  • Promote prescription products outside HCP-gated context
  • Store identifiable patient data without explicit GDPR consent
  • Route adverse events anywhere except HPRA yellow-card scheme
Audit trail: every conversation logged, every routing decision auditable, every claim traceable to a regulator-aligned source. ASAI-defensible by default.
Why this is the killer differentiator

oleo.ie's current chat is "contact us". This replaces that with a scaling sales surface.

Surfaceoleo.ie todayWith AI Chat Commerce
Patient with a question at 11pmForm submission, response next business dayAnswer in 30 seconds, eligibility screener offered, referral message drafted
HCP wanting to prescribeFind /pages/contact, email, waitStarted in Module 1 onboarding inside the chat. IMC verified. CPD enrolled. ~5 min.
Pharmacy ordering questionPhone call, voicemail, callbackRouted to Module 5 portal, stock visibility shown in-chat, order placed
Panacea device saleAdd to cart Shopify flow (anonymous)Q&A first - is it the right device for you? - then in-chat checkout
Adverse event reportedHopefully a contact form, more likely lostYellow-card draft auto-built, routed to HPRA + Oleo pharmacovigilance log
OleoCare app onboardingManual flow on app storeQR code + walkthrough inside chat, support handover ready
"Trusted by Doctors" claimStatic, unverifiedLive count from prescriber pipeline, with HPRA register link inline
What it ships with

Tony's ecom kit, adapted for medical-cannabis context.

Conversational engine

LLM-backed routing layer with strict tool-use scaffolding. No free-form clinical claims; every answer pulls from a regulator-aligned knowledge base.

Eligibility screener

5-question MCAP eligibility flow, consent-gated, GDPR-aware, output is a draft consultant message.

Shopify Storefront API tie-in

Cart + checkout primitives stay on Shopify (you keep Judge.me, Weglot, payment infra). Chat just orchestrates flow.

Prescriber portal handoff

Direct entry to Module 1 onboarding. IMC verification. CPD enrolment in Module 6.

Pharmacovigilance trigger

Adverse-event flag detection -> yellow-card draft -> Module 4 quarterly pack.

HCP-vs-patient routing

First-question gate. Different flows, different content, different commerce permissions per audience.

Citation-grade answers

Every clinical or regulatory answer ends with "Source: HPRA / gov.ie / [named clinician]". AI engines crawl this, trust grows.

Audit log

Every conversation stored 90 days minimum. Every routing decision auditable. Every claim traceable.

Multilingual ready

English first. Irish + Polish + Romanian on roadmap (matches Oleo's existing Weglot integration on the storefront).

Ship plan

Tony's ecom build pattern, applied to Oleo.

PhaseWeeksWhat ships
1 - Knowledge base + scaffolding1-2MCAP regulatory KB built, routing logic tested in sandbox, audit-log infra
2 - Patient + HCP flows3-4Eligibility screener live, consultant-routing draft, HCP gate live
3 - Commerce tie-in5-6Shopify Storefront API integration, Panacea sale path (conditional on MDR confirmation), OleoCare onboarding QR
4 - Module integrations7-8Module 1 onboarding link live, Module 4 yellow-card trigger live, Module 5 pharmacy routing live
5 - Soft launch + measurement9-1030% traffic A/B vs control, conversion + qualified-routing measured
6 - Full launch11-12100% rollout, multilingual flag, 90-day measurement frame
Compatible with current site: the chatbot drops into the existing Shopify storefront as a script tag. No rebuild required to ship v1. If the new Astro frontend lands later, the chatbot moves with it - it is decoupled.
New Site (host) → Modules behind the bot →
← Back to orb