Editorial Standards & AI Disclosure

How BossBot publishes: the workflow behind every post on bossbot.uk, our AI-assist policy, fact-checking standards, corrections process, and who to hold accountable when we get something wrong.

1 · Who we are

BossBot is a WhatsApp AI receptionist for small businesses. We publish practical guides for small business owners about WhatsApp Business API, customer conversations, pricing across the SaaS landscape, and the day-to-day realities of running a service business — plumbing, dental, salon, restaurant, coaching, tutoring.

The blog operates two byline tracks:

• Kseniia Petruk (Founder) — bylines English, Russian, and Ukrainian posts personally. Original research, product-decision essays, personal experience running a bootstrapped SaaS business. Read her full bio at /authors/ksenia-petruk.
• BossBot Editorial Team — collective byline for localized market guides (Portuguese, Spanish, Turkish, Indonesian, Arabic, and more). Every post under this byline is edited under Kseniia's direction and reviewed against the standards below. Read how the team works at /authors/bossbot-editorial.

2 · How we use AI in drafting

We disclose this openly because Google's 2026 Publisher Policies and our own principles both require it: every localized market guide on this site is drafted with AI assistance. Specifically:

• A structured content brief is written by our editorial workflow (topic, target reader, key questions, tone).
• A large language model (Google Gemini 2.5 Flash, as of publication) produces a first draft against the brief.
• A humanization pass rewrites AI-signature phrasing, restores natural rhythm, breaks up templated structures, and corrects article agreement.
• A meaning-quality gate scores the draft against our threshold — 78 minimum on our internal scale. Below the gate, the post is either sent back for revision or held from publication.
• A human editor at BossBot reviews the final draft before publication, cross-checks any factual claims that carry a specific number, price, or vendor detail, and adds source citations.

3 · Where AI is not used

• Personal essays (voice_persona: ksenia_personal in our JSON) — Kseniia's first-person Odessa-anchored writing about founder life, market experience, and business philosophy. These are written by hand. AI polish is limited to typo correction.
• Editorial notes and disclosures at the top of pricing-review and comparison posts — the first-person Kseniia block ("Editor's note: I run BossBot, a competitor to X…") is written by hand, one post at a time, and expresses her personal opinion about the specific competitor covered.
• Source verification — every source URL is opened and checked by a human before the post publishes. AI does not select or verify sources.
• Correction decisions — when we get a fact wrong (see §6 below), the decision on how to correct is made by a human, not by AI.

4 · Sources policy

Pricing review posts and competitor-comparison posts cite primary sources whenever possible:

• Vendor pricing pages (linked with the date they were checked, so drift is auditable).
• Public review databases (G2, Capterra) with reviewer-window context.
• Independent pricing benchmarks (Vendr, SpendHound, Gartner) when they cover the vendor.
• Vendor documentation (Meta WhatsApp Business Platform, Google, AWS) for API pricing that mirrors public rate cards.
• Investor relations reports for publicly-traded vendors (Freshworks, HubSpot, Shopify) when a claim depends on financial context.

We do not cite: AI-generated summaries of vendor pricing, unnamed "industry analysts," or affiliate links dressed up as sources. If a citation is not a real link we can verify, it does not go in.

5 · Conflict of interest disclosure

BossBot is a WhatsApp AI receptionist. Many of the platforms we cover in our pricing-review series are direct or adjacent competitors. Every such post carries a first-person editorial note at the top disclosing:

• That we compete with the vendor being reviewed.
• What the vendor does well — with specifics (G2 score, feature strength, target audience where they excel).
• The pricing point where the vendor becomes expensive for small-business use.
• Where the vendor is genuinely the right answer over BossBot — naming the specific segment, not hand-waving.

Our position is that competitor coverage is fair when we can honestly recommend the competitor for the segment they serve better, and that a competitor-review site that only ever recommends its own product is not credible.

6 · Corrections policy

When we publish a factual mistake, the process is:

1. Confirm the mistake against the primary source. If a vendor changed their pricing page, we update our post to match and note the change.
2. Update the post text with the correct fact.
3. Add a Corrections block at the bottom of the post noting: (a) what the mistake was, (b) when we corrected it, (c) how the reader should read the article now.
4. Update the _last_refreshed timestamp on the post so aggregators know the content was reviewed.
5. If the mistake was material (misstated a competitor's price by 20%+, misattributed a feature to the wrong vendor, cited a source that does not support the claim), the post carries a note at the top pointing to the Corrections block for the first 30 days after correction.

To report a factual issue, email [email protected] with the URL and the specific claim. Kseniia reads that inbox personally. We aim to respond within 3 business days.

7 · Fact-check standards

Not every claim needs the same rigor. Our internal tiering:

Tier A — vendor pricing, feature attribution, financial claims

Every price, every feature list, every claim about a specific vendor's roadmap or public statement must be verifiable against a source we can link. If the source disappears or changes, we update the post.

Tier B — market statistics, adoption rates, industry benchmarks

Cited to a public source (Statista, eMarketer, Gartner, Meta official blog, Google Trends) or omitted. Rule of thumb: if we can't find a source in 5 minutes, the number does not go in.

Tier C — editorial opinion, positioning, recommendations

Marked as opinion in the text ("I think," "in my experience," "our view is") and grounded in the editorial-note conflict-of-interest disclosure at the top of the post.

8 · Advertising, affiliate, and monetization disclosure

BossBot's primary revenue is from paid subscriptions to our SaaS product (see /pricing). We also participate in:

• Google AdSense — Google-served display advertising. Ads on this site are targeted based on Google's contextual signals, not on our editorial content. We do not control what specific ads Google shows. Ad placements are marked with the standard Sponsored label per FTC guidance.
• Affiliate partnerships — where we link to a product we recommend and receive a commission when readers subscribe, the link is marked with rel="sponsored nofollow" and the post includes an affiliate disclosure at the top of the recommendation block. See our Affiliate Disclosure page for the current partner list.

Affiliate commissions do not influence editorial coverage. A vendor whose product is not the right answer for a reader will not receive a positive recommendation because we happen to have an affiliate partnership with them.

9 · Accessibility & localization

We publish market guides in the reader's language, not translated word-for-word from English. Our localized content covers 15 markets (Brazil, Mexico, India, Indonesia, Nigeria, Philippines, South Africa, Turkey, US, UK, Canada, Australia, Singapore, France, Poland as of 2026-07). Each localized post is:

• Written to reflect the local reader's actual situation — local payment methods, local tax context, local currency, local regulatory constraints.
• Reviewed against the voice profile of the target locale (formality register, colloquial vs. professional tone).
• Marked with correct hreflang attributes so search engines route readers to the version in their language.

10 · How to contact us

• Editorial questions, corrections, factual issues — [email protected]
• Press or media requests — [email protected]
• Product support — /support
• Sales — /contact-sales