Import and inspect prospects in Valkyrie Assist
Map a small CSV, review validation results, and inspect research records before CRM promotion.
Valkyrie Assist is a research workspace for prospects before and alongside reviewed CRM updates. Importing a list gives you records to inspect; it does not mean every row is a qualified lead or that the CRM has been updated.
Use a small Northgate ESD Packaging demo list first, such as a few fictional buyers researching protective packaging. This makes mapping mistakes easy to identify before a larger import.
Prepare the file
Use a CSV with clear headers and one person per row. Include an email column: the import wizard requires one column mapped to Email before validation can continue. Keep company, name, and other supported fields in separate columns.
Review the source list before uploading. Remove accidental duplicate rows and information you do not need for the research task. Use clearly fictional addresses in training files, such as addresses under example.com; do not turn a training exercise into a real outreach list.
Do not assume a source's job title or company description is current. Importing preserves useful research material, but a later reviewer still needs to assess its origin and freshness.
Map and validate
- Select the correct account.
- Open Valkyrie Assist > Import.
- Choose Choose a CSV file and select the prepared file.
- Compare each CSV Header and Sample with its Prospect Field mapping.
- Set unused columns to Ignore.
- Map the email column to Email.
- Choose Validate Rows.
Inspect the sample values closely. A column called “Name” might contain a company name rather than a person's name. Header suggestions help you start, but the sample is what shows whether the mapping makes sense.
Import the valid rows
- Review the number of rows ready to import and any row errors.
- Correct the source or mapping if the errors indicate a systematic problem.
- Choose Import … Prospects for the reviewed valid rows.
- Read the Import complete. totals.
- Open Prospects and inspect several imported records.
Do not equate the original file's row count with the number of newly created prospects. Validation and existing-record handling can affect the result. Use the reported totals and inspect the affected records before reporting success.
For Northgate, check that a fictional buyer's email, company, and intended packaging context stayed together. A successful import with misaligned fields is still a problem worth fixing before enrichment or CRM work.
Inspect the research record
A prospect detail includes Details, any Custom Fields, and AI Enrichment. Where relevant, it also shows journey origin or activity. These are separate sources of context: imported values, observed behavior, and generated research should not be treated as equally certain.
If the record shows Identity Unresolved, resolve the identity through the authorized workflow before attempting downstream work that depends on a linked person. A Possible Double CRM Delivery notice requires investigation before creating another contact or repeating a delivery.
Use Segments to return to useful subsets of the research list. Use Columns and Mappings when preparing a consistent enrichment and CRM field workflow rather than inventing a different field structure for each record.
Know what done looks like
The import is ready for the next stage when the totals are understood, sample records are accurate, and unresolved rows have a clear disposition. The next stage may be enrichment, identity review, or CRM promotion; it is not automatically outreach.
The CRM remains the contact system of record. Keep research and proposed changes reviewable in Valkyrie until the appropriate person has checked them and confirmed the intended destination.