IP Telephony
voice that stays on the books.
Business communication and IP telephony, from a single PBX to hosted voice.
Services / IP Telephony
-
check_circle
3CX Gold Partner
How we stay current on editions, simultaneous-call limits, Microsoft 365 integration, and contact-centre configuration.
-
check_circle
Yeastar in the same portfolio
Appliance, software, or hosted PBX when the estate prefers Yeastar to 3CX. We will not force one SKU.
-
check_circle
Our time versus the licence
Design, cutover, SIP, queues, and training are this service. The entitlement is the product.
-
check_circle
Can live on Cloud EA
A Linux VPS can carry the PBX so it does not live in a cupboard. The VM stays on its own invoice line.
What this service is
IP Telephony is the Patolink voice practice: on-site, hosted, or hybrid. We design the system, deploy it, configure trunks and users, cut over, train the people who will live on it, and stay for support. The products that usually travel with it are 3CX and Yeastar.
Patolink is a 3CX Gold Partner in Kenya. That is the path for licences, unified communications, and call-centre work. Yeastar is the path for PBX appliances, software, and hosted instances. Poly and Jabra headsets and room systems can sit on the same order when the room needs them.
Buying a licence without implementation is how a contact centre ends up with a dial tone that still dumps callers into a generic IVR. This service is the professional work. The licence, the appliance, and any Cloud EA host stay on their own product lines so renewals stay honest.
Tell us extension count, sites, and whether you prefer 3CX or Yeastar. We quote from Unit 1105, Applewood Adams, Ngong Road. info@patolink.com · +254 709 343 000.
Who typically buys it
- —Contact centres that need queues, recording, and reporting — not only a dial tone.
- —Multi-site firms that have outgrown a single analog board.
- —Teams that want 3CX or Yeastar hosted on Cloud EA instead of a box on-site.
- —Estates already on Microsoft 365 that want the phone system in the same tenant.
Service areas
IP telephony
The overall voice practice: on-site, hosted, or hybrid — written before we order a licence.
IP phone systems
Handsets, softphones, and the systems they register to, including Poly and Jabra when the room needs them.
PBX solutions
Appliance or software PBX design that matches extension counts and call paths.
Hosted PBX
Voice hosted by Patolink or on a Cloud EA instance we operate, instead of a box in the cupboard.
SIP-based communication
Trunks, DIDs, and the SIP configuration that makes outbound and inbound calls reliable.
Unified communications
Presence, chat, and meetings where the chosen platform supports them — notably 3CX with Microsoft 365.
Call centre solutions
Queues, agents, recording, live chat, and reporting when the business is inbound-heavy.
Telephony deployment
Physical or remote install, cutover, and training — not a PDF left in a share.
Telephony configuration
Dial plans, IVR, recordings, and user provisioning for day one.
Support and maintenance
Ongoing changes, upgrades, and break-fix after go-live, on a recurring line.
How a voice project runs
-
Step 01
Count the estate
Sites, extensions, simultaneous calls, existing trunks, and whether the PBX should live on-site or on Cloud EA.
-
Step 02
Choose the product
3CX or Yeastar — or an honest recommendation when you have not chosen. Headsets and a VPS are named only if they belong.
-
Step 03
Deploy and cut over
Install, SIP, dial plan, IVR, users, and training. Go-live is a written window, not a Friday-night guess.
-
Step 04
Support after day one
Changes, upgrades, and break-fix on the service line. Licences and the VM renew on theirs.
What a quotation names
A quotation can mix this service with 3CX or Yeastar products. They stay separate catalogue records so billing stays clear.
Implementation hours
Design, deployment, SIP, cutover, and training — our time on this service line.
3CX or Yeastar product
Licences, edition, simultaneous calls, appliances, and extensions on the product record.
Hosting if needed
A Cloud EA Linux plan when the PBX should not live on-site. The VM is not hidden inside the voice invoice.
Support plan
Recurring maintenance after go-live, plus any headset or room system on its own product line.
How 3CX and Yeastar attach
3CX is licences, deployment, SIP, extensions, call-centre configuration, and maintenance. Gold Partner is how we stay current on editions and Microsoft 365 integration. That integration is scoped, not assumed.
Yeastar is PBX systems, communication appliances, licences, extensions, implementation, and support plans. Some accounts prefer hardware they can see. Some prefer 3CX software. We will not force one SKU when the other is the better fit.
What this page does not pretend
There is no public shelf price for seats, editions, or boxes. Extension count and call-centre scope change the quote. A CRM write-back into Dynamics is a Microsoft Solutions or Dynamics product conversation sitting next to this one — not a free extra.
After go-live the VM — if we host it — appears in the customer portal. Voice changes stay on this service. That is the point of keeping the lines separate.
Related products
Scope a voice project
Tell us extension count, sites, and whether you prefer Yeastar or 3CX. We will quote service and product together from Nairobi.