How we check prices and features

Last full re-check: 28 October 2026

Collect. We save the vendor’s homepage and pricing page as text on the check date. If a pricing page only renders in a browser, we read the structured data the vendor publishes instead and note it.
Extract with receipts. Prices, billing units, plan allowances, integrations and compliance claims are extracted together with the exact sentence they came from.
Match the quote. Software confirms each quoted sentence actually appears in the saved page. Quotes that don’t match are re-read by hand.
Second check. A separate classifier asks, claim by claim, whether the saved page supports it. Anything it rates as unsupported — a channel, an industry, an integration — is removed unless we can find it on the vendor’s page. On the launch dataset it reviewed 1,142 claims and we removed 22.
Model the bill. For vendors with published allowances and overage rates, we compute the cheapest plan at 100, 300, 600 and 1,000 calls (3-minute average). Every assumption is printed next to the number.
Test calls. Phone products get the same 12-call script, published on the profile’s test-call log. Until a product has been tested, the log says so.
Re-check. Prices are re-checked at least monthly and whenever a vendor or reader reports a change.

What we never do

Invent a price, guess an integration, or describe a test we haven’t run. When a vendor publishes no price, the page says “quote only”.

Spotted something out of date? Tell the editor; corrections are dated on the page.