21 June 2026 · 2 min read
Support is built into the platform rather than bolted on, because email authentication touches live mail flow and getting stuck is not an option. Every plan includes in-app ticketing from the dashboard at app.dmarcengine.com: open a ticket, attach the domain in question, and we can see the same DNS state, report data and timeline you do, so there is no back and forth pasting record values into emails. You can also reach us by email, and tickets and email replies land in the same thread so nothing gets lost between channels. If you have not signed up yet, the free diagnostic tools (the DMARC checker, SPF checker, DKIM checker and BIMI checker) answer most "is my record correct" questions on their own, and the DMARC report analyser explains what your aggregate reports actually mean.
Typical response expectations depend on urgency and plan, and we are honest about that rather than promising numbers we cannot keep across every tier. As a general guide:
- Anything affecting live mail delivery (legitimate mail being quarantined or rejected after a policy change) is treated as top priority and answered first, usually within hours during working hours.
- Configuration and onboarding questions (record syntax, which sources to authenticate, when it is safe to tighten policy) are normally answered the same working day or the next.
- General questions and feature requests are worked through in turn after the above.
We deliberately do not rush you from p=none to p=reject. The whole point of the platform is to take a domain there safely with no outage, so if a ticket is about tightening policy we will look at your real aggregate report data first and tell you whether your sending sources are fully aligned before recommending the change. If they are not, we will tell you exactly which source needs SPF or DKIM fixing before it is safe to move. See the requirements page and the glossary if any of the terms are unfamiliar.
Done-for-you onboarding is the part most people care about, and it is included rather than an upsell. When you bring a domain on board we map out every system that sends mail under it (your mail provider, marketing platform, helpdesk, invoicing tools and so on), generate the correct DMARC, SPF, DKIM and MTA-STS records, and either delegate DNS so we manage the records for you or hand you exact values to paste in if you would rather keep DNS in house. From there we monitor the incoming reports and email you when something needs attention: a new sending source appears, an existing one starts failing alignment, or your data shows it is finally safe to step the policy up. You are never left staring at raw XML wondering what to do next.
If you want to understand the moving parts before raising a ticket, the docs cover setup and DNS delegation, the knowledge base answers common how-to questions, and the blog goes deeper on alignment, reporting and policy strategy. For anything not covered there, open a ticket and a real person who understands DMARC will pick it up.