Skip to content
ReceptOwl

Trust

AI transparency and data, in plain English.

How ReceptOwl agents behave, when they hand over, what they collect and how that information is looked after.

One short line, then a natural conversation

Every conversation opens with a warm greeting in your business’s name from the receptionist you’ve named — for example “Hiya, you’re through to Harbour Road Motors, I’m Niamh, the AI receptionist.” After that, it’s simply a natural conversation in your tone: no robotic menus and no repeated disclaimers.

That one line is there because the EU AI Act asks for it: AI systems that talk with people must make clear they’re an AI, unless that’s already obvious. The rule has applied since 2 August 2026 (Article 50). If a customer asks whether they’re talking to a person, it answers honestly. Work that happens behind the scenes — updating your diary or CRM, summaries and reports — doesn’t talk to anyone, so it needs no mention.

Anything that needs you comes straight to you

Each setup has handover rules agreed with you — emergencies, complaints, payments, anything sensitive, anything outside approved answers — and says who is alerted, how, and what the customer is told. If a customer asks to speak to someone, it puts them through or takes a message, whichever you prefer. The step-by-step walkthrough shows where those rules apply, and the product tour shows the controls you keep.

It answers from what you approve

Each agent works from a knowledge base built from your public information and anything you send us. You review the critical parts — prices, hours, services and policies — before anything goes live, and you can change them at any time.

Text from websites, documents or customers is treated as information, never as instructions to the agent. That protects your setup from someone trying to talk it into doing something it shouldn’t.

Extra care in sensitive sectors

For clinics, physiotherapists, vets and other regulated services we keep agents deliberately narrow: general questions, appointment requests and handover. No diagnosis or clinical advice, and no health details beyond what a booking needs.

Only the data the job needs

We agree with you what each agent collects — typically a name, contact details and what the customer needs — and nothing more. Agents don’t take card details in conversation; if you want to take payment, they can send a secure link from your payment provider.

When we handle your customers’ data, we do it on your behalf and under your instructions. Before any real customer data is processed, we put a data processing agreement in place with you. It lists the service providers involved (for example telephony, messaging, AI model and hosting providers), where they process data, and how long information is kept.

How long information is kept

Retention is agreed with you for each setup and written into the data processing agreement. When it ends, data is deleted or returned. You can ask us to delete a customer’s information at any time.

Security basics

  • Access to conversations and leads is limited to the people who need it, with individual accounts.
  • Passwords and API keys stay on servers, never in the browser.
  • Data is encrypted in transit (HTTPS/TLS).
  • Changes to leads and settings are logged.
  • New connections are tested with sample data before they touch real customers.

What we don't claim

We don’t claim certifications we don’t hold. If your business needs a particular standard or contract term, ask us — we’ll tell you plainly where we stand.

About this website specifically — the demo form, analytics and cookies — see our privacy notice and cookie policy.

Always ready to answer.

You can close for the night. Your front desk doesn’t have to.

receptowl.com