One path for requests.
Staff know where to report a problem and who continues the investigation.
Agreed schedule → planned work → scenario check.
Symptom → priority and owner → recovery and verification.
New requirement → agreed scope → tested change.
Provider limits, extra work and response terms are agreed explicitly.
Routine maintenance, incidents and separate development have different scopes. Provider restrictions and extra work are agreed; a request is not a promise of a fixed resolution time.
Staff know where to report a problem and who continues the investigation.
Planned updates are separate from urgent incidents and new requests.
After a fix, we check whether a customer can actually book or order.
The scope of routine work, response hours and external dependencies are agreed in advance.
An application's dependencies, access and load change. The team has new tasks. An error can arise in your system, at a provider or at an exchange boundary. Without an agreed process even a small issue can become a long conversation without an owner.
We define supported systems, priorities and boundaries. Incidents, user questions and new features follow different paths rather than entering one queue with an unclear deadline.
We plan selected updates and checks of resources, access and backups. Changes account for compatibility and an acceptable window. We do not update a working system merely because a new version exists.
We record what is affected, its impact on work and who owns the next step. For an incident, detection time, current impact and a way to reduce consequences matter. A development request needs an expected result and separate agreement on scope.
We establish where a client or provider must act, what information may be shared and who decides. An external platform's availability is not fully under pNet's control, but escalation should still follow a clear process.
We maintain useful instructions: system components, normal operations, signs of a problem and failure responses. Instructions should help the responsible person, not merely list commands without context.
We compare the agreed version and verified scenario, then decide whether to fix configuration, revert the application or recover individual data. These actions require different risk assessments.
A running Odoo instance does not promise that a salon administrator can process a booking today. Operational investigation covers the application, containers, database, background queue and selected external services, then checks the scenario available to the operator. A third-party provider failure and internal configuration issue require different owners and actions.
An academy may update programmes and dates; a supplier may update its catalogue and terms. pNet separates content changes, planned updates, incident fixes and feature development so support does not become unlimited development. Actual support hours and response terms are agreed separately.
Technical monitoring is related to recovery testing, while a version change goes through a controlled release.
Note: support response time and actual recovery time are different terms. Round-the-clock support is not included by default.
Record the impact. Which system is affected and what does not work for staff and customers?
Define the next step. Clarify priority, assign an owner and identify which actions depend on providers.
Act and communicate. Agree the necessary measures and inform the owner of significant changes.
Verify and close. Confirm that a real scenario has recovered; do not confuse a separate enhancement with a fixed incident.
Limit: If the cause requires separate development, a temporary recovery is not presented as a final fix. Remaining risk and the next work are made visible.
The list of systems and access, support hours, contact methods, priority levels and approval process for changes. Response times, acceptable windows, external costs and work outside regular support are documented separately.
Round-the-clock cover, unlimited development and a guaranteed fix time for every problem are not implied. Response time is not the same as full recovery time.
Support hours, response expectations and included work are agreed separately. Monitoring, backups and provider responsibilities are made explicit rather than assumed to be part of every support arrangement.
Describe your systems, the problem and any known constraints. You do not need a complete technical specification. Please leave passwords, keys and customer data out of your message.
We first check documentation, rights, versions and current state. After familiarisation we agree a realistic scope of responsibility.
No. Routine operations, incident fixes and new features have different scopes. The rules are defined before work begins.
We follow the agreed process: check its state, limit repeated effects, inform owners and use an allowed temporary process. We do not promise another provider's availability as our own guarantee.
No. User reports and technical signals complement one another. Useful checks are selected separately for critical scenarios.
Tell us which systems need support and how problems are handled today. We will establish boundaries, priorities and a useful first scope.