Review enrichment and CRM writebacks

Valkyrie Assist keeps imported and enriched values available for review before they become CRM changes. Use the Review workspace to compare evidence, resolve conflicts, and inspect the complete proposed writeback batch.

For Northgate ESD Packaging, a useful enrichment might identify a prospect's packaging application. That is still a candidate finding until someone checks its source and decides whether it belongs in the contact system of record.

#Review enrichment where it was produced

1. Open Valkyrie Assist > Prospects.
2. Open the intended prospect.
3. Read AI Enrichment and the status of the relevant column.
4. Inspect the result and its supporting context before accepting its meaning.
5. Use the column's run or re-run control only when new research is needed and the account's allowance permits it.

A completed enrichment run means a result was produced, not that every statement is correct. Check that the result refers to the intended person and company. Prefer a specific supported value over a plausible but unverified description.

If identity is unresolved, address that first. Research attached to the wrong person can produce a convincing-looking but incorrect CRM update.

#Compare candidate fields

1. Open Review.
2. Locate the relevant prospect and field.
3. Compare Current CRM Value with Candidate Value.
4. Inspect Origin, Observed, Conflict, and Status.
5. Approve or reject candidates according to the evidence.

The optional Imported Value column can help explain how the current candidate differs from the original import. Use it when tracing a disagreement rather than assuming the newest value is automatically best.

For example, Northgate's research may suggest a company application while the CRM already has a value entered by a salesperson. Read the evidence and preserve the authoritative existing information unless the appropriate correction workflow supports a reviewed change.

#Inspect the whole writeback batch

1. Select the relevant candidate fields or prospects.
2. Choose Create Writeback Batch.
3. Read every item in the Writeback Batch preview.
4. Compare CRM Value At Preview with Value To Write.
5. Remove or resolve inappropriate items before proceeding.
6. Choose Confirm Batch only after the complete preview matches your intent.

Batch creation collects reviewable candidates for the selected prospects. Do not assume that checking one field guarantees the preview contains only that one field. The batch preview is the final description of what you are about to queue.

The confirmation uses an overwrite-empty-only policy. Its purpose is to fill eligible empty CRM fields rather than silently replace established values. The preview and current destination state still matter; a field may be skipped or fail instead of being written.

#Check the result

Review Written, Skipped, and Failed totals, then inspect individual item statuses and errors. A confirmed batch is queued work; it is not proof that every candidate reached the CRM.

A skipped item may reflect the policy or a changed destination value. Investigate that result before trying to force the original value through. A failed item needs its error understood and corrected; repeated batches can make the history harder to interpret.

Prospects without a linked CRM contact are excluded from writeback batches. Use the appropriate identity and promotion workflow first rather than expecting the writeback operation to create a missing contact implicitly.

#Know what done looks like

Completion means the reviewed batch has an understood result and the intended eligible values are present in the correct CRM record. Keep research that was rejected or remains uncertain out of that record.

Record the batch and any unresolved item for the next operator. This preserves the distinction between a research finding, a human review decision, and an actual CRM change.

#Related articles

• Import and inspect prospects
• Use Pulse and check form delivery
• Complete a first review without publishing