# Request for Proposals: AI Phone Agent for a City 311 or Main Line

Template version 1.0, November 2026

> **How to use this template.** Replace everything in [square brackets], delete requirements that don't apply, and add your city's standard RFP terms, insurance and submission rules. Have your IT manager, records manager, accessibility coordinator and city attorney review their sections. This template is not legal advice. Recording notice, records retention and public records rules vary by state.

## 1. Background

[City name] is seeking proposals for an AI phone agent to answer calls to its [311 / main] line at [phone number].

- **Population served:** [number]
- **How the line is answered today:** [e.g. staff at a front desk, Monday to Friday, 8 a.m. to 5 p.m.; voicemail after hours]
- **Approximate monthly call volume:** [number, from phone system reports]
- **Service request or work order system:** [system name], which requests must reach
- **Languages residents need:** [e.g. English and Spanish]
- **Phone system:** [vendor / type], which will forward calls to the vendor's number

The City intends to use the agent [at all hours / after hours only / for overflow only / starting after hours and expanding].

## 2. Scope of work

The selected vendor will provide a hosted AI phone agent that:

1. Answers calls forwarded from the City's line, during the hours the City sets.
2. Takes service requests and files them in [system name] with the request type, location, description and caller contact the City requires.
3. Gives callers the status of an existing request by request number.
4. Answers general questions using only content the City provides.
5. Transfers callers to City staff on request, and takes messages when staff are unavailable.
6. Sends text messages to callers only with their consent.
7. Keeps a record of every call that City staff can search, review, export and retain under the City's schedule.
8. Provides a staff console for configuration, review and reporting.

The vendor will also provide setup, configuration with City staff, testing support, training and ongoing support.

## 3. Required capabilities

Items in this section are **pass/fail**. A proposal that cannot meet a requirement should say so plainly. Responses must state, for each item, whether it is **available today**, **available with configuration**, or **on the roadmap** with a target date. Roadmap items will not be scored as available.

### 3.1 AI disclosure and recording notice

1. Every call opens by telling the caller they are speaking with an AI assistant, before any other content.
2. Every call states that the call may be recorded.
3. City staff cannot accidentally remove the disclosure from the greeting. Describe how this is enforced.

### 3.2 Emergencies and 911

1. The greeting tells callers to hang up and dial 911 for emergencies.
2. If a caller describes an emergency (for example fire, crime in progress, someone hurt, gas smell, downed power line), the agent tells them to hang up and dial 911 right away.
3. The City will be able to test this behavior during the demonstration.

### 3.3 Transfer to staff

1. Callers can reach a person at any time by voice (for example "talk to a person") and by keypad (for example pressing 0), without being asked to justify the request.
2. Transfers go to the department the City designates, with transfer numbers and hours the City controls.
3. Describe what staff hear or see before the caller is connected.
4. When staff don't answer or the office is closed, the agent takes a message. Describe where messages go.

### 3.4 Languages

1. The agent serves callers in [English and Spanish] for the full call, at all covered hours.
2. Request types, address confirmation and request numbers work the same in each supported language.
3. Describe what happens when a caller speaks a language that isn't supported.

### 3.5 Accuracy and limits

1. The agent confirms the address or nearest intersection, request type and details with the caller before filing anything.
2. The agent checks that the location is inside City limits, and refers callers to the responsible agency (for example the county or state) when it isn't.
3. The agent answers general questions only from City-provided content, and says when it does not know.
4. The agent never invents a request number, status, date, phone number or policy.
5. The agent does not collect card or bank account numbers by voice. Describe how sensitive numbers are kept out of recordings and transcripts.

### 3.6 Records, retention, legal hold and public records

1. For every call, the system keeps the transcript, recording, outcome and any request number created.
2. City staff can search calls and export a call (recording, transcript and details) for a public records request.
3. Authorized staff can place and release a legal hold. Calls on hold are never deleted automatically.
4. The City sets retention periods for recordings, transcripts and call records. Deletion is automatic when a period ends.
5. Every play, download, export and settings change is logged with the user and time.
6. Describe how the City receives its data at the end of the contract, in what format, and how the vendor confirms deletion.

### 3.7 Accessibility

1. Relay and TTY calls reach City staff.
2. A keypad option to reach a person is always available.
3. The staff console conforms to WCAG 2.2 Level AA. Provide a current VPAT or Accessibility Conformance Report, and describe how accessibility is tested.
4. Describe how City staff using assistive technology can review recordings and transcripts.

### 3.8 Security and data location

1. Calls and City data are processed and stored in the United States. List each location and sub-processor.
2. Describe encryption in transit and how stored data is protected.
3. Describe access control for vendor staff, including whether every access to City data is logged.
4. Describe audit status accurately. If an audit is planned rather than complete, say so and give the target date.
5. Describe how inbound webhooks and integrations are authenticated.
6. Complete the City's security questionnaire, attached as [Exhibit X].

### 3.9 Text messages, consent and STOP

1. The agent sends a text only after the caller agrees during the call.
2. Every text identifies the City and includes opt-out instructions (for example "Reply STOP to opt out").
3. STOP requests are honored, and HELP returns contact information.
4. Describe how consent is recorded.

## 4. Demonstration script

Finalists will give a live demonstration. Every vendor receives this script in advance and runs it on a demo line configured with the City's sample request types.

1. Report a pothole at [sample address]. Watch for the address read-back and request number.
2. Give an address outside City limits.
3. Report an issue on a state highway or county road. Does the agent name the right agency?
4. Ask a question the City's FAQ covers, then one it does not.
5. Say "talk to a person" mid-call. On another call, press 0.
6. Describe a gas smell.
7. Check the status of request [sample number].
8. Repeat one call entirely in [Spanish].
9. Ask for a text, then reply STOP.

Then show the staff side: find each call in the log, play the recording with the transcript, export a call for a records request, place a legal hold, and change an office hour.

## 5. Pricing structure

Pricing models for AI phone agents differ. To compare proposals fairly, every vendor must complete the pricing form in [Exhibit Y] using the same assumptions: [monthly call volume] calls per month, [average call length, if known], covering [hours].

Answer each question:

1. **Unit of pricing.** Per minute, per call, per resolved call, per seat or user, or a flat fee? If more than one applies, list each.
2. **How usage is measured.** For per-minute pricing, is time counted per second or rounded up? Does time after a transfer to staff count?
3. **Rate term.** Is the unit rate fixed for the full contract term? If not, how and when can it change?
4. **Commitment.** Is there a minimum commitment or prepaid bundle? What happens to unused capacity: does it roll over, and until when?
5. **Overage.** What does additional usage cost, and can the City set a not-to-exceed limit?
6. **Included items.** Are phone numbers, telephony, text messages, transcripts, recordings, languages, reports and integrations included, or priced separately?
7. **Per-user fees.** Are there per-seat or per-user fees for City staff using the console?
8. **One-time costs.** Setup, configuration, training and integration fees.
9. **Exit costs.** Any fee to export City data at the end of the contract.

Do not include costs that are not listed in the pricing form. The City will compare total cost over the contract term at the stated volume.

## 6. Implementation timeline

Describe your implementation plan against the phases below, with the City's responsibilities in each. Proposed dates are targets for discussion.

1. **Kickoff** [target date]: confirm hours, departments, transfer numbers and request types.
2. **Configuration** [target date]: greeting, languages, FAQ content, agency referrals and integration with [system name].
3. **Staff testing** [target date]: City staff place test calls, including the demonstration script, and review records in the console.
4. **Limited go-live** [target date]: for example after hours only, or overflow only.
5. **Full go-live** [target date]: the coverage the City selects.
6. **Post-launch review** [target date]: review calls, reports and settings with City staff.

State what the City must provide, such as content, phone system changes and staff time, and how long your typical implementation takes.

## 7. Vendor qualifications and references

Provide:

1. A description of your company, ownership and how long the proposed product has been in production.
2. At least [three] references from public agencies, preferably of similar size, using the proposed product. For each: agency name, contact name, title, phone and email, services provided and dates.
3. Whether each reference uses the same version and features proposed to the City.
4. Any contracts terminated for cause in the past [five] years.
5. Your current sub-processor list, and how the City is notified of changes.

If the product is new and references are limited, say so and describe any pilot or trial terms you offer.

## 8. Evaluation and scoring

Proposals that fail any pass/fail requirement in Section 3 will not be scored. Remaining proposals are scored on the criteria below. Suggested points are a starting point; adjust them to your City's priorities.

Score each criterion on this scale:

- **4: Demonstrated.** Shown working in the live demonstration.
- **3: Described in detail.** Clearly described and documented, but not shown.
- **2: Partly met.** Meets some of the requirement, or needs configuration the vendor did not describe.
- **1: Roadmap.** Planned, with a target date. Not scored as available.
- **0: Not met** or not addressed.

Points for a criterion equal its suggested points multiplied by the score, divided by 4.

**Suggested scoring rubric (100 points)**

| Criterion | What to look for | Suggested points |
|---|---|---|
| Live demonstration | How the agent handled every step of the demonstration script, including emergencies, transfers and Spanish | 25 |
| Service requests and accuracy | Read-backs, City limits checks, agency referrals, answers only from City content | 15 |
| Records and public records | Search, export, legal hold, City-set retention, access logging, data return at exit | 15 |
| Staff console and reporting | Configuration by City staff, call review, reports, change log | 10 |
| Accessibility | TTY and relay, WCAG 2.2 AA conformance evidence, testing approach | 10 |
| Security and data location | US data location, encryption, access control, accurate audit status, sub-processors | 10 |
| Pricing clarity and total cost | Complete pricing form, fixed rates, overage controls, total cost at stated volume | 10 |
| Implementation and references | Realistic plan, City responsibilities stated, comparable references | 5 |

## 9. Contract terms to include

Ask the City attorney to review these points for the agreement:

- The City owns all call recordings, transcripts, requests and call records.
- Retention periods, legal holds and deletion follow the City's schedule.
- Data stays in the United States, and the vendor gives notice before adding a sub-processor.
- A service level agreement covering availability, fallback to City staff if the agent is unavailable, support hours and response times.
- Return of City data in a usable format at the end of the contract, and written confirmation of deletion.
- Features on the roadmap are not contract deliverables unless listed with dates.
- Rates fixed for the contract term, with a not-to-exceed amount the City controls.

## 10. Submission requirements

- Proposals are due [date and time] to [contact and address or portal].
- Questions are due [date] to [contact]. Answers will be shared with all proposers.
- Format: [page limit, file format].
- Include a response to every numbered requirement in Section 3, in order, with the availability status for each.
- Include the completed pricing form, security questionnaire, VPAT or Accessibility Conformance Report, sample contract, and references.

---

*Prepared by SentraOperator (sentraoperator.com) as a free, vendor-neutral template. Copy, edit and share it freely; no attribution is required.*
