How TradeCall Lab Tests AI Receptionists
TradeCall Lab exists to separate what vendors publish from what the software actually does. Every commercial page carries a test-status label so readers can tell the difference between documentation research and hands-on observation.
Evidence levels
- Vendor-verified: pricing, plan limits, integrations or features confirmed on a current official page.
- Cross-checked: compared against at least one independent or competing source to identify discrepancies worth testing.
- Controlled-call verified (future evidence category): configured under a TradeCall Lab test business and subjected to the standard call battery.
- Retested: a hands-on test repeated after a meaningful product or pricing change.
No pay-to-rank rule
Affiliate commission, sponsorship availability and vendor advertising are excluded from evaluation criteria. If we earn from a link, that relationship is disclosed near the commercial content and in the sitewide disclosure.
Scoring dimensions used after hands-on testing
- Intake accuracy
- Emergency and safety behavior
- Handoff reliability
- Scheduling clarity
- Integration data quality
- Setup time and maintainability
- Pricing predictability
- Transcript/recording auditability
Corrections
Vendors and readers can submit a correction with a primary source. Material changes are dated. We preserve the distinction between “vendor says” and “we observed.”
Sources and verification
- OnCrew pricing
- The Snow Media: 13 AI receptionist options compared
- Stork.AI home-service AI receptionist guide
Decision this guide addresses
What must be proven for evidence publication?
A workflow that exposes the problem
A successful vendor demo is described as an independent performance test.
Requirements to put in the buying brief
Keep vendor documentation, planned tests and completed observations in separate records. Publish call conditions, rubric, raw outcomes and limitations before assigning a performance rank.
Configuration details that matter
Keep a written record of scope, accountable staff, required fields and exception paths. Match the caller’s understanding of the next step with the actual operational status.
| Checkpoint | Evidence to request | Reject the pilot when |
|---|---|---|
| Before the call | Written scope for this exact workflow | Only a broad integration or feature label is offered |
| During the call | Accurate request and truthful next-step wording | The caller is given a promise the business cannot keep |
| After the call | Record status and a named owner for exceptions | The transcript exists but nobody can act on it |
Acceptance test before purchase
Until comparable calls are completed, label shortlist positions as workflow hypotheses. Re-run the same scenario after configuration changes and retain the previous outcome for context.
Costs beyond the advertised tier
Budget the subscription, the billing unit used by the vendor, connector fees, phone charges and staff time spent correcting exceptions. Illustrative example: a $120 monthly tool plus $30 connector and two staff hours at $25/hour costs $200 before any additional usage. A lower base price does not establish lower operating cost.
Decision rule
Use the evidence from your own pilot to choose the workflow. A missing required action is a purchase blocker even when the advertised price is attractive.
Frequently asked questions
What must be proven for evidence publication?
Keep vendor documentation, planned tests and completed observations in separate records. Publish call conditions, rubric, raw outcomes and limitations before assigning a performance rank.
What evidence is still missing?
TradeCall Lab has not completed controlled calls for this workflow. The acceptance test above is a proposed buyer test, not a measured vendor result.
How should a failed pilot be handled?
Pause the affected route, preserve the failure record and return calls to the existing staff or voicemail path. Resolve ownership and configuration before expanding coverage.
Phase 4 verification: official pricing for Rosie, HighLevel, Frontdesk, OnCrew, Smith.ai and Goodcall was retrieved on October 3, 2026. Dialzara’s official monthly fees, included minutes and per-minute overages were directly verified in Phase 4.1 on October 3, 2026. Other inherited integration and feature claims require an account-specific demonstration. View the source-status ledger.