Support
Support.
How to reach Mailtruss, what to send, and what to expect. Written down so you do not have to guess.
On this page
How to reach us
Write to hello@mailtruss.com. It reaches the person who builds and runs Mailtruss, not a queue in front of them. Use the other addresses only for what they are for:
| For | Write to |
|---|---|
| Help, billing, raising a limit, moving to or from Mailtruss | hello@mailtruss.com |
| Security reports and vulnerabilities | security@mailtruss.com |
| Abuse reports (include the full headers of the message, not a screenshot) | abuse@mailtruss.com |
| Privacy and data requests | privacy@mailtruss.com |
| A higher daily limit while you move a real workload (paid plans) | Sending limits in the dashboard, not email |
| Legal notices and the terms | legal@mailtruss.com |
| Grievances | grievance@mailtruss.com |
Limit reviews. We reply within 1 working day and decide within 2 working days once we have everything we need. These are targets, not guarantees. They are measured in working days, Monday to Friday. See how limit reviews work.
What to send so the first reply can be an answer
- The email id from the dashboard or the API response, or the x-request-id header of the failing request. Either one lets us open exactly what happened.
- The sending domain, the time in UTC, and what you expected to happen instead.
- For a bounce or a delay, the message's trace page already holds the delivery id and the receiving server's reply. A link or a copy of that is enough.
- Never send an API key or a password. If you pasted one by mistake, revoke it in the dashboard first.
Check these first, they are faster
- The status page: is the API, the database or the delivery workers failing right now?
- The message's trace in the dashboard: it says what happened, in a sentence, and whether retrying is safe.
- The delivery errors guides and the API error list.
- API logs in the dashboard, searchable by request id.
What Mailtruss does not offer
- No round-the-clock on-call rota and no phone line. Monitoring runs all day and night (see the status page), but email is answered by a person, not around the clock.
- No uptime commitment or service-level agreement. The Billing and Refunds page covers what we do when the service fails you for a material part of a billing period.
- No dedicated account manager, and no certifications such as SOC 2 or ISO 27001. The security page says what exists.
If those limits matter for what you are building, plan for them: keep a second provider ready, and know how to leave. The exit and migration guide is written for exactly that.