Can Unify’s AI Send Emails to Contacts From Events or Other Sources?
Yes. Contacts acquired from events or other external sources can be imported into Unify and used in an AI-assisted email workflow. Importing the contacts and enrolling them into a sequence are separate actions. Verify the records, source context, recipient drafts, sender, and outreach eligibility before starting the sequence.
The supported route is to bring in the data through an appropriate import or integration, prepare the audience and copy, and review the enrollment path. An uploaded file is not automatically a sent campaign, and an event source does not by itself establish that every contact should receive outreach.
Import and inspect the external contacts
Unify’s CSV import guide documents CSV headers and a 20 MB upload limit. Company records use a domain for matching; people use an email address. Review the mapping carefully because imported values can update mapped fields on existing matched records.
Keep useful event or source context in appropriate fields, and inspect required custom fields before importing. If the workflow uses optional email enrichment, the documented inputs include first name, last name, and company domain. Enrichment does not guarantee a result; review the applicable credit behavior and the actual output.
After import, inspect the Activity report and any skipped or invalid rows. Reconcile the intended audience to the records that actually arrived. Import completion is a record-processing result, not proof that every row is eligible for a sequence.
For a custom integration, consult the Data API overview and record upsert documentation. Use the supported record and list operations rather than assuming that uploading a file to a chat creates the same saved audience.
Preserve context that the email can truthfully use
Record where the contact came from and what information supports the proposed message. Keep the actual relationship distinct from assumptions about attendance, interest, or a conversation. AI-generated copy should not invent a meeting or imply that a person requested follow-up when the source does not establish it.
Use Chat to work with the audience and request the desired drafting approach. Explain the source, the intended recipient, and which facts may be used. Ask for review before activation when using a workflow that supports that review.
The guide to CSV custom variables in sequences covers using imported fields in messages. Verify the actual recipient values and fallbacks; a correctly named variable can still contain missing or unsuitable data.
Review drafts through the correct enrollment path
Unify’s agentic sequence documentation describes generating recipient-level drafts through Chat or list workflows and reviewing them before enrollment. It also documents a person-record enrollment path that starts without a separate draft approval step. Choose the path that matches your required review process.
Review the generated message for the actual recipient. A template preview does not establish the final personalized draft. Check the source reference, claims, tone, and next step, and correct unsupported personalization before the message becomes eligible to send.
The sequence must be published and the sending mailbox connected for the documented workflow. Confirm the sender and account context rather than assuming the imported owner field selects the intended mailbox.
If the sequence already has active recipients, consult the guide to editing a live sequence before changing shared content. Treat the existing enrollment state and the new imported audience as separate review scopes.
Check eligibility before activation
Inspect sequence exclusions, relevant engagement policies, existing enrollments, and required fields. Resolve the underlying reason for an ineligible contact rather than using another import or enrollment route to bypass it.
Review the enrollment documentation for the applicable lifecycle controls. A contact that exists in a list is not necessarily ready to receive another message. Confirm ownership and current conversation context before activating the audience.
The turn research into outreach motion provides a broader workflow for translating context into a message. Use it after the underlying records and eligibility have been reviewed, not as a substitute for those checks.
Use a pre-enrollment checklist
This blank checklist records the required review without inventing a completed import or campaign result. Keep evidence references in an approved location and assign an owner to unresolved items.
| Review item | What to inspect | Observed result |
|---|---|---|
| Identity and import | Intended people, matched records, and skipped rows | |
| Source context | Verified event or external-source facts | |
| Personalization fields | Actual recipient values and missing information | |
| Copy approval | Final recipient draft and accountable reviewer | |
| Sender | Connected mailbox and intended sending identity | |
| Eligibility | Exclusions, policies, active enrollment, and required fields | |
| Enrollment decision | Approved audience and activation path |
If reporting review completion, use the saved intended audience as the population and denominator. Count only records whose required checks are accepted in the numerator, report unresolved records separately, and use not applicable when the denominator is zero.
Verify what happened after enrollment
Inspect the enrolled audience and actual status. Queued does not mean sent: sending windows, capacity, and other applicable controls can affect execution. Keep import, drafting, enrollment, sending, and replies as separate states when reporting the campaign.
Review exceptions with the responsible owner. If a record failed import, fix the record issue. If a draft is unsuitable, correct the copy. If a contact is ineligible, resolve or respect the applicable restriction. These are different problems and should not be hidden in a single campaign-complete label.
Frequently asked questions
Does importing event contacts automatically send emails?
No. Import creates or updates records under the import rules. Preparing drafts and enrolling contacts into a sequence are separate steps. Review the audience, sender, copy, and eligibility before activation.
Can AI use the event context in the email?
Yes, when the context is supplied through supported fields or instructions and accurately reflects the source. Inspect the actual recipient draft and remove claims about attendance, conversations, or interest that the evidence does not support.
Can recipient drafts be reviewed before enrollment?
The documented Chat and list workflows support recipient-draft review. The person-record route starts without a separate approval step, so choose the workflow that matches your team’s review requirements.
Why might an enrolled contact not receive an immediate email?
Enrollment and sending are different states. Applicable sending windows, capacity, eligibility controls, or missing requirements can affect execution. Inspect the actual enrollment and send status instead of treating queued work as a completed send.
