Support Service Overview
The support section is where you manage communication related to service issues, account questions, billing concerns, and other operational requests in PerLod Dash.
It is not a standalone infrastructure product. It is a support workflow built around tickets and account assistance.
What the support section is for
Use the support section when you want to:
- open a new support request
- review existing tickets
- track ticket progress
- reply to an active ticket
- follow support updates about a service or account matter
This section helps keep support communication organized and connected to your account activity.
What you may see in support
Depending on the current interface, the support area may include sections such as:
- ticket list
- ticket search and filters
- ticket statuses
- new ticket action
- ticket conversation view
- ticket information panel
- reply and close actions
The exact layout may change over time, but the overall flow remains the same.
How support works in PerLod
A new ticket does not start directly inside the final specialist department.
New tickets are first handled through Customer Care.
From there:
- you create a new ticket
- Customer Care reviews the request first
- the issue is answered directly if possible
- if needed, the case is referred to the related department
- the ticket continues in the same support flow until the issue is resolved
This helps keep new requests organized and routed to the right place when deeper review is needed.
Common support flow
The usual support flow is:
- open the support section
- review whether an existing ticket already covers the issue
- create a new ticket or open the correct existing one
- follow replies and status updates
- continue the conversation in the same ticket until the issue is resolved
This makes it easier to keep the support history in one place and avoid losing context.
When to open a new ticket
Open a new ticket when:
- the problem is new and unrelated to previous tickets
- you need help with a service or account issue
- the current issue does not match an older support thread
When possible, include the relevant service ID, invoice number, or domain name to help support review the issue faster.
When to use an existing ticket
Use an existing ticket when:
- the same problem is still being discussed
- support already asked for more information
- you tested a suggested step and need to share the result
- you have a useful update for the same issue
A simple rule is:
- same issue, same ticket
- different issue, new ticket
This keeps the support history cleaner and easier to manage.
Best practices when using support
To make support review easier:
- use a short and clear issue summary
- include the affected service, domain, or invoice if relevant
- explain what you were trying to do
- include exact error messages when visible
- avoid opening duplicate tickets for the same issue
- read the latest reply before sending another message
Clear details usually help speed up the review process.