Public log
Corrections log
Current through Jun 12, 2026
Every correction across our section datasets is recorded here: section, what changed, why, and who requested it. The log is append-only — entries are never edited away. Corrections are free for everyone, always, and verified errors are fixed within five business days.
6 entries, newest first. Each links its change to a section, scope and the party that requested it.
-
Call Tracking — Dialics — Pay As You Go. Recorded base as $0 (pure pay-as-you-go) per the live pricing page. A ~$99/mo entry figure in some third-party directories was deliberately not published because it does not appear on the vendor page. Requested by: Internal review
-
Call Tracking — CallRail / WhatConverts / WildJar / Convirza. Platform-wide per-minute usage rates recorded once on the relevant tier with a caveat, not copied across every plan, to avoid presenting a falsely uniform overage column. Requested by: Internal review
-
Call Tracking — Retreaver. Recorded as quote-only after its pricing page returned HTTP 404 at capture time. No per-plan figure was recorded rather than a guessed one. Requested by: Internal review
-
AI Receptionists — Trillet — Studio plan. Updated price/quota from a prior seed of $49 / 150 min to the live pricing page value of $99 / 100 min. The page value supersedes the seed. Requested by: Internal re-verification
-
AI Receptionists — AIRA & Upfirst. Flagged that the two vendors publish byte-identical pricing tables and appear to share a pricing engine. Both are recorded independently with their own sources; no row was merged or removed. Requested by: Internal review
-
AI Receptionists — AnswerConnect. Recorded as quote-only after its pricing page returned HTTP 404 at capture time. A third-party figure of ~$325/mo was deliberately not published because it could not be verified against a live vendor page. Requested by: Internal review
An append-only, SHA-256 hash-chained audit log underlies the dataset: each dated entry commits to the entire published dataset and to the previous entry's head, so any later edit to past data is detectable. See each section's methodology for how changes are verified before they are published.