Build an event audience and sales handoff

Why use this

1. An event organizer may need a regional audience list that reflects both contact eligibility and salesperson ownership. Separate CRM views can produce duplicates, stale ownership or contacts whose relationship to the event is unclear.

2. This job could prepare a reviewable audience and handoff package with the selection reasons visible. Clear ownership and exclusions help the team decide who should handle outreach before any lists are distributed.

Why an agent / simpler alternative

Useful judgment

Reconcile contact, opportunity and region evidence while preserving ambiguous eligibility or ownership.

Simpler alternative

Use a saved CRM report when fields and ownership rules are complete and stable.

Unsuitable when

The task requires contacting people without permission or inferring sensitive characteristics for targeting.

Proposed inputs

1. Name

   Event criteria

   Owner

   Event owner

   Minimum scope

   Region, intended audience and allowed selection rules

   Quality check

   Specify exclusions and consent requirements

2. Name

   CRM extract

   Owner

   Authorized sales operations owner

   Minimum scope

   Necessary contact IDs, account links and owner fields

   Quality check

   Check freshness, duplicate identities and permission scope

Access and setup — proposed or unknown

Proposed minimum

1. Read a limited approved extract and prepare private handoff drafts; no live CRM writes or messaging.

Compatibility unknowns

1. CRM schema, regional field meaning, sharing permissions and exact runtime compatibility are unknown.

External actions requiring approval

1. Distributing personal contact lists, posting to coordination channels, changing records and outreach require approval.

Expected deliverable and review checks

Proposed artifact

Proposed audience list with inclusion reason, account/opportunity link, responsible owner and unresolved exceptions.

Critical checks

1. Deduplicate by verified identity; check region evidence and exclusions; confirm each recipient's access to their subset.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   Contact location differs from account region

   Why it matters

   The selection rule may be applied inconsistently

   Proposed response

   Show both values and request the event owner's rule.

2. Signal

   Two salespeople claim the same contact

   Why it matters

   The handoff can trigger duplicate outreach

   Proposed response

   Leave ownership unresolved until reconciled.

Effort and cost — unknown

Setup work

1. Define eligibility and minimum handoff fields.

Ongoing review

1. Review exceptions and refresh ownership before use.

Unknowns

1. CRM field quality, consent evidence, coordination effort and service costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent six CRM contacts with a duplicate, an excluded entry and conflicting regional ownership; prepare a dry-run selection.

Acceptance checks

1. Explain inclusion/exclusion; flag ownership conflicts; keep lists private; generate no outreach.

Stop conditions

1. Stop if consent or audience permissions are unclear or distribution needs new authorization.

Limits

1. CRM inclusion is not proof of invitation consent, current interest or event attendance.