aore.ai hello@aore.ai

We build voice lines on your own servers

We take on the linesno cloud will hostand no headcount will cover.

Latency, language, data that can't leave your network: that's usually where talks with a vendor stall. We don't resell someone else's service. We build the line inside your network and get it to its first real call in three days.

01 / Who we build for

We work with companies
from delivery services to banks.

The hard part is the same everywhere: keeping latency down, surviving the peaks, staying inside your network. We've already built that part, and it runs on live lines today. All that changes by industry is the documents and the languages.

Banks and lenders

data stays inside your networkquestions about accounts and rates

Insurance

answers from policy documentscallback booking

Telecoms

high call volumeseveral languages on one line

Retail and delivery

order statuspeaks on sale days

Public sector and utilities

no outside cloudlocal language

Clinics

appointment bookingpatient data

BPO and contact centres

first-line callsroutine questions

If your industry isn't on this list, the line still works. All it needs is a phone number and the documents the agent will answer from.

02 / What you're choosing between

Three ways to solve this.
The third one is ours.

Cloud vendor

Live in a day, and cheap. But your audio and your documents end up in someone else's cloud.

Fast, but security won't sign it off

Operators only

No argument about the data. But the queue grows with volume, and a night shift costs more than a day shift.

Solid, but it won't scale

A line on your servers

We use the documents and the telephony you already have, and keep all of it inside your network.

Three days, and it stays yours

03 / What the agent does on the line

What you see
in every call.

The agent answers from your files and your systems, and under every answer we show the document it came from.

The agent's console: the call panel, the conversation panel and a knowledge base of ten documents.
The agent's console at call.aore.ai

One line speaks several languages: English, German, Russian and the other major European ones. Some languages, Georgian for one, aren't covered yet, and we tell you that up front. If the agent isn't sure of an answer, it passes the call to a person, following a rule you set.

Call summaryclosed
Caller's languageGerman
Duration1:12
Handed to an operatorNo
Transcriptin your CRM
The recording and the transcript stay inside your network

The transcript and the outcome land where your team already reads them.

A week on the lineMon–Sun
answered
closed without an operator
handed to a person
The report lands where you already read your metrics

04 / Where it already runs

Lines that are
live today.

2,000calls a day

95% closed without an operator

The agent handles first-line calls, with 10 to 20 operators behind it. R-10 sells the line under its own brand, with our engine underneath.

Liver-10.ai
An insurer's call centre600calls a day

The inbound line answers from the insurer's documents and books a callback.

Live
Under NDA1inbound line

A consumer-goods distributor: the agent takes inbound calls and answers from the catalogue and delivery terms. It only passes on the calls it isn't sure about.

Live

05 / How it's built

Here's where the call goes
and where your data stays.

Three steps sit between the caller's last word and the agent's first: recognition, retrieval and synthesis. Together they take about half a second. The fourth, recording, runs alongside.

Your network511 ms to first audio
INBOUND CALLANSWER TO THE CALLERYOUR NETWORK · YOUR SERVERS01RecognitionSpeech-to-text, streaming,with end-of-speech detection02RetrievalFrom your documents,not from the model's memory03SynthesisFirst audio goes out beforethe answer is finished04RecordingTranscript and outcomein your system

The dashed line is your network: the models, the index and the call recordings all stay inside it.

511 msp95 to first audio

Measured by us on production lines: first on a client's agent, then reproduced on a second

~1,000 msRoughly where callers start talking over the agent

We stay under it

On your hardware, we measure p95 again and write that number into the contract.

Models stay with youIndex stays with youRecordings stay with youTelephony is yoursNo outside cloud

06 / What we do in three days

A fixed scope
and the first call on day three.

One line, one set of documents, one handover rule. We send the terms by email after a short conversation.

three days

Start

scope agreed

Setup

line, documents, handover rule

First call

a real caller on the line

The line and your telephony

We connect your SIP trunk or give you a number, then set up routing and the handover rule.

three days

Your documents into the index

We take the documents the agent needs to answer from and build the index on your servers.

included

A test set written by a native speaker

A native speaker writes the test calls and sets the passing score.

included

A latency check on your stack

We measure on your GPUs, with your call routing.

included
The knowledge base panel in the demo: ten documents covering plans, payments, roaming, number porting and more.
The demo line's knowledge base: ten documents.

Let's talk about
your line.

Tell us what the line is for, how many calls a day it handles, and which documents the agent has to answer from. If you don't know yet, we'll work it out on a call.

The demo runs on a hosted stack so anyone can call it. Your line runs on your servers.

Or just write to hello@aore.ai