Our Consultants' Former Clients

Most calls are the same questions again

Live agents spend their time giving the same answers again, while the calls that really need them wait in the queue.

  • The same questions, every day

    Live agents answer the same questions all day long.

  • Important calls wait in the queue

    Calls that need a live agent, such as disputes and complaints, end up behind routine questions.

  • Information changes, answers lag behind

    When a procedure is updated, the change reaches the answers given on the phone late and unevenly.

  • Where voice data is processed gets asked

    Every call carries the caller's voice and personal details; a compliance assessment asks where this data is processed.

From call to record in four steps

One conversation for the caller; a sourced answer and a logged outcome for your organization.

  1. GreetingTakes the call in Turkish or English; listens when the caller cuts in and keeps the conversation natural.
  2. Sourced answerAnswers from your organization's documents, the same source RuneDesk uses.
  3. TransferDoes not make up an answer to a question the source does not cover; it hands the call to a live agent.
  4. LoggingWhen the call ends, it logs a summary and the outcome.

Designed for KVKK and GDPR processes.

Your organization carries out the compliance assessment. In it you can show clearly where RuneVoice processes voice.

Voice
Processed inside your organizationCall audio is not sent outside your organization for processing.
Notice
At the start of the callThe caller is informed at the start of the call.
Consent and deletion
Flows readyReady-made flows for obtaining consent and handling deletion requests.
Infrastructure
Installed in-houseInstalled on your own infrastructure or on RuneBox.

The same information on screen and on the phone.

RuneVoice and RuneDesk use the same document source: when your live agent asks RuneDesk on screen and a caller asks RuneVoice on the phone, the answer comes from the same documents. When a document is updated, both answer with the current information. If RuneGate is in place, AI requests go through RuneGate. RuneVoice is installed on your own infrastructure or on RuneBox; either way it runs on your organization's network.

Architecture On-premise setup
Corporate network
Applications RuneVoice RuneDesk
Access RuneGate
Infrastructure RuneBox

On your own infrastructure or on RuneBox, RuneVoice runs on your organization's network.

Frequent questions do not wait; difficult calls stay with live agents.

  • Answers without waiting

    Frequently asked questions are answered without joining the queue for a live agent.

  • Time for hard calls

    Live agents have time left for the calls that really need them.

  • Current information

    When a document is updated, RuneVoice answers with the current information too.

  • Every call on record

    A summary and the outcome of every call are logged.

Call center and customer service teams

For customer service teams whose call load is growing and who do not want voice data to leave the organization.

  • Call center managers

    Leave frequent questions to RuneVoice; reserve live agent capacity for the calls that get transferred.

  • Live agents

    Take over the calls the source cannot answer; find a summary and the outcome of every conversation in the record.

  • Compliance and legal teams

    Show where voice is processed; find notice, consent and deletion flows ready.

  • IT teams

    Use one document source on two channels; install RuneVoice on your own infrastructure or on RuneBox.

Frequently Asked Questions

What is a voice customer agent?

A voice customer agent is software that takes incoming phone calls and answers the caller's questions by talking with them. RuneVoice answers from the same document source as RuneDesk; when a question has no answer in the source, it does not make one up and hands the call to a live agent.

Which languages does it speak?

It speaks Turkish and English. When the caller cuts in, it listens and keeps the conversation natural.

Which knowledge source does it answer from?

From your organization's documents. RuneVoice and RuneDesk use the same document source; the answer on the phone matches the information in RuneDesk.

What happens if the source has no answer?

It does not make up an answer; it hands the call to a live agent. A summary and the outcome of the conversation are logged.

What happens when documents are updated?

When a document is updated, RuneVoice answers with the current information too; you do not need to update what is said on the phone separately.

Where is voice data processed?

Inside your organization. RuneVoice is installed on your own infrastructure or on RuneBox; either way, voice is processed in-house. The caller is informed at the start of the call, and consent and deletion flows are ready. RuneVoice is designed for KVKK and GDPR processes; your organization carries out the compliance assessment.

Request a demo with your own call scenario

Tell us about your customer line, the most frequent questions and your preferred setup; we will get back to you within one business day.

Request a demo