Connect. Secure. Manage.
Co-Managed Network Services
Share Cisco and Meraki network responsibilities with your internal IT team, defining access, escalation, change approval and the work each party owns.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
Co-managed network services let an internal IT team retain control while obtaining specialist Cisco and Meraki engineering support. The model works best when responsibilities are deliberately shared, not when both parties assume the other is watching the same problem. MCI Network Services defines the technical scope, access, approval and escalation arrangements so your team gains capacity without losing visibility of its own network.
Useful visibility
Monitor service-relevant conditions rather than collecting alerts without ownership.
Controlled change
Keep maintenance, automation and configuration work reviewable and recoverable.
Clear escalation
Connect incidents to the right engineering, provider and business contacts.
Decide which work should be shared
We begin by identifying the work your team wants to retain and the areas where external expertise is useful. That might include complex routing, planned changes, lifecycle management, incident escalation or specialist wireless investigation. The service is built around those gaps rather than replacing functions your team already performs well.
The division is recorded at an operational level. A statement that the customer owns first-line support is incomplete unless both parties understand what evidence is collected, when escalation occurs and who communicates with affected users. Clear entry criteria make specialist assistance faster and reduce repeated diagnostic work.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Create one responsibility model
The agreement identifies an owner for monitoring, configuration, change approval, vendor support and documentation. Shared activity still needs a lead at each stage. When a carrier or application supplier is involved, we specify who opens the case and who retains responsibility for coordinating the overall incident.
We also address absence and emergency situations. The arrangement should not depend on one named individual being available to approve every action. Delegated authority and emergency contacts can be agreed without granting unrestricted permission to make changes whenever a fault appears difficult to resolve.
A useful starting point
Tell us what is happening.
A short description of the problem is enough for an initial discussion.
Provide access appropriate to the role
MCI’s access is scoped to the agreed Cisco and Meraki responsibilities, with suitable authentication and auditability. Customer administrators retain the access needed to govern the estate. Shared credentials and undocumented personal accounts make accountability harder and should not become the foundation of a long-term service.
Access arrangements include recovery and revocation. We establish how an engineer can reach the supported systems during an incident and how permissions are removed when the relationship or personnel change. Sensitive credentials are exchanged through approved methods, not embedded in ordinary tickets or public contact forms.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Use a common change process
Customer and supplier changes need to appear in a shared record even when each party implements different parts. We agree the information required for assessment, the approval route and the checks that demonstrate completion. This prevents a well-intentioned local change from invalidating assumptions used by the other team’s design or monitoring.
Routine requests can follow a lighter process where their scope and risks are understood. Higher-impact work requires a specific implementation and rollback plan. Emergency changes remain attributable and receive follow-up review, including removal of temporary exceptions once the immediate problem is resolved.
Make escalations evidence-led
A useful escalation includes the business impact, affected paths, timeline and relevant observations. We help define practical diagnostic checklists for your team without expecting it to perform specialist analysis before asking for assistance. The objective is enough context to begin effectively, not a barrier that delays help.
MCI then investigates the agreed network scope and shares findings in a form the internal team can use. We distinguish a confirmed cause from a working hypothesis and explain the next action. The service should build operational understanding rather than leave a series of unexplained changes behind after each incident.
Review capacity, skills and service boundaries
Periodic reviews examine the workload, recurring issues and upcoming projects. The mix of responsibilities may change as your team grows or the network becomes more complex. We can adjust the arrangement through an agreed scope change rather than allowing informal expectations to expand without a corresponding plan.
Knowledge transfer can cover your actual topology, common fault patterns and recovery procedures. It is practical engineering handover, not a claim of vendor-accredited training. Your team should become better equipped to operate the estate while retaining a clear route to specialist support when needed.
Put commercial expectations in writing
The proposal specifies supported assets, service hours, response targets, included changes and any separately priced project work. It also explains vendor entitlements, on-site arrangements and the process for ending or transferring the service. A co-managed model is only transparent when these commercial boundaries match the operational ones.
MCI provides managed network services for Cisco and Meraki environments across the UK. Share your current team responsibilities and the gaps you want covered. We can then design a partnership that adds specialist capability without duplicating your existing work or making ownership less clear.
Talk to a specialist
Need a specialist view?
Tell us what is affected, what changed and what your team has already checked. A short outline is enough to start.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.