Your feedback is essential to maintaining and improving the quality of Data Mammoth's support services. Whether your experience was excellent or needs improvement, we want to hear about it. This guide explains the different ways you can share feedback and how we use it.
Why Your Feedback Matters
Every piece of feedback helps us:
- Recognize great support — Positive feedback highlights team members who go above and beyond.
- Identify improvement areas — Constructive criticism helps us address gaps in our processes.
- Improve documentation — Feedback on Knowledge Base articles leads to better, clearer guides.
- Shape future features — Your suggestions influence our product roadmap.
- Maintain accountability — Regular feedback ensures our team meets service standards.
Ticket Satisfaction Rating
After a support ticket is resolved, you may receive a satisfaction survey:
How It Works
What to Include in Your Feedback
When leaving a comment, consider mentioning:
- What went well — Was the response fast? Was the solution effective? Was the agent knowledgeable and friendly?
- What could be improved — Was there a delay? Did you need to repeat information? Was the solution unclear?
- Specific suggestions — Ideas for how the interaction could have been better.
Examples of Helpful Feedback
Positive:
"Agent resolved my SSH connection issue within 30 minutes. Clear instructions and very patient. Great experience."
Constructive:
"The solution worked, but it took 3 back-and-forth exchanges to get the right answer. It would help if the initial response asked for server logs upfront to speed things up."
Rating a Knowledge Base Article
Many Knowledge Base articles include a feedback mechanism at the bottom of the page:
This feedback directly influences article updates and improvements.
Submitting General Feedback
For feedback that is not tied to a specific ticket or article:
Feature Requests
If you have an idea for a new feature or improvement:
Feature requests are reviewed by our product team and may be prioritized based on demand and feasibility.
Escalation for Unresolved Issues
If you are not satisfied with how a ticket was resolved:
We take escalations seriously and will work to find a satisfactory resolution.
How We Use Your Feedback
| Feedback Type | How We Use It |
|---|---|
| Ticket ratings | Tracked per agent and team. Used for performance reviews and training. |
| Article ratings | Flagged for content team review. Low-rated articles are prioritized for updates. |
| Feature requests | Logged in our product backlog. Popular requests are prioritized for development. |
| General feedback | Reviewed by management. Used to identify systemic improvements. |
| Escalations | Investigated individually. Used to improve processes and prevent recurrence. |
Feedback Best Practices
What to Do Next
- How to Submit a Support Ticket — Submit feedback via a ticket.
- Browsing the Knowledge Base — Rate articles as you read them.
- All Ways to Contact Support — Choose the best channel for your needs.
- Understanding Ticket Priority & SLA — Know what to expect from support.