Back to blog Cross-Industry

When one robot rang another: our AI receptionist and a phone verification call

17 November 2026 · 3 min read ·CloudHeads Team

TL;DR

An automated verification call asked our AI receptionist, Kora, to press a key, and she could not. We taught her to recognise these calls, then locked the ability so it only works for ten minutes after we switch it on ourselves. If an AI answers your phone, do the same.

One robot rang another

Kora is the AI receptionist that answers the CloudHeads office line in Greek and English. She books appointments, takes messages and emails us a summary of every call.

This week OpenAI wanted to check our landline, so its system rang us. A recording said: "To hear your verification code, press 3."

Kora cannot press buttons. So she did what any polite receptionist would do and started talking. The recording waited a few seconds, asked again, then hung up. No code.

Why the call came at all

Most of us get verification codes by text message. A landline cannot receive texts, so when a service needs to confirm an office number, it rings the line and reads the code out instead. Account sign-ups, business listings and banking checks all do this.

For a business with a person on reception, this is routine. Someone picks up, listens and writes the code down. For a business whose phone is answered by an AI, it is a blind spot. The assistant was built to talk to callers, and a recording is not a caller. It does not wait for an answer, it does not understand "sorry, could you repeat that?", and it will not hold the line for long.

Fix one: teach Kora to recognise the call

The first fix was to teach Kora what these calls sound like. When a recording asks her to press a key to hear a code, she now:

1. stops talking 2. presses the key 3. listens quietly while the code is read out 4. puts the code at the top of the call summary in our inbox

That solved the problem. It also opened a new one.

Fix two: a lock we switch on ourselves

This was the part we cared about most. Some phone checks do not read out a code at all. They say "press 1 to approve this sign-in". An assistant that presses whatever a recording asks for could approve a sign-in that a stranger started.

So Kora cannot press keys at all in normal use. When we are expecting a verification call, one of us presses a button on a private page. That lets her press keys for ten minutes, and then the ability switches itself off. If we did not ask for the call, she will not act on it.

We tried OpenAI again. Kora pressed the key, stayed silent, and the code reached our inbox seconds later.

If an AI answers your phone

More and more services check phone numbers by calling them, so you will run into this sooner or later. Our advice:

  • Do not let the assistant press keys whenever a recording asks.
  • Make it something you switch on yourself, only for the few minutes you need it.
  • Have the code sent somewhere only you can see, such as your own inbox.
  • Before you rely on it, check three things:

  • What does your assistant do when a recording answers instead of a person? Trigger a verification call to your own number, or ask your provider, and find out whether it talks over the recording, hangs up or waits.
  • Where do call summaries go, and who can read them? A code that lands in a shared inbox is a code everyone with access to that inbox can see.
  • What else can it do during a call? If it can transfer calls, send links or make bookings, the same rule applies: anything it does because someone on the line asked should need your go-ahead first.
  • If you want to see how Kora is put together, the Kora case study covers the build.

    If your phone is answered by an AI and you are not sure how it handles calls like this, we are happy to take a look. Book a free 30-minute call.

    Some content creation may be supported by AI.
    All content is specified, edited and approved by a human in the loop.

    Enjoyed this post?

    Have a question or want to discuss your automation needs? We'd love to hear from you.

    Talk to us