prismAn AI receptionist budget has several parts. A setup quote does not tell you the full running cost, and a low monthly advertised price does not establish that the required integrations are included.
Start with the scope
At Prism, we discuss pricing after understanding your call volumes, the questions callers ask, required integrations and the point at which a person should take over. Your written proposal should separate setup, ongoing care and third-party usage. See how we work or request a conversation to explain your requirements.
Ask for the complete cost sheet
| Cost | Questions for the supplier |
|---|---|
| Build | Which call flows, languages and integrations are included? What counts as a change? |
| Care | What maintenance and response terms are included? Is it optional? |
| Voice and model usage | What units are billed? Are allowances shared with other projects? |
| Phone service | Who pays for the number, incoming minutes, transfers and messages? |
| Connected tools | Does your CRM or booking system require a higher plan? |
| Exit | Can you export records and retain the number and account access? |
Use a quiet, normal and busy month from your own call history. Multiply the relevant usage units by the supplier’s current rates, then add fixed costs. Currency conversion and tax should be explicit. Ask for spending alerts and an agreed response if usage exceeds the estimate. Do not assume a fixed support fee includes unlimited conversation time.
Judge value using contribution, not revenue
Suppose, purely as an illustration, improved intake produces four additional completed jobs per month, each contributing $150 after direct delivery costs. That is $600 of monthly contribution before receptionist costs. If ongoing costs total $400, the remaining $200 would take 20 months to recover a hypothetical $4,000 setup fee. If there are no extra completed jobs, that recovery does not occur.
Replace every assumption with evidence. Count incremental jobs, rather than appointments that would have been booked anyway, and include staff time spent correcting errors. A pilot should test those assumptions before a wider rollout.
What belongs in the acceptance test
Require correct contact capture, accurate answers within the agreed scope, confirmed calendar writes where included, visible failure alerts and a working route to a person. A fluent demo alone is not evidence of operational reliability.
For the service choice itself, see the call coverage comparison. For the value of missed inquiries, use the call-log worksheet.
Book a Free Strategy Call to discuss your workflow with Pieter.
Editorial note: revised with AI assistance to remove unsupported anecdotes and outcome claims. Examples are illustrative; this is not a report of client results.