FAQs

The questions owners actually ask.

Anything else, email the team at hello@freemi.ai.

No. Freemi runs alongside what you already use. It takes the messages, bookings, requests, staff administration and follow-up, and leaves your dispensing or clinical system where it is.

Days, not months. We configure your services, hours, staff, workflows and permissions with you, your team reviews the rules before launch, and then Freemi starts handling the agreed routine work.

Anything requiring professional judgement, approval or clinical action is routed to the right team member. Every important action is visible, permissioned and recorded.

Whichever ones you enable: WhatsApp, SMS, email, web chat, messages and your website. They all land in one place instead of four.

One monthly price per location, based on your setup rather than a tier chart. No setup fee, no minimum term, cancel anytime.

Freemi is built and supported in Dublin, and operates under GDPR. Access is role-based, so each staff member sees only what their responsibilities require, and every important action is written to an audit log with a name and a timestamp. Data is encrypted in transit and at rest, you can export it at any time, and we confirm exactly which regions your services run in during onboarding rather than making a blanket claim here.

Still deciding

Ask us the one that is not on this list.

If the question you actually have is not here, it is probably the interesting one. Email us or take fifteen minutes and we will answer it on a call.

Book a demo See pricing Read the journal
Getting started

Starting on Freemi.

How long does it actually take?

Days rather than months. The engine is already built, so the first week is configuration: your services, your hours, your team and their permissions, your note headings if you keep clinical records, your consent set and your channels. Most of that work is ours, not yours.

Do we have to move all our data first?

No. Freemi runs alongside your dispensing or practice system rather than replacing it, so you are not blocked on a migration. What can be brought across depends on what you already run, and we confirm that during onboarding rather than promising it up front.

What do you need from us?

One call to walk through a real workflow, your service list and fees, and someone who can sign off what Freemi is allowed to answer on its own. That last one matters more than the rest.

What if it is not a fit?

We will say so on the call. If part of what you need is not built, you hear it then rather than in month two, and there is no minimum term if you start and change your mind.

Your data

Records, access and getting out.

Who can see patient information?

Only the people you give access to. Roles are enforced on the server, not by hiding a button in the interface, so someone without permission is refused rather than merely not shown the link, and the attempt is logged.

What happens when a staff member leaves?

You remove their account and their access goes with it. What does not go is the record of what they did: the audit trail keeps the actor, the timestamp and the values before and after.

Where is our data held?

Freemi is built in Dublin. Rather than imply a location that would need qualifying, we will put the specifics of processing, hosting, retention and contractual terms in writing for you on request, so your practice has an answer it can actually rely on.

If we leave, what happens to it?

You export it and we delete our copy. There is no minimum term and no exit fee, and getting your own records back is not a professional-services engagement.

How the AI works

What runs on its own, and what does not.

Will it answer patients without us knowing?

Only where you have said it can. You decide per workflow what Freemi handles and what it routes to a person, your team signs that off before launch, and every action is visible afterwards.

Does it make clinical decisions?

No. Anything requiring professional judgement is routed to an authorised person rather than answered automatically. Freemi drafts, your team sends, and the audit trail shows which was which.

Does it learn from our patients?

You refine the rules over time; the system does not quietly change its own behaviour on your data. If you want something answered differently, you change the rule and you can see that you changed it.

What happens when it is unsure?

It hands over. The design bias is to escalate rather than guess, because a patient waiting ten minutes for a person is a far better outcome than a confident wrong answer.

Commitment

Money, terms and the small print.

How is it priced?

One monthly price per location, based on your setup rather than a tier chart. No setup fee, no minimum term. Tell us what you run and we will send a written figure.

Do we pay per user?

No. Adding a receptionist, a locum or a weekend assistant does not change the price. A busy team should not cost more to run than a quiet one.

Is there a contract?

There is an agreement, but not a lock-in. No minimum term, and you can leave with your data.

Do you replace our dispensing or practice system?

No, and we do not want to. Freemi runs the patient messages, the request queue, services, staff and the registers around it. Your clinical system keeps doing the job it is good at.