Empower Teams FAQs

Teams is the productized Empower LO platform deployed across a roster of producers inside Empower LO's white-labeled HighLevel environment. Each producer gets a configured mortgage CRM and marketing system, while leadership gets a shared operating layer for rollout, routing, brand standards, and support.

The difference is the management layer. Teams adds coordinated onboarding, reusable account configuration, team-level lead routing, brand governance, team-level LOS support, and a dedicated account manager instead of treating every producer as an unrelated account.

Teams is typically the more cost-effective option for organizations with fewer than 30 producers. It deploys the productized Empower LO system inside Empower LO's white-labeled HighLevel environment. A Custom Build uses a separate white-labeled HighLevel environment that the client pays for and owns, with the implementation designed around the client's workflows, governance, brands, and integration requirements. Producer count is a useful guide rather than a hard cutoff, so complexity and ownership requirements still matter.

With Teams, the service runs inside Empower LO's white-labeled HighLevel environment, which Empower LO owns and administers. With a Custom Build, the client pays for and owns its separate white-labeled HighLevel environment, while Empower LO designs and implements the agreed system. This distinction concerns the underlying platform environment, not ownership of the client's uploaded content and data.

Teams can be structured with individual producer subaccounts, a shared account, or a custom combination depending on how your company handles leads, branding, and permissions. We choose the structure during discovery rather than forcing every organization into the same model.

Permissions and account structure are defined during setup. Teams can use shared or separate producer accounts, and portal access can restrict billing or customer-request access by user. We document which roles can see contacts, conversations, pipelines, billing, and administrative settings before rollout.

A standard team rollout may target roughly two weeks after all required access, producer information, branding, approvals, and configuration decisions are complete. We confirm the actual launch plan during discovery. Migrations, custom routing, integrations, compliance review, and phased onboarding can extend the schedule.

Yes. Team setups can use round-robin, geography, source, or other approved routing rules. The exact rules depend on the account structure and available lead data. Routing should also include a plan for reassignment, inactive producers, and leads that do not match a rule.

Yes. Shared templates, approved assets, reusable snapshots, and account configuration can keep the roster aligned while still allowing the producer-specific details needed for local execution. We define which elements are standardized and which can be customized.

Teams includes team-level LOS integration support. The exact connection depends on the LOS, available APIs or webhooks, the desired fields and milestones, and how producers are separated across accounts. A deep or nonstandard integration may require custom scope.

Empower LO provides the agreed onboarding and platform guidance. Teams can choose a coordinated group onboarding model or separate producer sessions. The proposal should state the training format, number of sessions, internal owner, and what happens when new producers join later.

The rollout focuses on configured accounts, clear ownership, guided onboarding, and a limited set of first actions rather than asking each producer to build a CRM. Leadership should still define adoption expectations, required pipeline habits, and an internal owner because software alone cannot create team accountability.

Teams includes a dedicated account manager, priority support, and three Open Office Hours sessions each week for platform questions, troubleshooting, and guidance. Custom development, campaign execution, data cleanup, and nonstandard integrations may require separate scope.

Teams starts at $497 per month. Final pricing depends on producer count, account structure, onboarding format, support needs, and configuration requirements. We provide the complete pricing in a written proposal after reviewing the roster and operating model.

Yes. Launch, Scale, and Teams subscriptions are all offered month to month. Custom implementation, migration, integration, and other separately scoped work may have its own written terms.