Who writes this site
Every article is written and every test run by Charles Kwinda. There is no anonymous freelance pool and no syndicated content. If that changes, this page changes with it and each article will name its author.
How we choose what to cover
We cover customer support technology: helpdesk and ticketing, live chat, knowledge base and self-service, chatbots and AI support agents. We do not review CRMs, marketing suites, project management or general productivity tools, because covering everything is how a publication stops knowing anything.
Within that scope we prioritise the questions buyers are actually asking — which tool to replace an incumbent with, how two products compare at a real headcount, what something really costs. We do not publish a page simply because a vendor has an affiliate programme.
How rankings are decided
By the published weights on the how we test page, applied to measurements from the ten-step protocol. Nothing else.
Specifically, the following do not influence position, score or inclusion: commission rate, cookie length, whether a vendor has an affiliate programme at all, advertising spend, a vendor's willingness to provide a review account, or any relationship with a vendor's staff.
Intercom is the clearest test of this. It runs no affiliate programme we can join, so we earn nothing whatever we say about it. It still appears in our comparisons on merit, and we say on each page that it pays us nothing.
Commercial relationships
First Response Lab earns a commission when a reader buys certain software through our links. Full detail is on the affiliate disclosure page, which lists every vendor we have a commercial relationship with and the nature of it.
Three rules sit behind that:
- No pre-publication review. No vendor sees an article before it goes live. No vendor gets to correct, soften or approve a finding in advance.
- No paid placement. Position, badges, scores and inclusion are not for sale, in any form, including "sponsored comparison" formats.
- Nothing hidden. Where a vendor pays us, the page says so near the recommendation, not only in a footer.
We publish findings that cost us money. If the tool that pays us best is slow to set up or hard to cancel, that goes in the article.
Accuracy, sourcing and provenance
Every factual claim carries its provenance — tested, verified, vendor claim, or not verified. Pricing is read from the vendor's own pricing page and dated. We do not take commission rates, prices or product facts from affiliate directories or aggregators; during this site's research phase several of those were found to be materially wrong, including rates that had changed years earlier.
Where we cannot establish something, the page says "not verified". We would rather have a gap than a guess.
Corrections
If something here is wrong, we want to fix it, and we would rather hear it from you than leave it up.
Email the address on our contact page with the page and the specific claim. Material corrections are made at the top of the article with the date and what changed. We do not silently edit a factual error out of existence.
Vendors are welcome to submit corrections on the same basis as anyone else. A correction request is not an opportunity to revise our conclusions.
AI and how this content is made
Research, drafting and data work on this site are assisted by AI tools. Measurements are not. Every number in a test result comes from a human running the protocol with a stopwatch and taking the screenshots, and every published article is reviewed line by line by a person who takes responsibility for it.
We do not publish AI-generated product experience. If you read that we set something up and it took eleven minutes, someone sat there for eleven minutes.
Updates to this policy
This policy is versioned by its last-reviewed date above. Material changes will be noted here.