Prepare records for the next action
Use this workflow when RevDesk needs a controlled list of people or organizations before calling, messaging, or assigning work. The result is not a large database; it is an eligible, deduplicated audience with enough context to take the next approved action.Prerequisites
- An approved source such as Deal Operations, a verified CRM integration, or an imported list
- A named owner for field definitions and duplicate handling
- Documented eligibility, exclusion, consent, and suppression rules
- A defined downstream workflow and the fields it actually needs
Trigger and input
Choose one source and one trigger for the first launch. Examples include a saved CRM segment, a scheduled approved-list import, or a new record from a connected form. Record the source, import time, and applicable consent context so operators can explain why a person entered the audience.Controls
- Define required fields separately from optional enrichment.
- Match records using stable identifiers before creating a new contact or company.
- Exclude opt-outs, blocked records, existing customers when inappropriate, and records outside the approved geography or business criteria.
- Do not infer sensitive data or use a field merely because it is available.
- Decide which system owns each field and where corrections must be made.
Launch
- Build a small segment containing known matches, duplicates, exclusions, and incomplete records.
- Map only the fields needed by the downstream task.
- Preview which records will be created, updated, skipped, or flagged for review.
- Run the audience build without starting outreach.
- Review the result with the business owner, then enable the downstream workflow separately.
Verify
Confirm that eligible records appear once, excluded records do not enter the task, source attribution is preserved, and updates land in the agreed system. Open several records from each result category instead of checking only totals.Measure
Track eligible records, duplicates prevented, excluded records, records requiring review, and the share with all downstream-required fields. Treat contact or booking outcomes as measures of the later workflow, not of enrichment itself.Troubleshooting
- Too many duplicates: tighten matching rules and resolve the owning-system identifiers.
- Unexpected exclusions: inspect the source segment, consent state, and suppression reason.
- Fields revert later: two systems probably claim ownership; choose one write direction.
- Outreach starts too early: separate audience preparation from task activation and require review.