No. AIVA is best positioned as an AI SDR workspace that supports your team by handling repetitive outbound workflow steps such as lead preparation, draft generation, follow-ups, CRM continuity, and learning. Your reps still handle high-value conversations, judgment, and relationship-building.

Yes. Mid-Market teams should use Playbooks to standardize messaging, sequence structure, tone, and campaign strategy across reps and segments.

AIVA should support review and approval workflows where configured. Approval confirms content, but runtime checks still decide whether a message can actually be sent.

AIVA’s current direction supports Email + LinkedIn Campaigns where supported and configured, with InMail where account capability and configuration support it.

AIVA can support connected sender accounts where supported, but connected does not mean ready. Mailboxes still need sender readiness, safe daily capacity, campaign eligibility, and runtime checks.

AIVA can support CRM continuity where connected and configured. CRM behavior depends on supported provider, field mapping, identity matching, permissions, and sync state.

AIVA can help detect meeting intent, support booking workflows, assign or route handoff where configured, and stop unnecessary follow-ups after meeting state changes. It does not guarantee meetings.

AIVA can learn from outcomes and recommend improvements for future drafts and campaigns when enough data exists. It should not silently rewrite already generated, approved, queued, scheduled, or sent messages.

AIVA should use sender readiness, safe capacity, approvals, schedules, lead state, usage, and runtime checks to control execution. It should not be positioned as unlimited or risk-free sending.

Mid-Market teams usually need collaborative team workflows, shared Playbooks, CRM continuity, integrations, and learning. Enterprise is better suited when you need custom annual packaging, deeper governance, security review, advanced controls, or complex rollout support.