From the Local Government edition of September 21, 2026
Fort Worth seeks U.S.-hosted SOC 2 enterprise AI IVR/chat platform (RFP 26-0263)
City of Fort Worth · Municipal resident contact center, IVR, and digital services · Fort Worth, Texas, United States
- Publisher
- Bidscope
- Original publication
- Bidscope summary of solicitation posted August 26, 2026; proposals due October 22, 2026
- Source retrieved
- 2026-09-22
- Event date
- 2026-10-22
What happened
Bidscope summarizes City of Fort Worth RFP 26-0263 for an enterprise AI Interactive Voice Response platform unifying resident- and staff-facing voice, web chat, SMS, workflows, and knowledge services. The opportunity is listed open, posted Aug 26, 2026, due Oct 22, 2026, with a one-year base and four one-year options. Requirements cited include multilingual RAG/document-grounded responses, integrations with Cisco IVR, Microsoft 365, Accela, ESRI/ArcGIS, case management/FAQ, Motorola PremierOne and SMS gateways, U.S.-based hosting/processing/storage, SOC 2 Type II without material exceptions, AES-256/TLS 1.2+, RBAC/MFA, ≥99% uptime, five-year audit-log retention, 24-hour breach notification, vendor-led eight-week implementation, and references including two jurisdictions over 500,000 residents. Bonfire is named as the submission portal.
Why it matters
Open large-city CX AI procurement with unusually explicit residency, SOC 2, grounding, and integration shalls—useful checklist beside Denver Water’s still-open Sept 30 agent-assist RFP and Grand Rapids’ Sept 24 chatbot close.
Evidence and measured results
Bidscope: status Open; 26-0263; due Oct 22, 2026; posted Aug 26; channel/integration list; U.S. hosting; SOC 2 Type II without material exceptions; 8-week implementation; reference bars; Bonfire portal link.
Limitations and uncertainty
Secondary aggregator—not the sealed Bonfire PDF set; confirm every shall against official documents before bidding or advising.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-22; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Fragmented IVR/chat channels and knowledge bases create inconsistent resident answers and hard-to-audit automation.
- Stakeholders
- 311/customer service
- IT/security
- Development services (Accela)
- GIS
- Procurement/small-business office
- Discovery questions
- Which shalls are mandatory vs desirable?
- Where will knowledge live and who updates it?
- What is the live-agent escalation SLA?
- Can the 8-week plan cover Accela/ArcGIS/Cisco jointly?
- Value hypothesis
- A grounded enterprise AI contact layer can unify channels if residency/SOC2 and integration owners are real—without proving call deflection before acceptance tests.
- Potential engagement
- Compliance matrix and integration sequencing workshop against 26-0263—no award-probability claim.
- Unsupported claims
- Guaranteed award
- Any vendor meets all shalls from aggregator text alone
- 8-week full integration without risk
- FTE savings promised in RFP
Pre-sales engineering
Role takeaway
- Fit
- Enterprise AI IVR/chat/SMS platform with RAG grounding and municipal system connectors under U.S. residency/SOC 2 controls.
- Architecture and integration
- Cisco IVR + web/SMS/chat → grounded KB → workflows/forms → Accela/ArcGIS/M365/case/PremierOne; staff browser assist; audit trail.
- Prerequisites
- KB ingestion
- Integration credentials/owners
- SOC 2 package
- Accessibility/language plan
- Constraints
- Aggregator not substitute for Bonfire PDFs
- Aggressive 8-week implementation
- Five local-gov references including two >500k
- As-needed enterprise scope breadth
- Security
- U.S. hosting/processing/storage; SOC 2 Type II without material exceptions; AES-256 at rest; TLS 1.2+; RBAC/MFA; 5-year logs; 24-hour breach notice.
- Proof of value
- Grounded-answer audit sample
- Integration test results per system
- Uptime/SLA evidence
- Reference calls with >500k peers
Delivery
Role takeaway
- Work
- Ingest KB, integrate priority systems, train agents, cut over channels, and run acceptance on grounding and escalation.
- Dependencies
- Bonfire RFP documents
- Cisco/Accela/GIS owners
- Security review
- Department content stewards
- Ownership
- City customer experience/IT owns platform; departments own knowledge.
- Skills and adoption
- Train staff to correct KB sources rather than fight the bot; practice live-agent takeover.
- Governance checkpoints
- Security/SOC2 review
- Reference verification
- Channel pilot acceptance
- Go-live rollback plan
- Acceptance criteria
- U.S. residency attested
- SOC 2 evidence accepted
- Grounded sample passes
- Live-agent escalation works end-to-end
- Risks
- Schedule slip on integrations
- Hallucinated answers if grounding weak
- Vendor lock-in
- Scope exceeds budget
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Treat this as a platform-plus-integrations program; sequence Cisco/Accela/GIS owners before promising an eight-week cutover.
Governance
Who approves, reviews and stays accountable for outcomes?
Score SOC 2, residency, audit retention, and reference quality as heavily as NLP demos.
Security and privacy
What data, permissions and controls need testing?
U.S. data residency, encryption, MFA/RBAC, breach notice, and long audit retention are explicit evaluation criteria—not afterthoughts.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Multilingual and accessibility shalls need test evidence, not brochure claims, especially for voice channels.
Procurement
What should contracts, pricing and exit terms secure?
Use a shall/shall-not compliance matrix; verify Bonfire addenda and small-business forms.
Operating model
Which teams own the service once it runs?
Budget ongoing KB stewardship and live-agent escalation staffing alongside the platform fee.
Publication history
- 2026-09-21Local Government · Issue 164 resources
Stable resource ID: fort-worth-enterprise-ai-ivr-rfp-20261022