Editorial

Comparison Methodology

Last updated: 2 July 2026

1. What this covers

This page explains how RichAutomate builds its WhatsApp Business Solution Provider (BSP) comparisons — the “X vs Y” pages, “alternatives to X” pages, “best for” roundups, and pricing decode articles published on this site. The goal of every comparison is the same: let an Indian business operator estimate their real monthly cost and feature fit on each platform before signing up.

2. Comparison criteria

Every platform in a comparison is assessed on the same dimensions:

  • Total pricing, including Meta pass-through. WhatsApp conversation charges are set by Meta and apply on every BSP. We separate what Meta charges (identical everywhere) from what the platform charges on top, so readers compare the part that actually differs.
  • Platform fees. Monthly subscription tiers, setup or onboarding fees, minimum commitments, and mandatory annual billing — the fixed costs a business pays regardless of message volume.
  • Markup policy. Whether the platform passes Meta’s conversation rates through at cost or adds a per-message/per-conversation markup, and how transparently that markup is disclosed on the vendor’s pricing page.
  • Features. The capabilities that drive day-to-day value: shared team inbox, campaign broadcasting, chatbot/flow builders, template management, catalog and commerce support, integrations, APIs, and analytics — as documented publicly by the vendor.
  • Support and onboarding. Documented support channels and tiers, onboarding assistance, and whether adequate support is gated behind higher plans.

Where a comparison targets a specific segment (for example, a clinic, D2C brand, or logistics operator), we weight the criteria that matter most to that segment and say so in the article.

3. Data sources

  • Public pricing pages. Each vendor’s own published pricing page is the primary source for fees, tiers, and markup figures.
  • Official documentation. Feature claims come from the vendor’s public documentation, help centre, and product pages — not from reviews or forum posts.
  • Meta’s published rate card. WhatsApp conversation pricing for India comes from Meta’s official rate card, which is the same for every BSP.
  • Point-in-time capture. Figures reflect the source pages as of the article’s stated date. If a vendor shows pricing only on request, or pricing varies by negotiation, we state that instead of guessing.

4. Scoring approach

  • Scenario-based cost modelling. Rather than abstract scores, most comparisons model concrete monthly scenarios (for example, a given number of marketing and utility conversations) and compute the total cost on each platform from published figures. The assumptions are stated in the article so readers can re-run the maths for their own volumes.
  • Like-for-like plans. Costs are compared on the closest equivalent plan tier for the stated use case, not a vendor’s cheapest plan against another’s premium plan.
  • Documented features only. A feature counts if the vendor documents it publicly. Roadmap promises and sales-call claims do not count.
  • Stated verdicts. When an article names a “better for X” winner, the verdict follows from the criteria and figures shown on the page — readers can check the working, and verdicts sometimes favour competitors.

RichAutomate appears in many of these comparisons. The same evidence rules apply to us: our own pricing and features are cited from our published pages, and our independence commitments are documented in the Editorial Policy.

5. Update cadence

  • Pricing figures in comparison and cost-guide pages are re-verified against the source pages on a recurring schedule, and additionally whenever we learn of a vendor pricing change or a Meta rate-card revision.
  • Material updates (changed prices, added/removed features, changed verdicts) refresh the page’s modification date.
  • Comparisons that can no longer be verified — for example, a vendor removes public pricing — are rewritten to reflect the reduced certainty rather than left stale.

6. Reporting an error

If any figure or feature claim in a comparison is out of date or wrong, email [email protected] with the page URL and a link to the correct source. Confirmed errors are corrected under the process in our Editorial Policy.