Submitting a support ticket the right way helps your issue get fixed faster and keeps communication clear. This guide walks you through the essential steps and expectations when you open a ticket with our team.
Use the summary below to quickly compare channels, expected response times, and what details you should include depending on your case.
| Support Channel | Best For | Typical Response Time | Key Details to Include |
|---|---|---|---|
| Web Portal | Formal requests and attachments | Within 2 business hours | Order ID, screenshots, error codes |
| Detailed background and documentation | Within 4 business hours | Timeline, impacted users, configuration | |
| Live Chat | Quick clarification and short issues | Immediate during business hours | Concise description, current screen state |
| Phone | Urgent problems needing real-time guidance | Immediate during business hours | Account name, issue summary, urgency level |
Preparing Your Ticket Details
Before you submit, gather information that speeds up diagnosis. Clear context reduces back-and-forth and helps the support engineer reproduce the problem.
Gather Technical Information
Collect logs, screenshots, and exact error messages. Note the browser, operating system, and version numbers if relevant to the issue.
Define the Impact
Describe how the problem affects your workflow or users. Include the frequency, business process impacted, and any workarounds you have tried.
How to Create the Ticket in Our System
Our web portal is designed to capture structured data so your case routes to the right team quickly.
Step-by-Step Submission
Follow these steps to ensure your ticket includes everything needed for fast resolution.
- Log in to the support portal with your registered account.
- Select the appropriate product or service from the dropdown.
- Choose a priority level based on urgency and business impact.
- Write a clear title that summarizes the core problem.
- Describe the issue in the description field with timestamps and steps to reproduce.
- Attach screenshots, logs, and any relevant files.
- Submit the ticket and copy the ticket ID for follow-up.
Priority and Classification Options
Choosing the right priority and category helps us align resources with your business needs.
| Priority Level | Definition | Typical Use Case | Target Resolution Time |
|---|---|---|---|
| Critical | System down or severe outage | Production blocking for multiple users | Within 4 hours |
| High | Major feature broken for one team | Key workflow impaired but workarounds exist | Within 12 hours |
| Medium | Partial functionality issue | Single user or limited impact | Within 24 hours |
| Low | Enhancement or cosmetic issue | No workaround needed, low urgency | Within 5 business days |
Communication and Updates
Once your ticket is created, you will receive automated status updates. Proactive communication keeps you informed about progress and any required action from your side.
Status Transitions
Understand common status changes so you know when to expect the next update.
- New: Ticket received and not yet triaged
- Investigating: Engineer reviewing details and reproducing the issue
- Resolved: Fix applied and awaiting your verification
- Closed: Issue confirmed resolved and documentation updated
Next Steps for Effective Support
Use these actionable points to streamline future interactions and improve your experience with our support team.
- Include exact timestamps and error codes in every ticket.
- Select the correct priority level based on business impact.
- Attach screenshots and logs before submitting the ticket.
- Monitor ticket updates and respond promptly to requests for more information.
- Reference your ticket ID in all follow-up communication.
FAQ
Reader questions
How quickly will I receive an initial response after submitting a ticket?
You will typically receive an acknowledgement within minutes for web portal and chat submissions, and within a few hours for email, with initial triage completed in most cases within the first business day.
What should I do if my ticket status has not changed for several days?
Update the ticket with a brief note asking for status clarification, or reply to the latest message from the support team to surface the case back into the queue.
Can I add files or screenshots after I have submitted the ticket?
Yes, you can upload additional files through the ticket interface or reply with new information, and these attachments will be linked to the existing case for the engineering team.
Is it better to open one ticket per issue or combine related issues into a single ticket?
Open one ticket per distinct issue to keep focus and metrics clear, but link related tickets in the description so the team can see the full context without conflating separate problems.