Skip to content
Chatbotscape

Chatbotscape Editorial Policy

This page documents the editorial values, voice, fact-verification standards, and anti-pattern policies that govern every Chatbotscape review, comparison, best-of list, and methodology page. It is meant to be auditable — if you read a Chatbotscape review and want to know what editorial rules produced it, this page is the canonical answer.

Editorial values

Independence. Chatbotscape's editorial decisions — what we cover, how we score, what we flag as a strength or a weakness — are made by the editorial team without vendor input, vendor pre-publication review, or commercial-relationship pressure. Affiliate program participation does not influence scoring or framing. Sponsored placement is not accepted. Vendor relationships do not grant any vendor a higher floor or a lower ceiling than any other vendor in the same category. The defense for editorial independence is structural — published methodology, scoring-before-commerce protocol, audit-on-request access — not promised. See /methodology#monetization for the full mechanism.

Transparency. Every editorial decision that could materially affect a reader's purchase decision is documented and verifiable. Scoring rubric, weight clusters, refresh cadences, data sources, conflicts of interest, affiliate relationships, methodology versions — all of it is published. Where editorial decisions involve tradeoffs (for example, how literally we interpret hands-on testing claims vs. structured editorial inference), the tradeoff is documented either in the publishable review or in the per-review internal POC notes that the editorial review process can surface during audit.

Accountability. When we are wrong, we own it collectively. Corrections are made transparently, with dated changelog entries and visible refresh dates. We do not silently amend published content; every material correction is timestamped and described. The editorial-team byline is institutional — "Chatbotscape Editorial" — because the quality bar and the responsibility for findings sit with the process, not with an individual author. If you believe we have a factual error, write to editorial@chatbotscape.com and we will investigate within 7 days.

Reader-first framing. Reviews are written for the SMB owner making a purchase decision. We do not write for vendors hoping to be ranked favorably, for journalists looking for a quotable hot take, or for SEO bots looking for keyword density. When editorial decisions trade off between "more thorough" and "more readable for the SMB buyer", we err toward readable — depth lives in linked methodology pages and per-review POC notes.

Voice and persona

Voice 1 — editorial team. First-person plural for observations and measurements we made directly. "We tested", "we measured", "we verified". This voice carries the burden of accuracy — every claim under this voice has a primary source recorded in either the publishable review's "How we verified this review" section or the review's POC notes sibling file.

Voice 2 — market expert. Third-person framing for interpretation of what observations mean for the SMB buyer market. "Most SMB buyers in this category report", "In our category dataset", "Comparable platforms in this price range typically". This voice carries the burden of relevance — every interpretation under this voice should help a real SMB owner make a real decision.

Persona — the SMB owner with a deadline. The reader we write for is a 1-100 employee SMB owner, operator, or marketer who is evaluating chatbot platforms for their own business. She has a budget, a deadline, limited technical staff, and limited patience for vendor marketing. She wants to know: which platform should I pick, why, what does it cost, what are the risks, and where would I be wrong about my own decision.

Anti-personas we do NOT write for. Enterprise procurement teams (use Gartner Magic Quadrant). Journalists looking for industry-trend quotes (we publish data, not hot takes). SEO bots looking for keyword density (we write for humans). Vendor sales teams trying to demonstrate parity with competitor positioning (we publish independent findings; we do not republish marketing).

Fact-verification standards

Every factual claim in a Chatbotscape review must trace to a primary source verified within 90 days of publication. Primary sources, in order of priority:

  1. Vendor's current public pages — pricing page, product/features pages, channel/integration pages, help center, security/compliance pages, partner directory listings. Vendor pages are the canonical source for pricing claims, feature claims, channel availability, integration partners, and certification claims. Vendor pages are NOT canonical for vendor self-reputation claims (which we cross-check against third-party sources).
  2. Third-party aggregator pages — G2, Capterra, TrustPilot for user-voice claims (review counts, star ratings, sub-rating breakdowns, recurring strengths and weaknesses). Aggregator pages are canonical for "what do users say" claims; they are NOT canonical for vendor-marketing claims.
  3. Ahrefs API — multi-locale brand search volume across 10 target countries (US, Brazil, Mexico, Spain, Argentina, Colombia, India, United Kingdom, Germany, France). Ahrefs is canonical for platform popularity signal.
  4. Partner directories — Meta Business Partner Directory for BSP status, Google Partner / Cloud directories, AWS Partner Network, HubSpot Solutions Directory. Partner directories are canonical for partnership claims; vendor self-claims are NOT sufficient.
  5. Crunchbase / PitchBook / vendor press releases — for funding totals, vendor stability claims, and corporate-relationship facts.
  6. Hands-on testing observations — measurements we made directly during the six-scenario testing protocol. These are first-party observations, distinct from vendor or third-party claims.

What is NOT a valid source. Training data, memory, "I recall reading", unverified Wikipedia, vendor sales rep claims, third-party reviews that don't cite a primary source, marketing-team press release summaries that don't link to original press releases. The phrase "typical for vendors in this category" is a heuristic, not a fact, and is flagged as such when used.

Anti-pattern policies

The following editorial behaviors are NOT acceptable in any Chatbotscape review or content:

No unverified claims. Every claim in a publishable review must trace to a primary source. When a claim cannot be verified, it is either removed from the review or explicitly labeled as unverified with the methodology that produced it (for example, "estimated from category patterns" rather than presented as data).

No claim inflation. Specific counts (review aggregator counts, template counts, language counts) are particularly prone to training-data inflation. Every numerical claim of this type is independently verified before publication. Common failure modes — claiming G2 has 7,800 reviews when actual is 163, claiming 350+ templates when actual is 60, claiming 7 UI languages when actual is 3 — are blocked by the Feature-Claims Verification Checklist (see /methodology/review-standards).

No selective excerpting from aggregator reviews. When summarizing user-voice patterns from G2, Capterra, or TrustPilot, we report the dominant signal across at least the last 6 months of reviews, not the most flattering or most damning excerpts. Selective excerpting that manufactures sentiment that doesn't reflect the actual review distribution is editorial fraud.

No misleading comparisons. Cross-platform comparisons use the same methodology applied consistently — same pricing methodology (cheapest paid tier, monthly-billed), same testing protocol (six scenarios), same scoring rubric (17 dimensions). We do not compare platforms across different category boundaries unless the comparison is explicitly cross-category (and disclosed as such). We do not use comparison framing to manufacture buyer pressure ("unless you switch to X, you're losing") absent specific evidence.

No pre-publication vendor review. Vendors do not have right of pre-publication review, right of removal for findings they disagree with, or right of approval over scoring. Vendors have the right to submit factual corrections (with supporting evidence) post-publication and the right to request that specific factual claims be re-verified. Re-verification outcomes are documented in version history regardless of whether we ultimately agree with the vendor's position.

No silent amendment. Material corrections to published content are timestamped and described in version history. The first version of a review remains accessible through changelog references. We do not silently edit published reviews to match new vendor positioning.

Editorial production process

Every Tier 1 platform review follows this sequence:

  1. Keyword and market positioning research. Multi-locale brand search volume verified through Ahrefs API across the 10 target countries. Tier assignment is set based on aggregate brand vol, with new-platform exemption for vendors less than 2 years post-launch.
  2. Vendor source verification. Pricing, channels, features, integrations, founder names, funding totals, and certification claims captured directly from the vendor's current public pages. Monthly-billed pricing toggle activated to capture true monthly rates; URL parameter testing applied for multi-region currency capture.
  3. Hands-on testing. Six-scenario protocol executed on a paid-tier account: basic FAQ bot (Scenario A), lead capture with Sheets sync (B), commerce flow with WhatsApp Business API (C), AI knowledge base across multiple languages (D), human handover and multi-user inbox (E), analytics and ad-conversion tracking (F).
  4. Third-party aggregator scan. G2, Capterra, TrustPilot reviews from the last 6 months read in full; recurring strengths and weaknesses patterns extracted. Where aggregator scores and editorial findings diverge, the divergence is discussed openly in the review.
  5. Feature-claims audit. Every feature claim in the draft mapped against the six high-risk categories (specific counts, proper nouns, status/tier claims, existence claims, pricing details, aggregate scores). Unverified claims removed or labeled.
  6. Pre-publish audit. Cross-check pass against the review hygiene standard (see /methodology/review-standards). Manychat-anchor parity table populated in the review's POC notes sibling file.

Conflicts of interest

When a Chatbotscape editorial team member has a material financial relationship with a vendor — current employment or contractor status, equity holding above nominal threshold, advisory role, board position, or immediate family member as senior employee — the team member is recused from that vendor's review entirely. Less-material connections (prior employment more than 24 months ago, shared surname or name overlap that a reader could perceive as a connection) are disclosed in the publishable review body in a callout near the top, not only in internal notes.

Recusal and disclosure decisions are documented in the review's POC notes sibling file. When asked by a reader or vendor whether a specific review involved any disclosed connection, the editorial review process surfaces the disclosure status within the 7-day audit response window.

Corrections and reader recourse

Factual corrections. Submit via editorial@chatbotscape.com or the contact form at /contact. We respond within reasonable time as the editorial team scales — typically 7-14 business days for substantive review; significant corrections (factual errors that could influence buyer decisions) trigger an interim refresh published within reasonable time as the editorial team scales — typically 7-14 business days for substantive review of confirmation. Routine corrections (typos, link fixes, formatting) are batched into the next quarterly refresh.

Methodology disagreements. Readers who disagree with weight allocations, scenario selection, or any methodology decision can submit feedback through the same contact form. Methodology feedback is reviewed at each quarterly refresh cycle by the editorial review process.

Editorial-bias audit requests. Readers who suspect undisclosed commercial bias in any review can request a methodology audit. Audit outcomes are published as version-history entries on the affected review, with disclosure of what was reviewed and what changed. We do not retaliate against readers who request audits.

Version history

  • 2026-05-26 (v1.0) — Initial publication aligned to methodology v3.12.1. Editorial policy formalized after Manychat anchor review iteration cycle revealed the need for explicit anti-pattern documentation (claim inflation, selective excerpting, silent amendment).