FAQ / Before an introduction
Questions a careful buyer should ask.
Managed IT should become clearer as you evaluate it. These answers separate the public offer from details that must be confirmed for your environment.
Lire cette page en françaisWhat does “white glove” mean here?
It describes an attentive direct service standard: context carried across issues, clear handoffs, and technical choices made readable. It does not mean partner fulfilment or service under another company’s name.
Is the service available in English and French?
The Canadian site and evaluation journey are offered in both languages. Confirm the working language for employee intake, status updates, documentation, and leadership decisions during scoping; the site does not imply universal staffing or coverage.
How are employee arrivals, role changes, and departures handled?
The agreed workflow can connect manager authorization to accounts, licences, applications, devices, and data decisions. Your organization still names authorized requesters and business owners; the provider executes and records the technical steps included in scope.
Is this a 24×7 SOC or guaranteed-response service?
No such claim is made on this site. Support coverage, escalation, and any service commitments must be established explicitly for the engagement.
What is included in the listed CAD price?
Essential begins with core IT and Microsoft 365 stewardship. Plus adds product-defined security baselines, audit cadence, and priority support. Exact coverage, projects, onsite work, licensing, taxes, and third-party costs require a proposal.
Can an internal IT lead retain control?
Yes, if a co-managed boundary is a good fit. The responsibility matrix should identify who receives work, who executes it, who approves changes, and who communicates with employees and vendors.
What Microsoft 365 work belongs in managed service?
Routine user and licence administration, supported collaboration issues, identity hygiene, documentation, and agreed configuration work may fit. Migrations, major redesigns, complex compliance, and remediation projects can require separate scope.
Why do you need an introduction before quoting?
User count alone does not reveal device mix, workplace patterns, Microsoft 365 condition, lifecycle processes, existing vendors, or responsibilities your team plans to retain.
Can you take over from another provider?
A transition may be possible. The handover should distinguish known, unknown, inaccessible, and awaiting-approval items; move administrative custody through secure channels; communicate the employee intake path; and stabilize recurring work.
What happens when another vendor causes the issue?
Vendor coordination can be included, but responsibility and authorization must be defined. A managed provider can carry context and follow through; it cannot invent control over another supplier’s response.
Should we send credentials through the contact form?
No. Never send passwords, recovery codes, API keys, or other secrets through a marketing form.
Next step
Turn your IT context into a clear scope.
An introduction covers your team, Microsoft 365, devices, vendors, and responsibilities to transfer. You leave with the scope questions that need answers—without sharing secrets.
Prepare an introduction