One Voice.
A sense of where it is used.
Website, app or embedded system: Voice recognises its digital environment. Three illustrative scenarios show how this context could be used in a conversation.
See the exampleThe Voice Operating Layer
Your knowledge has more to say. The Voice Operating Layer makes it accessible through conversation in everyday work – and opens a path for your team’s experience to flow back.
What makes the answer possibleSearch. Ask around.
Compare information.
Knowledge sits in manuals, PDFs and people’s heads. Your team first has to bring the information together before it can move forward.
Ask. Understand.
Clarify the next step.
Your team asks in its own words. Information backed by evidence and open questions become visible together. Existing knowledge helps directly in the work situation.
01 · The foundation
Four building blocks help Frank turn existing knowledge into a clear answer.

Illustrative example · Shift handover
“What is still open since yesterday?”
Makes your sources accessible and provides relevant evidence with a traceable knowledge version.
Connects the task, knowledge and conversation. This is where the people responsible review new submissions and approve knowledge in their domain.
Listens, explains and asks relevant follow-up questions – adapted to the task and the user.
Shows what has been understood, which information is missing and what stage the result has reached.
02 · Voice Design
Which information is essential to the task? What has the user already said? Which exception changes the next step? With your domain experts, we develop conversation rules for relevant follow-up questions, clear explanations and well-defined handovers.
03 · The interface
Type. Speak. Work together. In your existing system.
Illustrative concept view · Content and functions are agreed during the pilot.
Frank now knows the status. But at work he discovers something that is not yet in any source.
04 · The knowledge cycle
Frank describes a new observation and explicitly confirms his submission. Voice can pass it on for review.
KSE ingests sources, makes knowledge accessible and preserves the evidence.
KSE provides evidence and versioned knowledge.
Voice speaks, listens and guides the conversation through the interface provided by Frontend.
Voice passes them on — a “correction” or “new knowledge” remains a proposal.
TalkTo handles new statements, contradictions, steward follow-up questions and approvals.
Approved knowledge flows back into KSE as a new knowledge version.
Stage 6 returns to stage 1
This is how the knowledge cycle is designed. We connect KSE with TalkTo during the project.
Fictional example · Frank's submission
“The spare part has been confirmed, but this is not yet documented in the handover.”
At this point, that is Frank's statement. The person responsible checks whether it is supported by evidence and applies to the equipment concerned.
Frank explicitly confirms what he wants to submit for review. The correction includes the original question and its evidence context. Voice passes on the confirmed submission.
The person responsible for the knowledge checks: Who confirmed the spare part? Where is this documented? Which equipment does it apply to? Missing information leads to a follow-up question.
The domain expert decides on approval in TalkTo. Inclusion in KSE must then be confirmed. Only then is the submission part of the confirmed knowledge version.
Frank can ask for the “Status of my submission”. We configure the review process and the connection between TalkTo and KSE during the project. Knowledge approval, conversation profile and interface design remain separate decisions.
05 · Five checkpoints
You can see what an answer is based on and who decides on knowledge and access.

People approve knowledge, not the AI.
Answers rely on your evidence.
Every knowledge version is traceable.
Access is time-limited and revocable.
Limits and responsibilities are defined during the project.
New at Overmind
Website, app or embedded system: Voice recognises its digital environment. Three illustrative scenarios show how this context could be used in a conversation.
See the exampleOutlook: Components and connections could become structured data—a basis for questions in conversation. We explore the idea with a simplified example.
Explore the idea06 · Working together on the project
During the project, we agree which sources apply, how VOP speaks and where your team accesses it.
Illustrative scenario
Set up the company, appoint a steward and add sources. Once processed, the knowledge is available for retrieval.
Define the name, solution and conversation goal. The use case identifies the topic and knowledge area.
Configure the voice, language and conversation profile. New conversations use the active profile version.
Test live, approve the voice sample and deliberately start the service. It is then active internally.
Create the design and assign it as a fixed version. Its name and version number are visible.
Approve access and share a link or widget. Guests use a time-limited access code to speak.
A person approves the voice sample and deliberately starts the service.
The design is adopted as a fixed version.
Guest access is explicitly published.
A test does not open guest access. A new design does not replace the deliberate start or the publication of access.
What partners say
“Overmind's Voice Operating Layer is a great technology that helps companies in South Africa take the fast route to automation and advanced voice AI solutions.”

“Overmind.one supports Europe's companies in becoming the most innovative and sought-after in the world. With care, critical reflection, creativity, courage and commitment. The Voice Operating Layer is closely linked to my understanding of innovation.”
Hans LercherProfessor, entrepreneur“Our VOP gives companies the tool they urgently need to strengthen the flow of knowledge, and so to make the people in companies more confident and more competent. Not replacing people — making them better. That is our credo.”

The portraits show the people quoted. Quotations translated from German.
From the example to your company
Frank has a clearer picture: He can pass on confirmed information, identify open questions and submit a new observation for review. Which task could this help your team with?
We focus on shaping conversations around your domain. Together with your experts, we clarify which details matter, when a follow-up question helps and what needs to be available at the end. With Social Coding, we adapt the conversation, knowledge and interface to this workflow. What matters is whether it helps your team handle a specific task better.
Microsoft already offers tools for voice agents, enterprise knowledge and system actions. Overmind makes sense when you want to develop the domain-specific design and rollout for your business together with us: relevant questions, your terminology, typical exceptions and a verifiable result. We clarify whether and how your Microsoft systems can be integrated for the chosen use case.
These gaps are explicitly part of testing. Together, we define which sources apply and when a follow-up question or human clarification is required. Evidence and the knowledge version make the basis of an answer verifiable. An open question must not be presented as confirmed information.
No. A submission confirmed by the user initially remains a proposal. The domain expert responsible checks evidence, validity and possible contradictions and decides on approval. It only becomes part of the new knowledge version once its inclusion has been confirmed. We set up the review process and the connection between TalkTo and KSE for your use case.
That depends on the agreed use case and the available integrations. We define whether VOP explains, captures information, prepares a draft or executes a system action. During the pilot, we explicitly distinguish between simulation, draft and actual submission. An executed action must have a verifiable result status.
We start with a clearly scoped task, selected sources and a person responsible for the domain. This reveals which content is missing or needs clarification. We develop the conversation and interface for this use case. The effort depends mainly on source quality, domain rules, desired integrations and the review and approval process required.
Before use, we clarify which content may be processed, which services are involved and who should have access to knowledge and results. This also includes storage, deletion and the handling of sensitive information. The specific solution must fit your domain and organisational requirements; we review these for the agreed use case.
We agree a specific task and verifiable success criteria in advance. For example: Are reports more complete? Are unnecessary follow-up questions avoided? Can corrections be incorporated correctly? Does the handover reach the target system? We test the agreed cases, including errors and exceptions, and record what works and where limitations remain.
Solution concept · Availability and scope are agreed for each project.