Give people a place to ask for help. Give operations a clear view of what is being done, who owns the decision and what happens next.
Built around your workday
For a 64-person design studio, support is not only fixing laptops. It is getting a new designer ready, keeping project access organised and making the next office move predictable.
Use the filters to see delivery, business ownership and the important boundary for each workstream.
4 workstreams
01
People & everyday support
A familiar situation
A new colleague starts on Monday. A designer cannot reach a shared project. Someone needs an approved application.
Request history · Access approval · Handover checklist
Relay coordinates
One request route, triage, user support and a documented next action. Joiner, mover and leaver tasks follow the access list approved by your business.
Your team owns
Your manager approves the person, role and required access. HR confirms start or leaving dates.
Where the scope stops
Specialist application faults are coordinated with the software vendor where its support is needed.
02
Devices & workplace standards
A familiar situation
The team has a mixture of laptops, unclear device ownership and no consistent setup for replacements.
Asset register · Setup standard · Maintenance record
Relay coordinates
An agreed device baseline, inventory, scheduled maintenance and replacement planning. Configuration and patching follow the approved scope and change process.
Your team owns
Your budget owner approves purchases and exceptions. Employees make devices available for agreed work.
Where the scope stops
Hardware purchase, physical repair and manufacturer warranties remain separate unless expressly included.
03
Accounts & collaboration
A familiar situation
Microsoft 365 permissions have grown with the company. Nobody is quite sure who owns each shared workspace.
Account list · Approval trail · Licence inventory
Relay coordinates
Account administration, agreed access groups, licence coordination and workspace ownership. Changes have an authorised requester and a recorded approval.
Your team owns
Business owners decide who needs access and approve licence spend. Relay implements the agreed change.
Where the scope stops
Licences and specialist software subscriptions are third-party costs. Product limitations stay with the vendor.
04
Planning & vendor coordination
A familiar situation
An internet issue, a software renewal and an office move all land with the same busy operations manager.
Service review · Risk register · Change plan
Relay coordinates
A shared issue register, vendor follow-up and a recurring service review. Planned changes show a dependency, an owner and a business decision.
Your team owns
Your service owner sets priorities, approves downtime and makes commercial decisions.
Where the scope stops
Major migrations, cabling and office projects are separately scoped so daily support stays clear.
Choose the working relationship
A full IT partner. Or your team’s extra capacity.
Both arrangements begin with a responsibility map. Pricing follows the actual scope, estate and support model.
Managed service
For teams without an internal IT function.
Relay coordinates agreed day-to-day IT services. A named business owner approves access, spend and priorities.