Zum Inhalt springen
Leitfäden 7. November 2026 10 Mindestlesezeit

Call List Hygiene: Clean a List Before Dialing

A step-by-step checklist to clean a call list before dialing: E.164 formatting, deduplication, validation, DNC and consent scrubs, field mapping and upkeep.

D
7. November 2026

Kurze Antwort

To clean a call list, normalise every number to E.164, then deduplicate, then validate structure and line type, then scrub against DNC lists and consent records, then check for reassigned numbers where a database exists. Map region, time zone, language and consent source, segment by source and age, and keep the raw file. Re-check at dial time, because a list goes stale.

A dialer treats every row as a call to place. A row with a malformed number wastes a dial, a duplicate calls the same person twice, a number on a do-not-call list creates a complaint, and a row with no time zone gets dialed at the wrong hour. The list is the cheapest place to fix all of these, because at that point nothing has happened yet.

This is a step-by-step checklist, written from the contact-centre side. It does not cover finding or buying data; for enrichment, see skip tracing and lead list enrichment, and for the wider tactics, Wie man die Quote ausgehender Kontakte verbessert.

What list hygiene is, and why the dialer pays for bad rows

List hygiene is the set of checks that turns a raw file (an export, a purchased list, a spreadsheet from sales) into rows the dialer can use safely. The dialer pays for a bad row in three ways: a wasted dial (a number that cannot ring), a wasted agent minute (a wrong or duplicate contact) and a compliance risk (a number that should never have been called).

Two habits underpin everything below. Keep the raw file untouched and work on a copy. And log how many rows each step removes or changes, so you can see what the file was really like and spot a source that is consistently poor.

Step 1: normalise every number to E.164

Numbers arrive as "0790 123 456", "(079) 0123456", "+962 7 9012 3456", "00962790123456" and with extensions in the same cell. The first job is one format for all.

E.164 is the ITU-T recommendation titled "The international public telecommunication numbering plan"; the ITU page lists the current edition as E.164 (02/26), in force (ITU-T E.164, checked November 7, 2026). In dialer practice, an E.164 number is the plus sign, the country code and the national number with no spaces, brackets or dashes. Google's libphonenumber library, for example, can output numbers in E.164 style such as +41446681800 from the national form "044 668 18 00" plus a region (libphonenumber, checked November 7, 2026).

Points to settle:

  • Default region. A number without a country code can only be parsed if you tell the parser which country to assume. Use the file's known country per row, not a global default, when the file mixes countries.
  • Trunk prefixes. Many countries write a leading 0 nationally that is dropped internationally. A parser that knows the region handles this; a find-and-replace does not.
  • Extensions and notes. Move "ext. 214" or "after 5pm" into a separate field. Do not leave them inside the number.
  • Rows that will not parse. Send them to a reject file with the reason. Do not guess.

Step 2: deduplicate after normalising, not before

The same phone appears in many spellings, so a duplicate check on the raw text misses most duplicates. Normalise first, then compare.

Raw value (illustrative)After normalising
0790 123 456+962790123456
079-0123456+962790123456
00962 79 0123 456+962790123456

Three rows became one. Decide the rule for what survives: usually the row with the most recent activity, the most complete fields or a consent record. Also decide what to do when one number belongs to two different named contacts (a shared household or switchboard). Often the right answer is to keep both records, but to limit attempts to the number as a whole, so one phone is not called twice in a day.

Step 3: validate structure and line type

After normalising, check that each number is plausible. A library such as libphonenumber offers a validity test, which checks length and prefix rules for the region, and a faster "possible" test that checks length only. It can also report a number type, such as fixed-line, mobile, toll-free or premium rate, where it is feasible to tell (libphonenumber, checked November 7, 2026).

What these checks do and do not do:

  • They catch obvious errors: too short, too long, impossible prefix.
  • They tell you the type of number, which matters for pacing, for message channels and for rules that treat mobile and fixed lines differently.
  • They do not tell you whether the line is connected or who holds it. That needs a live check against the network or a data provider, which is a separate service.
  • Premium-rate numbers in a customer list are usually a data error. Review them rather than dial them.

Step 4: scrub DNC and consent before import, and again at dial time

Compare each number with your internal do-not-call list, the relevant national registers and your own records of consent and opt-out. For the rules and how to set them, see calling hours, DNC and consent rules, Einwilligungsmanagement und die DNC glossary entry.

Run the scrub twice. Before import it keeps suppressed numbers out of the list. At the moment of the call it catches numbers that joined the list since. A number added to your DNC list this morning should still be blocked on a file uploaded last week. Scrub against the normalised number, never the raw text, or formatting differences will let suppressed numbers through.

If you are not sure where you stand, the Checkliste DNC und Einwilligungsbereitschaft is a short way to find the gaps.

Step 5: reassigned numbers, where a national database exists

Phone numbers are recycled. A person who consented in 2022 may have given up the number, and the person who has it now has consented to nothing. In the United States, the Reassigned Numbers Database lets callers query numbers before calling or texting to find those reassigned from a previous consumer. Service providers submit monthly reports of permanently disconnected numbers to it, and the site describes it as a way to help avoid calls to people who have not given permission (reassigned.us, checked November 7, 2026).

Outside the US, find out whether your country has an equivalent. Whatever the country, apply the principle: the older the consent, the more likely the number now belongs to someone else. Re-check older records before dialing them, and prefer fresh consent where you can get it.

Step 6: map the fields the dialer needs

A number alone is not enough. The dialer needs these to behave properly:

  • Region and time zone. A calling window is the customer's local time. DialerBee's compliance page notes that for US calling, the time zone follows the number. For other countries, hold the region on the row.
  • Sprache. So the contact reaches an agent or voice who speaks it.
  • Consent source and date. Where the permission came from and when, so you can prove it and age it.
  • Source and import date. For segmentation (next step) and for tracing problems back.
  • Your own custom fields. Account balance, appointment date, product. These feed scripts and routing.

Check the column mapping on a preview before writing anything. A column that lands in the wrong field, unnoticed, can spoil a whole campaign.

Step 7: segment by list source and age

Do not pour all rows into one list. A list from last week's web form and a list from three years ago behave differently, and so do numbers from different suppliers. Keep a source and an import date on every row, and run reports by both. Over time you learn which sources produce contacts and which produce rejects.

Age matters twice: contact data decays, and consent weakens with time. Put older segments through the reassigned-number check and a refreshed DNC scrub before you work them.

Keeping a list clean: suppression from dispositions and deliberate resets

A clean list does not stay clean. Feed the outcome of each call back into it:

  • A wrong-number disposition suppresses that number for that contact.
  • A refusal or do-not-call request suppresses the number everywhere, at once.
  • A number that never connects after the permitted attempts is closed or rested; see call retry strategy by disposition.
  • A stale list is reset deliberately, not re-imported. Re-importing brings back the numbers you removed.

If your list comes from a CRM, close the loop in the other direction too: write dispositions back so the source stops sending the same bad rows. See CRM integration setup for an outbound dialer.

Import checklist in DialerBee

The product pages state the following:

  • Lead management imports CSV and XLSX files and shows a preview of how each column mapped to a lead field or custom field before anything is written, so you fix a bad mapping on the screen and not in the dialed list.
  • A do-not-call scrub runs on import, so suppressed numbers do not enter the list.
  • Custom fields come through the import and appear in the agent desktop.
  • Max attempts and a retry delay are set per list, and stale contacts can be reset deliberately.
  • Der compliance page describes a phone format rule that checks numbers against the expected format before they are dialed, so a malformed row in an imported list is caught rather than dialed, and a DNC check at the call itself.

These are compliance-supporting controls. They do not replace cleaning your file before it reaches the dialer, and they do not decide what your consent records must contain; that is for you and your counsel.

A one-page import checklist

  1. Keep the raw file; work on a copy.
  2. Parse every number with the right region; send failures to a reject file.
  3. Output E.164; move extensions and notes to their own fields.
  4. Deduplicate on the normalised number.
  5. Run structural validation and read the number type.
  6. Scrub DNC and consent; log the count removed.
  7. Check reassigned numbers where a database exists.
  8. Fill region, time zone, language, consent source and date.
  9. Tag source and import date.
  10. Preview the mapping, then import.
  11. Record how many rows each step removed, and review the source if the rate is high.

Häufig gestellte Fragen

How do I clean a call list before dialing?

Work in a fixed order: normalise every number to E.164, deduplicate after normalising, validate structure and line type, scrub against do-not-call lists and consent records, check for reassigned numbers where a database exists, map the fields the dialer needs, and segment by source and age. Keep the raw file untouched and log what each step removed.

What is E.164 and why use it for a dialer list?

E.164 is the ITU-T international public telecommunication numbering plan. In practice, an E.164 number is written with a leading plus sign, the country code and the national number, with no spaces or punctuation, such as +41446681800. One format for every row means the dialer, the DNC check and the deduplication all compare like with like.

Why deduplicate after normalising rather than before?

Because the same number is written many ways. 0790 123 456, 079-0123456 and +962 79 0123 456 look like three different strings but may be one phone. If you deduplicate first, they all survive, and the contact is called three times. Normalise first so identical numbers become identical strings, then remove the duplicates.

Is a valid number the same as a live number?

No. A structural check, such as a library's validity test, tells you whether the number fits the length and prefix rules of a country. It does not tell you whether the line is connected or who holds it today. Treat structural checks as a filter for obvious errors, not as proof that someone will answer.

What is a reassigned number and how do I check for one?

A reassigned number is one that was disconnected and later given to a new person, so your consent record belongs to someone else. In the US, the Reassigned Numbers Database lets callers query numbers before calling. Outside the US, check whether your country has an equivalent, and refresh older lists before you dial them.

Should DNC be checked at import or at dial time?

Both. A scrub on import keeps suppressed numbers from entering the list. A check at the moment of the call catches numbers added to the DNC list after the import. DialerBee describes a scrub on import in lead management and a per-call check in compliance.

Quellen

  1. ITU-T Recommendation E.164, The international public telecommunication numbering plan. itu.int/rec/T-REC-E.164 (checked November 7, 2026).
  2. Google libphonenumber, a library for parsing, formatting and validating international phone numbers. github.com/google/libphonenumber (checked November 7, 2026).
  3. Reassigned Numbers Database (United States). reassigned.us (checked November 7, 2026).

Weiterführende Lektüre

Haftungsausschluss: This article is general information, not legal advice. DialerBee does not provide legal advice or guarantee regulatory compliance. Confirm the rules for your markets, including DNC and consent requirements, with qualified counsel and the competent authority.

Weiterführende Lektüre: What Is Number Portability?

Bereit, DialerBee in Aktion zu sehen?

Fordern Sie eine 15-minütige Live-Demo an oder starten Sie eine 14-tägige kostenlose Testphase – ohne Folien, ohne Verpflichtung. Das Telefonieren beginnt, sobald Ihr eigener SIP-Trunk oder Ihre TK-Anlage verbunden und freigegeben ist.

14-tägige kostenlose Testphase · kostenloses KI-Guthaben · keine Kreditkarte · 11 Sprachen · BYOC · Kontrollen zur Unterstützung der Compliance

Vollständige Website auf Englisch ansehen →