Contact Us
Questions, suggestions, or corrections? We'd love to hear from you.
Email Us
The best way to reach us is via email. We read every message and respond to most within 48 hours.
hello@saasautomationtools.comWhat You Can Contact Us About
Tool Suggestions
Know of an automation tool we should review? We're always looking to expand our coverage. Let us know what you'd like to see analyzed.
Corrections & Updates
Found an error in our content? Pricing changed? Features added or removed? Help us keep our reviews accurate and up-to-date.
Questions About Tools
Trying to decide between automation tools? Confused about which solution fits your use case? We're happy to provide personalized guidance based on your specific needs.
Partnership Inquiries
We maintain editorial independence and don't accept paid placements or affiliate arrangements. We're open to providing honest feedback to tool makers looking to improve their products.
Media & Press
For media inquiries or interview requests, please reach out via email with details about your publication and topic.
What We Can Help With
To make our replies useful, tell us the four details below. The more specific your context, the more actionable our answer.
| Detail | Example |
|---|---|
| Your business model | "B2B SaaS with Stripe subscriptions, no sales team" |
| The workflow you want to automate | "Trial users who ignore the setup checklist" |
| Your current stack | "Sequenzy + HubSpot CRM + Zapier" |
| What you've already tried | "Manual sequences; a failed dunning via webhooks" |
When to Expect a Slower Reply
Some messages need more context than a quick reply can offer, so here's how to help us help you faster:
| Situation | What slows us down | How to speed us up |
|---|---|---|
| Feature claim correction | We must verify against vendor docs | Link the exact doc or pricing page you checked |
| Pricing correction | Frequent vendor repricing requires re-validation | Screenshot or quote the current official pricing page |
| Fit advice request | Vague context yields vague answers | Describe business model, team size, and current stack |
| Vendor disputes | We need primary sources | Provide written vendor statements or documentation links |
What We Typically Cannot Do
| Request | What we do instead |
|---|---|
| Quote live vendor pricing | Point you to the official pricing page with hedging context |
| Guarantee or broker deals | Provide fit guidance only; purchase decisions remain yours |
| Expedite vendor support issues | Suggest escalation paths through the vendor's own support |
| Advise on regulated-data compliance | Recommend qualified legal counsel |
Questions by Category
Pricing questions
We don't quote vendor prices — we hedge them and point to official pricing pages, because tier contents shift too fast for any editorial snapshot to be reliable. If you've spotted a specific discrepancy on one of our pages, send the correction; it's the fastest way to help the readers who come after you.
Suitability questions
We answer fit questions with honest brevity: the tool class that fits your model, the comparisons that apply, and what a bounded pilot should test. We don't run implementations for readers, and we say so when a question falls outside our tested experience.
Common Questions About Contacting Us
Do you sell tools or earn commissions?
No. We have no affiliate relationships, no paid placements, and we don't operate any of the tools we review. When we recommend a tool, we receive nothing from the vendor — editorial independence is the entire point of the site.
Can you help me pick between two specific tools?
Yes — describe the two tools, your business model, and the workflow you want to run. We'll point you to the relevant comparison page if one exists, and give an honest fit opinion from context. For final decisions, we always advocate a bounded pilot of both finalists plus checking each vendor's official pricing page, since prices change faster than any editorial site can track.
How do corrections work?
Point us to the page, quote the claim you believe is wrong, and include your source if you have one (vendor docs are best). We verify against the vendor's official documentation before editing, and we annotate the change when it affects a recommendation.
How quickly do you respond?
Most messages get a reply within 48 hours on business days. Corrections to factual errors jump the queue, because inaccurate content is worse than delayed content.
Contact turnaround commitments
| Request type | Target response | Notes |
|---|---|---|
| Corrections | 48 business hours | Highest priority; verified against vendor docs |
| Tool suggestions | Within a week | Evaluated against the site's framework |
| Fit guidance | 48-72 business hours | Answered with fit framing and caveats |
| Media and press | 48 business hours | Include publication and topic |
Looking for specific tool comparisons? Check our comparison pages, browse the category guides, or see our latest articles before writing in — your question may already be answered.