When you need assistance with your Data Mammoth services, submitting a well-structured support ticket is the fastest way to get help. Our support team handles technical issues, billing questions, account management, and service requests. This guide explains how to submit a ticket and provides tips for getting a quick resolution.
When to Submit a Ticket
Submit a support ticket for:
- Technical issues — Server not responding, performance problems, service errors.
- Billing questions — Invoice inquiries, payment issues, refund requests.
- Account management — Password resets, 2FA recovery, account changes.
- Service requests — Migrations, managed service tasks, custom configurations.
- Feature requests — Suggestions for improvements or new features.
How to Submit a Ticket
Step 1 — Navigate to Support
Step 2 — Select the Department
Choose the department that best matches your issue:
| Department | Use For |
|---|---|
| Technical Support | Server issues, connectivity, performance, software |
| Billing | Invoices, payments, refunds, pricing |
| Sales | Pre-sales questions, custom quotes, enterprise plans |
| Account | Password recovery, 2FA issues, account changes |
| Migrations | Server migration requests and coordination |
Step 3 — Select the Related Service
If your issue relates to a specific server or service, select it from the dropdown. This gives our team immediate context about your infrastructure.
Step 4 — Choose a Priority
Select the priority level that matches the urgency of your issue:
- Low — General questions or non-urgent requests.
- Medium — Issues affecting a non-critical service or feature.
- High — Issues affecting a production service with limited impact.
- Critical — Complete service outage or data loss risk.
Step 5 — Write the Subject and Message
Subject: Write a concise, descriptive subject that summarizes the issue.
Good examples:
- "Server 203.0.113.10 not responding to SSH"
- "Invoice INV-2026-0042 incorrect charge"
- "Cannot install SSL certificate on VPS"
Message: Include all relevant details:
203.0.113.10), service name, OS version.Step 6 — Attach Files (Optional)
If relevant, attach:
- Screenshots of error messages
- Log file excerpts
- Configuration files (remove any passwords or sensitive data)
Step 7 — Submit
Click Submit to create the ticket. You will receive a confirmation email with your ticket number.
Example of a Well-Written Ticket
Subject: Website returning 502 error on server 203.0.113.10
Message:
My website at example.com started returning 502 Bad Gateway errors at approximately 14:30 UTC today (March 15).>
Server IP: 203.0.113.10
OS: Ubuntu 24.04
Web server: Nginx>
Steps I have taken:
1. Restarted Nginx — service started but the error persists.
2. Checked error logs at /var/log/nginx/error.log — see attached screenshot.
3. Verified PHP-FPM is running — it appears to be crashing and restarting.
4. Checked disk space (df -h) — 62% used, no space issues.>
The error log shows "upstream sent too big header" messages. I believe this may be a buffer configuration issue but am not sure how to fix it.
This ticket provides everything the support team needs to investigate immediately, resulting in a faster resolution.
After Submitting
- You receive a confirmation email with your ticket number and a link to track the ticket.
- Our team will respond according to the priority level and SLA. See Understanding Ticket Priority & SLA.
- You can view and respond to the ticket from your dashboard. See Checking Your Ticket Status.
- Enable email notifications to stay updated on replies.
What to Do Next
- Understanding Ticket Priority & SLA — Learn about response times.
- Checking Your Ticket Status — Track your open tickets.
- Browsing the Knowledge Base — Find answers to common questions.
- All Ways to Contact Support — Explore other support channels.