Buy a bounded operating outcome, not exposure to a growing category. The following are desk recommendations based on the evidence above.
| Market signal | Procurement response |
|---|---|
| Large funding rounds | Ask for financial continuity information, support commitments and a funded product roadmap; do not infer runway from headline capital alone |
| Acquisition or ownership change | Review assignment clauses, data-processing arrangements, support ownership and migration obligations |
| Native agents inside existing software | Obtain both an incumbent-platform quote and an independent alternative on identical scope |
| Different billing units | Reprice using the same monthly calls, unique callers, durations, transfers and peak concurrency |
| High reported containment or booking rates | Request denominators, exclusions, call mix, human involvement and downstream verification |
| Vertical integration announcements | Test the precise system actions your workflow requires before committing to rollout |
| Low advertised usage rates | Include implementation, monitoring, fixed controls, support and human rescue |
How do US calling rules affect addressable volume?
Do not treat every lead or telephone number as legally callable demand. The FCC’s 8 February 2024 declaratory ruling brought AI-generated voices within the TCPA’s artificial-or-prerecorded-voice framework. Obtain current legal review of the proposed outbound purpose, consent and applicable exemptions before counting those calls in a business case. (docs.fcc.gov)
For healthcare, HHS guidance explains that a cloud provider creating, receiving, maintaining or transmitting ePHI on behalf of a covered entity can be a business associate, requiring an appropriate BAA. This can affect supplier eligibility and the required commercial package; it is not solved by a broad compliance badge. (hhs.gov)
This report provides procurement evidence, not legal clearance or a complete statement of federal and state requirements.
What should buyers request before signing?
- A dated quote showing every billing unit, minimum, overage, fixed charge and excluded service.
- A normal-month and peak-month cost model using the buyer’s actual call distribution.
- Separate definitions for answered, contained, transferred, autonomously completed and human-rescued calls.
- Proof that bookings and other transactions exist correctly in the operating system.
- Representative tests covering unavailable capacity, interruptions, unsupported requests and integration failure.
- A staffed fallback route, including an after-hours failure procedure.
- Data-flow, retention, subprocessor and applicable contractual evidence.
- Acceptance milestones before broader rollout or long-term commitment.
- Export and exit arrangements that preserve numbers, records and essential workflow knowledge.
Bottom line: public evidence is sufficient to justify testing specific voice-agent workflows, but not to assume a universal saving, completion rate or US market size. The useful buying question is: what does this supplier cost to complete this task correctly on our calls, including the work people must still do?