Skip to content

How to contact support and manage your service Print

  • 1

A useful support request tells the receiving team what the business cannot do, which service is affected and what evidence is available. This reduces the need for repeated clarification and helps distinguish an access problem, an application fault, a restore request or an account administration issue.

Netcloud24 support is provided through email and the customer ticket system; telephone support is not offered. For service-specific assistance, sign in to the customer portal and open a ticket in the appropriate department. Use an authorized account contact for requests that change access, billing, recovery state or the service itself.

Identify the service and the business impact

Start with the service identifier and server name shown in the portal or handover. If your organization has several servers, state the environment and application as well. “Our server is broken” is difficult to act on when the account contains a production RDS server, a test server and several unrelated services.

Describe the task that fails: signing in, opening the accounting application, reaching a shared folder, printing a report or restoring a deleted document. State whether the problem affects one person, a particular office or everyone. Include any safe workaround already in use and whether the business is completely stopped or partially affected.

Business impact is more useful than an unexplained urgency label. For example, “All five authorized users receive the same sign-in error and payroll processing cannot start” gives a clear operational picture. Do not exaggerate the scope; accurate information helps the team choose the right starting point.

Include a precise timeline

Give the first observed failure time and the last known successful use, including the time zone. If a problem started around 9:15 a.m. Eastern Time, say so rather than writing “this morning.” Support may need to compare application events, access logs, maintenance activity and backup records from systems using different time settings.

List recent changes that could be relevant: a new office router, changed internet provider, application update, password reset, new printer, added user or permission change. Report facts without assuming the change caused the problem. The correlation is useful evidence even if it later proves unrelated.

For intermittent issues, provide two or three specific examples with times, the user’s location and the task being performed. Distinguish a slow connection from a slow report or a failed file export. Broad descriptions such as “sometimes slow” are difficult to compare with resource and network measurements.

Capture errors safely

Copy the exact error text and any error code. Include the application or Remote Desktop client version and the operating system of the local device when access is involved. Screenshots can help when the message cannot be copied, but crop unrelated desktop content and conceal customer records or other unnecessary personal information.

Do not include permanent passwords, full payment-card details, authentication recovery codes or private keys. If support requires a log or configuration file, review it for credentials and confidential data and use the approved transfer method. A connection file or diagnostic archive can contain more information than its visible name suggests.

Summarize the steps already attempted and their results. “Reconnected to the approved VPN; the same error appeared at 10:32 a.m. Eastern” is useful. A long list of unrecorded setting changes makes diagnosis harder, especially if the original configuration is no longer known.

Use a clear incident structure

The following structure can be adapted to the situation. Replace the examples with accurate service information and omit fields that do not apply:

  • Service: portal service identifier, expected server name and application.
  • Impact: who is affected and which business task is blocked.
  • Timeline: first failure, last success and time zone.
  • Observed error: exact wording or a safely prepared screenshot.
  • Connection context: approved VPN or gateway, local operating system and client version.
  • Recent changes: relevant account, application, endpoint or network changes.
  • Checks performed: specific actions and the result of each.
  • Authorized contact: the person who can approve a proposed change or recovery.

Keep related findings in the existing ticket so the history stays together. If a separate issue emerges, explain the relationship and use a separate request where appropriate. Multiple parallel tickets describing the same outage can fragment the evidence and approvals.

Match the request to the outcome needed

Connection problems: say whether the VPN connects, whether a Remote Desktop sign-in prompt appears and whether other authorized users can reach the same service. Do not make repeated password guesses. A timeout and a credential rejection require different checks.

Application problems: name the exact product, version, dataset and failing workflow. Include the vendor’s relevant support requirements if known. Infrastructure support and vendor-specific database or application repair may have different owners, so expect the scope to be reviewed before changes are made.

Restore requests: give the last known good time, affected paths or database, desired recovery destination and whether current data must be preserved. Identify who can accept downtime or data rollback. Follow the backup and restore guide rather than asking support to “undo everything.”

Security incidents: explicitly mention suspected unauthorized access, malware, lost devices or unexpected account changes. Include the timeline and preserve relevant evidence. Avoid deleting logs or restoring over the server before containment and investigation have been considered.

Request planned changes with enough context

For new users, provide the approved person, required role and access scope. Confirm any licensing implications before the account is used. Do not ask for a shared employee password or simply request “the same access as everyone else” when permissions differ across the team.

For capacity changes, describe the workload that is growing: more simultaneous users, larger data, a new database or heavier reports. Include the expected timing and business constraints. Resource increases should address a demonstrated need, and some changes may require a maintenance window or a fresh quotation.

For application installation or upgrades, provide vendor instructions, supported Windows and database versions, licence availability and a rollback plan. Agree who will perform application acceptance. A successful installer exit does not show that users can complete their daily work.

Manage billing, contacts and cancellation deliberately

Keep authorized contacts and billing information current in the portal. Decide internally who can approve service changes, restores and financial requests. If the only approver is unavailable, a technically simple task can still be delayed while authorization is established.

Submit cancellation requests through the customer portal before the next invoice due date, following the applicable Terms of Service. Stopping use or sending an informal message does not automatically complete the cancellation process. Check the current contractual rules and retain the portal confirmation for your records.

Before a service ends, export required company data, application configuration and records. Verify that the exported copy can be opened in the destination environment and retain any necessary licences, keys or vendor instructions securely. Arrange the cutover and data ownership decisions before access is removed.

Do not assume that a backup will remain available indefinitely after termination. Confirm the applicable data and retention arrangements with support while the service is active. If your organization has legal or regulatory retention requirements, plan an appropriate independent archive rather than relying on a hosting recovery window.

Confirm completion and keep the record useful

When support reports a resolution, repeat the failing business task and confirm the result. For an access change, use the affected ordinary user account; for a restore, have the data owner validate representative information. Report a remaining issue with a new timestamp and the exact observed behaviour.

Keep the final decision, maintenance notes and any outstanding actions with your service documentation. Review the managed plan scope when responsibilities are unclear. Open requests through the customer support ticket form and consult the Terms of Service for the contractual process.


Was this answer helpful?

« Back