Requests become work
Website requests are formatted for the support mailbox and portal ticket path.
Service catalog
VoIP first, then every layer that keeps the office running.
Phones, Microsoft 365, networks, cameras, servers, security, POS, and workstations are treated as one operational stack, not scattered one-off jobs.
VoIP
M365
Networks
Cameras
Servers
Security
POS
Desktop
YEG VoIP
Business phones, routing, queues, voicemail, desk phones, softphones, and cutover support.
Open service page 02Microsoft 365
Email, MFA, tenant cleanup, licensing, shared mailboxes, onboarding, and account security.
Request M365 help 03Network installs
Firewall, switching, VLANs, Wi-Fi, cabling coordination, rack cleanup, and documentation.
Plan network work 04Camera systems
NVRs, cameras, remote viewing, retention, network readiness, and access controls.
Start camera project 05Server installs
Windows Server, Hyper-V labs, file services, Active Directory, backups, and restore planning.
Scope server work 06Security installs
MFA, endpoint controls, backup checks, firewall rules, patch posture, and hardening.
Improve security 07POS support
Retail terminals, receipt printers, payment device coordination, network checks, and uptime.
Stabilize POS 08Desktop upgrades
Windows 11 rollouts, SSD and RAM upgrades, migrations, hardening, and workstation refreshes.
Refresh computersOperating model
Every service points back to tickets, billing, and documentation.
The public website is the polished front door. The yegIT portal remains the operating record for customer contacts, quotes, tickets, invoices, recurring services, and payment work.
Payments stay in the portal
Invoices, recurring service, and payment methods stay behind the customer portal.
Details do not vanish
Service details are structured so they can become documentation and future project notes.
Support-ready
Requests can include device, site, urgency, and remote-support context from the start.