Skip to content

Databases

Requires the "Databases" permission.

A database is a list of contacts: the people or companies to call, each with one or more phone numbers and their contact details. Each campaign works on one database only: when you create a campaign you choose which database to take the contacts from (optionally filtering them). The same database can feed several campaigns.

You open the page from the menu DATA → Databases.

At the top of the page are Search all databases, Create new database, Anonymize (only with the permission) and Import contacts. For each database the page shows contacts, campaigns, status and RPO, with the action icons on the right.

The list of databases

Under the title you see how many databases there are (e.g. "4 contact databases").

Work groups

If your account has work groups and you do not have the All work groups permission, you only see the databases of your groups and those without a group; another database cannot be opened or edited, and cannot be used for imports, corrections or exports.

For each database:

Column What it shows
Name The name of the database
Work groups The names of the database's work groups, separated by commas, or "—" if it has none. The column appears only if there is at least one group you can see
Contacts How many contacts it contains
Campaigns How many campaigns use it
Status Active or Inactive. Databases created by Thelgo are born active and for now there is no command to deactivate them
RPO Yes if the database is an RPO database (subject to the check against the Public Opposition Register), No otherwise. It is chosen at creation and never changes (see Public Opposition Register (RPO))

Click a column header (Work groups included) to sort the list. On narrow screens the list becomes a series of cards with the same data.

Clicking a row opens the preview of the database's contacts: the full list with all the columns, 50 rows per page, with no filters (see Contact search).

The actions of each row

Icon Action
Person with + Add contact: enters a single contact by hand
Pencil Rename: opens Edit database, where you change the name and, if the database is empty, the dynamic fields schema (see Editing a database)
Magnifying glass Search: opens the contact search limited to this database
Down arrow Export database: generates an Excel or CSV file with all the contacts (see Exporting a database). It only appears with the "Download databases" permission
Wrench Correct database: updates the contacts already present with a correction file (see Correct database)
Trash can Delete: deletes the database with all its content

The buttons at the top

Button What it does
Search all databases Opens the contact search on all databases
Create new database Creates an empty database
Anonymize Opens the page to anonymize contacts from a list of numbers (right to be forgotten). The button is red and only appears with the "Anonymization" permission
Import contacts Opens the import wizard from an Excel or CSV file

Creating a database

  1. Press Create new database.
  2. Write the Name.
  3. If the database contains numbers to check against the Public Opposition Register, turn on RPO database (Public Opposition Register). Leave it off in other cases: the choice is final and cannot be changed after creation (see Public Opposition Register (RPO)). The popup explains this with the text "Limits this database to Phone1 only and subjects its campaigns to the Public Opposition Register (RPO) check. Final choice: cannot be changed after creation."
  4. If there is at least one work group that you can assign, Work groups appears below: one switch per group (optional; a database can belong to several groups, or to none).
  5. Press Create.

The name must be unique: if a database with the same name already exists, a red warning appears at the bottom: "A database named "…" already exists."

The database starts empty. To fill it, import a file or add the contacts by hand. You can also create a database directly from the first step of the import, with the + New button: the popup is the same, with the same RPO database (Public Opposition Register) choice.

The dynamic fields schema

If you need more fields than the standard ones (e.g. "Contract expiry", "Power kW"), first prepare a dynamic fields schema. The schema is linked to the database at the first import, or you choose it from Edit database. While the database is empty you can change or remove it; as soon as it has contacts or campaigns, the schema stays locked (see Editing a database).

Editing a database

Press the pencil on the database row: Edit database opens, with two fields (and, if there are work groups you can assign, the Work groups choice, as at creation).

Field What you do
Database name Changes the name. It must be unique, as at creation. Renaming has no effect on campaigns or contacts
Dynamic fields schema The dynamic fields schema linked to the database (see below)

On an empty database, besides the name you can choose the Dynamic fields schema. On a database with contacts or campaigns the schema is disabled and the text "The schema can only be changed while the database has no contacts and no campaigns." appears.

Press Save to confirm. Renaming also works for databases created with RPO database (Public Opposition Register); the RPO mode stays the one chosen at creation.

Changing the dynamic fields schema

  • If the database is empty (no contacts and no campaigns), Dynamic fields schema is a drop-down list: choose one of the existing schemas or No schema.
  • If the database has at least one contact or one campaign, the field is disabled, shows the current schema (or No schema) and the explanation "The schema can only be changed while the database has no contacts and no campaigns." appears below.

The reason for the lock: the values of dynamic fields are stored in the contacts under the field name, and filters, ordering and text placeholders of the campaigns refer to the fields by name. With a different schema you would be left with orphan values and filters that no longer find the field.

If the save is rejected, a red warning appears at the bottom: "The dynamic fields schema can only be changed if the database has no contacts: this one has …." or "The dynamic fields schema can only be changed if the database has no campaigns: this one has …, and their filters, sorting and texts refer to the fields of the schema." This can happen if in the meantime someone imported contacts or created a campaign. In that case the name may already have been saved.

Chose the wrong schema on a database already in use?

It cannot be changed. Create a new database with the right schema and import the contacts again.

Adding a contact by hand

Useful for entering a single contact without preparing a file.

  1. Press the person-with-+ icon on the database row.
  2. Fill in the fields. The group at the top contains the phone fields: at first you see a single field, the others (up to Phone 9; in an RPO database only Phone 1) appear when you press Add phone number. At least one phone number is required. All the other fields (contact details, address, the database's dynamic fields) are optional.
  3. If the database is used by at least one campaign, Also add to campaigns appears: tick the campaigns where you want to add the contact right away.
  4. Press Create.

What Thelgo checks:

  • phone numbers are cleaned: only the digits are kept, and a leading "+" becomes "00" (e.g. "+39 02 1234567" becomes "0039021234567");
  • none of the numbers entered may already be present, in any phone field, in another contact of the same database. Otherwise a red warning appears at the bottom, "Number already in the database: ….";
  • the number 9999999999 is reserved for anonymized contacts and cannot be entered: "The number … is reserved and cannot be used." appears.

Ticked campaigns receive the contact without filters

The campaigns you tick in Also add to campaigns receive the contact even if it does not meet the filters set on the campaign (e.g. a campaign limited to one ZIP code). Tick only the right campaigns.

For each ticked campaign Thelgo applies the contact blocks already active (if the contact falls within a block, it enters blocked) and starts an Ordering recalculation (you see it in Operations), so that the new contact finds its place in the campaign's ordering.

If you have connected external systems through webhooks, the entry generates the new contact event (see External API).

Exporting a database

Requires the "Download databases" permission (which can only be given to those who have the "Databases" permission).

To get all the contacts of a database in a file (for example for a check or to work on them in Excel):

  1. Press the Export database icon (down arrow) on the database row.
  2. Choose the format: Excel (.xlsx) or CSV (.csv).
  3. Press Export.

The popup (titled with the database name) offers the two formats Excel (.xlsx) and CSV (.csv) and the note "The file will be available for download from Logs → Operations once processing is complete."

The export starts in the background and the message "Export started. Check Logs → Operations to download the file." appears. When the status is Completed, the file is downloaded from the Operations page (type Database export) with the Download button: to download it you need both the "Operations" permission and the "Download databases" permission (without the latter the Download button does not appear on database exports, not even on those already generated). The file name is database-<database name>-<date and time>.xlsx (or .csv).

The file contains all the contacts of the database, without filters, with these columns:

Columns Content
Id The contact's identification number in Thelgo
Standard fields The same fields as the import, from Company name to Reference ID 2 (in an RPO database only Phone 1)
Dynamic fields One column for each field of the database's schema, if it has one

The CSV uses the semicolon as separator and is UTF-8, so it opens directly in Excel. The Excel file has a single sheet, called "Dati".

Very large databases

An Excel sheet cannot hold more than 1,048,576 rows. If the database has more contacts than fit (the rows are the contacts plus the header), in the popup the Excel (.xlsx) format is disabled, CSV (.csv) is already selected and the warning "This database has too many contacts for an Excel sheet (the limit is 1,048,576 rows): use the CSV format, which has no such limit." appears.

The export is recorded in the Audit log with the action Report exported, with the number of contacts exported.

Deleting a database

Deletion is final and removes, besides the database:

  • all its contacts;
  • all the campaigns that use it, with all the linked data: appointments, sent emails, calls.

For this reason Thelgo asks for an explicit confirmation:

  1. Press the trash can on the database row.
  2. Read the summary (e.g. "You are about to delete Clienti Nord and its 12,000 contacts, its 2 campaigns and all related data (appointments, sent emails, calls). This action cannot be undone.").
  3. To confirm, write the word delete in the box under "Type delete to confirm:" (upper and lower case do not matter; the word is in the interface language).
  4. Press Delete permanently.

The deletion continues in the background: you see a progress bar with the number of contacts deleted. When it finishes, the popup closes and the database disappears from the list. The operation stays recorded on the Operations page (type "Database deletion") and in the Audit log.

If the red warning "The deletion did not complete successfully. Check the operation log." appears at the bottom, check the Operations page: part of the data may already have been deleted.

To delete a person's data without deleting the database

If you only need to satisfy a request to delete personal data, you do not need to delete the database: you can anonymize single contacts, or many at once from a list of numbers.

The Not authorized blocks disappear with the database

The "Not authorized" block (the contact who asked not to be called any more) is recorded on the database contact. If you delete the database and then import the same numbers again, those contacts can be called again. Before deleting a database, consider whether you need to keep this information. The block can be removed from the contact details, but it cannot be recreated if you have deleted the database.

Public Opposition Register (RPO)

Anyone doing telemarketing to numbers taken from lists must check them against the Public Opposition Register (RPO), the register in which citizens ask not to receive commercial calls. In Thelgo the check is provided for the databases that require it, and is managed campaign by campaign.

RPO databases

A database is RPO only if you choose it at creation, with RPO database (Public Opposition Register) (from the Databases page or from step 1 of the import). The choice is final: the Databases page does not allow changing it afterwards (Edit database changes the name and the schema, not the RPO mode). If in doubt, create a new database instead of converting the existing one.

An RPO database:

  • allows only Phone 1: the other phone fields do not appear in the import, in Correct database, in manual entry and in contact editing (with the text "RPO database: only Phone1 is allowed."). If a contact has more than one number the save is rejected with "The database is set as "Do-Not-Call Registry": only one phone number is allowed.";
  • subjects its campaigns to the Register check: a campaign can be worked only if it has a validated, non-expired RPO list (or if the administrator has disabled the check for that campaign). Otherwise operators cannot take contacts and Thelgo answers "The RPO list is not validated or has expired: this campaign cannot be worked on.";
  • receives its contacts in campaigns already blocked for RPO: a contact added to a campaign of an RPO database stays uncallable until the next RPO list import confirms it free.

In the list, the RPO column shows Yes for these databases. In step 2 of the import, the Import type box reflects the choice made (Standard or Do-Not-Call Registry) and cannot be changed from there.

Extracting and importing the RPO list

The exchange with the Register is manual: Thelgo does not connect to the Register's servers. It is done from the page of each campaign that uses an RPO database, in the Public Opposition Register (RPO) section:

  1. Extract list: Thelgo generates a .zip file with the numbers (Phone 1) of the campaign's contacts, without the 0039 prefix. You download it from Operations (type RPO list extraction).
  2. You upload the file to the Register's official portal and wait for the reply (up to 24 hours, as indicated on the page).
  3. Import validated list: you upload the Register's reply file (.zip or .txt), indicate the Validity start and which contacts to exclude. Thelgo blocks for that campaign the contacts registered with the Register and unblocks the others. The operation appears in Operations as RPO list import.

Step-by-step instructions, the campaign statuses (Not applicable, Never validated, Valid, Expired, Check disabled) and the check that can be disabled for a single campaign are on the Public Opposition Register (RPO) page.

In the contact details a red box appears if the contact is registered with the Register. For a contact of an RPO database registered with the Register, the red box at the top reads, for example, "This contact is registered with the Public Opposition Registry (RPO) since …: whether it can be called in a given campaign depends on the rules chosen at the last RPO list import." The status belongs to the contact (it applies to all the campaigns of the same database), while the actual block depends on the campaign and on the exclusion mode chosen at the last import. RPO activities are recorded in the Audit log (extraction, import, enabling and disabling of the check).