How Aventora Works Together

Overview (business use case): Most teams need one place to see who they are working with (CRM) and a way to reach those people at scale (Engagement Hub). Domain Assistant handles questions on the website before a human is needed. Part 1 explains how those pieces fit so daily work stays in the right application.

1.1 Two applications, one workflow

Type: Operation | Audience: All users

Overview: Sales and service leads live in the CRM so everyone shares the same truth about contacts, deals, and history. Outreach and automation run from Admin because those tools need credits, phone lines, and account-wide rules. Splitting the apps avoids duplicating your contact list while still letting coordinators run campaigns.

Aventora is split into two places you sign in:

1. Aventora CRM — Your contact list, companies, deals, tasks, notes, and activity timeline. This is where relationships and pipeline live.
2. Aventora Admin — Engagement Hub (phone, SMS, email outreach, live chat queue) and Domain Assistant (website chatbot). Only administrator accounts can open Admin.

There is no contact directory in Admin. When you call or message someone from Hub, you use their name, phone, and email; matching records and history appear in CRM after sync.

• Aventora CRM holds contacts and deals; staff can start outreach from a contact (Engage by Aventora).
• Aventora Admin runs Engagement Hub (calls, SMS, email, live chat) and Domain Assistant (website chatbot).
• CRM Sync (configured by the Hub account owner) sends engagement results back to the right people in CRM.

1.2 Daily engagement lifecycle

Type: Operation | Audience: CRM workspace member, Admin user (Engagement Hub)

Overview: The lifecycle is the story of a lead from “in the system” to “contacted” to “updated in the pipeline.” Following the same steps keeps marketing, sales, and operations aligned and prevents leads from going cold because nobody knew a call already happened.

A typical flow:

1. Contact exists in CRM — Created manually, imported, or updated from synced outreach.
2. Someone engages — From the contact record (Engage by Aventora) or from Hub (Single Call, Bulk Call, Email Pull).
3. Conversation runs — Voice, SMS, or email; or a customer chats and your team responds in Chat Center.
4. Outcome is visible — In Hub Analysis and on the contact timeline in CRM (when sync is on).
5. Deal moves — Stages updated in CRM so forecasts and handoffs stay accurate.

1.3 Who configures what

Type: Administration | Audience: CRM workspace admin, Engagement Hub account owner, Domain admin

Overview: Clear ownership avoids “why can’t I see Agents?” or “who owns the phone bill?” questions. CRM admins own team access to records; the Hub account owner owns outreach rules and CRM connection; the domain admin owns chatbot content.

Responsibility	Who	Where
CRM team invites and roles	CRM workspace admin	CRM → Settings → Members, Roles
Connect CRM to Hub	Engagement Hub account owner	Admin → Account Settings → CRM Sync
Phone/SMS defaults for CRM users	CRM workspace admin	CRM → Settings → Apps (Aventora Phone)
Hub call rules, inbound numbers, calendars	Engagement Hub account owner	Admin → Account Settings
Chatbot knowledge and domain users	Domain admin	Admin → Domain Assistant
Credits and billing	Engagement Hub account owner	Admin → Billing

Delegate admins on Hub can adjust Calendar, Aventora Calendar, and Inbound for themselves but cannot change most other Account Settings tabs.

---

See the full Aventora User Manual for CRM, Engagement Hub, and Domain Assistant workflows.

Client Growth Hub is a related product for finding and qualifying new prospects before they enter CRM and Engagement Hub. Start at Client Growth Hub Overview.

Changelog

Date	Change
2026-08-12	Linked Client Growth Hub as the prospect-discovery product that feeds CRM and Engagement Hub.