About CallBotScore & methodology

CallBotScore compares AI receptionists for trade businesses: plumbers, HVAC, electricians, roofers. We publish what vendors publish, link to it, date it, and say plainly when something isn't published.

Independence

No vendor pays to change what we publish about it. Some links may earn us a commission (see the disclosure), and vendors can pay for clearly labelled featured placement (see Get listed). Neither changes a figure, a badge, the table order or, once we publish them, a score.

How the data is collected

We read each vendor's public pricing page and feature pages by hand and record plans, included usage, overage, trials and booking claims.
Every figure links to the page it came from and shows the date we checked it. The current data set was last reviewed 2026-10-16.
We don't round, estimate or fill gaps. If a vendor doesn't publish a price we show Not published; if we couldn't confirm something we show Unknown.
When a vendor's own pages disagree, we say so in a data note on that vendor's page.
A script re-fetches each pricing page and flags changed text or dollar amounts, so we know when to re-check by hand.

Integration status definitions

Integration badges

Native Vendor's own page (or the software's marketplace listing) says it books or syncs directly.
Via Zapier Only through a Zapier connector. Usually creates a contact, not a booking.
Vendor claim Vendor marketing claims it; we couldn't confirm the details.
No Doesn't work with it (e.g. a product built only for another platform).
Unknown Nothing published that we could find. It may exist; ask the vendor.

Underlined badges link to their source.

We only care about integrations that matter to a trade shop: ServiceTitan, Jobber, Housecall Pro and Google Calendar. "Native" requires a page from the vendor (or the software maker's marketplace) saying it books or syncs directly. A general "works with Zapier" claim isn't counted as native.

How we will score (coming, not live)

No scores are shown in v1. Scores and test-call results are coming. The planned CallBotScore criteria:

Booking depth: does it take a message, send a link, or put a real job on the schedule?
Field-service integrations: native connections to ServiceTitan, Jobber, Housecall Pro and calendars.
Pricing transparency: are prices, included usage and overage published?
Overage risk: what happens to your bill in a busy month?
Trades fit: is it built for home-service calls (emergencies, addresses, job types)?
Test-call quality: how it handles real trade scenarios on our test calls.

We'll publish the weighting and the test-call scripts before any score goes live.

Corrections

Spot something wrong or out of date? Email [email protected] TODO: placeholder address with the page and a link to the source. Vendors are welcome to send corrections too; we'll update the figure and its checked date once we can see it on a public page.