Skip to main content

Contact SaaSSoftwareReviews, Tell Me What Actually Happened (Not Just What Was Promised)

 





Most SaaS reviews read well because nothing went wrong.

This site exists for the opposite reason.

If you’ve used a tool and something didn’t behave the way it was supposed to—support went quiet, a feature broke under real use, or billing didn’t match expectations—that’s the kind of detail I take seriously.

SaaSSoftwareReviews is built around what happens after signup, not just what a product page claims. And a good number of updates here have come directly from reader emails pointing out things I didn’t catch on the first test.


 How to Reach Me

Email: sandraroberts507@gmail.com

I handle every message myself.

Typical reply time is 1–3 days.
If it takes longer, it usually means I’m in the middle of testing a tool or working through a backlog—but I do come back to every message.

Last month, a reader flagged a billing issue in one of the tools I reviewed. I went back, retested it, and updated the article the same week. That’s generally how things work here.


 What You Can Reach Out About

1. Something in a review doesn’t match your experience
Send it through. If there’s a gap, outdated detail, or context missing, I’ll verify it and update the page.


2. You ran into a real problem using a tool
Some of the most useful insights don’t show up until:

  • a workflow breaks halfway through
  • support responses slow down after the first reply
  • cancellation or refunds take longer than expected

If that’s happened to you, it’s worth documenting.


3. You want a tool tested before you commit
If you’re considering a SaaS product, tell me what matters to you:

  • reliability over time
  • support quality when something goes wrong
  • whether the tool holds up under actual use

I don’t review everything, but I focus on tools people are actively deciding on.


4. You represent a SaaS company
You’re welcome to reach out—but a quick note upfront:

  • I don’t accept paid reviews
  • I don’t offer sponsored rankings
  • I don’t publish pre-written content

If I test your product, I publish what I find—good or bad.

If there’s an affiliate relationship, it’s disclosed clearly. It doesn’t affect how the review is written.


 How This Site Stays Independent

Some links on this site are affiliate links.

If you use them, I may earn a commission—at no extra cost to you.

That said:

  • Tools are tested before they’re recommended
  • Weak performance is not softened or edited out
  • No company can pay to improve their position

If something doesn’t hold up during testing, it doesn’t get recommended.


 Privacy

Anything you send—email, feedback, or experience—is used only to respond or improve the content on this site.

No selling data. No sharing personal details.


A Quick Note

Most review sites help you choose tools.

This one also tries to help you avoid the wrong ones—especially the ones that look good until you actually rely on them.

If you’ve seen something that didn’t match expectations, your message genuinely helps make these reviews more accurate for the next person.


— Sandra Roberts 
Founder, SaaSSoftwareReviews
I test SaaS tools the way they’re actually used—over time, under pressure, and sometimes when they fail


Page last updated: July 10, 2025




Comments

Best SaS Tools

I Tested Free vs Paid SaaS Support Tools — What Actually Changed (After 527 Real Tickets)

  Disclosure: Some of the links in this post are affiliate links, meaning I may earn a small commission if you decide to use them (at no extra cost to you). I only recommend tools I’ve personally used to solve real-world customer support challenges, not because I was paid to promote them. Introduction: Why I Didn’t Upgrade Just for Features I didn’t upgrade to a paid support tool because I wanted fancy features. I upgraded because small issues kept happening that I couldn’t ignore anymore. At the time, I was handling 40–70 customer messages per day — mostly email with some live chat mixed in. At first, this felt manageable. But as things grew, I started realizing the issue wasn’t volume. It was consistency . A reply I thought I sent (but didn’t). A customer following up… twice. Rewriting the same answer over and over again. These small issues didn’t seem critical at first, but when they stacked up, I could feel the friction slowing down my entire workflow. The Moment ...