Contact centre solutions
Three contact centre approaches, one set of criteria: let’s work out which fits you
A contact centre is where an organisation meets its customers by phone and in writing: answering inbound calls, running outbound campaigns, handling WhatsApp and web chat conversations, and reporting on all of it are parts of the same operation.
No two organisations need the same thing. Some change their call flow often and want a flexible platform; some want to start fast; some need a corporate phone system rather than a contact centre. We deploy all three options: Voyce, Alotech and 3CX. Our real job is positioning the right product for your needs and making it work with the systems you already have.
Settle this first: contact centre or PBX?
This is the point most often confused when choosing. Both make phones ring, but they are built for different jobs.
Three options, three different relationships
Solution Partner
Voyce
Cloud contact centre platform. Voice and messaging channels, auto-dialler, quality evaluation and a visual IVR designer in one system. Licence, installation, support and development for your needs are ours.
- In the cloud or on your own server
- Your own team builds the IVR flow
- Per-agent monthly licence
Business Partner
Alotech
Ready-made cloud contact centre service. Alotech operates the platform; we provide the licence, number delivery, integration and first-line support.
- No hardware, short deployment
- WhatsApp Business API and WhatsApp Call
- Peki chatbot integration
Silver Partner
3CX
IP-based corporate phone system. In the cloud or on your own server; web, mobile and desktop apps. Licence, installation, integration and support are ours.
- Licensed by simultaneous calls
- Extensions, routing, video conferencing
- CRM and Microsoft 365 compatibility
Comparison table
The rows are the questions asked most often when deciding. The cells describe what each product offers today, not a promise.
| Criterion | Voyce | Alotech | 3CX |
|---|---|---|---|
| What is it for? | Full contact centre: voice, messaging, campaigns, quality | Ready-made cloud contact centre service | Corporate phone system and internal communication |
| Whose product, and Tecmony’s role? | Voyce; we are its solution partner. Licence, installation, support and development for your needs are ours | Alotech; we are its business partner. Licence, number delivery, integration and first-line support are ours | 3CX; we are a Silver Partner. Licence, installation, integration and support are ours |
| Call flow flexibility | You build and change the flow yourself in the visual IVR designer | Within the platform’s ready-made flow structure | PBX-level routing and voice menus |
| Development for your needs | We build custom reports, integrations and flows | Tied to the platform roadmap; we develop the integration layer | Licensed product; through integration and configuration |
| Deployment speed | Fast in the cloud; custom flow design sets the timeline | Fastest start, ready-made service | Cloud or on-premises; depends on scale |
| Where it runs | Cloud or your own server | Cloud | Cloud or on-premises |
| Messaging channels | WhatsApp, web chat, Telegram, SMS, e-mail in one inbox | WhatsApp Business API, WhatsApp Call, live chat; with the Peki chatbot | WhatsApp integration and internal chat |
| Campaigns / auto-dialling | Campaign management with power and dialer modes | Outbound within the platform scope; blended setup | Not contact-centre oriented |
| Quality and reporting | Quality forms, quality score, AI evaluation, speech analytics (AIQ) | AI-assisted CX Quality; standard reporting | Call recording and reporting |
| Licence model | Per agent per month; voice and messaging separate | Under a Tecmony contract | By number of simultaneous calls (SC) |
| Choose it when | Your flow changes often, it must run on your own server, or you want deep integration | You want to start fast and your needs sit within standard cloud contact centre scope | You need a PBX rather than a contact centre; extensions and corporate telephony come first |
Shared infrastructure
Whichever you choose, your numbers stay in our routing layer
All three platforms receive the call from the same place: your numbers terminate not in your building but at the Türk Telekom Esenyurt Data Centre on our VoIP Router infrastructure. Where the call goes is written there as a rule.
The number is not ported; the destination changes
A call delivered to Alotech today can be routed to Voyce or 3CX tomorrow. No porting process starts on the carrier side; only the delivery target changes.
Two data centres, synchronised configuration
The routing layer runs separately in Istanbul and Ankara. If one data centre has a problem, calls move to the other; you do not need to do anything.
Different carriers in one pool
Your 444 number, geographic numbers and international numbers are defined over a single interconnect. A call that cannot be answered in Izmir lands in the Istanbul or Ankara office without interruption.
How we work
If you cannot decide, this is how it goes
- Needs analysisYour call volume, agent count, channels, existing systems and how often your flow changes are measured. We do not guess the numbers; we read them from your current PBX or platform records.
- Product positioningBecause we deploy all three, we tell you which one fits and why. When needed, two run together: 3CX on the PBX side and VoIP Router on the call delivery side, for example.
- Integration and installationThe chosen solution is connected to your CRM, ERP and in-house applications; numbers are delivered, queues and flows are defined, the team is trained.
- Ongoing supportAfter installation, first-line support and coordination with the vendor stay with us as your single point of contact.
Products considered alongside the contact centre
CallGem
Recording of calls on mobile lines and device management; field teams’ phone conversations are archived with contact centre discipline.
Cloud PBX
PBX functions as a service with no hardware on your premises; for needs that call for a PBX rather than a contact centre.
VoIP Router
Numbers terminate in the carrier’s data centre and are delivered to the platform of your choice by rule; the common ground of all three solutions.
Frequently asked
Frequently asked questions
How do we choose between Voyce, Alotech and 3CX?
First answer the contact-centre-or-PBX question. If it is extensions and corporate telephony, 3CX. If it is a contact centre, the second question is your rate of change: if your flow changes often, it must run on your own server, or you want development done for you, Voyce; if your needs sit within standard scope and you want to start fast, Alotech. We deploy all three, so we are under no obligation to sell one in particular.
Do we have to replace our existing PBX?
Not always. We often run solutions side by side: 3CX or your current PBX on the telephony side, Voyce on the contact centre side, VoIP Router on delivery. Our routing layer hands the call over in whatever form the far end understands: to an on-premises PBX, a cloud PBX or a contact centre platform over a corporate SIP trunk. Once we have reviewed your current setup, we tell you what can be kept, and why.
Will our numbers be ported, and do we need to change carriers?
You do not need to change carriers. Instead of bringing your numbers down to your own location, we terminate them at the Türk Telekom Esenyurt Data Centre and route them to wherever you want. A number is never tied to a single carrier or a single building; your 444, geographic and international numbers are defined over one interconnect. Whichever contact centre solution you choose, delivery runs over this infrastructure.
Will our calls be interrupted during the migration?
The routing layer runs in Istanbul and Ankara under a synchronised configuration; if one data centre has a problem, calls move to the other. The real technical risk in a migration is not downtime but the two ends not speaking the same language: a codec or SIP version mismatch, or whether DTMF travels as an RFC 2833 event or inside the audio. We resolve these at the SBC layer by inspecting SIP messages and the RTP stream at packet level; what each side expects is measured.
We want an AI-assisted agent or a voice assistant. Which option?
On messaging channels, the AI agent is ready in Voyce’s flow designer: you set the provider, system prompt and knowledge base, and the conversation is handed to a person when needed. On the quality side, Voyce offers AI evaluation and speech analytics, and Alotech offers CX Quality. For a voice assistant we plan the request per project together with speech recognition and text-to-speech providers; scope and cost are settled after the needs analysis.
Let’s work out the right solution together
Tell us your agent count, your channels and your current PBX; we will assess all three options with reasons and present them in a single quote.
Or reach us directly: +90 (216) 912 00 79[email protected]