Call center software for Italy.

Italy runs a national opt-out register, the Registro Pubblico delle Opposizioni (RPO). Consumers can register both landline and mobile numbers, and companies are generally expected to scrub their calling lists against the RPO before each telemarketing campaign. An important nuance often missed by teams new to the market: registering a number on the RPO also cancels consents previously given to that number, so an old consent record is not enough on its own. Treat the RPO as a live gate, not a one-time import.

Marketing calls generally require prior consent, and the Garante — Italy's data protection authority — has issued significant fines for unlawful telemarketing and for unclear or undocumented consent chains. Responsibility can extend along the call-center supply chain, so a caller relying on a partner's list should still be able to show where each consent came from. Data handling sits under the GDPR and the Italian Privacy Code, while AGCOM oversees communications and numbering, including the requirement to present a valid, displayed CLI on outbound calls.

In day-to-day operations that means Italian-language agents and scripts, scheduling within the CET/CEST timezone and locally accepted calling hours, and re-scrubbing against the RPO before every campaign rather than trusting a stale list. DialerBee is built to support that workflow, not replace your legal judgement: RPO and DNC list management with checks before each dial, consent tracking with provenance, CET-aware scheduling, configurable retry caps, append-only audit logs, and Italian-language AI AMD. These are compliance-supporting controls, not a guarantee of compliance — confirm current rules with the Garante and AGCOM and qualified counsel before you launch.