Depending on the service: stable power, router placement, LAN readiness, access to comms room, and any required permissions (e.g., wayleaves for certain builds).
Blakewater House,
Capricorn Business Park,
Blakewater Rd,
Blackburn
BB1 5QR
Depending on the service: stable power, router placement, LAN readiness, access to comms room, and any required permissions (e.g., wayleaves for certain builds).
Yes — we can phase deployments by site, standardise configurations, and manage a consistent go-live process across locations.
Often minimal, but we can provide quick-start guides and short training for admins and end users (apps, call handling, voicemail, handset features).
Yes — we frequently deliver alongside internal IT or third parties and can agree responsibilities for networking, firewall rules, device rollout, and support boundaries.
We’ll update the scope and plan — common examples include “hidden” analogue devices, extra numbers, or additional sites needing connectivity or call routing.
You can contact support via the agreed support channels (phone/email/portal if applicable). We’ll confirm the best route during onboarding/handover.
Your company name, site/postcode, affected service (number/circuit/SIM), symptoms, when it started, and any error messages. This speeds diagnosis.
SLA availability depends on the service (e.g., leased lines often have stronger SLAs). We’ll confirm response/restore targets per product and contract.
For some managed services, yes — we can monitor key components and alert/respond earlier, depending on the solution and agreed scope.
An incident is something broken or degraded. A service request is a change (e.g., new user, routing tweak, additional SIM, new handset).