I've uploaded the new creative for the door-to-door canvasser for the "Fixed Energy 12" offer. Can you validate it?
ARERA disclosures on energy offers go out compliant before publication.
ARERA Disclosure Validator checks price disclosures in energy or gas retail offers before publication — commercial website, sales canvasser, marketing materials. It verifies compliance with ARERA-specific requirements: regulated formulations, mandatory elements, correct regulatory references. Every decision is traced for audit.
ARERA Disclosure Validator at work.
Six points checked. Four compliant: "price fixed for 12 months" with correct lock conditions, typical customer annual cost per the ARERA schema, comparison with the protected market, system charges disclosed. Missing: the 14-day right of withdrawal — mandatory for door-to-door sales under the Consumer Code. Compliant phrasing attached.
I'll add the proposed text. Can you recheck?
All six points compliant. The creative can proceed to print. The event — initial version, flag, modification, final approval — is in the audit registry for inspection by the ARERA compliance officer.
Why it exists.
ARERA regulates in specific terms the price disclosures for energy and gas retail offers: regulated formulations (e.g. "price fixed for 12 months" requires precise lock conditions), mandatory elements (comparison with the protected market, typical customer annual cost, system charges), correct regulatory references. For AI assistants, advance notice of the automated nature of the interaction and a human fallback are required.
How it works before publication.
ARERA Disclosure Validator activates before publication of an offer or commercial material. It extracts the price disclosures from the artefact, compares them against the ARERA declarative rules configured by the utility's compliance team, identifies missing or non-compliant disclosures, and proposes compliant formulations. Integration with the commercial CMS and offer management system is delivered during the project.
Three outcomes, a clear scope.
Silent pass, flag with alternatives, block with escalation to the utility's ARERA compliance officer. The completeness of the rules repository against current ARERA deliberations is the responsibility of the utility's compliance team — the agent runs the check; the regulatory oversight stays human.
Who it serves and where it applies.
Commercial retail manager
Gets focused pre-screening on price disclosures, before a material goes to print, on the website, or to the canvasser. Formal ARERA errors are caught before publication, not after a customer complaint or a regulator inspection.
ARERA compliance officer
Has an inspectable trace of disclosure decisions for every offer — initial version, requested changes, final decision, date. The registry is available at the first ARERA audit, readable with a standard SQL client.
Utility marketing team
Sees compliance-approval iterations on commercial materials fall. Flags arrive with the compliant phrasing already proposed, not with a generic "this doesn't work". Time-to-market for materials goes down.
A concrete example.
A marketing team prepares a new canvasser.
A utility's marketing team prepares a new creative for the door-to-door canvasser for a new energy offer. The creative enters the approval system. The agent activates, extracts the price disclosures, and starts the verification of ARERA points.
Six ARERA points checked, one missing.
Six ARERA points checked. Four compliant: the "price fixed for 12 months" formulation is consistent with the declared ARERA lock conditions, the typical customer annual cost is present and formulated per the schema, the comparison with the protected market is present, system charges are disclosed. Missing: the 14-day right of withdrawal — mandatory for door-to-door sales.
The team applies the change, the registry stays.
Flag with the proposed compliant formulation. The marketing team applies the change, confirms. The creative passes approval and goes to the canvasser. The full event — initial version, flag, applied modification, final approval — stays in the runtime audit registry for inspection by the ARERA compliance officer.
Configuration and technical resources.
The ARERA Disclosure Validator rules are declarative. The utility's ARERA compliance team defines the specific rules on price disclosures for each publication channel — website, canvasser, print materials, radio and TV communications. The rules live in the utility's repository, versioned, validated at agent startup. When ARERA publishes new deliberations or modifies the requirements, the compliance team updates the rules in the repository.
- Language
- TypeScript (Node.js)
- LLM model
- customer's choice: Anthropic, OpenAI, Mistral, open source models hosted internally, AWS Bedrock for a private model
- Built-in controls used
- pii-detector, topic-guardrail
- Native channels
- Slack, Telegram, OpenAI-compatible HTTP
- Commercial CMS and offer management system integration
- dedicated adapter delivered during the project
- ARERA rules
- declarative, versioned, written and maintained by the utility's compliance team
- Completeness of rules against current ARERA deliberations
- responsibility of the utility's compliance team
- Memory
- persistent per instance, pgvector + PostgreSQL FTS
- Registry
- immutable, ARERA audit inspectable
Frequently asked questions about the agent.
Energy Offer Validator covers the entire retail offer — structure, modulation, duration, conditions, ancillary costs, sign-up method. ARERA Disclosure Validator focuses on the mandatory price disclosures per publication channel. The two agents can coexist or one can replace the other depending on the utility's needs.
The declarative rules in the utility's repository are updated by the compliance team when ARERA publishes new deliberations or modifies disclosure requirements. The responsibility for timely updates and completeness against the current regulatory landscape stays with the compliance team. The repository is versioned: every change is tracked with date and author.
The typical pattern for ARERA Disclosure Validator is 8-12 weeks. Discovery 2 weeks, configuration of disclosure rules for the main channels 3-4 weeks, integration with the offer approval system 2-4 weeks, hand-off to the compliance team 1-2 weeks.
Yes, if configured for that case. For AI assistants in energy and gas customer service, ARERA requires advance notice to the customer of the automated nature of the interaction and a guaranteed human fallback. The corresponding rules can be included in the utility's compliance repository.
From a 30-minute conversation to the squad in production.
A 30-45 minute conversation to understand how ARERA Disclosure Validator would configure to the utility's case. Which publication channels, which current ARERA deliberations to cover, which offer approval flow.