Speech-to-Text · Text-to-Speech · Conversational Voice AI
Turkish-specialized Voice AI for enterprise operations
Built for Turkish. Adapted to your organization. No 3rd party solutions.
Mank Yazılım develops its own Speech-to-Text, Text-to-Speech and end-to-end Conversational Voice AI technologies, and adapts them to each organization's data, infrastructure, operational processes and security requirements. The technology is designed for real enterprise and contact-centre operations, and can run on-premise, in a private cloud, or on Mank infrastructure located in Türkiye.
AI that goes beyond talking in a demo and completes the job in live operations.
Built for real operations
Three technology layers, one operation
Each layer can be used on its own; together they form a system that runs the call from start to finish.
Conversational Voice AI
A voice assistant that completes the job, not just the conversation
An end-to-end voice assistant layer that listens on inbound and outbound calls, understands intent, executes transactions in your systems and reports the outcome in natural Turkish.
Explore Voice AISpeech-to-Text
Turkish speech recognition built for real call conditions
A Turkish speech recognition model developed for real call-center audio, with noise, line quality, accents, dialects and the disfluencies of natural speech.
Explore STTText-to-Speech
Natural voice technology that carries the rhythm of Turkish
Text-to-speech technology that respects Turkish stress, intonation and sentence rhythm, for enterprise notifications, call flows and accessibility scenarios.
Explore TTSWhat makes Mank different?
Own technology
Mank is not a wrapper that stitches together third-party chat services. It develops the speech recognition, synthesis and dialogue management layers itself, which is what makes real control over behaviour, latency and boundaries possible.
Turkish specialization
The models are developed with Turkish morphology, stress patterns and the disfluencies of spoken language in mind. This is not a general-purpose system localised through a translation layer.
Deployment under institutional control
The choice between on-premise, private cloud and Mank infrastructure in Türkiye belongs to the organization's data policy. Processing location, retention and access rights are configured per project.
End-to-end approach from PoC to production
The process is run as a whole: from discovery and success criteria to integration, controlled go-live and continuous improvement. The goal is a measurable operation, not an impressive demo.
How it works
Five stages, one flow. Every stage is bound to the organization's rule set and integrations.
- 01
Listens
Converts speech to text with low latency using Turkish-specialized STT under real call conditions.
- 02
Understands
Extracts intent, topic and required data fields, and evaluates them against the rule set defined by the organization.
- 03
Takes action
Runs queries or transactions in your systems through authorized API and tool calls.
- 04
Responds
Delivers the outcome in a consistent, controlled voice suited to the rhythm of Turkish, and hands off to a human when required.
- 05
Measures
Makes the conversation summary, structured data and process metrics reportable.
Where is it used?
Filter by category to find the scenarios closest to your own operation.
12 / 12
Inbound call handling and routing
Understanding the request through natural Turkish dialogue instead of a menu tree, completing what can be completed end to end, and handing off to the right team when needed.
ServicePayment reminders and collections calls
Rule-bound outbound calls with controlled tone that deliver reminders, capture payment intent and write the outcome back as structured data.
CollectionsSalesAppointment creation, changes and reminders
Creating, rescheduling, cancelling and reminding appointments through calendar and core-system integrations without human intervention.
AppointmentServiceIdentity and information verification steps
Confirming information according to the organization's own verification rules and safely escalating to a human when verification fails.
VerificationPolicy, account and transaction information
Retrieving current information through authorized API queries and relaying it to the customer in natural language.
ServiceShipment and delivery status enquiries
Status lookups by tracking number or customer record, delivery-window guidance and address confirmation.
LogisticsServicePost-call satisfaction and feedback
Short, natural and repeatable feedback conversations that collect structured satisfaction data.
FeedbackCall transcription and operational analytics
Transcribing all conversations with Turkish-specialized STT and making them reportable with topic, intent and outcome labels.
AnalyticsLead qualification and sales preparation
Pre-qualifying inbound interest, asking fit questions and delivering a structured summary to the sales team.
SalesControlled human handoff
Transferring the conversation to an agent together with its summary whenever there is uncertainty, objection or an out-of-policy situation.
ServiceVoice notification and announcement flows
Publishing updatable, consistently voiced notification flows produced with TTS.
ServiceLogisticsQuality monitoring and compliance checks
Making mandatory disclosures, durations and process adherence measurable once conversations are transcribed.
AnalyticsFeedback
How is it deployed?
| Criterion | On-premise | Private cloud | Mank infrastructure in Türkiye |
|---|---|---|---|
| Data control | Data and models stay in the organization's own data centre; access is governed by the organization's own authorization structure. | Runs in the organization's own cloud account, in a dedicated environment governed by the organization's policies. | The service is delivered from Mank infrastructure located in Türkiye; the scope of data processing is defined contractually. |
| Isolation | The highest level of network isolation; outbound connectivity requirements are defined by the organization. | A tenant-isolated environment; network and identity controls follow the organization's cloud configuration. | Per-organization isolated configuration; access and retention periods are defined per project. |
| Operating responsibility | Hardware, capacity and operations sit with the organization; Mank provides installation, adaptation and version support. | Capacity elasticity is higher; operational responsibility can be shared between the organization and Mank. | Operations and version management sit with Mank; the organization's infrastructure investment is lowest here. |
| Best suited when | When data residency and network isolation requirements are the deciding factor. | When scalability and institutional control are both required. | When a fast start and low operational overhead are the priority. |
On-premise
- Data control
- Data and models stay in the organization's own data centre; access is governed by the organization's own authorization structure.
- Isolation
- The highest level of network isolation; outbound connectivity requirements are defined by the organization.
- Operating responsibility
- Hardware, capacity and operations sit with the organization; Mank provides installation, adaptation and version support.
- Best suited when
- When data residency and network isolation requirements are the deciding factor.
Private cloud
- Data control
- Runs in the organization's own cloud account, in a dedicated environment governed by the organization's policies.
- Isolation
- A tenant-isolated environment; network and identity controls follow the organization's cloud configuration.
- Operating responsibility
- Capacity elasticity is higher; operational responsibility can be shared between the organization and Mank.
- Best suited when
- When scalability and institutional control are both required.
Mank infrastructure in Türkiye
- Data control
- The service is delivered from Mank infrastructure located in Türkiye; the scope of data processing is defined contractually.
- Isolation
- Per-organization isolated configuration; access and retention periods are defined per project.
- Operating responsibility
- Operations and version management sit with Mank; the organization's infrastructure investment is lowest here.
- Best suited when
- When a fast start and low operational overhead are the priority.
None of the three models is universally superior. The right model follows from the organization's data policy, existing infrastructure, expected scale and operating capacity.
From PoC to production
A voice assistant speaking fluently in a demo does not mean it completes the job in live operations. That is why the process starts with measurable success criteria and continues with a controlled go-live.
A PoC is not success. Success is measured in live operations.
- 01
Discovery
- 02
Success criteria
- 03
PoC
- 04
Integration
- 05
Controlled production
- 06
Continuous improvement
- Fibabanka
- Genç Sigorta
- TRAI
- KOSGEB
- Kadraj Group
- AiThinks
- Verti
- Co-one
Let's assess your operation together
Let's clarify which use case fits automation, which integrations are required and which deployment model suits your organization.
