Contact Support
Get help from the Et'al MDM support team.
Need help? Our support team is here to assist you. Choose the best way to reach us based on your needs.
Support Channels
Email Support
For general support inquiries, technical issues, and troubleshooting:
support@etalmdm.comWhen emailing, please include:
- Your account email address
- A description of the issue or question
- Steps to reproduce the problem (if applicable)
- Screenshots or screen recordings if they help illustrate the issue
- Your deployment type (hosted or self-hosted)
Sales Inquiries
For pricing, partnerships, and volume licensing:
sales@etalmdm.comSecurity Reports
To report a security vulnerability or concern:
security@etalmdm.comFor security reports, please do not disclose vulnerability details publicly. Email security@etalmdm.com and we will respond within 24 hours.
Response Times
| Tier | Response Time | Priority Support |
|---|---|---|
| Base | 48 hours | |
| Pro | 24 hours | Email, priority queue |
| Enterprise | 4 hours | Email, priority queue, dedicated contact |
Enterprise customers receive a dedicated support contact during onboarding.
Before Contacting Support
To help us resolve your issue faster:
Check the documentation — Your answer might be in our FAQ or Troubleshooting guide
Identify the scope — Is the issue affecting one device, a device group, or the entire fleet?
Gather details — Note the device ID, command ID, or policy name related to the issue
Check server status — For self-hosted deployments, verify your containers are running (docker compose ps)
What to Include
For Device Issues
1. Device ID (e.g., dvc_abc123) or serial number
2. Device platform and OS version
3. What you expected to happen
4. What actually happened
5. Screenshots of the device detail pageFor Command Issues
1. Command ID or command type (lock, wipe, etc.)
2. Target device ID
3. Command status (pending, delivered, failed)
4. Timestamp when the command was sent
5. Any error messages displayedFor Policy Issues
1. Policy name and ID
2. Affected device group
3. Which policy settings aren't applying
4. Device compliance status and violation detailsFor Self-Hosted Deployment Issues
1. Docker Compose version and host OS
2. Container status output (docker compose ps)
3. Relevant container logs (docker compose logs web)
4. Supabase status (docker compose logs supabase)
5. Network configuration (reverse proxy, TLS)Feature Requests
We welcome feedback and feature ideas. Email your suggestions to:
support@etalmdm.comInclude:
- A description of the feature you'd like
- Your use case — what problem does it solve?
- How you're working around the limitation today (if applicable)
Support Resources
| Resource | Link |
|---|---|
| Documentation | /docs |
| FAQ | /docs/faq |
| Troubleshooting | /docs/troubleshooting |
| Features | /docs/features |
| Request Early Access | /early-access |