Your personal support archive in the CURIAWEB Client Area
In the CURIAWEB Client Area, you can access your previous support requests at any time. This is especially useful if an issue has already been solved in the past and you would like to read the answer, instructions or technical recommendation again. Your support tickets are therefore not only used for current communication with our support team, but also serve as your personal archive for previous requests related to web hosting, domains, email, DNS, invoices and other CURIAWEB services.
For technical topics in particular, it is helpful when previous solutions remain documented. Perhaps we have already explained how to set up an email address, change a DNS record, renew a domain or solve a problem with your website. Instead of searching for the same information again, you can simply open the existing ticket in the Client Area and review the complete conversation history.
Why is the support archive useful?
The support archive helps you quickly find previous answers and solutions. This can save a lot of time, especially with recurring questions. For example, if a specific setting for your domain, hosting package or email account has already been discussed, you can find the relevant answer directly in the old ticket.
Attachments, screenshots and technical notes also remain available in the ticket history. This allows you to check later which steps have already been carried out and which recommendations our support team provided. This is also useful if several people in your company have access to the CURIAWEB Client Area and need to understand previous support cases internally.
How to find old support tickets in the CURIAWEB Client Area
To access previous support requests, first log in to the CURIAWEB Client Area with your login details. You can then access your existing tickets through the support section.
- Log in to the CURIAWEB Client Area.
- Go to “Support” and then select “Tickets”.
- You will now see an overview of your previous support requests.
- If necessary, use the “Status” filter to display closed tickets as well.
- Click on the subject of a ticket to open the complete message history.
- If needed, also check any attachments, screenshots or files included in the ticket.
What information can you find in an old ticket?
When you open a ticket, you can view the full communication history between you and CURIAWEB Support. This includes your original request, all replies from our support team, possible follow-up questions, technical notes and uploaded files or screenshots.
Depending on the request, a ticket may contain important information such as:
- Details about hosting or domain settings
- Instructions for setting up email accounts
- Information about DNS, SPF, DKIM or DMARC settings
- Explanations regarding invoices, payments or renewals
- Recommendations for troubleshooting website issues
- Links to further guides or knowledgebase articles
- Support replies about cPanel, WHMCS or other CURIAWEB services
Reopening closed tickets
A closed ticket simply means that the request was considered completed at that time. If the same problem occurs again or if you have a follow-up question about an existing case, you can often reply directly to the existing ticket. This keeps the previous conversation history intact and allows our support team to immediately understand the original context.
Reopening an existing ticket is especially useful when it concerns the same topic. This helps avoid duplicate requests and makes it easier for support to assign the case correctly. However, if your request concerns a new issue or a different product, we recommend opening a new support ticket.
When should you create a new ticket?
Not every request should be continued in an old ticket. If your new request is not related to the original issue, creating a new support ticket is usually the better option. This keeps communication clear and allows our support team to assign your request to the correct category more quickly.
A new ticket is useful, for example, if your request concerns another domain, a different hosting package, a new invoice or a completely different technical issue. If you only have a follow-up question about a previous solution, you can use the existing ticket.
Tips for using your support archive efficiently
To find your previous support requests more easily, you should use clear and descriptive subject lines when creating new tickets. A subject such as “Email sending does not work for info@domain.ch” is more helpful than a general subject such as “Problem”. The clearer the subject, the easier it will be to find the ticket later.
Also use the filter options in the Client Area. Depending on the status, tickets may be open, answered, in progress or closed. If you do not immediately see an older ticket, check whether closed tickets are currently hidden.
Frequently asked questions about the support archive
Can I still view old support tickets after a long time?
Yes. Your previous support requests remain stored in the CURIAWEB Client Area and can be accessed again later.
Can I download attachments from old tickets again?
If attachments are available in the ticket, they can usually be viewed or downloaded directly from the ticket history.
Should I create a new ticket for every problem?
For a new topic, a new ticket is recommended. If it concerns the same problem or a direct follow-up question about an earlier reply, you can reply to the existing ticket.
Why can I not see my old ticket immediately?
Check the status filter under “Support” > “Tickets”. Closed tickets may currently be hidden.
Summary
The support archive in the CURIAWEB Client Area is your central overview of previous support requests. You can view old tickets, reread previous solutions, check attachments and reply to existing tickets if needed. This helps you keep track of earlier requests and quickly find important information about your hosting, domains, email accounts or invoices.
If you need to read a previous reply from CURIAWEB Support again, simply open “Support” > “Tickets” in the Client Area and search for the relevant ticket.
