Fixed quote after a free call

AI customer service for supplement brands that knows when to stop

We build an AI support agent for your help desk, website chat and email that answers from your approved product information (ingredients, allergens, label directions, shipping and subscription terms), looks up orders, and can skip or update subscriptions where you allow it. Any message that could describe an adverse event is routed to a trained person at once with the details preserved, and the agent never gives medical advice. Projects typically cost $2,500 to $7,500 and take six to eight weeks.

The problem

Why supplement support needs an AI agent with guardrails

Supplement support inboxes are full of the same questions: where is my order, can I skip next month, is this vegan, does it contain soy, how many capsules a day. Each is quick for a person, but at volume they bury the messages that matter.

Some of those messages matter a great deal. A customer who mentions a reaction after taking a product may be reporting an adverse event. In the US, the brand named on the label must send FDA reports of serious adverse events received through the label contact within 15 business days and keep records for six years. An AI agent that answers that message with a canned reply, or misses it, is a real risk. It must spot it and hand it to a person.

What we build

What our AI customer support for supplement brands includes

Approved product knowledge

Ingredients, allergens, label directions, certifications, shipping and subscription terms, approved by your team and the only source the agent uses.

Order and subscription actions

Order lookups, address changes before fulfilment, and skips or date changes in Recharge or Skio, within limits you set.

Adverse event detection and hand-off

Messages that mention symptoms, reactions or a doctor visit are stopped, flagged and routed to your trained person with the product, lot number if given and contact details.

No medical advice

Questions about conditions, medications or pregnancy get a fixed reply suggesting the customer speak to their healthcare provider, and a person follows up.

Help desk native

Runs inside Gorgias or your help desk, with drafts for agents or direct replies for categories you approve.

Clear AI disclosure and review

Tells customers it is automated, offers a person, and logs conversations for weekly review.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Message arrives

    An email, chat or help desk ticket comes in.

  2. 02 Automated

    Safety screen

    Any sign of a possible adverse event or medical question stops automation and alerts a person.

  3. 03 Automated

    Routine answer or action

    Other questions are answered from approved information, or an order or subscription action is taken.

  4. 04 Team review

    Agents handle the rest

    Support agents handle hand-offs, edits and anything outside the approved categories.

  5. 05 Regulatory lead or founder decides

    Adverse event assessment

    A trained person or the regulatory lead decides whether a report is serious and must go to FDA.

How it behaves

How the AI support agent behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • A clear note that they are talking to an automated assistant
  • Fast answers about orders, ingredients and subscriptions
  • A person following up quickly if they mention a reaction or a medical question

What the team sees

  • Adverse event flags at the top of the queue with details preserved
  • Drafts or sent replies for routine tickets
  • A weekly review of flags and unanswered questions

What the automation does

  • Screens every message for possible adverse events first
  • Answers only from approved product information
  • Takes allowed order and subscription actions and logs everything

Edge cases and fallbacks

Message is ambiguous about symptoms
Treated as a possible adverse event and routed to a person.
Customer asks about combining with a medication
Fixed reply to speak to their healthcare provider, and a person follows up.
Question not in the knowledge base
Handed to an agent and added to the weekly review.
AI provider or help desk outage
Tickets stay in the normal queue for people; adverse event keywords still trigger a basic alert.

Architecture

AI support with adverse event routing at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Customer message Email, chat Help desk Gorgias Safety screen Possible AE? AI agent Approved answers AE handler Trained person Shopify, Recharge Order actions AE records Kept 6 years
  • Input
  • Logic and services
  • AI step
  • People
  • Output
  • Data

How it flows

  1. 1 A customer message arrives in the help desk from email or chat.
  2. 2 A safety screen runs first: anything that could be an adverse event or a medical question goes straight to a trained person.
  3. 3 Routine questions are answered from approved information, and allowed order or subscription actions are taken.
  4. 4 The adverse event handler assesses each flagged case, and records are kept for the required period.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

AI support agent with adverse event routing project plan

Typical time to launch: about 6 weeks, then support

  1. 01

    Discovery

    About 1 week

    Ticket categories, real questions, current adverse event procedure, help desk setup and allowed actions.

  2. 02

    Knowledge and rules

    About 1 week

    Approved product information, fixed replies, safety screen terms and hand-off rules, signed off by your team.

  3. 03

    Build

    About 2 weeks

    Help desk integration, retrieval, safety screen, actions, alerts and logging.

  4. 04

    Test

    1 to 2 weeks

    Real tickets plus adverse event, medical and tricky prompts; the regulatory lead signs off the screen.

  5. 05

    Launch

    2 to 3 days

    Start with drafts for agents, then allow direct replies for approved categories.

  6. 06

    Support

    Ongoing

    Weekly review of flagged messages and missed questions, then monthly updates.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

Claude, Gemini or OpenAI models Gorgias REST API Shopify Admin API Recharge or Skio API n8n or Laravel Slack or email for adverse event alerts

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and knowledge base

    Ticket analysis, approved product information and safety rules.

    $500 – $1,200

  • Build

    Help desk integration, retrieval, safety screen, actions and logging.

    $1,200 – $3,800

  • Integrations

    Shopify, subscription app, help desk and alerts.

    $300 – $1,100

  • Testing and evaluation set

    Real, adverse event, medical and tricky prompts.

    $300 – $1,000

  • Launch and training

    Draft-mode launch and team training.

    $200 – $400

  • Total project estimate

    $2,500 – $7,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Help desk, model usage and messaging are billed to you directly. Your adverse event procedure and FDA reporting stay with your team.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • AI model usage: Billed by the provider per use; depends on ticket volume.
  • Help desk: Your Gorgias or help desk plan, including any AI features it charges for.
  • Hosting: n8n Cloud from about €20 a month (Starter, billed annually), or your own server.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: serious adverse event reports

FDA guidance says serious adverse event reports received through the label address or phone number must reach FDA within 15 business days, and records of each report must be kept for 6 years.

Source: www.fda.gov

US: no disease claims in replies

Support answers are advertising too; the FTC guidance applies to implied claims, so the agent only uses approved wording and never suggests a product treats a condition.

Source: www.ftc.gov

EU: AI disclosure

Article 50 of the EU AI Act requires that people are told they are interacting with an AI system, from 2 August 2026. We add it on every channel.

Source: artificialintelligenceact.eu

EU and UK: health data

Symptoms customers describe are special category data under Article 9 GDPR and UK GDPR, so access is limited to the people who handle adverse events.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

AI support agent with adverse event routing questions, answered.

One that answers only from approved product information, can take simple order and subscription actions, and recognises possible adverse events and medical questions and hands them to a person. Many help desks have AI features; we configure or extend them with those guardrails.

The safety screen runs before any answer. If a message could describe an adverse event, automation stops, the details are preserved and a trained person is alerted at once. That person, with your regulatory lead, decides whether it is serious and must be reported to FDA.

It can repeat the directions printed on your label from approved text. Questions about conditions, medications, pregnancy or going beyond the label get a fixed reply suggesting the customer speak to their healthcare provider, and a person follows up.

It can skip or change dates in Recharge or Skio where you allow it. Cancellation requests are processed promptly through your normal cancel path; the agent never argues or makes leaving harder.

Yes. Gorgias has a REST API for tickets and messages, so the agent can draft or send replies inside the help desk your team already uses.

Track tickets resolved without hand-off, first response time, customer satisfaction on automated replies, and every safety-screen flag reviewed weekly to check nothing was missed.

Free 20-minute call

Want this for your health & supplement brand?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call