Skip to main content

Ticket Details

This page explains how to review a support ticket in detail, follow the conversation, and continue the same support flow when needed.

What the ticket details page is for​

The ticket details page shows the full conversation for a specific support request.

Use it when you want to:

  • read support replies
  • review the latest update
  • understand the current ticket status
  • send a follow-up reply
  • attach more information if needed
  • keep track of the issue history
  • close the ticket when the issue is finished

Open a ticket​

Sign in to Dash, go to the support section, and open the ticket list.

From there, select the ticket you want to review.

This opens the full ticket details page.

What you may see in ticket details​

Depending on the current interface, the ticket details page may include:

  • ticket subject
  • ticket ID
  • current status
  • conversation history
  • support replies
  • your previous replies
  • timestamps
  • department information
  • reply box
  • close ticket action

The exact layout may change over time, but the purpose remains the same.

Review the latest reply first​

Before sending a new message, always review the most recent reply carefully.

This helps you understand:

  • whether support asked for more information
  • whether a test step was requested
  • whether the issue is already considered resolved
  • whether you need to reply now or wait for the next update

The latest reply usually tells you what should happen next.

Use status and conversation together​

Do not rely on the visible ticket status alone.

It is usually best to read the ticket status together with the latest message.

This helps you understand whether:

  • the issue is still active
  • support is waiting for your reply
  • the case is still under review
  • the ticket is moving toward closure

The message gives context. The status gives structure.

Reply in the same ticket when the issue is the same​

If the same issue is still being discussed, continue in the same ticket instead of opening another one.

Reply to the ticket when:

  • support asked for more details
  • you tested a suggested step
  • the issue changed and you need to provide an update
  • the problem is still happening
  • you want to confirm that the issue is resolved

A good rule is:

  • same issue, same ticket
  • different issue, new ticket

This keeps support history cleaner and avoids splitting one issue across multiple conversations.

Write a focused reply​

When replying, include only the new information that matters.

Good examples include:

  • the result of a test you performed
  • the exact error you are still seeing
  • confirmation that access now works
  • clarification about the affected service, domain, or invoice
  • a screenshot or attachment that helps explain the issue

Try to keep your reply direct and tied to the same problem already being discussed.

Avoid duplicate explanations​

Because the full history is already visible in the ticket, you usually do not need to repeat everything from the beginning.

Focus on:

  • what changed
  • what you tested
  • what still does not work
  • what support needs to know next

This keeps the conversation cleaner and easier to review.

Know when to wait​

Sometimes the latest reply is only an update and does not require immediate action from your side.

In that case, the best next step is usually to:

  • review the message carefully
  • keep the ticket in mind
  • wait for the next support update unless you have important new information

Avoid sending replies that do not move the ticket forward.

Close the ticket when appropriate​

If the issue is resolved and no more follow-up is needed, use the close ticket action if it is available in the interface.

Before closing the ticket, make sure:

  • the issue is actually resolved
  • no more testing or confirmation is still needed
  • the ticket no longer requires support attention

If something looks wrong​

If the ticket details page does not load correctly, the reply option is missing, the status looks unclear, or the conversation appears incorrect:

  • refresh the page
  • review the ticket again
  • compare the latest message with the visible status
  • confirm that you are in the correct account
  • contact support if the issue continues