From the Local Government edition of October 22, 2026
L'Aldea, Catalonia begins testing ALDEA, an AI phone assistant that forwards unresolved calls to staff, with periodic reports on accuracy and forwarding rules
Ajuntament de l'Aldea (Catalonia, Spain); CorelixIA · Municipal telephone citizen services · L'Aldea, Catalonia, Spain
- Publisher
- Diari de Catalunya
- Original publication
- 20 October 2026 (Diari de Catalunya, Pere Roca Soler)
- Source retrieved
- 2026-10-23
- Event date
- 2026-10-20
What happened
L'Aldea's town council in Catalonia has begun testing ALDEA, an AI telephone assistant developed by CorelixIA, to answer common questions about municipal services, hours, contact channels and the documents needed for procedures. Queries needing personalised attention or that the assistant cannot resolve are forwarded to municipal staff by established criteria. During testing, responses are validated, operational limits reviewed and forwarding criteria evaluated through periodic reports. Details such as the phone number and scope will be set at final launch.
Why it matters
A small-municipality example of staging a voice assistant with explicit test-phase validation of answers and handoff rules before launch, a practice U.S. councils are now asking for after accuracy disputes.
Evidence and measured results
Municipal statement as reported: testing phase, vendor, scope of queries, forwarding to staff, periodic validation reports. No outcomes yet.
Limitations and uncertainty
No results. Small Spanish municipality; transferability to U.S. 311 operations is limited. Vendor and capabilities are as described by the council.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-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
- Small councils need to handle routine phone inquiries outside staff capacity while keeping a personal channel for complex cases.
- Stakeholders
- Town council and mayor
- Citizen service staff
- IT or digital lead
- Vendor (CorelixIA)
- Discovery questions
- What accuracy and handoff thresholds must be met before go-live?
- Which query types are in scope?
- How will periodic reports be shared with elected officials?
- What languages are supported?
- Value hypothesis
- Bounded: a validated voice assistant may handle common informational calls, subject to test results not yet published.
- Potential engagement
- A pre-launch evaluation design for a municipal voice assistant: test scripts, thresholds and reporting.
- Unsupported claims
- Call deflection rates
- Cost savings
- Resident satisfaction
Pre-sales engineering
Role takeaway
- Fit
- Small municipalities with predictable informational phone queries.
- Architecture and integration
- Natural-language voice assistant connected to telephony with rule-based forwarding to municipal staff.
- Prerequisites
- Curated content on services and procedures
- Forwarding criteria
- Telephony integration
- Call logging for review
- Constraints
- Testing phase only
- GDPR and EU AI Act transparency apply
- Scope and hours not yet defined
- Security
- Data handling of call recordings and transcripts was not described and must be checked.
- Proof of value
- Measure answer correctness on scripted calls
- Test forwarding accuracy on edge cases
- Review periodic test reports
Delivery
Role takeaway
- Work
- Run the testing phase, validate responses, tune forwarding and prepare the final launch.
- Dependencies
- Vendor configuration
- Staff availability for forwarded calls
- Content accuracy
- Ownership
- Ajuntament de l'Aldea citizen services.
- Skills and adoption
- Staff need to review assistant responses and handle forwarded calls.
- Governance checkpoints
- Periodic test reports
- Go-live decision after validation
- Public announcement of scope and hours
- Acceptance criteria
- Proposed: documented accuracy threshold met on test calls
- Proposed: forwarded calls reach correct staff
- Proposed: scope published at launch
- Risks
- Inaccurate guidance on procedure requirements
- Callers stuck without human route
- Unclear data handling
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?
Voice channel natural-language assistant with rule-based forwarding to staff; integration with telephony and staff routing implied but not described.
Governance
Who approves, reviews and stays accountable for outcomes?
Defines a pre-launch evaluation gate covering answer validation, operational limits and forwarding criteria, with periodic reporting.
Security and privacy
What data, permissions and controls need testing?
Not described; EU GDPR and the AI Act transparency obligations would apply to a public-facing voice assistant.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Phone channel may serve residents less comfortable with web tools; staff still handle forwarded personalised queries. Languages not stated.
Procurement
What should contracts, pricing and exit terms secure?
Vendor CorelixIA; procurement route and cost not disclosed.
Operating model
Which teams own the service once it runs?
Staged launch with a formal test phase and periodic reports before final service definition.
Publication history
- 2026-10-22Local Government · Issue 475 resources
Stable resource ID: laldea-es-aldea-ai-phone-assistant-testing-phase-20261020