Marcus Reed
Senior editor, ChatbotRadar — I cover live chat and AI chatbot tools for small teams, and my name is on every guide we publish.
How I test
- Start from the vendor's own numbers. I read the pricing page, the plan comparison table and the documentation first, and record what they actually say today.
- Sign up and use it. Where a free plan or trial exists, I create an account, build a small test knowledge base, and fire real questions at the bot to see where it answers well and where it gives up.
- Write for owners, not engineers. Every review has to answer one question: does this tool fit this kind of business, and what does it really cost once you add seats and usage?
- Review pass before publishing. Each article is checked for spelling and grammar, factual consistency with our verified dataset, and tone — no marketing fluff, no hype words.
- Re-check on a schedule. Vendors change pricing and plan limits constantly, so the dataset is re-verified against vendor sites once a month and every page carries its last-verified date.
What I do — and do not — claim
- I do verify pricing, plan limits and feature lists against vendor documentation, and say so when a figure can't be confirmed.
- I do run hands-on trials on free plans and trials, and mark clearly when a conclusion comes from my own use of the product.
- I do not dress up hypothetical examples as case studies. When a guide describes a fictional business ("a bakery with 40 orders a week", say), it illustrates who the advice fits — it is not a customer and not a measured result.
- I do not accept payment for rankings. Vendors cannot buy a position in our comparisons, and some of the tools we recommend pay us nothing.
About this byline
ChatbotRadar is produced by a small independent team, and we publish under a single editorial identity so that every guide has one clearly accountable author. Marcus Reed is that identity — the person whose name goes on the review, who signs off on it before publication, and who answers when you write in. He is not affiliated with any vendor we cover.
Corrections
Spotted something wrong — a price that moved, a feature we described incorrectly, a tool that no longer behaves the way we said? Email [email protected] and it gets fixed, usually within 2–3 business days. Being accurate matters more to us than being first.
Last updated: see the date on each individual guide. Browse all guides