Skyline Comms is your business phone system, run as a service and driven from the same console as your servers, domains and mailboxes. Extensions and SIP devices, inbound and outbound routing, IVR menus, ring groups, call queues with agent tiers, voicemail, fax, call recording, business hours and live call monitoring — all self-service, all billed in SAR by a Saudi provider. Free 14-day trial, no credit card.
No card to start. Your wallet opens with SAR 50 of credit using code SKY30.
Servers move to the cloud, mail moves, files move — and the phones stay exactly where they are, because the phones are the one system nobody in the company is willing to break. There is a box in a cupboard, an integrator who understands it, and a quiet agreement not to touch either. When something does need changing — a new branch, a new IVR greeting for Ramadan hours, a salesperson who wants calls to follow them to a mobile — it becomes a ticket, a site visit, and a wait.
A cloud PBX changes the ownership of that work rather than merely the location of the hardware. Skyline Comms puts the whole administrative surface in your console: not a cut-down "self-care" page with three toggles, but the same screens an administrator would expect from a full PBX. That is the honest measure of a hosted phone system — how much of it you can change on a Thursday afternoon without phoning anybody.
Six groups of screens, each doing one job. Nothing below is a roadmap item; every row is a page you get on day one.
| Group | Screens | What you do there |
|---|---|---|
| Extensions & devices | Extensions, Devices, Registrations | Create extensions, register desk phones and softphones, hold each device's SIP lines and its BLF / speed-dial keys, and request a device provisioning URL so the handset pulls its own configuration |
| Numbers & routing | Phone Numbers, Inbound Routes, Outbound Routes, Number Translations, Emergency | Point an inbound number at an extension, ring group, IVR or voicemail box; send a dialled pattern out a chosen trunk; rewrite a number before routing continues; set the emergency caller ID and trunk |
| Answering & flows | IVR menus, Ring Groups, Queues, Call Flows, Business Hours, Follow Me, Call Forward | Build digit-by-digit auto-attendant menus and sub-menus, ring a group of members, run queues with agents in tiers, flip a flow between day and night, define time windows with a match and no-match destination, chase a person across several legs |
| Messaging & media | Voicemail, Fax, Recordings, Audio Prompts, Music on Hold, Streams | Voicemail boxes with their messages and greetings, fax boxes with received files, call recordings, the IVR and system prompts your callers hear, and hold music |
| Live operations | Operator Panel, Active Calls, Active Queues, Active Conferences, Call History, Overview | See who is registered and who is on a call, watch live channels and live queues, and read call history with a thirty-day summary |
| Controls | Call Block, PIN Numbers, Feature Codes, Conferences, Call Broadcast, Domain Settings | Block nuisance numbers, require a PIN for certain dialling, enable or disable the star-prefixed feature codes, run conference centres with rooms, and send a broadcast call |
There is a particular failure mode in self-service telephony: the vendor exposes a text box, the customer pastes configuration into it, and the next support call begins with "we don't know what changed". Skyline Comms is built the other way round. Every screen collects named fields and the platform composes the underlying dialplan from them.
Four screens refresh against the live switch: active calls, active queues, active conferences and SIP registrations. The operator panel adds presence for your own extensions — registered, on a call — which is the view a receptionist or a floor supervisor actually wants. Call history lists recent calls with a thirty-day summary alongside, so "did that customer ever get through?" is a search rather than an escalation.
Call recording exists in the console. Recordings are produced by the call path and listed for your team; a member can play one back or delete it. There is deliberately no way to add a recording by hand, because a call log that can be authored is worth nothing as a record.
What we will not do is tell you when you may record, whom you must notify, or how long you should keep the audio. Recording obligations depend on your sector, your contracts, your employment terms and advice we are not qualified to give. We build the switch and the storage; the policy is yours, and it is worth writing down before you enable recording rather than after.
Read screens are open to your members; changes are not casual. Creating an extension, editing a route, resetting a device password or deleting a recording all require a two-factor step-up, and tenant scoping is enforced on the server for every screen — including the live ones, which re-fetch through the same scoped path. No screen accepts a tenant identifier from the browser, so there is no request to tamper with.
Written walkthroughs for each screen live in the Skyline knowledge base, in English and Arabic. If the rest of your stack is moving too, the cloud server and business email pages cover compute and mail, domains and DNS covers the names your services answer on, and data residency in Saudi Arabia is the page to read if residency is what put telephony on your agenda in the first place.
It is a cloud PBX — the phone system for your business, run as a service and administered from the same Skyline console you use for servers, domains and mail. You create extensions, register SIP desk phones or softphones against them, point your inbound numbers at whatever should answer, and watch calls as they happen. There is no appliance in your comms room and no separate vendor portal to learn.
Nearly all of it. The console ships more than thirty telephony screens: extensions, devices, phone numbers, inbound and outbound routes, number translations, IVR menus, ring groups, call queues with agent tiers, call flows, business hours, follow-me, call forward, voicemail, fax, call recordings, audio prompts, music on hold, streams, call block, PIN numbers, feature codes, conferences, call broadcast, emergency routing, plus live views of active calls, SIP registrations, active queues and active conferences, an operator panel and call history.
No — and by design you cannot. Every screen collects structured fields and the platform composes the underlying dialplan on your behalf. An inbound route is a destination number plus an action and a target; an outbound route is a dialled pattern plus a trunk. The console never sends raw XML, which is what keeps a wrong click from becoming a broken phone system.
Yes. Outbound routes send a dialled pattern out a nominated trunk or gateway, and inbound routes take a destination number and hand it to an extension, ring group, IVR or voicemail box. Number translations rewrite a matched number before routing continues — the usual Saudi case being to strip a leading 0 and prefix 966 so that internal habits and international format stop fighting each other.
Yes. Recordings are produced by the call path and appear in the console, where a member can play back or delete a recording. The screen is deliberately read-and-delete only: nothing in the console can fabricate a recording that did not happen. What you must decide is your own policy for recording, notifying and retaining — that is a legal and HR question for your organisation, not a setting we can answer for you.
Scoping is enforced on the server, not in the browser. Every telephony screen renders only what the controller returned for the caller's own domain, the live screens re-fetch through the same scoped path, and no screen accepts a tenant identifier as input. On top of that, changes — creating an extension, editing a route, resetting a device password — require a two-factor step-up, so a hijacked session cannot quietly re-route your calls.
Each device row holds its SIP lines and its BLF or speed-dial keys, and a row action asks the PBX for that device's provisioning URL. You point the handset at the URL and it pulls its own configuration — far less error-prone than typing SIP credentials into a phone screen with a numeric keypad.
Billing is in Saudi riyals from your Skyline wallet, and invoices are issued as ZATCA Phase 2 e-invoices. Current rates are shown in the console rather than printed here, because a marketing page goes stale and a console does not. There is a free 14-day trial and no card is required to look.
Create an extension, register a softphone, build an IVR menu and dial your own number — in an afternoon, for free, for fourteen days. Support in Arabic or English, billing in SAR.
SAR 50 free credit with code SKY30
No card to start. Your wallet opens with SAR 50 of credit using code SKY30.