{ "version": 2, "generatedAt": "2026-07-17T00:00:00.000Z", "services": [ { "product": "arive", "slug": "arive-integration", "name": "Arive Integration", "eyebrow": "LOS AUTOMATION", "summary": "How Arive events move mortgage milestones into Empower LO and HighLevel.", "serviceUrl": "/los-integrations", "cta": { "label": "Scope the Integration", "href": "/los-integrations#get-started" }, "faqs": [ { "id": "arive-integration-001", "product": "arive", "question": "What does the Arive integration do?", "answer": "It connects selected loan data and milestone changes from Arive to your Empower LO or HighLevel account. That can include creating or updating borrower contacts, moving opportunities through the right pipeline stages, updating mapped loan fields, assigning records to the correct user, and triggering communication or follow-up workflows.", "revision": 1, "featured": true, "order": 1 }, { "id": "arive-integration-002", "product": "arive", "question": "Does Empower LO replace Arive?", "answer": "No. Arive remains the system of record for the loan file. Empower LO and HighLevel use selected Arive data to support communication, CRM visibility, marketing, and follow-up around the loan.", "revision": 1, "featured": true, "order": 2 }, { "id": "arive-integration-003", "product": "arive", "question": "Is this a full two-way sync?", "answer": "No. The standard integration is an event-driven Arive-to-HighLevel workflow, not an unrestricted two-way mirror of every field in both systems. This reduces conflicts and keeps Arive authoritative for the loan file.", "revision": 1, "featured": true, "order": 3 }, { "id": "arive-integration-004", "product": "arive", "question": "Which Arive milestones can update HighLevel?", "answer": "The standard mapping supports major milestones such as application intake, disclosures sent, underwriting submission, approval with conditions, clear to close, docs out, funded, and adverse status. The exact milestones and actions are reviewed during setup so they match your HighLevel pipelines and customer communication plan.", "revision": 1, "featured": true, "order": 4 }, { "id": "arive-integration-005", "product": "arive", "question": "What information can be mapped into HighLevel?", "answer": "Common mappings include borrower identity, loan amount, loan purpose, program, term, rate, property details, lock dates, closing dates, appraisal, title and insurance status, loan officer details, and an Arive deep link. Only fields that serve a defined workflow should be mapped.", "revision": 1, "featured": true, "order": 5 }, { "id": "arive-integration-006", "product": "arive", "question": "How does the integration know which loan officer or subaccount should receive a loan?", "answer": "Loans are matched to the correct producer using the originator email rules configured during setup. If no active rule matches, the loan is held for review rather than sent to another producer's account. After the correct route is added, eligible held events can be replayed. Unresolved event data is not retained indefinitely.", "revision": 1, "featured": true, "order": 6 }, { "id": "arive-integration-007", "product": "arive", "question": "Will the default setup overwrite our existing HighLevel customizations?", "answer": "No. The default mapping workflow is additive. It skips fields and mappings that are already configured rather than overwriting account-specific customizations. We still review your pipelines and custom fields before activation.", "revision": 1, "featured": true, "order": 7 }, { "id": "arive-integration-008", "product": "arive", "question": "How are duplicates handled?", "answer": "The integration checks available email and phone identity before creating or updating contacts, and it keeps the HighLevel opportunity linked for future updates. That greatly reduces duplicate creation, but incomplete or inconsistent source data can still require review.", "revision": 1, "featured": true, "order": 8 }, { "id": "arive-integration-009", "product": "arive", "question": "What happens if Zapier, HighLevel, or a webhook is temporarily unavailable?", "answer": "Once Empower LO receives an Arive event, failed processing or HighLevel delivery can be retried and eligible events can be replayed. If Arive, Zapier, or another upstream service fails before the event reaches Empower LO, recovery depends on that provider and may require a resend or backfill.", "revision": 1, "featured": false, "order": 9 }, { "id": "arive-integration-010", "product": "arive", "question": "Is the integration real time?", "answer": "The integration is event-driven rather than a continuous field-by-field sync. Arive typically sends a configured webhook when a new loan is created, a loan application is completed, a Key Date is updated, a Loan Tracker is updated, or a Loan Status is updated. Edits made between those trigger events are not captured simply because the field changed. After a qualifying event is sent, processing time can still vary based on Arive, Zapier, HighLevel, network conditions, retries, and the event configuration, so we do not promise an exact number of seconds for every update.", "revision": 1, "featured": false, "order": 10 }, { "id": "arive-integration-011", "product": "arive", "question": "Can Arive milestones trigger borrower or agent communications?", "answer": "Yes. A mapped milestone can move an opportunity, update fields, and activate the HighLevel workflows configured for that stage or event. We decide during setup which communications should be automated, who should receive them, and which conditions should stop them.", "revision": 1, "featured": false, "order": 11 }, { "id": "arive-integration-012", "product": "arive", "question": "What do you need from us to set it up?", "answer": "We typically need an Arive administrator or technical contact, Zapier access for the approved webhook connection, HighLevel location access, a current list of originators and email addresses, the pipelines and stages you use, and agreement on the fields and milestones that should drive action. Sensitive credentials are collected through the approved secure handoff, not pasted into a general onboarding form.", "revision": 1, "featured": false, "order": 12 }, { "id": "arive-integration-013", "product": "arive", "question": "Is Arive integration included in my plan?", "answer": "Standard LOS integration is available on Scale and Teams. Launch customers can add standard initial LOS setup for a one-time $250 fee. Ongoing LOS support is included with Scale and inherited by Teams. Nonstandard mappings, unsupported LOS providers, company-wide architecture, or custom workflow requirements may require separate scope.", "revision": 1, "featured": false, "order": 13 }, { "id": "arive-integration-014", "product": "arive", "question": "How do we test the integration before relying on it?", "answer": "We confirm originator routing, send representative loan events, verify the expected contacts and opportunity, check field and stage mappings, and review communication triggers before broader rollout. The go-live plan should also identify who reviews exceptions and how a failed or missing event is escalated.", "revision": 1, "featured": false, "order": 14 }, { "id": "arive-integration-015", "product": "arive", "question": "What are the warning signs that the integration needs attention?", "answer": "Common warning signs include no recent Arive events, loans held because no originator route matched, missing field or stage mappings, a disabled subaccount sync, repeated delivery errors, or a HighLevel record that stopped updating after an Arive milestone.", "revision": 1, "featured": false, "order": 15 } ] }, { "product": "teams", "slug": "teams", "name": "Empower Teams", "eyebrow": "FOR TEAMS AND LEADERS", "summary": "Productized mortgage CRM and marketing infrastructure for a roster of producers.", "serviceUrl": "/solutions-teams", "cta": { "label": "Book a Team Call", "href": "/book-team" }, "faqs": [ { "id": "teams-001", "product": "teams", "question": "What is the Empower LO Teams service?", "answer": "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.", "revision": 1, "featured": true, "order": 1 }, { "id": "teams-002", "product": "teams", "question": "How is Teams different from buying several individual accounts?", "answer": "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.", "revision": 1, "featured": true, "order": 2 }, { "id": "teams-003", "product": "teams", "question": "How is Teams different from a Custom Build?", "answer": "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.", "revision": 1, "featured": true, "order": 3 }, { "id": "teams-004", "product": "teams", "question": "Who owns the underlying white-labeled HighLevel environment?", "answer": "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.", "revision": 1, "featured": true, "order": 4 }, { "id": "teams-005", "product": "teams", "question": "Does every producer get a separate account?", "answer": "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.", "revision": 1, "featured": true, "order": 5 }, { "id": "teams-006", "product": "teams", "question": "What can managers, processors, administrators, and loan officers see?", "answer": "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.", "revision": 1, "featured": true, "order": 6 }, { "id": "teams-007", "product": "teams", "question": "How long does a team rollout take?", "answer": "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.", "revision": 1, "featured": true, "order": 7 }, { "id": "teams-008", "product": "teams", "question": "Can leads be distributed automatically?", "answer": "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.", "revision": 1, "featured": true, "order": 8 }, { "id": "teams-009", "product": "teams", "question": "Can leadership control branding and campaigns?", "answer": "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.", "revision": 1, "featured": false, "order": 9 }, { "id": "teams-010", "product": "teams", "question": "Does Teams include LOS integration?", "answer": "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.", "revision": 1, "featured": false, "order": 10 }, { "id": "teams-011", "product": "teams", "question": "Who trains the team?", "answer": "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.", "revision": 1, "featured": false, "order": 11 }, { "id": "teams-012", "product": "teams", "question": "How do you reduce the risk that our loan officers will not use the system?", "answer": "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.", "revision": 1, "featured": false, "order": 12 }, { "id": "teams-013", "product": "teams", "question": "What support does the team receive?", "answer": "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.", "revision": 1, "featured": false, "order": 13 }, { "id": "teams-014", "product": "teams", "question": "How does pricing work?", "answer": "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.", "revision": 1, "featured": false, "order": 14 }, { "id": "teams-015", "product": "teams", "question": "Is Teams month to month?", "answer": "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.", "revision": 1, "featured": false, "order": 15 } ] }, { "product": "custom-builds", "slug": "custom-builds", "name": "Custom Builds", "eyebrow": "CLIENT-OWNED INFRASTRUCTURE", "summary": "Mortgage-specific HighLevel architecture designed around a company’s operation.", "serviceUrl": "/custom-builds", "cta": { "label": "Scope a Custom Build", "href": "/custom-builds#get-started" }, "faqs": [ { "id": "custom-builds-001", "product": "custom-builds", "question": "What is an Empower LO Custom Build?", "answer": "A Custom Build is a scoped HighLevel implementation designed around a mortgage company's operating model rather than the standard Empower LO product. We map how the company handles producers, branches, brands, leads, borrowers, referral partners, permissions, campaigns, automations, integrations, and operational handoffs, then configure the client-owned HighLevel environment around those decisions.", "revision": 1, "featured": true, "order": 1 }, { "id": "custom-builds-002", "product": "custom-builds", "question": "How is a Custom Build different from Empower LO Teams?", "answer": "Teams deploys Empower LO's productized mortgage platform 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 architecture and implementation designed around the client's business. Teams is typically more cost-effective for organizations with fewer than 30 producers, while Custom Builds are better when platform ownership or operational complexity justifies the additional investment.", "revision": 1, "featured": true, "order": 2 }, { "id": "custom-builds-003", "product": "custom-builds", "question": "Who is a Custom Build best suited for?", "answer": "Custom Builds are best suited for mortgage companies with a defined operating model and enough complexity to justify company-owned infrastructure. Common signals include multiple branches or brands, specialized roles and permissions, custom lead ownership, deeper integrations, existing HighLevel technical debt, or a need to standardize how producers and operations work across the organization.", "revision": 1, "featured": true, "order": 3 }, { "id": "custom-builds-004", "product": "custom-builds", "question": "Who owns the HighLevel environment?", "answer": "The client does. The client pays for and owns the separate white-labeled HighLevel environment, including its account access and platform relationship. Empower LO receives the access needed to design, build, test, and document the agreed implementation. Any post-launch support or optimization is separately scoped.", "revision": 1, "featured": true, "order": 4 }, { "id": "custom-builds-005", "product": "custom-builds", "question": "Who pays the HighLevel licensing and usage costs?", "answer": "The client pays for its white-labeled HighLevel environment and the associated platform relationship. The proposal should also identify responsibility for usage-based services, phone, email, domains, third-party applications, integration vendors, and any other recurring costs required by the approved architecture.", "revision": 1, "featured": true, "order": 5 }, { "id": "custom-builds-006", "product": "custom-builds", "question": "What can a Custom Build include?", "answer": "Depending on scope, a build can include account and subaccount architecture, pipelines, custom fields, permissions, lead routing, workflow automation, borrower and referral-partner communication, campaigns, forms, funnels, calendars, producer onboarding, LOS or lead-source handoffs, documentation, training, and launch support. The written proposal defines the actual deliverables.", "revision": 1, "featured": true, "order": 6 }, { "id": "custom-builds-007", "product": "custom-builds", "question": "Can you clean up our existing HighLevel account instead of rebuilding it?", "answer": "Often, yes. We can audit the existing account, identify what should be kept, retired, renamed, documented, or rebuilt, and recommend the safest path. Sometimes cleanup is the fastest answer. In other cases, rebuilding the architecture in the client-owned environment creates a cleaner and more maintainable result.", "revision": 1, "featured": true, "order": 7 }, { "id": "custom-builds-008", "product": "custom-builds", "question": "Can you migrate our existing contacts and data?", "answer": "Data migration is not automatic. It may be included when it is specifically listed in the project scope and the source system, permissions, export format, and data quality support a safe import. Before migration, we define what will move, field mappings, duplicate handling, cleanup responsibilities, and validation steps.", "revision": 1, "featured": true, "order": 8 }, { "id": "custom-builds-009", "product": "custom-builds", "question": "Can you integrate our LOS, lead vendors, website, or other systems?", "answer": "Potentially. No specific integration is guaranteed until feasibility is confirmed. Feasibility depends on available APIs, webhooks or exports, authentication, field access, vendor cooperation, security requirements, and the requested workflow. The project scope identifies any additional middleware, third-party work, recurring fees, or client-managed vendor access.", "revision": 1, "featured": false, "order": 9 }, { "id": "custom-builds-010", "product": "custom-builds", "question": "Does every producer need a separate subaccount?", "answer": "Not necessarily. The right structure depends on lead ownership, brand separation, permissions, shared operational teams, producer autonomy, and how the company intends to administer the platform. Discovery determines when producers should share infrastructure and when separate subaccounts create a cleaner operating model.", "revision": 1, "featured": false, "order": 10 }, { "id": "custom-builds-011", "product": "custom-builds", "question": "What information do you need to scope the project?", "answer": "We need the company structure, producer and branch model, current HighLevel or CRM setup, lead sources, core workflows, LOS and connected tools, known pain points, required permissions, rollout goals, and the people who can make process decisions. The more clearly the operating model is defined, the more accurately we can scope the build.", "revision": 1, "featured": false, "order": 11 }, { "id": "custom-builds-012", "product": "custom-builds", "question": "What does the Custom Build process look like?", "answer": "The engagement normally moves through discovery, architecture, build, testing, and rollout. We first define what the system should own and how it should work. After architecture approval, we configure and connect the system, test representative workflows, train the appropriate users, and launch according to the agreed rollout plan.", "revision": 1, "featured": false, "order": 12 }, { "id": "custom-builds-013", "product": "custom-builds", "question": "How long does a Custom Build take?", "answer": "A typical Custom Build may target roughly 30 to 60 days after requirements, access, decision-makers, and approvals are available. Larger multi-branch projects, substantial data cleanup, custom integrations, compliance review, or delayed decisions can extend the timeline. The proposal provides the project-specific schedule before work begins.", "revision": 1, "featured": false, "order": 13 }, { "id": "custom-builds-014", "product": "custom-builds", "question": "How does Custom Build pricing work?", "answer": "Custom Builds are priced after discovery. Pricing depends on the size of the operation, the depth of integrations, the rollout footprint, and any ongoing partnership requested after launch. Before the client commits, we explain the cost, expected timeline, required client inputs, and what is and is not included.", "revision": 1, "featured": false, "order": 14 }, { "id": "custom-builds-015", "product": "custom-builds", "question": "What does a paid discovery or scoping deposit include?", "answer": "Some Custom Builds begin with a paid discovery or scoping engagement. Before payment, we define what the fee covers, which stakeholders need to participate, what decisions or deliverables the client will receive, and whether any portion is credited toward later work. Those terms are project-specific and should be confirmed in writing.", "revision": 1, "featured": false, "order": 15 }, { "id": "custom-builds-016", "product": "custom-builds", "question": "Can the build be delivered in phases?", "answer": "Yes, when phased delivery is the safest way to meet a deadline or reduce rollout risk. A project may launch the core architecture and highest-priority workflows first, then add business units, integrations, migrations, automations, or producer groups in later approved phases. The proposal should identify what is included in each phase and what must be ready before launch.", "revision": 1, "featured": false, "order": 16 }, { "id": "custom-builds-017", "product": "custom-builds", "question": "How are producers and administrators onboarded?", "answer": "The rollout plan should distinguish administrator training from producer onboarding. Administrators need to understand architecture, permissions, ownership, and maintenance. Producers need a simpler role-based experience focused on the records, tasks, conversations, and workflows they actually use. The proposal defines the sessions, materials, rollout groups, and client responsibilities.", "revision": 1, "featured": false, "order": 17 }, { "id": "custom-builds-018", "product": "custom-builds", "question": "What support is included during implementation?", "answer": "Implementation support covers the agreed discovery, build decisions, testing, training, and launch activities in the project scope. It does not automatically create an unlimited support desk for every user or future request. Escalation paths, response expectations, and any post-launch support should be defined before rollout.", "revision": 1, "featured": false, "order": 18 }, { "id": "custom-builds-019", "product": "custom-builds", "question": "What happens after launch?", "answer": "The client can operate the system in its own environment using the delivered documentation and training. Many clients retain Empower LO for support, optimization, additional rollouts, or new initiatives, but ongoing partnership is separately defined rather than assumed to be unlimited.", "revision": 1, "featured": false, "order": 19 } ] }, { "product": "empower-lo", "slug": "empower-lo", "name": "Individual Empower LO", "eyebrow": "FOR INDIVIDUAL PRODUCERS", "summary": "A ready-to-run mortgage CRM and marketing platform for individual loan officers.", "serviceUrl": "/solutions-lo", "cta": { "label": "See Plans", "href": "/pricing" }, "faqs": [ { "id": "empower-lo-001", "product": "empower-lo", "question": "What is included in an individual Empower LO account?", "answer": "Individual plans include the HighLevel-based CRM, multi-channel conversations, mortgage email templates and automations, appointment scheduling, website, form and funnel tools, social planning, AI content tools, API and Zapier access, support users, and Empower Toolkit access. Your account starts with mortgage-specific configuration rather than a blank HighLevel workspace.", "revision": 1, "featured": true, "order": 1 }, { "id": "empower-lo-002", "product": "empower-lo", "question": "Is this just a HighLevel login?", "answer": "No. HighLevel is the underlying platform, but Empower LO adds the mortgage configuration, campaigns, automations, onboarding, support, and operating guidance needed to make the account useful without building everything from scratch.", "revision": 1, "featured": true, "order": 2 }, { "id": "empower-lo-003", "product": "empower-lo", "question": "Who is the individual plan best for?", "answer": "It is designed for solo producers and small operations that want one system for CRM, follow-up, marketing, scheduling, and borrower or referral-partner nurture without hiring an internal marketing and automation team.", "revision": 1, "featured": true, "order": 3 }, { "id": "empower-lo-004", "product": "empower-lo", "question": "I am not technical. Can I still use it?", "answer": "Yes. The account is preconfigured, onboarding is guided, and the system can run core campaigns and follow-up without requiring you to become a HighLevel builder. You can customize more as you become comfortable, but technical expertise is not a prerequisite.", "revision": 1, "featured": true, "order": 4 }, { "id": "empower-lo-005", "product": "empower-lo", "question": "How quickly can I get started?", "answer": "Standard onboarding is typically targeted within about a week after required branding, contact, domain, compliance, and access information is complete. Carrier registration, domain changes, data cleanup, integrations, or custom requests can extend the timeline.", "revision": 1, "featured": true, "order": 5 }, { "id": "empower-lo-006", "product": "empower-lo", "question": "Can you import my existing contacts?", "answer": "Yes. We can help import a clean contact file and map the fields needed for your CRM and campaigns. The quality of the import depends on the quality and permissions of the source data, so duplicates, missing consent history, and inconsistent fields may need cleanup first.", "revision": 1, "featured": true, "order": 6 }, { "id": "empower-lo-007", "product": "empower-lo", "question": "Will you build everything for me?", "answer": "Your account includes the standard mortgage platform configuration and guided setup. It does not include unlimited custom development. Requests that change the standard product, require custom integrations, or rebuild your business logic may need separate scope or a Custom Build.", "revision": 1, "featured": true, "order": 7 }, { "id": "empower-lo-008", "product": "empower-lo", "question": "Can I customize the campaigns and automations?", "answer": "Yes. The prebuilt assets are a starting point. You can edit copy, timing, branding, forms, funnels, pipeline stages, and workflows. We recommend changing one clear business outcome at a time instead of customizing the account before you have used the standard system.", "revision": 1, "featured": true, "order": 8 }, { "id": "empower-lo-009", "product": "empower-lo", "question": "Does it include a website?", "answer": "The platform includes website, form, funnel, and landing-page tools. The exact done-for-you setup and design work depends on your onboarding scope and plan, so we confirm what will be configured before launch rather than promising an unlimited custom website project.", "revision": 1, "featured": false, "order": 9 }, { "id": "empower-lo-010", "product": "empower-lo", "question": "How do SMS, email, and calling costs work?", "answer": "Launch includes $20 per month in usage credits and Scale includes $30 per month. These credits cover services such as email, SMS, and calling through the platform. Additional usage is billed based on actual consumption.", "revision": 1, "featured": false, "order": 10 }, { "id": "empower-lo-011", "product": "empower-lo", "question": "What is the difference between Launch and Scale?", "answer": "Launch includes the core configured platform and standard support. Scale adds three Open Office Hours sessions per week, priority support, ongoing LOS integration support, more monthly usage credit, and eligibility to add LeadEngine.", "revision": 1, "featured": false, "order": 11 }, { "id": "empower-lo-012", "product": "empower-lo", "question": "Is there a contract?", "answer": "Launch, Scale, and Teams subscriptions are all offered month to month. Plan changes, cancellation timing, and any separately scoped work are governed by the applicable subscription and order terms.", "revision": 1, "featured": false, "order": 12 }, { "id": "empower-lo-013", "product": "empower-lo", "question": "What support do I receive?", "answer": "Launch and Scale include chat and ticket support. Scale adds priority communication and three Open Office Hours sessions each week for platform questions, troubleshooting, and guidance. Support does not include unlimited custom development or implementation work.", "revision": 1, "featured": false, "order": 13 }, { "id": "empower-lo-014", "product": "empower-lo", "question": "Is Empower LO worthwhile if I do not have a large database yet?", "answer": "It can be, but the value depends on what you will use now. A smaller database may still benefit from immediate lead follow-up, referral-partner nurture, scheduling, landing pages, and a system that grows with production. If you have little existing data, no active lead sources, and no plan to use the workflows, waiting may be the better decision.", "revision": 1, "featured": false, "order": 14 }, { "id": "empower-lo-015", "product": "empower-lo", "question": "How much work is required from me after setup?", "answer": "You provide the business, branding, compliance, domain, calendar, phone, and integration information needed to configure the account. After launch, the standard automations reduce repetitive work, but you still need to respond to leads, keep pipeline outcomes current, approve marketing, and attend to exceptions.", "revision": 1, "featured": false, "order": 15 } ] }, { "product": "leadengine", "slug": "leadengine", "name": "LeadEngine", "eyebrow": "MANAGED GOOGLE ADS", "summary": "Managed Google Ads lead generation connected to an Empower LO account.", "serviceUrl": "/mortgage-leads", "cta": { "label": "Check Market Availability", "href": "/mortgage-leads#get-started" }, "faqs": [ { "id": "leadengine-001", "product": "leadengine", "question": "What is LeadEngine?", "answer": "LeadEngine is Empower LO's flat-fee managed Google Ads service for mortgage professionals. We manage the campaigns, mortgage landing pages, tracking, CRM delivery, and quality-based follow-up strategy while you provide the ad budget and work the opportunities.", "revision": 1, "featured": true, "order": 1 }, { "id": "leadengine-002", "product": "leadengine", "question": "Do you sell leads or charge per lead?", "answer": "No. LeadEngine is not a marketplace or pay-per-lead program. You pay a management fee, fund the ad budget separately, and leads submitted through your campaign are routed to your connected CRM. Empower LO does not intentionally filter, withhold, or resell submitted leads.", "revision": 1, "featured": true, "order": 2 }, { "id": "leadengine-003", "product": "leadengine", "question": "Are the leads exclusive?", "answer": "Leads submitted through your campaign and landing page are delivered to your account and are not resold by Empower LO through a lead marketplace. Market protection means Empower LO will not add more than two LeadEngine accounts within the defined geographic market.", "revision": 1, "featured": true, "order": 3 }, { "id": "leadengine-004", "product": "leadengine", "question": "Why do I need to check market availability?", "answer": "LeadEngine limits each defined geographic market to no more than two accounts. We review the target geography, licensing, expected search demand, competition, budget, and current availability before accepting a campaign.", "revision": 1, "featured": true, "order": 4 }, { "id": "leadengine-005", "product": "leadengine", "question": "Is the ad budget included in the management fee?", "answer": "No. The management fee covers the managed service. You control and fund the Google Ads budget separately. This keeps the service price independent of how many leads are generated and lets campaign budgets be adjusted to the market.", "revision": 1, "featured": true, "order": 5 }, { "id": "leadengine-006", "product": "leadengine", "question": "How much does LeadEngine cost?", "answer": "LeadEngine pricing is provided privately after we review your market and campaign requirements. Your proposal separates the managed-service price from Google Ads spend and any approved setup work.", "revision": 1, "featured": true, "order": 6 }, { "id": "leadengine-007", "product": "leadengine", "question": "How much ad spend do I need?", "answer": "There is no responsible universal number. The starting budget depends on search volume, competition, geography, average click cost, and the amount of lead flow you can work. We recommend a market-specific budget after reviewing availability and goals.", "revision": 1, "featured": true, "order": 7 }, { "id": "leadengine-008", "product": "leadengine", "question": "What kind of leads does LeadEngine generate?", "answer": "LeadEngine primarily targets consumers searching Google for purchase mortgage information and options. Borrowers complete a mortgage-specific form that captures contact information and objective inputs such as credit range, income, down payment, purchase price, property status, location, and timeline.", "revision": 1, "featured": true, "order": 8 }, { "id": "leadengine-009", "product": "leadengine", "question": "Are all leads ready to apply immediately?", "answer": "No. Some are active buyers, some are earlier in the process, and some need education or a readiness path. A stated timeline is not always the same as true opportunity because consumers often estimate timing based on what they think qualification will require. The objective profile and the follow-up conversation both matter.", "revision": 1, "featured": false, "order": 9 }, { "id": "leadengine-010", "product": "leadengine", "question": "How do you evaluate lead quality?", "answer": "We use objective form inputs such as credit profile, income, down payment, purchase price, property status, loan fit, and geography. We also use downstream response and outcome data when it is available and reliable. Quality indicators guide follow-up priority, but they do not prevent a submitted lead from being delivered.", "revision": 1, "featured": false, "order": 10 }, { "id": "leadengine-011", "product": "leadengine", "question": "Do you filter out or withhold lower-quality leads?", "answer": "We do not intentionally withhold leads based on quality. Submitted leads are designed to flow into the connected Empower LO or HighLevel account with their source and form data. Delivery is monitored, but timing and availability can be affected by third-party platforms, account configuration, and network conditions.", "revision": 1, "featured": false, "order": 11 }, { "id": "leadengine-012", "product": "leadengine", "question": "What follow-up is included?", "answer": "The connected CRM can provide immediate first-touch automation, tasks, pipeline placement, and longer-term nurture. The loan officer still needs to call, respond, qualify, advise, and update outcomes. LeadEngine improves the system around the conversation, but it does not replace the salesperson.", "revision": 1, "featured": false, "order": 12 }, { "id": "leadengine-013", "product": "leadengine", "question": "Do you guarantee a cost per lead, number of leads, appointments, or closings?", "answer": "No. Search volume, competition, click costs, borrower behavior, market conditions, licensing, ad policy, budget, and follow-up performance all affect results. We manage and optimize the engine, but we do not promise a fixed CPL or guaranteed production.", "revision": 1, "featured": false, "order": 13 }, { "id": "leadengine-014", "product": "leadengine", "question": "What do I need to do for LeadEngine to work?", "answer": "You need capacity to respond quickly, make multiple follow-up attempts, use the connected pipeline, keep lead outcomes current, and nurture borrowers who are not ready on the first call. The program is not a good fit if every lead will be judged only by whether the borrower answers immediately or applies today.", "revision": 1, "featured": false, "order": 14 }, { "id": "leadengine-015", "product": "leadengine", "question": "Who owns the Google Ads account and campaign assets?", "answer": "You do. You own the Google Ads account, campaign assets, billing history, and account access. Empower LO manages the campaigns through authorized access, but ownership remains with you.", "revision": 1, "featured": false, "order": 15 }, { "id": "leadengine-016", "product": "leadengine", "question": "How many leads can my market realistically generate?", "answer": "There is no fixed number that applies to every market. Expected volume depends on search demand, geography, competition, click costs, budget, landing-page conversion, licensing, seasonality, and campaign maturity. We provide a market-specific expectation rather than a universal lead promise.", "revision": 1, "featured": false, "order": 16 } ] } ] }