 Sunco Communication and Installation Ltd. Cloud Communications Fit Assessment Prepared for Bowfort Medical Group |
Hello Priya Raghunathan, Thank you for completing the Sunco Cloud Communications Fit Assessment. Your personalized results are below. Assessment completed: August 24, 2026 |
Your Score A private tenant fits of the indicators point to your current model | | Platform Fit A private tenant fits Enough indicators point to a dedicated platform that a shared tenant would be worked around rather than used |
|
HOW THIS SCORE WAS CALCULATED This assessment does not score you. It reads 30 indicators and reports which of two platform models your profile points at — a shared-tenant public cloud service, or a private tenant dedicated to your organization. There is no grade, and the bands are not good and bad: a business whose indicators point at public cloud is not behind one whose indicators point at a private tenant, and the reverse is equally true. Each answer counts 0 to 3 toward a dedicated platform, so the 90 available points measure how strongly your profile leans rather than how well you are doing. The band boundaries are Sunco’s own division of that scale and nothing more — unlike the other assessments in this family, which take their boundaries from the ISO/IEC 33020:2019 achievement scale — ISO being the International Organization for Standardization and IEC the International Electrotechnical Commission — there is no published scale for platform fit, and borrowing one would lend authority this does not have. Some of these questions ask about preferences: how you would rather fund technology, whether you want one invoice, how much a support relationship matters to you. That is deliberate and it is the difference between this instrument and a readiness assessment. A preference is a legitimate input to a fit decision — a business that wants pure operating expense and self-service support is genuinely better served by a shared platform — where the same question inside a maturity assessment would be scoring a purchasing choice as though it were a capability. Where an answer is a legal requirement rather than a preference, the assessment says so and cites what is published: the Office of the Privacy Commissioner of Canada on your continuing accountability for personal information processed by a third party and on what you must tell people about processing in another jurisdiction; the provincial private-sector and health privacy laws deemed substantially similar to the Personal Information Protection and Electronic Documents Act (PIPEDA); and Recommendation G.114 of the International Telecommunication Union (ITU) for the delay budget speech has to fit inside. The three bands sit at the same boundaries the rest of this family uses — above 85% of the available points, above 50%, and below it — because a familiar division is easier to read than a novel one. Here they mean public cloud fits, either could work, and a private tenant fits. Answer options are shown in a fixed order rather than shuffled, because the order carries meaning here — each set runs from the simplest case to the most demanding, and shuffling it would make the question harder to answer without making the result harder to game. Six areas of five questions each means a single answer moves a fifth of that area, so read an area as direction rather than precision. This assessment surfaces which platform model fits your requirements — it does not certify compliance with any standard, and it is not legal advice. |
Section Breakdown | Section | Aligned | Risk Level | | Scale & Operational Complexity | 33% | A private tenant fits | | Security, Compliance & Data Location | 33% | A private tenant fits | | Customization & Integration | 40% | A private tenant fits | | Control, Administration & Support | 47% | A private tenant fits | | Reliability & Internet Dependency | 53% | Either could work | | Budget Model & Total Cost | 33% | A private tenant fits |
|
AT A GLANCE 0 point to public cloud | 28 could go either way | 2 point to a private tenant |
Every answer you gave, sorted by which way it points. Areas appear strongest-first within each. |
POINTS TO PUBLIC CLOUD · 0 What points to a shared platform Nothing in your profile points to a shared-tenant platform, which is unusual and worth reading the list below carefully for. |
|
MIXED · 28 What could go either way These lean toward a dedicated platform without settling anything on their own. Each one names what to check or ask before it becomes decisive. |
| Scale & Operational Complexity | 5 of 5 · 33% aligned |
| How many physical locations does your organization operate? | Toward private |
Your answer: 6–15 locations with varying needs Both models run multi-site organizations well; they charge for it differently. A shared-tenant platform prices by user and treats site-level differences — separate hours, separate routing, separate attendants — as configuration you do yourself or licensing you add. A dedicated platform treats them as ordinary configuration but costs more to stand up. The number of sites is not what decides it: how DIFFERENT the sites are from each other is. How Sunco closes this Six or more sites with genuinely different hours, routing and staffing is the point where shared-tenant platforms begin charging for what a private tenant treats as ordinary configuration. Worth pricing against your real site list rather than a per-seat average. |
No published standard governs this question · A circumstance or a preference, not an obligation How many places you operate from is a fact about your business. No standard says a number of sites requires a particular platform — what it changes is how much administration you are buying, which is a cost question rather than a compliance one. |
|
| What is your total user or seat count across all locations? | Toward private |
Your answer: 51–150 users Seat count changes which model is cheaper, and the crossover is not fixed — it moves with your feature list and how long you keep the platform. Below about fifty seats a shared platform is usually cheaper by a clear margin. Above that the two converge and the comparison becomes arithmetic you can do with two quotes, provided both are priced on the same feature list rather than on the entry tier. How Sunco closes this Above fifty seats the per-seat model and a dedicated platform converge, and which one wins depends almost entirely on how long you keep it. Two quotes and your own retention period settle this question in an afternoon. |
No published standard governs this question · A circumstance or a preference, not an obligation Seat count is arithmetic, and every platform prices it differently. Nothing published governs the threshold at which one model becomes cheaper than the other; two quotes on your real number do. |
|
| Does your organization have a contact centre, reception desk, or high-volume inbound call environment? | Toward private |
Your answer: Dedicated reception or queue with reporting needs Contact-centre capability is where the two models diverge most sharply in licensing. Queue reporting, agent management, wallboards and skills-based routing are usually a separate per-agent product on a shared platform, and part of the platform on a dedicated one. Neither is wrong — a business with one reception desk should not pay for a contact centre, and a business with twelve agents should price both models per agent rather than per employee. How Sunco closes this Once a queue has reporting requirements, the licensing difference between the two models widens sharply: contact-centre functionality is usually a separate per-agent product on shared platforms and a capability of the platform on a private tenant. Price it per agent, on your real agent count. |
No published standard governs this question · A circumstance or a preference, not an obligation No body publishes a rule about when a queue becomes a contact centre. The practical boundary is reporting: the moment a supervisor needs to see what happened, the licensing conversation changes on both sides. |
|
| Do different departments or teams require custom call routing, ring groups, or auto-attendant logic? | Toward private |
Your answer: Multi-level interactive voice response (IVR) and department-specific routing built over time Custom routing moves between platforms, but it is rebuilt rather than exported — there is no format that carries a menu tree from one vendor to another. The question is therefore not whether your routing can be reproduced, but who reproduces it, how it is tested, and what changing it costs afterwards. That last part is where the models differ: one hands you a console, the other hands you a person. How Sunco closes this A multi-level menu with department routing built up over time is portable, but it is rebuilt rather than exported. Ask any prospective provider who rebuilds it, how it is tested, and what happens when it needs changing afterwards. |
No published standard governs this question · A circumstance or a preference, not an obligation Routing complexity is a description of how your business answers its phone. There is nothing to comply with — but it is the item most often underestimated when a platform changes, which is why it is asked. |
|
| How would you characterize the overall complexity of your communications environment today? | Toward private |
Your answer: Complex — we have significant routing, integrations, and workflows Your own read on complexity is worth as much as the four questions before it, and it is often more accurate. A customised environment represents real operational value — it is how the business answers its phone — and it is also the largest single item in any migration estimate. Both things are true at once, which is why this question is asked plainly rather than framed. How Sunco closes this Significant routing, integrations and workflows mean the platform is carrying business logic, not just calls. That logic has to land somewhere in a new platform, and where it can land is exactly what separates the two models. |
No published standard governs this question · A circumstance or a preference, not an obligation Your own judgement of complexity is the point of this question, and no standard can supply it. It is included because it is often more accurate than the four questions before it. |
|
| Scale & Operational Complexity: Complexity is not a problem to be fixed here — it is the single strongest indicator of which model will cost less to live with. |
| Security, Compliance & Data Location | 4 of 5 · 33% aligned |
| Does your industry require compliance with Canadian privacy regulations — the Personal Information Protection and Electronic Documents Act (PIPEDA), Ontario’s Personal Health Information Protection Act (PHIPA), a provincial Personal Information Protection Act (PIPA), Quebec Law 25, or sector-specific standards? | Toward private |
Your answer: Sector-specific obligations (health, legal, financial, municipal) The starting question is which statute actually applies to you, and the answer is often not the federal one. Alberta’s and British Columbia’s Personal Information Protection Acts and Quebec’s private-sector Act are deemed substantially similar to the federal law and apply in place of it, and six provincial health statutes sit alongside them. Under any of them you stay accountable for personal information a third party processes for you — the obligation does not transfer to the platform. How Sunco closes this Sector-specific obligations change this from a preference into a requirement you will have to evidence. Ask any prospective provider for their data location, sub-processors and breach notification terms in writing, before the demonstration rather than after it. |
Provincial privacy law deemed substantially similar to the Personal Information Protection and Electronic Documents Act (PIPEDA) · Which statute actually applies to your organization Three provincial private-sector laws are deemed substantially similar to the federal Act and apply in place of it — Alberta’s and British Columbia’s Personal Information Protection Acts and Quebec’s private-sector Act — and six health-specific laws sit alongside them. Which one governs you is a fact you can look up, and it decides how much of this section is a requirement rather than a preference. |
|
| Do you record calls? Are those recordings subject to audit trails, legal hold, or defined retention periods? | Toward private |
Your answer: We record regularly with defined retention requirements Recording is available on both models. What differs is where the recordings rest, who can reach them, and what it costs to keep them: storage, retention management and audit access are commonly priced separately on shared platforms. The Privacy Commissioner’s requirements — tell the caller, state the purpose, offer an alternative, keep it only as long as the purpose needs — apply whichever you choose. How Sunco closes this Defined retention requirements mean the storage location and deletion behaviour are contract terms rather than settings. Confirm both in writing, and confirm who can export the archive if you leave. |
Office of the Privacy Commissioner of Canada · Disclosure, purpose, consent and retention for recorded calls The guidance is specific: tell the caller the call is being recorded, state the purpose, offer an alternative to a caller who objects, and keep the recording only as long as that purpose requires. All of that is satisfiable on either platform model — what differs is where the recordings rest and who can reach them. |
|
| Does your organization require that voice data, call logs, and recordings physically remain within Canada? | Toward private |
Your answer: Canadian data residency is a contractual or policy requirement Data residency and legal jurisdiction are different questions, and the second one is the one people miss. A Canadian data centre answers where the data sits. It does not answer who can compel its production: 18 U.S.C. § 2713, added by the Clarifying Lawful Overseas Use of Data (CLOUD) Act in 2018, requires a provider subject to US jurisdiction to preserve or disclose data in its possession, custody or control “regardless of whether such communication, record, or other information is located within or outside of the United States.” If that matters to your organization, it is a question to ask before the demonstration. How Sunco closes this A contractual or policy requirement for Canadian residency narrows the field immediately, and it is worth being precise about what it covers: the recordings, the call detail records, the directory, the backups, and the support staff who can view them. |
Office of the Privacy Commissioner of Canada · Accountability for personal information processed in another jurisdiction The Commissioner is explicit that a transfer for processing is a use rather than a disclosure, so you remain accountable: you must use contractual or other means to give the information comparable protection, and you must tell people it may be sent to another jurisdiction where courts, law enforcement and national security authorities can reach it. That obligation does not move to the platform, whichever one you choose. |
|
| Have you reviewed your cyber insurance policy requirements as they relate to cloud communications? | Slightly toward private |
Your answer: We carry cyber insurance but have not reviewed communications-specific requirements Cyber policies increasingly ask about where data is held and how access to it is controlled, and the answers are easier to give for some architectures than others. This question is not about whether cloud is insurable — it plainly is — but about whether your own policy has already made a requirement you have not read. That is a half-hour of reading that occasionally changes a platform decision. How Sunco closes this Carrying cyber insurance without having read what it says about communications is common, and the clauses that matter are usually about where data is held and how access is controlled. Half an hour with the policy before you choose a platform is cheaper than a declined claim afterwards. |
No published standard governs this question · Your own policy is the authority here, and it is written down No regulator requires you to hold cyber insurance or dictates what the policy must say about communications. What makes this question worth asking is that your policy may already have decided the platform question for you, in a clause nobody has read since renewal. |
|
| Security, Compliance & Data Location: Data location is a yes-or-no question with a legal answer, not a feature comparison. |
| Budget Model & Total Cost | 4 of 5 · 33% aligned |
| How does your organization prefer to fund technology investments? | Slightly toward private |
Your answer: Flexible — open to either model depending on total cost A shared platform is a pure operating expense. A dedicated one can be either — bought outright or taken as a managed subscription — so the funding preference narrows the field less than it appears to. Where it does matter is existing hardware: if you have recently invested, ask what a managed private tenant would do with it, and check honestly whether it is still vendor-supported. How Sunco closes this Flexibility on funding model means cost comparison decides this section, which is the right way round — compare over the years you actually keep a platform. |
No published standard governs this question · A circumstance or a preference, not an obligation How you prefer to fund technology is a commercial preference with no right answer. On a readiness assessment scoring it would be a defect; on a fit assessment it is a legitimate input, and it is treated as one. |
|
| When you received per-seat pricing from a public cloud provider, did it include all the features your business actually needs? | Toward private |
Your answer: Partially — significant add-ons were required to meet our needs Entry per-seat pricing is built for a simpler buyer than most organizations turn out to be. Contact centre licensing, recording storage, integration, analytics and administrative tooling are commonly separate, so the number that matters is a quote against YOUR feature list rather than the advertised rate. Ask for it in writing from both models and the comparison usually changes shape. How Sunco closes this When significant add-ons were needed to meet your needs, the headline per-seat figure was not the price. Rebuild the comparison at your real feature list — the distance between the two models usually narrows or reverses. |
No published standard governs this question · A circumstance or a preference, not an obligation Nothing published governs what a platform quote must include. Comparing like with like is your protection, and it is built from your own feature list rather than from a standard. |
|
| Have you factored migration costs — number porting, data migration, staff retraining, integration rebuild — into your comparison? | Toward private |
Your answer: No — we have focused on per-seat pricing only Number porting, call-flow rebuild, integration rework and staff time all arrive once, and none of them is in a per-seat quote. They are not hidden costs so much as costs nobody was asked for, and they differ between the two models rather than cancelling out. Ask both providers to quote them as a separate line. How Sunco closes this Comparing per-seat pricing alone leaves out the costs that only appear once. Add them to both sides of the comparison, because they differ between models rather than cancelling out. |
No published standard governs this question · Nothing published sets what a migration costs — but it is quotable There is no authority to cite here, and no credible published figure for what moving a communications platform costs a business this size. The recommendation is Sunco’s: ask for the one-time costs as a separate line from both providers, because they differ between the two models rather than cancelling out. |
|
| How important is a single, predictable monthly invoice from one trusted partner covering all communications services? | Toward private |
Your answer: Important — we actively prefer simplified vendor relationships One invoice and one number to call is a preference rather than a requirement, and it is worth quantifying before it decides anything: count what your communications currently touch — platform, circuits, handsets, maintenance, support — and how many relationships that actually is. The answer often surprises the person who has been paying them. How Sunco closes this Actively preferring a simplified vendor relationship is worth pricing rather than assuming: count what your communications currently touch — platform, circuits, handsets, maintenance — and how many relationships that is. |
No published standard governs this question · A circumstance or a preference, not an obligation One invoice from one partner is a preference. It is asked last because it rarely decides the answer alone, and often confirms one the earlier sections already gave. |
|
| Budget Model & Total Cost: Neither funding model is better. What matters is comparing them over the period you actually keep a phone system, with the same feature list on both sides. |
| Customization & Integration | 5 of 5 · 40% aligned |
| Does your organization integrate your phone system with a customer relationship management (CRM), enterprise resource planning (ERP), healthcare record system, or other business application? | Toward private |
Your answer: Active integration with customer relationship management (CRM)/ERP with screen-pop and logging Integration is available on both models and priced differently. Shared platforms ship connectors for the common systems and charge for the rest through middleware or development; a dedicated platform is more open to being extended and costs more to extend. The practical test is not the connector list but the change after it: when your customer system is upgraded next year, who fixes the integration and how quickly. How Sunco closes this Screen-pop and automatic call logging are where integration stops being a checkbox: the useful question is which system is the source of truth, and what breaks in the other one when the phone platform changes. |
No published standard governs this question · A circumstance or a preference, not an obligation Nothing published requires a phone system to integrate with anything. What integration decides is the cost and risk of changing platforms, which is a commercial question you can answer with a list. |
|
| Do you use specialized hardware — overhead paging, door entry systems, analog fax lines, or analog devices? | Toward private |
Your answer: Multiple analog endpoints including paging or door entry Analog endpoints — overhead paging, door entry, a fax line a regulator still requires — are supported on both models, but only one supports them without adding hardware at the site. That is a real cost and it is often left out of a comparison, because it is a site count rather than a user count. Inventory the analog devices and what each one is FOR before comparing prices. How Sunco closes this Overhead paging and door entry are the two analog endpoints that most often survive a migration badly, because they are physical, safety-adjacent, and owned by somebody who was not in the platform conversation. Inventory them before choosing. |
No published standard governs this question · A circumstance or a preference, not an obligation No standard governs analog endpoints, though a specific one may govern what an endpoint is FOR — a fax line a regulator still requires, or a door release. The equipment is a fact; the obligation, if any, sits with the function. |
|
| How reliant is your organization on custom auto-attendant greetings, seasonal schedules, and department-specific routing that has been refined over time? | Toward private |
Your answer: Significant — extensive routing refined over multiple years An auto-attendant is documentation of how a business actually operates: holiday schedules, after-hours routing, emergency overrides, who answers what. None of it exports between vendors, so it is rebuilt whichever direction you move. The useful step, and it is cheap, is to export or photograph every menu now — it makes two quotes comparable and it is business knowledge that currently exists only inside a phone system. How Sunco closes this Routing refined over multiple years usually contains decisions nobody remembers making. Export or photograph every menu before any migration conversation gets serious — it is the artefact that makes quotes comparable. |
No published standard governs this question · A circumstance or a preference, not an obligation Nobody publishes rules about auto-attendant schedules. They are business knowledge that happens to live inside a phone system, which is exactly why they are worth exporting before any platform conversation. |
|
| Does your communications system connect to on-premise applications, local door access systems, or building infrastructure? | Slightly toward private |
Your answer: Minor integration with one on-premise system Connections to building systems — access control, emergency notification, an on-premise application that talks to the phone system — are physical dependencies, and a platform in somebody else’s data centre reaches them through equipment at your site. That is possible on either model. It just means a cloud-only comparison is not really cloud-only, and the honest total includes whatever sits in the rack either way. How Sunco closes this A single on-premise connection is usually solvable either way. Establish whether it needs to be on the same local network as the phone system or merely reachable from it — the answer changes the options. |
No published standard governs this question · A circumstance or a preference, not an obligation Connections to building infrastructure are engineering facts rather than governed ones. They matter here because a physical dependency is the one thing a platform in somebody else’s data centre cannot inherit. |
|
| How quickly does your business need to add users, change call flows, or reconfigure routing when your organization changes? | Toward private |
Your answer: Same-day response to changes is important Self-service administration is genuinely faster than asking somebody — when there is somebody with the time, the training and the access to use it. Where there is not, the same portal is slower than a phone call, because the change waits for whoever is least busy. This question is really about your own team rather than about the platforms. How Sunco closes this Same-day change response is achievable on both models but by different routes: self-service administration on one, a responsive provider on the other. Which suits you depends on whether you want to make the change or ask for it. |
No published standard governs this question · A circumstance or a preference, not an obligation How fast you need changes made is an operational preference. No standard sets it, and the honest answer usually depends on whether you intend to make the changes yourself. |
|
| Customization & Integration: The question is not whether a platform can be customised — it is what happens the day you need to change the customisation. |
| Control, Administration & Support | 5 of 5 · 47% aligned |
| When your phone system has a critical issue, how quickly do you need expert response? | Toward private |
Your answer: Within 1–2 hours during business hours, regardless of issue type Both models publish response commitments and they mean different things. A shared platform’s commitment is to respond within a stated time with an agent who does not know your configuration; a managed dedicated platform’s is usually to respond with somebody who does. Ask what "response" means in each contract, and what happens outside business hours — that is where the two differ most. How Sunco closes this A one-to-two-hour commitment regardless of issue type narrows the field to arrangements with a named support path. Ask what happens outside business hours, because that is where the two models differ most. |
No published standard governs this question · A circumstance or a preference, not an obligation Response-time expectations are contract terms, not regulated ones. What is worth checking is what "response" means in each contract you are offered — an acknowledgement and a fix are different promises. |
|
| How important is it to work with a partner who knows your business, your staff, and your communications history? | Toward private |
Your answer: Important — I want a partner who knows our setup Institutional knowledge is a real product feature even though it never appears on a feature list. If every support call starts by re-explaining your setup, the cost lands in your own people’s time rather than in the invoice, which is why it rarely gets compared. How much that matters to you is a preference, and a legitimate reason to choose either way. How Sunco closes this Wanting a partner who knows your setup is a real requirement, not a soft one — it is the difference between explaining your call flow to somebody and being asked about it by name. |
No published standard governs this question · A circumstance or a preference, not an obligation How much a support relationship matters to you is a preference, and a legitimate one. It is also the answer that most often decides this question in practice, whatever the feature comparison says. |
|
| Does your internal information technology (IT) team have dedicated capacity to manage a cloud communications platform? | Toward private |
Your answer: Limited — information technology (IT) is reactive and has minimal capacity for proactive management Every platform is easy to administer in a demonstration. The question that predicts reality is whether anybody at your organization has time to open the console in a normal week. A team that does gets real value from self-service; a team that does not ends up with an unadministered platform, which drifts in both models. How Sunco closes this Limited and reactive information technology (IT) capacity means self-service administration will not get used, and an unadministered platform drifts. Budget for somebody to hold it, in either model. |
No published standard governs this question · A circumstance or a preference, not an obligation Nothing published governs how much internal capacity a platform requires. The useful test is honest rather than technical: will anybody actually open the administration console? |
|
| When you evaluate technology vendors, how important is single-point-of-contact and simplified billing? | Slightly toward private |
Your answer: Somewhat important — simplified billing would help A new platform usually means a new supplier relationship alongside the ones you have for internet, hardware and support — a separate bill, a separate portal and a separate escalation path. Some organizations manage that comfortably. For others it is a real administrative cost that never appears in a per-seat comparison, which is the reason this question is asked at all. How Sunco closes this Simplified billing being helpful rather than essential leaves this section neutral — useful, because it means your decision rests elsewhere. |
No published standard governs this question · A circumstance or a preference, not an obligation Vendor consolidation is a purchasing preference. It is asked because it is quantifiable — count the invoices and support numbers your communications touch today. |
|
| Have you had frustrating experiences with vendor support queues, slow responses, or agents unfamiliar with your configuration? | Slightly toward private |
Your answer: Occasionally — some frustrations but generally acceptable Your own support history is the most reliable predictor in this section of what you will find acceptable next time. It is worth being specific: what the last three problems had in common is usually the requirement you are actually buying against, and it is more useful in a supplier conversation than any feature list. How Sunco closes this Occasional support frustration is normal and not by itself a reason to change anything. Note what the frustrations had in common, because that pattern is the requirement you are actually buying against. |
No published standard governs this question · A circumstance or a preference, not an obligation Your experience of support is evidence rather than compliance. It is the most reliable predictor in this section of what you will find acceptable next time. |
|
| Control, Administration & Support: This layer is mostly about what your own team has capacity for, and there is no wrong answer. |
| Reliability & Internet Dependency | 5 of 5 · 53% aligned |
| Does your organization have redundant internet connections at primary locations? | Slightly toward private |
Your answer: Some locations have redundancy, others do not Any platform that carries calls over the internet inherits whatever the internet connection does. With one connection at a site, a connection failure is a communications failure — which is fixable and usually cheaper than people expect, and better fixed before a platform change than after. With two carriers over two paths, this question stops constraining the decision. How Sunco closes this Redundancy at some locations and not others means the sites without it set your exposure, not the average. Any cloud platform runs at the speed of the weakest connection. |
No published standard governs this question · A circumstance or a preference, not an obligation No standard requires a business to hold two internet connections. What redundancy decides is how much of your communications risk moves onto the connection when the platform moves off your site. |
|
| What is your organization's tolerance for phone system downtime? | Toward private |
Your answer: Low — downtime directly impacts revenue or client relationships The honest answer here decides how much the per-seat comparison actually matters. An organization that can absorb a few hours is a different buyer from one where a missed call is missed revenue or a regulatory event, and ISO 22301 — the business continuity standard of the International Organization for Standardization (ISO) — asks for that period to be DETERMINED rather than assumed. It is a short conversation and most businesses have never had it. How Sunco closes this When downtime hits revenue or client relationships directly, the platform decision and the connectivity decision stop being separate purchases and should be quoted together. |
ISO 22301:2019 — Business continuity management systems · Determining the tolerable period of disruption rather than assuming it The standard asks the organization to determine the period it can be without an activity, and then to build a response that meets it. Applied to a phone system that is a short and answerable question — and it is the input that decides whether the platform needs an alternative path or simply a good connection. |
|
| Do you require the ability to make and receive calls even if your internet connection goes down? | Toward private |
Your answer: Important — our business requires some calling capability during outages Calling during an internet outage is achievable on either model and by more than one route: a second connection, cellular failover, or call processing that lives at your site. They differ enormously in cost, so the useful question is which of them you actually need — and whether the requirement is all calls, or the three numbers that matter. How Sunco closes this Requiring some calling capability during an outage is satisfiable in several ways — a second connection, cellular failover, or local call processing — and they differ enormously in cost. Establish which you actually need. |
No published standard governs this question · Calling during an outage is a design requirement, not a regulated one Nothing published requires a business to be able to call during an internet outage. The recommendation is Sunco’s, and it depends entirely on what stops when the phones stop — which is why the question is asked here rather than assumed either way. |
|
| Do you have remote workers, branch offices, or locations with variable or unreliable connectivity? | Slightly toward private |
Your answer: Some remote workers on standard residential internet Remote and branch connections are the part of the experience nobody monitors and everybody judges. Voice quality at each endpoint is a function of that endpoint’s connection, so the worst site sets your reputation. Traffic can be prioritised on a network you control; on a connection you do not control — a home broadband line — neither model can promise much, which is worth knowing before it is promised to you. How Sunco closes this Remote workers on ordinary residential connections are usually fine for voice, and they are also outside anything you can monitor. Expect a support pattern rather than an outage. |
No published standard governs this question · A circumstance or a preference, not an obligation Where your people work is a fact about your organization. It is asked because remote and branch connections are the part of the experience nobody monitors and everybody judges. |
|
| Have you experienced VoIP call quality issues — jitter, latency, dropped calls — related to internet performance? | Slightly toward private |
Your answer: Occasionally — minor quality issues under heavy load Call quality problems are almost always the connection rather than the platform, and they are measurable rather than debatable: Recommendation the International Telecommunication Union (ITU)-T G.114 puts essentially transparent speech below 150 milliseconds of one-way delay, with 400 milliseconds as the general planning limit. Measure during the busy hour before accepting any explanation, including ours. How Sunco closes this Minor quality issues under heavy load are usually prioritisation rather than capacity — something has to decide that voice goes first when the connection is busy, and by default nothing does. |
International Telecommunication Union — Recommendation the International Telecommunication Union (ITU)-T G.114 · One-way delay below 150 ms; 400 ms the general planning limit G.114 puts essentially transparent interactivity for speech below 150 milliseconds one way, with 400 milliseconds as the upper limit for general network planning. It is the one threshold in this subject that is testable, and it settles arguments about call quality that otherwise run on opinion. |
|
| Reliability & Internet Dependency: The right question is not "is cloud reliable" — it is "how good is the connection this would run over, and what happens when it fails". |
|
POINTS TO A PRIVATE TENANT · 2 What points to a dedicated platform These are the requirements a shared platform meets with an add-on, an exception, or not at all. They are the strongest indicators in your profile. |
| Security, Compliance & Data Location | 1 of 5 · 33% aligned |
| Does your organization handle personal health information, legal privilege, or other categories of highly sensitive data in voice communications? |
Your answer: Always — virtually all our communications involve regulated sensitive data When calls routinely carry health information, legal privilege or financial detail, the phone system becomes a records system. That raises the same questions you would ask of any system holding that data: where it rests, who can reach it, how long it is kept, and how it comes back to you at the end. Shared platforms answer those questions with contract terms; a dedicated platform answers some of them with architecture. Both can be adequate — they are audited differently. How Sunco closes this When virtually every call involves regulated data, the platform is a records system that happens to make phone calls. Data location, access control, retention and export stop being preferences. |
Provincial privacy law deemed substantially similar to the Personal Information Protection and Electronic Documents Act (PIPEDA) · Health information is governed separately from other personal information Alberta’s Health Information Act, Ontario’s Personal Health Information Protection Act and four other provincial health statutes are deemed substantially similar to the federal law and apply to custodians in their provinces. If your calls carry health information, the governing statute is probably not the one you would name first. |
|
| Security, Compliance & Data Location: Data location is a yes-or-no question with a legal answer, not a feature comparison. |
| Budget Model & Total Cost | 1 of 5 · 33% aligned |
| How many years does your organization typically retain a communications platform before replacing it? |
Your answer: 10+ years — we run platforms until they are truly end-of-life Retention period is the single largest variable in this comparison, and the one most often left out of it. Over one or two years a monthly per-seat model is almost always cheaper. Over five or more the arithmetic moves, because a subscription does not stop when a purchase would have finished paying for itself. Neither is a trick — they are different shapes of the same spend. How Sunco closes this Running platforms to true end of life makes total cost over a decade the honest comparison, and it is one most per-seat quotes are not built to answer. Ask for it anyway. |
No published standard governs this question · A circumstance or a preference, not an obligation Retention period is a habit rather than a rule, and it is the single largest variable in a five-year comparison between a monthly fee and a capital purchase. |
|
| Budget Model & Total Cost: Neither funding model is better. What matters is comparing them over the period you actually keep a phone system, with the same feature list on both sides. |
|
⚡ Quick Wins — Act On These Now | | Write down, in one line, whether Canadian data residency is a contractual requirement for you or a preference — and if it is a requirement, where it is written down. It is the single question most likely to decide your platform, and the one most often answered from memory. Typically 15 minutes. |
| | Export or photograph every auto-attendant menu, schedule and routing rule you have, before any migration conversation gets serious. It is the artefact that makes two quotes comparable, and it is business knowledge that currently exists only inside a phone system. Typically an afternoon. |
| | List everything your phone system talks to — the customer system, the record system, the paging, the door, the fax — and put a name against who would rebuild each connection. Integration is where platform quotes differ most and where migration estimates go wrong most. Typically an afternoon. |
|
Assessment Framework & Standards Alignment Most of this assessment is about your circumstances and preferences, which nothing published governs. These are the sources behind the few answers that are obligations rather than choices. PRIVACY COMMISSIONER OF CANADA Personal Information Protection and Electronic Documents Act (PIPEDA) guidance Your continuing accountability for personal information a third party processes, what you must tell people about processing in another jurisdiction, and what you must tell a caller before recording them. The clearest published answer to the data-location question this assessment asks. | PROVINCIAL PRIVACY LAW Laws deemed substantially similar to the Personal Information Protection and Electronic Documents Act (PIPEDA) Alberta’s and British Columbia’s Personal Information Protection Acts and Quebec’s private-sector Act apply in place of the federal law, and six health-specific laws sit alongside them — including Alberta’s Health Information Act. Which one governs you decides how much of Section 2 is a requirement rather than a preference. | US CLOUD ACT Clarifying Lawful Overseas Use of Data (CLOUD) Act — 18 U.S.C. § 2713, enacted March 2018 Requires a provider subject to United States jurisdiction to preserve or disclose data in its possession, custody or control “regardless of whether such communication, record, or other information is located within or outside of the United States”. The reason data residency and legal jurisdiction are two separate questions. | the International Telecommunication Union (ITU)-T G.114 (International Telecommunication Union) One-way transmission time, International Telecommunication Union Below 150 milliseconds one way for essentially transparent speech, 400 milliseconds as the general planning limit. The one testable threshold in a subject full of assertions about call quality. | ISO 22301:2019 Business continuity management systems Determining the period you can tolerate being without an activity, then building to it — which is what turns "how much downtime can you take" from an opinion into a number. | STATISTICS CANADA Survey of Digital Technology and Internet Use, 2023 What Canadian businesses have actually adopted — cloud computing at 48%, the most commonly used technology measured. A measurement of what is, used here for context and never as a requirement. |
This assessment reports which platform model your requirements point at. It does not certify compliance with any standard, it is not legal advice, and twenty-one of its thirty questions are circumstances and preferences with nothing published behind them — which is what they should be. |
|
Sunco’s Recommendation A private tenant fits: Enough indicators point to a dedicated platform that a shared tenant would be worked around rather than used. |
|
Book Your Platform Conversation A Sunco advisor will walk through your results and identify the highest-impact next steps for your organization. 30 minutes • Free • No obligation |
Research Sources and Methodology Every figure and framework reference in this report is listed below with a link to the original source, so you can verify any of it yourself. Office of the Privacy Commissioner of Canada — Guidelines for processing personal data across borders An organization is responsible for personal information in its possession or custody, including information transferred to a third party for processing, and shall use contractual or other means to provide a comparable level of protection while it is processed. Organizations must advise customers that their personal information may be sent to another jurisdiction for processing and that while there it may be accessed by the courts, law enforcement and national security authorities. A transfer for processing is a use, not a disclosure, so additional consent for the transfer itself is not required. Tier 1 source · Canada · verified 2026-08-24 |
Office of the Privacy Commissioner of Canada — Provincial and territorial privacy laws and oversight Three provincial private-sector privacy laws are deemed substantially similar to PIPEDA and apply in place of it: Alberta’s Personal Information Protection Act, British Columbia’s Personal Information Protection Act, and Quebec’s Act respecting the protection of personal information in the private sector. Six health-specific laws are also deemed substantially similar, including Alberta’s Health Information Act and Ontario’s Personal Health Information Protection Act, 2004. Tier 1 source · Canada · verified 2026-08-24 |
Office of the Privacy Commissioner of Canada — Recording of customer telephone calls — PIPEDA guidance An organization recording customer calls must inform the customer that the call is being recorded, clearly state the purpose and ask for consent; a caller who objects must be offered an alternative; and retention is limited to the stated purpose. Tier 1 source · Canada · verified 2026-08-24 |
Statistics Canada — Survey of Digital Technology and Internet Use, 2023 Cloud computing was the most commonly used information and communications technology among Canadian businesses in 2023, at 48%, up from 45% in 2021. 28% of businesses offered employees the option to telework — 23% of small businesses, 45% of medium-sized and 64% of large. Tier 1 source · Canada · verified 2026-08-24 |
IBM / Ponemon Institute — Cost of a Data Breach Report 2026 (Canada release) The average cost of a data breach in Canada reached CA$7.11 million, taking an average of 205 days to detect and contain. The sample is enterprise-weighted, so the direction is more informative than the figure for a small business. Tier 2 source · Canada · verified 2026-08-24 |
Information Technology Intelligence Consulting — ITIC 2024 Hourly Cost of Downtime Report, Part 1 The average cost of a single hour of downtime exceeds $300,000 for over 90% of mid-size and large enterprises, and 41% put it between $1 million and over $5 million. Over 1,000 firms surveyed globally between November 2023 and mid-March 2024. Measures mid-size and large enterprises — not small business. Tier 2 source · International · verified 2026-08-24 |
International Telecommunication Union — Recommendation ITU-T G.114 (05/2003) — One-way transmission time One-way mouth-to-ear delay below 150 ms gives essentially transparent interactivity for speech; 400 ms is the recommended upper limit for general network planning. Tier 1 source · International · verified 2026-08-24 |
Canadian Radio-television and Telecommunications Commission — Canadian Telecommunications Market Report 2026 More than 96% of Canadians have access to Internet at the universal service objective level — 50 Mbps download, 10 Mbps upload, with the option of unlimited data. Over 85% subscribe to speeds over 50 Mbps and nearly 90% of households can reach gigabit speeds. Data year 2024; the report tracks retail business and home fixed Internet together and its detail is residential. Tier 1 source · Canada · verified 2026-08-24 |
United States Congress (text published by the US Department of Justice) — Clarifying Lawful Overseas Use of Data Act (CLOUD Act), Division V, section 103(a) 18 U.S.C. § 2713, added by the CLOUD Act: “A provider of electronic communication service or remote computing service shall comply with the obligations of this chapter to preserve, backup, or disclose the contents of a wire or electronic communication and any record or other information pertaining to a customer or subscriber within such provider’s possession, custody, or control, regardless of whether such communication, record, or other information is located within or outside of the United States.” Tier 1 source · United States · verified 2026-08-24 |
Statistics are reproduced as published by the sources above and were verified on the dates shown. Regulatory positions reflect the law in force at the time of verification and may change. This assessment surfaces readiness gaps and does not certify compliance with any standard; consult qualified counsel regarding your specific obligations. |
Sunco Communication and Installation Ltd. 18961 111 Ave NW, Edmonton, AB T5S X4 1-866-310-7007 | marketingteam@sunco.ca | sunco.ca |
© 2026 Sunco Communication & Installation Ltd. All rights reserved. |
|
|