ServicesSecure chat and voice AI

Customer chat and voice AI that knows what it mustn't keep

We build and run chat and phone agents for WhatsApp, web chat, the phone and other channels. They hear names, numbers, health details and payment questions, so the rules for disclosure, consent and retention are set before the first conversation.

  • Says it's AI
  • Card numbers never stored
  • Hands over with the full history
Web chatExample, billing questionLive
Assistant

Hi, I'm the AI assistant for the billing team. I can help with invoices and payments, or pass you to a person at any time.

Can I just pay the balance? My card is ████ ████ ████ ████

Assistant

Please don't share card details in chat. I've removed them. Here's a secure payment link for the balance on your account.

Card number detected and removed before storage or the model. Payment handled by the payment provider.

The rules, built in

What a customer-facing AI may say, ask, store and pass on, decided with your compliance team and enforced by the system.

  • It says it's AI

    At the start of each conversation, and whenever someone asks. For systems that talk to people, the EU AI Act has required this since 2 August 2026.

  • Notice and consent

    Callers hear about recording before it starts. Messaging follows each channel's opt-in rules, and people can ask for a person at any time.

  • Only what it needs

    Questions limited to what the task requires. A booking assistant asks for a name and a time, not a medical history.

  • Card and health data kept out

    Card numbers are detected and removed, and payments go through hosted links. Health details are steered to secure forms that write straight into your system.

  • Transcripts on your terms

    Sensitive values redacted, transcripts kept for the period you set, stored in your systems or a vendor you've approved.

  • Handover with history

    Anything outside its scope goes to your team with the conversation attached, so nobody asks the customer twice.

Where each kind of data goes

Channels we build for

The most common ones. We build for other channels too, with the same rules.

  • Phone

    Answers in seconds, books, routes and takes messages in a natural voice, with recording notices and call summaries for staff.

  • WhatsApp and Telegram

    Booking, updates and questions through the official business APIs, with opt-in and template rules followed.

  • Website chat

    On your own domain, answering from approved content, with lead capture limited to the fields you need.

  • Instagram

    Replies to messages and comments, and hands sales or complaints to your team.

Questions

Does it pretend to be a person?

No. It sounds natural, and it says it's AI at the start and whenever anyone asks.

Can it take payments?

It sends a secure payment link from your payment provider. Card numbers never pass through the conversation, the transcript or the model, which keeps the AI out of your card data environment.

Can we use WhatsApp with patient data?

Carefully. We keep the assistant to scheduling, keep clinical details off the channel, and write bookings straight into your practice system. Your privacy officer should confirm the approach against your own HIPAA risk analysis.

Where are transcripts stored?

Where you decide: your CRM, your helpdesk or your own storage, redacted and kept for the period you set.

Talking to customers with AI? Set the rules first.

On a free 15-minute discovery call, tell us which channels you use and what customers share on them. We'll tell you what needs disclosing, what shouldn't be stored, and how we'd build it.

  • Pick a time that suits you
  • 15 minutes with an engineer
  • Clear next steps

Prefer to write first? hello@agentimus.io, or WhatsApp. We're glad to sign an NDA before you share details.

Or send us a message

Only your email is required. We use these details to reply to you. Privacy policy

Book a discovery call