Creating a support ticket: The direct line to CURIAWEB Support
If you have a technical question, need assistance with a hosting product or want to clarify an issue regarding an invoice, the ticket system in the CURIAWEB client area is the recommended way to contact support. A support ticket is more structured than a regular email and helps ensure that your request is assigned directly to the appropriate department.
This allows your request to be handled more precisely. Technical questions can be assigned to technical support, while administrative or billing-related issues can be sent to the responsible team. At the same time, the entire communication remains documented in the client area.
In brief: Why open a support ticket?
A support ticket ensures that your request is recorded in a structured way, assigned to the correct department and answered in a traceable manner. Especially for technical issues, billing questions or product-related requests, this is usually more efficient than an unstructured email.
How to open a support ticket
You can create a new request directly in the CURIAWEB client area.
Procedure overview:
- Log in to the CURIAWEB client area.
- Click Support -> Tickets or directly on Open Ticket.
- Select the appropriate department, for example Technical Support or Billing.
- Enter a meaningful subject.
- If applicable, select the affected product or service.
- Describe your request in as much detail as possible.
- If needed, add files or screenshots using Attach File.
- Submit the ticket.
Why is the correct department important?
Selecting the correct department helps classify your request more quickly. A technical fault, a website issue, a cPanel question or an email problem usually belongs with technical support. Questions about invoices, payments or payment receipts should be directed to billing.
If a ticket is submitted to the most suitable department, it can be reviewed directly by the right team. This reduces follow-up questions and avoids unnecessary forwarding between departments.
What should a good ticket description include?
The more precisely you describe your request, the better support can understand the situation. A good description does not only say that something “does not work”, but explains what exactly happens, when the problem started and which steps have already been tried.
For technical issues, the following information is helpful:
- Which domain, website, email address or hosting package is affected?
- Which error message is displayed?
- When did the problem first occur?
- Does the problem occur permanently or only occasionally?
- Were any changes made shortly before the issue appeared?
- Which steps have you already tried?
For billing questions, details such as invoice number, affected service, payment date or payment method can be helpful. Please avoid sending sensitive information unless it is necessary for processing your request.
Use attachments and screenshots
Screenshots can make troubleshooting much easier. An error message, a suspicious browser display, an issue in the client area or a view from an email program can often be understood more quickly with an image than with a long written explanation.
Tip: Use Attach File to upload screenshots of error messages or problematic views. This often helps support identify the issue more quickly and respond more precisely.
Make sure that the relevant error message is clearly visible in the screenshot. Remove or hide sensitive information that is not required for processing, such as private content, passwords or confidential customer data.
Replies to your ticket
As soon as CURIAWEB Support replies to your ticket, you will automatically receive an email notification. You can also view the history of your request in the client area. This keeps the communication organised in one place.
When replying to follow-up questions, it is best to stay within the existing ticket. This keeps the context intact and ensures that all previous information remains available for processing.
Recommendation for faster processing
Create separate tickets for different issues whenever possible. For example, if you have both a billing question and a technical problem, it is often better to open two separate requests. This allows each request to be assigned to the appropriate department and processed independently.
Avoid very general subject lines such as “Problem” or “Help”. More precise subject lines such as “Email sending for example.ch does not work” or “Question about invoice no. 12345” are better. This makes the topic clear before the ticket is even opened.
Summary
The ticket system in the CURIAWEB client area is the recommended way to submit technical questions, billing issues or product-related support requests. Select the appropriate department, use a clear subject, describe your request as precisely as possible and add attachments or screenshots if needed. As soon as a reply is available, you will automatically receive an email notification.
