IT SUPPORT SERVICES
IT support services: pinpoint the right issue, coordinate a clear resolution
When IT systems get in the way of your work, start by describing the issue and its impact. Work with BMITC to clarify the support scope, the information to prepare and the way of working that fits your service terms.
A single, clear
point of contact
A transparent
intake process
Actions only within
granted permissions
Documented results
and next steps
Situations where IT support services fit
The service fits when your business needs a technical point of contact to receive, analyse and coordinate the resolution of issues that arise while operating your systems.
End-user support
Users run into errors or need guidance with devices, software, office applications and business systems within the service scope.
Incidents affecting operations
Systems are slow, interrupted or behaving abnormally, and the symptoms need to be recorded, the impact assessed and checks coordinated to decide how to resolve it.
Multi-party technical coordination
The issue spans several systems or vendors and needs one point of contact to clarify the scope, identify who is involved and agree on the next step.
i
Intake conditions: your business assigns an authorised contact, provides information about the systems involved and grants valid access when needed. Each request is assessed against the agreed service scope before any work begins.
Support scope and exclusions
Support for users, systems and IT services within the agreed scope. What is not included by default is stated clearly below.
Users
Devices, software and office applications.
Infrastructure
Servers, networks, storage and equipment.
Cloud
Cloud environments and their connection to existing systems.
Business applications
Business systems and software within scope.
Security
Access rights and related layers of protection.
Support activities
Performed within the scope agreed in the service terms.
✓
Record the issue description, affected systems and level of impact.
✓
Review information, configurations or logs that may be shared within the agreed scope.
✓
Guide users and recommend remediation steps; make changes only once authorised.
✓
Coordinate with the customer's technical contacts or other parties when needed.
✓
Record the resolution, guidance given and any open issues.
Not included by default
The items below require a separate agreement.
✕
Upgrades, redesigns, new deployments or system and data migration.
✕
Ongoing operations management, scheduled maintenance or continuous monitoring.
✕
Replacement hardware, software licences, vendor services and third-party costs.
✕
Security incident response, in-depth investigation or data recovery beyond the approved scope.
✕
Systems that may not be accessed or that do not meet safe-collaboration conditions.
Information to provide with a support request
Complete and accurate information from the start helps our engineers identify the right issue, assess its impact and propose a suitable resolution.
01
Issue description
Symptoms, when it started, error messages and steps to reproduce, if any.
02
Affected systems
Affected systems and applications, plus any recent changes you know of.
03
Level of impact
Affected users and work, and the measures already tried.
04
Point of contact
Contact person, who can approve actions and when they are available.
05
Attachments
Screenshots and logs with sensitive data removed, sent through a confirmed channel.
Information security notice
Do not send passwords, authentication codes, access keys or confidential data through public forms. Technical access, if needed, is agreed and granted through a secure channel.
Channels and intake hours
Support channels, intake hours and remote or on-site delivery are confirmed in the service terms before work begins.
How we work together
Four steps to clarify each request, act strictly within granted permissions and confirm the outcome with you.
01
Intake and clarification
Identify the symptoms, the impact and any missing information.
→
02
Scope definition
Agree on the work, access conditions, way of working and approver.
→
03
Investigation and resolution
Carry out the approved steps; report findings and seek approval if the scope needs to change.
→
04
Confirmation and guidance
Check the result together and record the handover and next steps if the issue is not yet closed.
Deliverables and handover
What is documented after each engagement, with the acceptance conditions agreed by both parties.
DELIVERABLE 01
Resolution report
A complete record of what was checked and done for the request.
HANDOVER CONTENTS
✓
Symptoms and scope investigated
✓
Actions taken
✓
Results observed after resolution
ACCEPTANCE CONDITION
The customer checks the result against the original request and the work performed.
DELIVERABLE 02
Guidance documentation
Usage or remediation guidance that users can apply on their own.
HANDOVER CONTENTS
✓
Steps to apply
✓
Applicable environment and conditions
✓
Limitations and usage notes
ACCEPTANCE CONDITION
The customer's owner verifies that it applies in the real environment.
DELIVERABLE 03
Open items and next steps
Clarifies outstanding work so both parties can continue in the right direction.
HANDOVER CONTENTS
✓
Unresolved items and reasons
✓
Dependencies and contacts
✓
Recommended next actions
ACCEPTANCE CONDITION
Both parties agree on the status; an escalation does not mean the issue is resolved.
Specific deliverables depend on the scope of each request; not every request includes a root-cause report or full recovery.
Responsibilities and service terms
Clear collaboration between BMITC and the customer keeps support safe and effective.
BMITC
✓
Clarify the support scope before starting work.
✓
Act only within granted permissions.
✓
Report findings, risks and out-of-scope work.
✓
Document the outcome of each engagement.
Customer
✓
Provide relevant information about the issue and systems.
✓
Assign an authorised point of contact.
✓
Approve changes before they are made.
✓
Prepare backups or other data protection before any action is taken.
✓
Verify the result in your own environment.
Scope, support channels and service levels
Scope, support channels, intake hours, remote or on-site delivery and service levels are agreed under the approved service terms in the contract.
Related capabilities
Areas often involved in support requests; specific support still follows the agreed scope.
IT infrastructure
Understand how servers, storage, networks and applications connect.
View infrastructure solutions →
Cloud
Explore cloud environments and how they connect to existing systems.
View cloud solutions →
Security
Review access rights and the related layers of protection.
View security solutions →
Your needs
PRODUCTS
Related products in our shop
Browse related hardware and software in the BMITC shop (opens in a new tab).
Infrastructure hardware
Servers, networking and storage.
↗
Cloud services
Microsoft 365, Azure and other cloud services.
↗
Cyber security
Protection for devices, identities and data.
↗
SOLUTIONS
Related BMITC solutions
Explore approaches and architectures for common IT challenges.
IT system solutions
Infrastructure modernisation, backup and recovery.
→
Cloud solutions
Hybrid cloud architecture and platform selection.
→
Security solutions
Layered protection, identity and data governance.
→
Let's clarify the issue you are facing
Share the systems involved, the symptoms and the impact. Together with BMITC, define the right support scope and the information needed for the next step.
Do not send passwords or confidential data through the form.
