Services / IT operations & remote support
Remote IT support and maintenance with your approval
When a system becomes unreliable or its current setup is poorly understood, the first step is an assessment. Repairs and ongoing support can then be planned on a sound basis.
Who and what this is for
For businesses with a specific fault, an accumulated system setup or a need for accountable technical support. We establish which system is affected, what has been observed and who can authorise access.
An investigation does not have to change anything immediately. An initial read-only assessment can organise configuration, error messages and dependencies. A state report provides a basis for choosing the next action.
A concrete example
Illustrative scenario explaining the service
Narrow down a recurring failure
- The situation
- An operational application becomes unavailable intermittently. A restart helps briefly, but incident times, errors and recent changes have not been documented together.
- The starting point
- Observed times, visible errors and an overview of affected systems. Access is then arranged deliberately through an agreed channel.
- What we would build
- A structured state report with a traceable fault hypothesis. Any suitable configuration change follows approval, a backup and an established recovery path.
- How the result would be checked
- The affected user journey is checked before and after the change. The observation period, outcome and remaining uncertainty are recorded, rather than declaring success after a restart alone.
What you receive
- A system assessment or fault investigation within the agreed access boundary.
- A state report covering observations, open questions and prioritised actions.
- Approved repairs or configuration changes with a traceable activity record.
- Operating notes, recovery information and a defined support scope where commissioned.
How we work
- Set access and task boundariesWe agree the system, permissions, working window and permitted actions. Access is provided through an agreed channel; passwords do not belong in an initial enquiry.
- Separate diagnosis from changesWe record the starting state. Backups, a recovery path and approval are established before relevant changes. The affected workflow is checked afterwards.
- Explain the resulting stateYou receive the actions performed, the checked result and remaining limitations. Ongoing maintenance and availability require their own agreement.
Remote support requires authorised access. Round-the-clock availability and fixed recovery times are not automatically included.
Useful for a first conversation
- What fails, since when and for which users.
- Known changes and available error messages.
- The responsible person and possible maintenance windows.
Define the scope together
One-off investigation, repair and ongoing support are agreed separately. Priority and availability follow the support scope actually selected.
Working together
How is the price determined?
It depends on the objective, starting point and agreed scope. Deliverables, required input and fees are described before commissioning. A limited first step can help resolve open questions.
How long does a project take?
Timing depends on scope, available material, access and approvals. A schedule is agreed for the actual project. Changed requirements or missing content can affect it.
What is included after handover?
The agreed files, source material, setup notes and check results are handed over. Hosting, ongoing maintenance, support and further changes are explicitly agreed as needed.
More services
What would you like to change?
Tell EVA – right now, no appointment, no waiting. She clarifies goal and scope with you and passes your project straight to us.
Prefer email: hello@obholz.solutions
Opens your email app with a prepared enquiry.