Best for support, privacy requests, and general inquiries. Prefer not to email? Start from the how-to guides or the blog.
What to include
Clear reports help us reproduce issues without accounts or server logs. Include the tool name, the steps you took, what you expected, and what happened instead. For layout bugs, note the browser and device. For email questions, a minimal sample is enough — strip secrets, tokens, and personal data before you send.
What we can and cannot help with
We can clarify how a Tools Viewer feature works, track down a reproducible bug, answer privacy questions, and point you to the right guide or blog post. We cannot provide custom agency email development, recover local drafts from our servers, or guarantee native inbox rendering beyond what the free browser simulations show. We also cannot debug proprietary ESP setups that we cannot access.
Response time
We aim to reply within a few business days. Privacy-related requests are prioritized. Tools Viewer does not require an account, so include enough detail for us to reproduce the problem without login access. If your message is about an upcoming tool listed as coming soon, tell us which product you are waiting for — product feedback is welcome even before launch.
Contact FAQ
What can I contact ToolsViewer about?
Support for live tools, privacy requests, feedback, licensing questions, and bug reports. We also welcome ideas for upcoming tools.
Do I need an account to get help?
No. ToolsViewer does not require signup. Include the tool name, steps to reproduce, and browser details so we can investigate without login access.
How fast do you reply?
We aim to reply within a few business days. Privacy-related requests are prioritized.
Can you recover my draft from your servers?
No. Core editing stays in your browser. We cannot retrieve local drafts. Export or copy work you need to keep.
Send a message
Prefer email? Use the address above. Or send a short note here and we’ll reply to the address you provide.