Create a Good Ticket
A helpful ticket should explain:- What happened
- What you expected to happen
- The affected business or store
- Any steps needed to reproduce the issue
- Relevant product, sale, import, report, or payment references
Use the Ticket Conversation
Ticket messages work like a conversation. Your messages and support replies appear in the ticket thread so both sides can follow the history. When replying, keep each message focused. If a new unrelated issue appears, create a separate ticket so it can be tracked properly.Attach Files
Attachments are useful when support needs to see a screenshot, CSV file, receipt, or error message. After selecting a file, wait for the upload indicator to finish and confirm that the file appears in the message before sending. If the upload fails, try again with a smaller file or a common file format such as PNG, JPG, PDF, or CSV.Mobile Ticket Experience
On mobile, tickets should be easy to use like a chat screen. The ticket list shows open and recent tickets. Selecting a ticket opens the conversation. The back button should return to the ticket list, not exit the dashboard. The message box and attachment button should remain easy to reach, even on small screens.Understand Notifications
MyStockPulse uses notifications to alert you about important workspace events. Some notifications are informational, while others require action. Examples include:- Subscription expired
- Subscription renewed
- Payment successful
- Support ticket updated
- Import completed
- System announcements