We test your AI chatbots and voice agents before your customers do.

You get a clear go or no-go for every journey and language, with the evidence behind it.

  • Written authorization first
  • No access to your code
  • Every result labelled
Passport Example · fictional data
  • Change a bookingEnglish · Chat. Every check met.
    Go
  • Change a bookingEuropean Portuguese · Chat. Works, but the tone is too informal.
    Review
  • Ask for a refundRomanian · Chat. Invents a refund policy you don’t have.
    No-go
  • Check an orderEnglish · Voice. Not tested yet, and we say so.
    Not tested
Every verdict links to the conversation behind it. Not tested is never counted as a pass.

Your chatbot speaks for your company.

These are the failures we find before a customer does.

  • It promises a refund you don’t offer.

  • It answers in the wrong language, or the wrong tone.

  • It shares one customer’s details with another.

How it works

  1. 1

    Tell us what your AI agent does.

    Give us a test chat or an endpoint, and say what it must never do. We never need your code.

  2. 2

    We test it the way customers would.

    Simulated customers run your real journeys. We try to talk it into breaking your rules. Native speakers set the standard in each language.

  3. 3

    You get a clear go or no-go.

    A verdict for every journey, language and channel, with the conversation behind it and a fix for each finding.

We check three things

  • Security

    Can it be talked into breaking your rules or leaking customer data?

    How we test security
  • Customer journeys

    Do real journeys, from bookings to claims, end with a customer who got help?

    How we test journeys
  • Language

    Does it sound right to a native speaker, in chat and on calls?

    How we test language

See it in the platform.

Your team gets a login to the AltaSec console for the whole engagement. This is a verdict view from our lab, with lab data.

The Passport in the AltaSec console, lab data: a verdict matrix with security in chat for English marked No-go, 185 breaches found in 185 assessed attacks, and the same check for Romanian and European Portuguese marked Not tested, with the note that no attack has been run in that language yet.
  • No-go, with the evidence. Every breach is a conversation you can open and read.
  • Not tested, and it says so. A language we haven’t attacked yet is never shown as a pass.
  • Lab data. Nothing in this view belongs to a client.

See the whole platform

A clear go or no-go for every launch.

This is what you receive: the Passport.

  • A verdict for every journey, language and channel, with the conversation behind it.
  • Every test conversation, in full, in your own console login.
  • Each finding with a suggested fix.
  • What we did not test, and why.

The Passport is our verdict from our tests, not a certificate or badge: no test can prove an AI is right 100% of the time.

How we test and judge

  • Go

    Ready for this journey, language and channel. Every check met.

  • Review

    It works, with a problem to fix first.

  • No-go

    A failure you can’t afford. Some are never averaged away: one customer’s data shown to another is always a no-go.

  • Not tested

    Not tested, with the reason stated. Never counted as a pass.

Start with a pilot.

One chatbot or voice agent, one or two journeys. Bring one journey and we’ll show you how it would be tested.

  • Your data stays in the EU
  • Written authorization before we test
  • No access to your code
  • You work with the founders

Questions from your security or legal team? Read the answers.

Make AI trustworthy.