BlogSupportSystem statusEspañolHosted in the USA

Buying & budgeting

Writing an RFP for an AI phone agent: scope and scoring

Many cities buy through a formal solicitation, and AI phone agents are new enough that there are few templates to borrow. This post covers how to structure an RFP or RFQ for one: the scope of work, the demo script and how to score responses so they can be compared fairly.

Start with the problem, not the product

The strongest scopes describe what the city needs, not a feature list copied from one vendor. Open with a short description of your line:

  • what number residents call and how it is answered today
  • when the city wants the agent to answer: all hours, after hours or overflow
  • which work order or 311 system requests must reach
  • the languages your residents need
  • rough monthly call volume, from your phone system reports

That gives every vendor the same picture, and it makes pricing comparable. For estimating volume, see sizing your minute bundle.

Required behaviors

Write the safety and accuracy requirements as must-haves. A vendor that can't meet them should not advance. Examples:

  1. The agent states it is an AI and that the call may be recorded at the start of every call.
  2. The greeting tells callers to dial 911 for emergencies, and the agent directs callers who describe an emergency to hang up and dial 911.
  3. Callers can reach a person at any time by voice or by pressing 0, without being asked why.
  4. The agent confirms the address and request details before filing anything.
  5. The agent answers general questions only from city-provided content and says when it does not know.
  6. The agent does not take card or bank numbers by voice.
  7. Relay and TTY calls reach staff.

Our buyer's checklist has a longer list of questions to draw from.

Records, security and accessibility

These sections are where your records manager, IT manager and accessibility coordinator should write the requirements in their own words. Topics to include:

  • Records. What is kept for each call, export for public records requests, legal holds, city-set retention, and a log of every access.
  • Security. Where data is processed and stored, encryption in transit, role-based access and how vendors answer a security questionnaire. Ask vendors to describe audit status accurately. If an audit is planned rather than complete, the response should say so.
  • Accessibility. The standard the staff console meets, and a VPAT or accessibility conformance report.

Ask the city attorney to review anything that touches recording notice or public records, since rules vary by state.

Ask for a scripted demo

Written answers only go so far. Require a live demo, and give every vendor the same script in advance. A sample script for the City of Riverbend:

  1. Report a pothole at 200 Elm St. Watch for the read-back and request number.
  2. Give an address outside city limits.
  3. Report a pothole on a state highway, and see if the agent names the right agency.
  4. Ask an FAQ question, then one the FAQ does not cover.
  5. Say "talk to a person" mid-call, and press 0 on another call.
  6. Describe a gas smell.
  7. Check status on request SR-1185.
  8. Repeat one call in Spanish.

Then have the vendor show the staff side: finding each call in the log, playing the recording, exporting it and placing a legal hold.

Scoring that rewards honesty

A scoring sheet should separate what is available today from what is planned. Some suggestions:

  • Score demonstrated features higher than described ones. If it was not shown, it gets partial credit at most.
  • Require roadmap items to be labeled with a target date, and do not score them as available.
  • Weigh the demo heavily. It shows how the agent behaves with real callers.
  • Score pricing clarity, not just price. Ask how minutes are counted, what happens when the bundle runs out, and what is included.

For SentraOperator, roadmap items include quality review with nightly scoring, live transcript and listen-in, inspection booking, pay by text link, web chat and additional connectors. We label them as coming, and we would expect any vendor to do the same.

Pricing and contract terms

Ask every vendor to price the same way, so responses can be compared. Useful asks:

  • a unit rate and what it covers
  • whether the rate is fixed for the term
  • how unused capacity is treated
  • the cost of additional capacity and any cap the city can set
  • what is included, such as texts, phone numbers, transcripts and languages
  • any per-seat or per-user fees

Also ask about implementation time, what the city must provide and what happens to city data at the end of the contract. Our going live in weeks post shows what setup involves on our side.

The short version

Describe your line, make safety behaviors must-haves, let records, IT and accessibility staff write their own sections, require a scripted demo and score what vendors show over what they describe. Ask for pricing in a common format, and make sure roadmap items are labeled as roadmap.

Request a demo