Client referential import Formats, column mapping and rejections
The client referential joins your own contacts to the analysed calls: the phone number is the join key, every other column becomes a client attribute. The import parses the file in the browser and prepares the rows before anything is stored.
Formats and column mapping
A CSV or XLSX file up to 10 MB is accepted. CSV bytes are decoded before parsing, so accented exports from any spreadsheet keep their characters. Only the first sheet of a workbook is read; the interface warns you when several exist.
The mapping step assigns a role to each column: phone (the join key), name, attribute, or ignore. A phone-like and a name-like header are pre-selected; you adjust every role before verifying the file.
Numbers without an area code: manual column and prefix
Some exports list numbers stripped of their leading area code, so no column is recognised as a phone. When that happens, you designate the phone column by hand and add a prefix applied to every non-empty number before it is normalised.
- Prefix example. A file whose numbers dropped their "02" is fixed with the prefix "02", concatenated in front of each cell.
- Empty cell. An empty phone cell stays empty, never turned into the prefix alone, and its row is rejected with an "empty number" reason.
Sample file
A sample CSV downloads from the import screen: the canonical headers (Téléphone, Nom) and one attribute column, over two example rows. It is a ready template whose headers the automatic detection recognises.
Motivated rejections
Every dropped row carries the reason it was rejected, never a silent loss. The preview counts them, lists the first ones, and the full list downloads as a CSV — source line, content, reason — so it can be corrected offline and re-imported.
- Invalid number. A number that cannot be normalised is rejected; a prefix that produces an invalid number names the derived value in the reason.
- Oversized cell. A row with a name or attribute cell over the length limit is rejected, with the column and the actual length in the reason.
Import limits and deduplication
Two kinds of limit keep every stored value bounded. Structural limits block verification until you fix the mapping; a cell limit rejects the offending row alone.
20 attribute columns
Set the surplus columns to "ignore" to pass verification.
64-character header
A longer attribute header blocks verification.
256-character cell
A longer name or attribute cell rejects its row.
Numbers appearing several times are deduplicated on the phone key: the last occurrence wins, and the preview reports how many duplicates were merged.
Join cap and incomplete referential
The referential loaded for the join holds up to 20,000 contacts. Beyond that, a banner on the client panel states that the referential exceeds the loaded cap and the join is incomplete, rather than showing partial matches without saying so.
Back to the documentation
The client referential enriches every analysed call with your own attributes. See how the same page prices and tracks your call handling cost.