Skip to content

Public Opposition Register (RPO)

Requires the "Campaigns" permission.

The Public Opposition Register (RPO) is the official list of people who asked not to receive commercial phone calls. For databases that require it, Thelgo helps you check the numbers of each campaign before calling them: from the campaign's Public Opposition Register (RPO) page you extract the list of numbers, have it checked by the Register and import the response. As long as the list is not valid, the campaign cannot be worked.

How the exchange with the Register works

Thelgo does not connect to the Register's portal: the exchange of files is manual. You download from Thelgo the file with the numbers, upload it to the Register's official portal, wait for the response (up to 24 hours) and then upload the response file into Thelgo.

When it applies to a campaign

The function applies only to campaigns whose database was created as an RPO database (Public Opposition Register): this is a final choice, made when the database is created and which can no longer be changed (see Databases). In an RPO database only Phone1 is allowed (the other phone columns are not available), and that number is the one that is checked.

For the campaigns of a normal database the page is not needed: no RPO icon appears in the campaign list.

How to open it

In the campaign list, on the campaigns of an RPO database, among the action icons there is an icon that shows the RPO status (when you hover over it you read "Public Opposition Register (RPO) — " followed by the status). Click it to open the Public Opposition Register (RPO) page, with the campaign name under the title. The arrow at the top left goes back to the campaign.

Icon Status Meaning
Green check mark Valid The imported list is still valid: the campaign is workable
Amber triangle/exclamation mark Expired The validity of the list has ended: the campaign is not workable until you import a new one
Red cross Never validated There is no imported list yet (or a new extraction was made after the last import): the campaign is not workable
Grey shield Check disabled The check was excluded by hand (see below): the campaign is always workable

The page of a never-validated campaign has the Current status box (showing Never validated, with no dates) and the Extract list to send to the Register section; further down there is Import validated list.

Current status

At the top of the page the Current status box shows the status (Not applicable, Never validated, Valid, Expired, Check disabled) and four dates, with "—" if there are none:

Item Meaning
Last extraction When you extracted the last list to send to the Register
Last import When you imported the last response
Validity start The validity start date chosen at import
Expiry Until when the list is valid

Below you see "Validity set to N days from the validity start date.": the validity duration (15 days, unless otherwise decided) is a setting valid for the whole platform, decided by the Thelgo provider, not by you. The list is valid until the Expiry day included, in your account's time zone.

1. Extracting the list

The Extract list to send to the Register section generates "the file with this campaign's phone numbers to upload to the official RPO portal".

  1. Press Extract list.
  2. "Extraction completed: N phone numbers extracted." appears together with the link Go to Logs → Operations to download the file: the file is a .zip archive that contains a text file with one number per line.
  3. Download the file from the Operations page (type RPO list extraction) and upload it to the Register's portal.

What the file contains: the Phone1 of all the campaign's contacts (non-empty, without duplicates, in order), without the 0039 country prefix.

A new extraction cancels the validity of the list

If after importing a list you extract again, the previous validation is considered overridden and the campaign goes back to Never validated, and therefore not workable, until you import the new response. Extract again only when you really need to, for example after adding contacts to the campaign.

If the campaign does not use an RPO database, "This campaign does not use a database marked as "Public Opposition Register"." appears, and if starting fails, "Unable to start the extraction." appears. The extraction is recorded in the Audit log ("RPO list extraction performed").

2. Importing the Register's response

The Import validated list section is used to upload "the response file received from the RPO (.zip or .txt) to update this campaign's workability status".

  1. Choose the Response file (.zip or .txt) (.zip or .txt, 26 MB at most). If it is a .zip, Thelgo looks by itself inside it for the file with the list of numbers, ignoring any other files.
  2. Set Validity start: the date from which the list is valid (default: today). It cannot be in the past: "The start date of validity cannot be in the past."
  3. Choose Contacts to exclude:
    • Exclude everyone registered (default): anyone who appears as registered with the Register is blocked for this campaign;
    • Exclude only those who registered after a certain date: you enter a Reference (cutoff) date and only those registered with a registration date after the cutoff are blocked (those who registered before or on the same day remain workable). If the Register does not give the date for a registered person, they are blocked to be safe. The cutoff is required with this option and cannot be a future date.
  4. Press Start import. The button stays disabled while the file, the date or (with the second option) the cutoff is missing.

The file must have one line per number, in the form number,flag or number,flag,date (flag 1 = registered, 0 = not registered; date in yyyy-mm-dd format). Lines that do not follow this format do not stop the import: they are counted as Errors.

The import starts in the background: you see the progress bar and, below it, "You can leave this page open: the import continues even for large files." When it finishes Import completed (or Import failed) appears with the summary:

Item Meaning
Total Lines in the file
Blocked for this campaign Contacts that the Register indicates as registered and that, according to the chosen mode, were blocked
Unblocked for this campaign Contacts not registered (or registered but not excluded by the chosen mode) that are workable
Ignored Numbers in the file that do not match any contact of this campaign
Errors Invalid or unprocessable lines

With New import you can upload another one; with View the operation log you open the line-by-line detail in Operations (type RPO list import). The import is recorded in the Audit log ("RPO list import performed").

If the check does not start, messages appear such as "The uploaded file is not a valid .zip archive." or "Could not find the text file with the list of numbers in the uploaded .zip archive." or "Unable to start the import."

A registered contact stays flagged in other campaigns too

When a number turns out to be registered with the Register, Thelgo also flags it on the contact's record (see Contacts). The block, however, is per campaign: it depends on the mode chosen in each import, and a contact can be blocked in one campaign and workable in another.

A contact's number is searched in the Phone1 of the database's contacts; the Register returns the same number without 0039 and Thelgo recognizes it even if it is saved in the database with that prefix.

What happens to the campaign

  • If the list is Never validated or Expired, the campaign cannot be worked: an operator who tries to take a contact, to open one from the search or from Callbacks, or to open the Quality Check queue gets "The RPO list is not validated or has expired: this campaign cannot be worked on." and the Predictive engine does not launch calls for that campaign.
  • Contacts blocked by the import are not proposed to operators nor called by the Predictive engine, do not appear in the Callbacks and Quality Check pages and cannot even be opened from the Contact search: the operator sees "This contact is in the Do-Not-Call Registry and is excluded from this campaign." They stay in the campaign with their history.
  • When the list expires, the campaign stops by itself: to resume you must extract and import a new list.

Plan the renewal

Since the Register's response can take up to 24 hours, start the extraction before the expiry: this way the campaign does not stay stopped. Remember, however, that a new extraction immediately makes the current list no longer valid (see above): import the new response as soon as you receive it.

Disabling the check for a campaign

The Disable the check for this campaign section "makes the campaign always workable, ignoring the RPO status. Every change is tracked in the Audit Log."

  • Tick Check disabled (bypass) and confirm "Disable the RPO check for this campaign? The campaign will stay workable even without a recent, valid list." The status becomes Check disabled and the icon in the campaign list a grey shield.
  • To turn it back on, untick it and confirm "Re-enable the RPO check for this campaign?"

Use with caution

With the check disabled no verification against the Register prevents the numbers from being called: responsibility for complying with the regulations is yours. Every activation and deactivation is recorded in the Audit log ("RPO check disabled for a campaign", "RPO check re-enabled for a campaign"). The bypass does not unblock the contacts already blocked by a previous import: they stay excluded from the proposal to operators and from the Predictive engine until you unblock them with a new import.