How AIVA Works Under the Hood
A step-by-step deep dive into how AIVA operates, executing campaigns, drafting emails, verifying contacts, and synchronizing with your CRM in real time.
Connect Your Core Systems
AIVA works best when it is connected to the systems that support outbound execution. Start by connecting your sending mailboxes, CRM, calendar or meeting setup, LinkedIn where supported, and workspace controls.
This setup helps AIVA understand which accounts can be used, which systems are available, and what rules should guide outreach before campaigns begin.
Setup areas:
- Mailboxes — Connect sending mailboxes and manage sender readiness.
- CRM — Connect CRM where configured to support activity, replies, meetings, and handoff continuity.
- Calendar / Meetings — Connect Google Calendar and Google Meet where supported for booking and meeting creation.
- LinkedIn — Connect LinkedIn where supported and configured for multi-channel workflows.
- Workspace Controls — Set roles, approvals, and access controls where needed.
Connect Your Core Systems
AIVA works best when it is connected to the systems that support outbound execution. Start by connecting your sending mailboxes, CRM, calendar or meeting setup, LinkedIn where supported, and workspace controls.
This setup helps AIVA understand which accounts can be used, which systems are available, and what rules should guide outreach before campaigns begin.
Setup areas:
- Mailboxes — Connect sending mailboxes and manage sender readiness.
- CRM — Connect CRM where configured to support activity, replies, meetings, and handoff continuity.
- Calendar / Meetings — Connect Google Calendar and Google Meet where supported for booking and meeting creation.
- LinkedIn — Connect LinkedIn where supported and configured for multi-channel workflows.
- Workspace Controls — Set roles, approvals, and access controls where needed.

Find, Import, and Prepare Leads
AIVA helps your team start with the right prospects before outreach begins. You can discover leads from the built-in Lead Database, import existing lists, use CRM data where configured, or organize saved lists for campaign use.
Before a lead enters a campaign, AIVA helps prepare it with useful readiness signals such as enrichment, verification, deduplication, suppression checks, and campaign eligibility.
Lead preparation actions:
- Search / Find Leads — Discover prospects from the built-in Lead Database.
- Import Leads — Bring leads from CSV or connected systems where configured.
- Save Lists — Organize prospects into lead lists for campaigns.
- Enrich — Add useful business context where available.
- Verify — Check email and contact readiness where supported.
- Dedupe — Reduce duplicate outreach risk.
- Suppress — Respect unsubscribes, exclusions, and do‑not‑contact states.
- Check Eligibility — See which leads are ready for campaign use.
Find, Import, and Prepare Leads
AIVA helps your team start with the right prospects before outreach begins. You can discover leads from the built-in Lead Database, import existing lists, use CRM data where configured, or organize saved lists for campaign use.
Before a lead enters a campaign, AIVA helps prepare it with useful readiness signals such as enrichment, verification, deduplication, suppression checks, and campaign eligibility.
Lead preparation actions:
- Search / Find Leads — Discover prospects from the built-in Lead Database.
- Import Leads — Bring leads from CSV or connected systems where configured.
- Save Lists — Organize prospects into lead lists for campaigns.
- Enrich — Add useful business context where available.
- Verify — Check email and contact readiness where supported.
- Dedupe — Reduce duplicate outreach risk.
- Suppress — Respect unsubscribes, exclusions, and do‑not‑contact states.
- Check Eligibility — See which leads are ready for campaign use.

Build or Select a Playbook
Before AIVA launches outreach, your team defines the strategy it should follow. A Playbook gives AIVA the reusable outbound direction for who to target, what to say, which channels to use, and how the sequence should run.
You can create a new Playbook or select an existing one, then use it as the foundation for future campaigns.
Playbook includes:
- ICP — Defines who the campaign should target.
- Pitch — Defines the value AIVA should communicate.
- Templates — Provides starting structure for messages.
- Sequence — Sets Email, LinkedIn, waits, follow-ups, and InMail where supported.
- Tone — Guides how messages should sound.
- CTA — Defines what action the prospect should take.
- Personalization Direction — Decides which signals should guide personalization.
- Learning — Helps AIVA reuse or improve strategy from past performance.
Build or Select a Playbook
Before AIVA launches outreach, your team defines the strategy it should follow. A Playbook gives AIVA the reusable outbound direction for who to target, what to say, which channels to use, and how the sequence should run.
You can create a new Playbook or select an existing one, then use it as the foundation for future campaigns.
Playbook includes:
- ICP — Defines who the campaign should target.
- Pitch — Defines the value AIVA should communicate.
- Templates — Provides starting structure for messages.
- Sequence — Sets Email, LinkedIn, waits, follow-ups, and InMail where supported.
- Tone — Guides how messages should sound.
- CTA — Defines what action the prospect should take.
- Personalization Direction — Decides which signals should guide personalization.
- Learning — Helps AIVA reuse or improve strategy from past performance.

Launch a Multi-Channel Campaign
Once your leads and Playbook are ready, AIVA helps your team set up a campaign for execution. Select the lead list, choose the Playbook, confirm the channels, assign sending accounts, set the schedule, and review the approval rules before launch.
This step turns strategy into a live outbound workflow across Email and LinkedIn where supported, while keeping campaign setup, account readiness, and launch checks clear before execution begins.
Campaign setup includes:
- Lead List — Choose the prospects that should enter the campaign.
- Playbook — Select the outbound strategy AIVA should follow.
- Channels — Use Email, LinkedIn, and InMail where supported and configured.
- Sending Accounts — Assign eligible mailboxes or connected accounts.
- Schedule — Define when the campaign should run.
- Routing / Fallback Rules — Decide how AIVA should handle channel availability or blocked steps.
- Approval Rules — Confirm whether drafts need review before sending.
- Launch Readiness — Review blockers, warnings, and setup status before launch.
Launch a Multi-Channel Campaign
Once your leads and Playbook are ready, AIVA helps your team set up a campaign for execution. Select the lead list, choose the Playbook, confirm the channels, assign sending accounts, set the schedule, and review the approval rules before launch.
This step turns strategy into a live outbound workflow across Email and LinkedIn where supported, while keeping campaign setup, account readiness, and launch checks clear before execution begins.
Campaign setup includes:
- Lead List — Choose the prospects that should enter the campaign.
- Playbook — Select the outbound strategy AIVA should follow.
- Channels — Use Email, LinkedIn, and InMail where supported and configured.
- Sending Accounts — Assign eligible mailboxes or connected accounts.
- Schedule — Define when the campaign should run.
- Routing / Fallback Rules — Decide how AIVA should handle channel availability or blocked steps.
- Approval Rules — Confirm whether drafts need review before sending.
- Launch Readiness — Review blockers, warnings, and setup status before launch.

Generate Verified Channel-Aware Drafts
After the campaign is set up, AIVA helps generate outbound drafts based on the selected leads, Playbook strategy, campaign sequence, channel rules, and available personalization signals.
Instead of creating one generic message, AIVA prepares drafts that fit the channel and the sequence step — whether it is an email, LinkedIn message, follow-up, or InMail where supported.
Draft generation includes:
- Lead Context — Uses available prospect and company information.
- Playbook Strategy — Follows the selected ICP, pitch, tone, CTA, and templates.
- Channel Rules — Adjusts drafts for Email, LinkedIn, and InMail where supported.
- Sequence Step Context — Understands whether the draft is a first touch, follow-up, wait-step response, or later sequence message.
- Personalization Signals — Uses relevant business signals without forcing unnecessary personalization.
- Verifier Checks — Reviews drafts for quality, consistency, and risk before they move forward.
- Approval Awareness — Keeps drafts aligned with review and approval rules.
Generate Verified Channel-Aware Drafts
After the campaign is set up, AIVA helps generate outbound drafts based on the selected leads, Playbook strategy, campaign sequence, channel rules, and available personalization signals.
Instead of creating one generic message, AIVA prepares drafts that fit the channel and the sequence step — whether it is an email, LinkedIn message, follow-up, or InMail where supported.
Draft generation includes:
- Lead Context — Uses available prospect and company information.
- Playbook Strategy — Follows the selected ICP, pitch, tone, CTA, and templates.
- Channel Rules — Adjusts drafts for Email, LinkedIn, and InMail where supported.
- Sequence Step Context — Understands whether the draft is a first touch, follow-up, wait-step response, or later sequence message.
- Personalization Signals — Uses relevant business signals without forcing unnecessary personalization.
- Verifier Checks — Reviews drafts for quality, consistency, and risk before they move forward.
- Approval Awareness — Keeps drafts aligned with review and approval rules.

Review, Approve, or Block Drafts
Before messages move into execution, your team can review the drafts AIVA prepares. This gives users control over what gets sent, what needs editing, and what should be blocked before outreach continues.
AIVA helps make the review process clearer by showing the draft content, channel, sequence step, verifier status, personalization context, and the next action required.
Draft review actions:
- Review — Check the message before it moves forward.
- Edit — Adjust wording, tone, CTA, or personalization.
- Approve — Mark the draft as ready for execution.
- Reject — Send the draft back when it does not meet expectations.
- Regenerate — Ask AIVA to create another version where supported.
- Block — Stop a draft from being used when it is unsafe, irrelevant, or not aligned with policy.
Draft review signals:
- Channel — Email, LinkedIn, or InMail where supported.
- Sequence Step — First touch, follow-up, or later step.
- Verifier Status — Passed, needs review, or blocked.
- Personalization Summary — Shows why AIVA used specific context.
- Approval Status — Pending review, approved, rejected, or blocked.
Review, Approve, or Block Drafts
Before messages move into execution, your team can review the drafts AIVA prepares. This gives users control over what gets sent, what needs editing, and what should be blocked before outreach continues.
AIVA helps make the review process clearer by showing the draft content, channel, sequence step, verifier status, personalization context, and the next action required.
Draft review actions:
- Review — Check the message before it moves forward.
- Edit — Adjust wording, tone, CTA, or personalization.
- Approve — Mark the draft as ready for execution.
- Reject — Send the draft back when it does not meet expectations.
- Regenerate — Ask AIVA to create another version where supported.
- Block — Stop a draft from being used when it is unsafe, irrelevant, or not aligned with policy.
Draft review signals:
- Channel — Email, LinkedIn, or InMail where supported.
- Sequence Step — First touch, follow-up, or later step.
- Verifier Status — Passed, needs review, or blocked.
- Personalization Summary — Shows why AIVA used specific context.
- Approval Status — Pending review, approved, rejected, or blocked.

Execute Safely Through Runtime Checks
Once drafts are approved and the campaign is ready, AIVA moves into controlled execution. Before each action runs, AIVA checks whether the campaign, lead, sender account, channel, schedule, usage, and safety conditions are still valid.
This helps prevent outreach from running when a mailbox is not ready, a lead should not be contacted, a schedule window has passed, an approval is missing, or a channel/account is not eligible.
Runtime checks include:
- Sender Readiness — Confirms the mailbox or account is eligible before execution.
- Channel State — Checks whether Email, LinkedIn, or InMail is available where supported.
- Lead State — Confirms the lead is still eligible and not suppressed, duplicated, or blocked.
- Approval Status — Ensures required approvals are complete before a message can move forward.
- Schedule Window — Runs actions only within the configured campaign timing.
- Usage / Capacity — Checks safe daily capacity, limits, and available usage before sending.
- Safety Rules — Applies suppression, stop conditions, compliance checks, and blocker logic.
- Runtime State — Decides whether the action should run, wait, skip, or be blocked.
Execute Safely Through Runtime Checks
Once drafts are approved and the campaign is ready, AIVA moves into controlled execution. Before each action runs, AIVA checks whether the campaign, lead, sender account, channel, schedule, usage, and safety conditions are still valid.
This helps prevent outreach from running when a mailbox is not ready, a lead should not be contacted, a schedule window has passed, an approval is missing, or a channel/account is not eligible.
Runtime checks include:
- Sender Readiness — Confirms the mailbox or account is eligible before execution.
- Channel State — Checks whether Email, LinkedIn, or InMail is available where supported.
- Lead State — Confirms the lead is still eligible and not suppressed, duplicated, or blocked.
- Approval Status — Ensures required approvals are complete before a message can move forward.
- Schedule Window — Runs actions only within the configured campaign timing.
- Usage / Capacity — Checks safe daily capacity, limits, and available usage before sending.
- Safety Rules — Applies suppression, stop conditions, compliance checks, and blocker logic.
- Runtime State — Decides whether the action should run, wait, skip, or be blocked.

Handle Replies, Meetings, and Handoff
When prospects respond, AIVA helps your team understand what happened and what should happen next. Replies can be classified by intent, routed for review, paused when human takeover is needed, or moved toward meeting booking and handoff.
This step connects outreach activity to real sales outcomes — not just sent messages. AIVA helps surface positive replies, objections, meeting intent, unsubscribe requests, out-of-office replies, and conversations that need human attention.
Reply and meeting handling includes:
- Reply Detection — Captures Email, LinkedIn, and InMail replies where supported.
- Intent Classification — Identifies positive replies, objections, meeting intent, unsubscribe/DNC, out-of-office, referrals, and wrong-contact replies.
- Human Handoff — Routes conversations to the right owner when a person should take over.
- Meeting Intent — Detects when a prospect is interested in booking or discussing next steps.
- Booking Flow — Supports meeting booking, reschedules, cancellations, and reminders where configured.
- Automation Stop Rules — Pauses or stops future outreach when replies, meetings, opt-outs, or human takeover require it.
- Conversation Context — Keeps reply history and next-step context visible for the team.
- CRM Continuity — Prepares meaningful reply and handoff context for CRM sync where configured.
Handle Replies, Meetings, and Handoff
When prospects respond, AIVA helps your team understand what happened and what should happen next. Replies can be classified by intent, routed for review, paused when human takeover is needed, or moved toward meeting booking and handoff.
This step connects outreach activity to real sales outcomes — not just sent messages. AIVA helps surface positive replies, objections, meeting intent, unsubscribe requests, out-of-office replies, and conversations that need human attention.
Reply and meeting handling includes:
- Reply Detection — Captures Email, LinkedIn, and InMail replies where supported.
- Intent Classification — Identifies positive replies, objections, meeting intent, unsubscribe/DNC, out-of-office, referrals, and wrong-contact replies.
- Human Handoff — Routes conversations to the right owner when a person should take over.
- Meeting Intent — Detects when a prospect is interested in booking or discussing next steps.
- Booking Flow — Supports meeting booking, reschedules, cancellations, and reminders where configured.
- Automation Stop Rules — Pauses or stops future outreach when replies, meetings, opt-outs, or human takeover require it.
- Conversation Context — Keeps reply history and next-step context visible for the team.
- CRM Continuity — Prepares meaningful reply and handoff context for CRM sync where configured.

Maintain CRM Continuity
After replies, meetings, and handoffs happen, AIVA helps keep your CRM aligned with meaningful outbound activity. Instead of leaving campaign activity disconnected, AIVA can sync relevant lead context, reply outcomes, meeting events, and handoff details to CRM where connected and configured.
This helps sales teams see what happened, why it matters, and what should happen next without losing context between AIVA and the CRM.
CRM continuity includes:
- Lead Identity — Keeps CRM-linked lead, contact, company, or deal context connected where configured.
- Campaign Activity — Logs meaningful outbound activity instead of internal draft or queue noise.
- Reply Outcomes — Carries reply classification and conversation context into the sales timeline.
- Meeting Events — Syncs meeting intent, booked meetings, reschedules, cancellations, and handoff details where supported.
- Handoff Context — Gives the sales owner useful context before taking over.
- CRM State — Shows whether CRM is connected, disconnected, blocked, or needs re-authentication.
- Sync Health — Surfaces failed, blocked, or review-required CRM continuity states.
- Timeline Updates — Helps CRM tell the same sales story as AIVA.
Maintain CRM Continuity
After replies, meetings, and handoffs happen, AIVA helps keep your CRM aligned with meaningful outbound activity. Instead of leaving campaign activity disconnected, AIVA can sync relevant lead context, reply outcomes, meeting events, and handoff details to CRM where connected and configured.
This helps sales teams see what happened, why it matters, and what should happen next without losing context between AIVA and the CRM.
CRM continuity includes:
- Lead Identity — Keeps CRM-linked lead, contact, company, or deal context connected where configured.
- Campaign Activity — Logs meaningful outbound activity instead of internal draft or queue noise.
- Reply Outcomes — Carries reply classification and conversation context into the sales timeline.
- Meeting Events — Syncs meeting intent, booked meetings, reschedules, cancellations, and handoff details where supported.
- Handoff Context — Gives the sales owner useful context before taking over.
- CRM State — Shows whether CRM is connected, disconnected, blocked, or needs re-authentication.
- Sync Health — Surfaces failed, blocked, or review-required CRM continuity states.
- Timeline Updates — Helps CRM tell the same sales story as AIVA.

Learn and Improve Future Campaigns
After a campaign runs, AIVA helps your team understand what worked, what did not, and what can improve next time. Campaign outcomes can feed learning insights, Playbook recommendations, and future draft optimization.
Instead of treating every campaign as a one-time send, AIVA uses performance signals to help improve future outreach strategy, messaging, personalization, and sequence decisions.
Learning includes:
- Campaign Outcomes — Reviews replies, meetings, positive signals, objections, unsubscribes, and underperforming steps.
- Playbook Learning — Identifies what may need to change in ICP, pitch, tone, CTA, templates, or sequence.
- Draft Optimization — Helps improve future drafts based on past performance patterns.
- Personalization Insights — Shows which personalization sources or signals performed better.
- Channel Performance — Compares Email, LinkedIn, and InMail outcomes where supported.
- Recommendations — Suggests improvements your team can review before applying.
- Future Campaign Improvements — Uses approved learnings to make the next campaign stronger.
Learn and Improve Future Campaigns
After a campaign runs, AIVA helps your team understand what worked, what did not, and what can improve next time. Campaign outcomes can feed learning insights, Playbook recommendations, and future draft optimization.
Instead of treating every campaign as a one-time send, AIVA uses performance signals to help improve future outreach strategy, messaging, personalization, and sequence decisions.
Learning includes:
- Campaign Outcomes — Reviews replies, meetings, positive signals, objections, unsubscribes, and underperforming steps.
- Playbook Learning — Identifies what may need to change in ICP, pitch, tone, CTA, templates, or sequence.
- Draft Optimization — Helps improve future drafts based on past performance patterns.
- Personalization Insights — Shows which personalization sources or signals performed better.
- Channel Performance — Compares Email, LinkedIn, and InMail outcomes where supported.
- Recommendations — Suggests improvements your team can review before applying.
- Future Campaign Improvements — Uses approved learnings to make the next campaign stronger.


