Rather than making you resolve every problem before importing, EasyDigz fixes what it can and shows you what it did. The review step is a summary, not a task list.
#What gets fixed
| Problem | What happens |
|---|---|
| No name | One is generated from the email address, or a placeholder such as "Contact Row 5". The row is never dropped for this |
| Malformed email | Repaired automatically where possible, a missing @ becomes a sensible address. If it cannot be safely repaired, it is cleared rather than replaced with a made-up one |
| No email, but a phone | Nothing is invented. The row is imported and flagged No email, this contact cannot be emailed |
| A phone, but no email | Nothing is invented. The row is imported and flagged No phone, this contact cannot be called |
| No email and no phone | Nothing is invented. The row is flagged Cannot be contacted and still imported so the record is not lost |
| The same email twice in your file | The first occurrence keeps the real email; every later duplicate has its email cleared, never replaced with a new made-up one |
| Email already in your database | Never auto-resolved, you choose Merge (update the existing account) or Skip (leave it untouched) for each match |
| Badly formatted phone | Reformatted where possible. A phone over 20 characters keeps everything up to the limit and only trims the extra digits at the end, it is never fully replaced |
| Duplicate phone numbers | Cleared if the row also has an email; if it has neither, a new number is generated so the row still has one way to be reached |
| Unrecognisable birthdate | Cleared |
| Secondary phone problems | Same treatment as the main phone number, trimmed or reformatted where possible, cleared where not |
| Invalid firm email | Same treatment as the main email, repaired where possible, otherwise cleared |
| Invalid website | A bare domain gets https:// added automatically; anything else that still is not a real URL is cleared |
| Invalid employee count | Cleaned up to a plain whole number where one can be salvaged, cleared if nothing numeric is there at all |
A missing email or phone would normally block an import. Here the row still comes in, flagged for you to see, rather than being dropped or filled in with a fake value.
#Rows with no way to reach them
Rather than inventing a placeholder address, EasyDigz keeps the row exactly as it was and marks it Cannot be contacted in review, in the import preview, and with a tag next to the name in your Accounts list. Its account page shows a warning banner that disappears as soon as you add a real email or phone and save.
A made-up email bounces the first time you send to it, and enough bounces pause your campaigns and hurt the reputation of your sending domain. A blank is honest, and safe.
#Reviewing before you commit
The review table lists every affected row with a plain description, "Duplicate email, cleared", "Name missing, generated", "Invalid phone, trimmed", "No email, cannot be emailed", "No phone, cannot be called", "No email or phone, cannot be contacted". Rows with no way to be contacted are sorted to the top so you see them first rather than finding them on page nine.
A flagged missing email or phone is a warning, not a blocker. The row imports as it is, and you can click its empty Email or Phone cell to type the real value in before you import.
You can edit any row inline, or remove a row from the import entirely, and undo the removal if you change your mind.
#When to intervene
| Leave it | Fix it |
|---|---|
| Cleared birthdates you were never going to use | A generated name for someone important, set the real one |
| Cleared duplicate phone numbers | A "Cannot be contacted" row for an active client, add their real email or phone by hand |
| Placeholder names on cold rows | Anything you plan to email this week |
#Editing an email by hand
If you edit an email during review, it is validated strictly, remove the @ and you get a clear error and cannot save. Automatic fixes are generous; your own typing is checked.