Skip to content
English navigation, shared controls and page contents.

CSV import rules: what gets rejected and why

Last verified 2026-07-01

Bad data quietly ruins outreach: bounced sends, broken personalization, embarrassing messages. Every imported row is validated before it can be saved. Rows that fail are reported with the reason, never silently dropped.

What a row needs

  • A way to reach the person: a valid email address or a valid LinkedIn URL.
  • Email must be a real address shape; web addresses must start with http or https.
  • Phone numbers must include the country code, e.g. +1 415 555 0123.

What gets rejected

  • Invalid filler values: literal "undefined", "null", "n/a", or whitespace-only fields.
  • Machine-generated filler text that no team member wrote.
  • Stylized lookalike letters (such as 𝐀𝐜𝐦𝐞) that can disguise the original text.
Duplicates are combined automatically. Contacts are matched by email, LinkedIn profile, or consistently formatted international phone number, so the same person imported twice stays one record.
Was this helpful?

Still stuck? hello@klosent.com. Our support team can help.