Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Local Government edition of October 18, 2026

Independent reportingEmergingNew this fortnight

Aguadilla, Puerto Rico launches AIDA, a free 24/7 WhatsApp AI assistant for municipal requests, service status and cultural information, built with Numeral8

Municipio Autónomo de Aguadilla, Puerto Rico · Municipal resident access and community services · Aguadilla, Puerto Rico, United States

Publisher
Metro Puerto Rico
Original publication
14 October 2026 (Metro Puerto Rico); WAPA TV also reported 18 October 2026
Source retrieved
2026-10-19
Event date
2026-10-14
Read original source

What happened

On 14 October 2026 Aguadilla presented AIDA (Asistente Inteligente de Aguadilla), a free WhatsApp AI assistant available 24/7 in Spanish and English. Metro reports the mayor called it the first of its kind in a Puerto Rico municipality. Residents can report potholes, damaged streetlights and abandoned vehicles; check pharmacy and health-centre hours; follow municipal request status; access municipal procedures; request community and household assistance; and get cultural-agenda information. Users may write in everyday language without menu numbers. The city plans neighbourhood QR codes so conversations start from a barrio and needs can be mapped locally. AIDA sits under the Oficina de Asuntos Comunitarios y Desarrollo Social serving more than 55,000 residents. Mayor Julio Roldán Concepción said it does not replace municipal employees and that social media, email, phone and in-person channels remain. Developed with Numeral8. Why now: WAPA TV also covered the launch on 18 October, the edition date; the source is new to the archive.

Why it matters

Shows a mid-sized U.S. municipality using WhatsApp as the primary resident AI channel, with bilingual conversational intake, neighbourhood QR routing and an explicit non-replacement staffing claim—useful for cities weighing SMS/WhatsApp bots versus website chat.

Evidence and measured results

Metro Puerto Rico article opened in full via curl and BeautifulSoup. WAPA TV 18 Oct article opened for corroboration of same-day republication. Vendor documentation and accuracy metrics were not published.

Limitations and uncertainty

Launch coverage only; no accuracy, resolution-time or volume metrics. Vendor claims of first-in-PR status and conversational quality are untested in the reporting. English/Spanish support stated without evaluation method.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-18; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Residents need municipal help outside office hours without navigating phone menus or waiting for counters.
Stakeholders
  • Mayor or city manager
  • Community affairs / 311 lead
  • IT / digital services
  • Communications
  • Vendor conversational-AI partner
Discovery questions
  • Which resident channels already dominate (WhatsApp, SMS, web, phone)?
  • Must the assistant be bilingual and conversational rather than menu-driven?
  • How should neighbourhood QR codes map to service routing?
  • What happens when the bot cannot create or update a request?
Value hypothesis
A WhatsApp assistant could divert routine reports and status checks after hours; no measured diversion is reported here.
Potential engagement
90-day WhatsApp pilot for three report types with human fallback and weekly quality sampling.
Unsupported claims
  • First-in-Puerto-Rico uniqueness as a performance claim
  • Accuracy of status or service answers
  • Guaranteed staff-time liberation or FTE savings

Pre-sales engineering

Role takeaway
Fit
High-volume, low-complexity reports and FAQ over WhatsApp where bilingual conversational intake matters.
Architecture and integration
WhatsApp Business API to Numeral8 assistant; ticket/status connectors; QR deep-links with barrio metadata; human escalation path.
Prerequisites
  • Curated municipal knowledge and service catalogue
  • WhatsApp Business account and number governance
  • Transcript retention and public-records policy
Constraints
  • WhatsApp/Meta platform terms and data handling
  • Unknown accuracy of status lookups
  • No published SLA for handoff
Security
Define what PII may enter chat; encrypt transit; restrict vendor training on city data; log access to transcripts.
Proof of value
  • Sample routing accuracy for seeded report scenarios
  • Bilingual paraphrase tests
  • Measure handoff rate when the bot cannot resolve

Delivery

Role takeaway
Work
Configure assistant, install neighbourhood QR signs, train community-affairs monitors, publish channel matrix.
Dependencies
  • Numeral8 configuration
  • Community Affairs ownership
  • Communications for QR rollout
  • Service departments receiving tickets
Ownership
Oficina de Asuntos Comunitarios y Desarrollo Social, per municipal announcement.
Skills and adoption
Staff monitoring of conversation quality, escalation and knowledge-base updates.
Governance checkpoints
  • Pre-launch content approval
  • Weekly quality sample in first 30 days
  • Channel-matrix check that phone/email/counter remain
Acceptance criteria
  • Proposed: pilot report types create tickets end-to-end
  • Proposed: human handoff available when confidence is low
  • Proposed: published non-replacement staffing statement matches operations
Risks
  • Unmeasured answer quality
  • Public-records exposure of chats
  • QR mapping errors by neighbourhood
  • Over-reliance if other channels are quietly degraded

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?

WhatsApp conversational channel to a vendor assistant (Numeral8), bilingual natural-language intake, planned QR deep-links by neighbourhood; backend case/status integration not described.

Governance

Who approves, reviews and stays accountable for outcomes?

Program ownership assigned to Community Affairs and Social Development; mayor publicly commits that staff channels remain and that the tool does not replace employees.

Security and privacy

What data, permissions and controls need testing?

WhatsApp messaging of service requests and status queries raises retention, Meta/WhatsApp processing and public-records questions the articles do not address.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

24/7 WhatsApp access plus retained non-digital channels; mayor frames staff time as freed for higher-priority work rather than headcount cuts.

Procurement

What should contracts, pricing and exit terms secure?

Developed with Numeral8; contract value, term and competitive status not disclosed in the articles.

Operating model

Which teams own the service once it runs?

Resident reporting and information shift partly to asynchronous chat; community office remains first municipal link; no automated decision-making described.

Publication history

  1. 2026-10-18Local Government · Issue 436 resources
Read preserved resource versions (JSON)

Stable resource ID: aguadilla-pr-aida-whatsapp-ai-assistant-numeral8-20261014