Comparison
Holdfast vs Smith.ai

Outcome-priced vs per-call. Four axes that decide which one actually books the after-hours call.

Smith.ai is a live AI-receptionist product targeting solo and small practitioners. Holdfast is an outcome-priced missed-call-recovery layer that writes to the same dispatch board. The comparison below grounds each axis in the same page it appears on elsewhere on this site.

Side by side

Four axes, side by side.

Outcome-pricing vs per-minute / per-call, AI voice vs human receptionist, scheduling-integration depth, and 24/7 coverage — the four places where the two products diverge. Holdfast’s column leans on the pricing page, the audit-request scheduler dropdown, and the per-shop ROI math.

Outcome-pricing vs per-minute / per-call

Holdfast

Outcome-priced, on the booking.

A small monthly retainer plus a per-booked-job bonus aligned to the invoice the booking actually generated. The bonus is never billed unless a confirmed slot lands on the tech’s calendar — same math as the pricing worked example.

  • Bonus is invoiced one week in arrears, after you see the recovery
  • No booking, no bonus — the calendar drives the bill, not the meter
  • Retainer is refundable against the first booked invoice during pilot

Smith.ai

Per-call, billed by the call.

Smith.ai is publicly listed as a live AI-receptionist product priced on a per-call basis — each after-hours call the agent picks up is a line item, win or miss. A per-minute partner fallback in the same category would price by talk-time; either way the meter sits between the recovery and the booked revenue.

  • Per-call line item regardless of whether the call converts
  • Long calls (the ones most likely to convert) cost the most
  • ROI depends on call volume and call duration, not on booked jobs
AI voice vs human receptionist

Holdfast

AI voice that books on the call.

The voice agent books the slot on the same call and writes it straight to the dispatch board the shop already runs. There is no human handoff — the booking path is one continuous AI flow, and the tech receives a confirmed slot on a calendar they already live in.

  • No live receptionist handoff — booking closes on the same call
  • Job lands on ServiceTitan / Housecall Pro / Jobber, not in an inbox
  • Caller and shop both see the same confirmed slot, with no morning follow-up gap

Smith.ai

Sounds human, but only takes a message.

Smith.ai’s AI voice is tuned to sound like a live receptionist — the caller hears a human-sounding agent, then the call ends with an SMS or email summary in the shop’s inbox rather than a slot on ServiceTitan, Housecall Pro, or Jobber. Conversion depends on the shop’s morning follow-up turning the message into a job.

  • Caller hears a “live receptionist” voice, but no slot is booked on the call
  • After-hours recovery lands as a summary in the inbox, not on the calendar
  • Booking depends on the shop opening the summary and converting it themselves
Scheduling-integration depth

Holdfast

Sends SMS and writes to the dispatch board.

When the voice agent confirms a slot, the SMS goes out to the caller and the job is written directly to the dispatch board the shop already runs — ServiceTitan, Housecall Pro, or Jobber. The audit-request scheduler dropdown confirms which one the shop is on.

  • Native writeback to ServiceTitan, Housecall Pro, and Jobber
  • Tech sees one job alongside everything else they already manage
  • No double-entry: jobs live in one system, not in a side notification

Smith.ai

Sends SMS, but the job lands in the inbox.

Smith.ai’s publicly listed positioning focuses on answering calls and sending SMS / email summaries back to the shop. A recovered after-hours call typically surfaces as a notification rather than a job on the shop’s dispatch board — the conversion loop stops at the inbox.

  • Booking attribution ends at the SMS, not on the calendar
  • The shop still has to convert a handoff into a scheduled slot
  • After-hours recovery slips if no one opens the summary the next morning
24/7 coverage

Holdfast

24/7/365, included.

The voice agent covers after-hours calls every day of the year — weekends, holidays, one-tech-on-call nights. Coverage is included in the retainer; there is no after-hours meter and no separate add-on line item.

  • No separate after-hours add-on in the invoice
  • Holidays, weekends, and one-tech-on-call nights are all covered
  • SMS handoff routes back to the shop’s own follow-up workflow

Smith.ai

Always on, but every call is metered.

Smith.ai advertises 24/7 live-answering coverage, but billing is per-call. After-hours coverage is included in the sense that the agent picks up — every off-hours call is its own invoice event, whether it lands a booking or not.

  • After-hours calls are the highest-cost line items on the invoice
  • A missed booking still produces a billable call
  • Coverage scope is set by plan tier, not by a flat retainer

Proof framing

The fee follows the booking — not the per-call meter.

The same per-shop math the pricing page walks through — calls recovered, jobs booked, invoice dollars attributed, Holdfast invoice, contractor’s net — applies here.

From /pricing
Effective fee, applied to recovery dollars.

The pricing worked example reads an effective fee as a small fraction of the revenue the booking actually generated — the contractor keeps over 90% of every dollar the recovery layer actually produced. On a per-call Smith.ai meter, that same fraction depends on call volume and call duration, not on whether a missed call landed a job on the calendar. A per-call meter sitting between the recovery and the recovery-dollar math is the source of the gap this page is named for.

The 20-minute audit fills the same per-shop table for a real shop — ten recent recordings, last quarter’s ticket values, and confirmation the shop runs ServiceTitan, Housecall Pro, or Jobber.

Next step

See your own number on this sheet.

A 20-minute audit uses ten of your recent inbound calls and your last quarter’s ticket values to fill the same per-shop table for your shop — no install, no commitment.

Book an audit

What we need

  • Ten recent inbound recordings (or a calendar link)
  • Last quarter’s service-ticket value range
  • Confirmation you run ServiceTitan, Jobber, or Housecall Pro

FAQ

The AI-receptionist objection.

The question every contractor-comparing-Smith.ai asks before signing /pricing — answered in the same plain voice as /faq.

Why not just go with Smith.ai?

See also
  • /pricing — the outcome-priced worked example and the per-shop ROI math.
  • /faq — ten contractor questions, including how missed-call bookings are written back to the dispatch board.

Sources & methodology

Where each claim comes from.

Holdfast claims on this page are sourced inline from in-repo pages: the outcome-priced model and worked example math on /pricing; the ServiceTitan / Housecall Pro / Jobber scheduler dropdown on /audit-request; the 24/7 voice coverage on /plumbing, /hvac, and /electrical; the per-call consent capture surfaced on the TCPA SMS compliance resource and the weekly ROI report shape across the dashboard shell.

Smith.ai claims on this page reflect publicly listed product positioning for a typical per-call, AI-receptionist offering — and are framed here as such, not as a verbatim reproduction of any specific Smith.ai marketing copy. Where a Smith.ai feature claim could not be verified from a public source, it is described in general positioning terms. For an exact side-by-side against Smith.ai’s current offering, request the audit and ask for the Smith.ai-specific comparison sheet.