--- title: "Qualify and Route Commercial Solar Inquiries in HubSpot" description: "Qualify and Route Commercial Solar Inquiries in HubSpot. Follow the evidence, approvals, and completion checks with a copyable Genie job description." canonical: https://www.stacksync.com/blog/qualify-and-route-commercial-solar-inquiries-in-hubspot last_modified: 2026-09-18 --- # Qualify and Route Commercial Solar Inquiries in HubSpot > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Commercial solar inquiry qualification should establish the business identity, existing account relationship, and whether the requester is an end customer or an installation partner. Author Ignacio Malpartida · GTM Engineer Published September 15, 2026 Updated September 18, 2026 Read time 8 min read APP TIPS ## Qualify the relationship before assigning the inquiry Commercial solar inquiry qualification should establish the business identity, existing account relationship, and whether the requester is an end customer or an installation partner. These determine who should respond and which questions will advance the conversation. A company name or industry label alone does not establish the requester’s role in a specific project. Start from the inquiry in HubSpot and search existing accounts and contacts. An installation partner may already have an owner, while an existing end customer may be asking about another facility. Preserve those relationships instead of creating a new prospect and routing it as an unrelated inbound lead. ![Match the business: Use the inquiry’s business domain and existing HubSpot records to identify the company and relationship.; Establish the role: Determine whether this inquiry concerns the business’s own project or an installation partner’s customer.; Prepare the brief: Summarize the stated project, sourced business facts, relationship, and useful unknowns.](https://www.stacksync.com/images/blog-highlights/genies-commercial-inquiry-guide.webp) *Match the business: Use the inquiry’s business domain and existing HubSpot records to identify the company and relationship.; Establish the role: Determine whether this inquiry concerns the business’s own project or an installation partner’s customer.; Prepare the brief: Summarize the stated project, sourced business facts, relationship, and useful unknowns.* ## Systems and prerequisites This is a workflow design to configure with Stacksync Genies and your existing systems. Connecting an application does not by itself establish the permissions, record mappings, approval routing, or operational process described here. Before enabling the job, confirm which records the Genie can read, which actions it can take, and who receives clarification or approval requests. | System or owner | Evidence and responsibility | | --- | --- | | HubSpot | Inquiry, existing account relationships, sourced enrichment, and owner routing. | | Enrichment provider | Business attributes and their source references. | | Business website | Public company context and evidence for the project brief. | Required context for this workflow design. ## Research the business and separate facts from project unknowns Use the configured enrichment provider and business website to add sourced company information. Record source links and observation dates, and preserve verified CRM values when enrichment conflicts. Public information can establish what the business does, but it may not establish site ownership, project authority, financing, or procurement timing. Read the actual inquiry for the requester’s role. Language about installing for clients suggests a partner conversation, while a request about the company’s own facility suggests an end-customer conversation. Treat those as evidence to interpret, not hard-coded conclusions that override an ambiguous message. Ask whether they are buying for their own operation or working on behalf of a customer when unclear. ## Route with a brief that prepares the first response Apply existing account ownership and the organization’s approved end-customer or partner routing rules. Prepare a brief covering the requester, sourced company context, stated project, known relationship, unresolved role questions, and suggested follow-up. Keep a request awaiting clarification visible to an owner rather than silently assigning it to the wrong queue. Tailor the questions to the role once established. An end-customer brief might ask which facility is in scope and who coordinates the project. A partner brief might ask the service area and whether the inquiry concerns a specific customer installation. Do not invent project capacity, incentives, estimated savings, or technical suitability from general company enrichment. ## A five-step operating sequence 1. 01 Match the business Use the inquiry’s business domain and existing HubSpot records to identify the company and relationship. Preserve customer or partner ownership. A new project question should not erase a long-standing commercial relationship. 2. 02 Research public context Read the configured enrichment provider and business website, adding sources for allowed company fields. Preserve verified values and distinguish estimates. Public context should prepare discovery, not establish unverified budget, project capacity, or purchasing authority. 3. 03 Establish the role Determine whether this inquiry concerns the business’s own project or an installation partner’s customer. Ask for clarification when the message is ambiguous. A company’s industry classification is a clue, not a substitute for the requester’s project role. 4. 04 Apply owner rules Route the inquiry using established account ownership and the approved end-customer or partner path. Keep any unresolved routing decision visible to the responsible team. Do not invent a territory or assign an unrelated owner to force completion. 5. 05 Prepare the brief Summarize the stated project, sourced business facts, relationship, and useful unknowns. Choose discovery questions appropriate to the confirmed role. Avoid unsupported savings estimates, incentive eligibility, or technical conclusions about the proposed installation. ![Qualify and Route Commercial Solar Inquiries in HubSpot — match the business, then research public context, then establish the role, then apply owner rules, then prepare the brief.](https://www.stacksync.com/images/blog-diagrams/genies-commercial-inquiry.webp) *Qualify and Route Commercial Solar Inquiries in HubSpot — match the business, then research public context, then establish the role, then apply owner rules, then prepare the brief.* ## Illustrative workflow example An inquiry says the business wants equipment for a client’s warehouse. Existing HubSpot records show an installation-partner relationship. The workflow routes it to the partner owner with the project statement and questions about the customer installation scope. This example uses fictional records to show the decision logic. It is not a customer case study or a claim of measured results. In a live case, retain the actual record IDs and evidence behind each statement, and replace all illustrative quantities or timing assumptions with the approved operational inputs. ## What the handoff should contain A sourced HubSpot project brief with the requester’s confirmed role, existing relationship, correct owner, and role-specific follow-up questions. Keep the evidence reference, observation time, current owner, and outstanding decision with the case. A colleague taking over should be able to distinguish a proposal from a confirmed result without reading every previous message. If a source value changes while the case is waiting, recheck the affected decision before proceeding. ![Required systems feed case verification; missing evidence or decisions return to clarification before the workflow proceeds.](https://www.stacksync.com/images/blog-diagrams-mermaid/genies-commercial-inquiry.webp) *Required systems feed case verification; missing evidence or decisions return to clarification before the workflow proceeds.* ## Approval and completion checklist - Check existing account relationships before enrichment or routing. - Add sourced business information without treating estimates as verified project facts. - Determine end customer versus installation partner from the inquiry and clarify ambiguity. - Route to the appropriate owner with a brief and relevant follow-up questions. ## Validate the job before enabling it Start with a small reviewed set of cases from the systems above. Include a complete case, an ambiguous match, a missing source record, and an interrupted action where the result is uncertain. Use a draft or test environment for validation and compare the output with the source records before allowing the configured production actions. For this job, the most important checks are check existing account relationships before enrichment or routing. Route to the appropriate owner with a brief and relevant follow-up questions. Record the expected result before the trial, then compare both the proposed action and the final evidence. A fluent message is not a passing result if it skips one of these conditions. - Inquiries routed with an established requester role - Ambiguous roles clarified before final routing - Company attributes with recorded sources Use these as operating measures, not promised performance improvements. Establish the current baseline and review exceptions with the team that owns the process. Investigate an increase in incorrect matches, unauthorized actions, or premature closure before expanding the job’s scope. ## Give your Genie a job description Copy the job description below. It preserves the scope and decision boundaries of this use case. Configure the referenced systems, record relationships, policies, and approval owners in your workspace before enabling the job. Commercial inquiry · Easy When a commercial solar inquiry arrives in HubSpot, research the business through our enrichment provider, check existing account relationships, and add sourced company information. Determine from the inquiry whether the requester is an end customer or an installation partner, asking for clarification when unclear. Route the inquiry to the appropriate owner with a short project brief and suggested follow-up questions. Paste this into “Give your Genie a job description.” [Explore Stacksync Genies](https://www.stacksync.com/ai-agents). ## Apply this in solar installation and O&M services: hubSpot opportunity and site and property relationship Once a commercial solar inquiry has been qualified and routed in HubSpot, the next handoff is the approved project account. The linked HubSpot–Acumatica guide preserves customer and project identity without treating a qualified inquiry as a finance-approved customer or installation commitment. | Record to reconcile | Responsible owner | Rule to preserve | | --- | --- | --- | | HubSpot opportunity | Sales operations | Track commercial stage and the approved scope reference. | | Site and property relationship | Project administration | Maintain the physical project location separately from the payer. | | Acumatica customer | Finance | Own approved legal identity and billing terms. | An exception to plan for: **Property manager is not the legal customer**. Preserve the relationship contact and request finance approval for the actual project customer. Acceptance check for the pilot: each project resolves to an approved customer and physical site. The [solar installation and O&M services hub](https://www.stacksync.com/industry/construction/solar-installation-service) connects the broader operating context. These guides develop the specific record mappings and decisions for this application: - [Solar Installer Customer Handoffs: Align HubSpot Opportunities With Acumatica Project Accounts](https://www.stacksync.com/blog/solar-installer-customer-handoffs-align-hubspot-opportunities-with-acumatica-project-accounts) - [HubSpot–Acumatica Two-Way Sync for Solar Installers](https://www.stacksync.com/use-case/hubspot-acumatica-solar-installers) ## Related workflow and integration guides - [Distinguish Solar End Customers from Installation Partners](https://www.stacksync.com/blog/distinguish-solar-end-customers-from-installation-partners) - [All Genies workflow examples](https://www.stacksync.com/ai-agents#genies-use-cases) - [When a workflow should escalate to a person](https://www.stacksync.com/blog/human-in-the-loop-automation-when-to-escalate) - [Check Solar Installation Readiness Across Salesforce and NetSuite](https://www.stacksync.com/blog/check-solar-installation-readiness-across-salesforce-and-netsuite) - [Coordinate Equipment Repairs Across Service, Inventory, and Scheduling](https://www.stacksync.com/blog/coordinate-equipment-repairs-across-service-inventory-and-scheduling) - [Hubspot integrations](https://www.stacksync.com/connectors/hubspot) ## Implementation references These first-party references document the underlying records and interfaces. The cross-system sequence, approvals, and completion rules in this article are a proposed operational configuration; validate them against your connected workspace before enabling it. - [HubSpot: company records and properties](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/companies/guide) FAQ ## Frequently asked questions | | | | --- | --- | | What does the commercial inquiry workflow produce? | A sourced HubSpot project brief with the requester’s confirmed role, existing relationship, correct owner, and role-specific follow-up questions. | | What should the team verify before the job can proceed? | Check existing account relationships before enrichment or routing. Add sourced business information without treating estimates as verified project facts. | About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector HubSpot integrations](https://www.stacksync.com/connectors/hubspot) - [platform AI agent operations](https://www.stacksync.com/ai-agents) - [AI agent operations guides Explore practical Genies workflows across industries, with source evidence, human approvals, and confirmed outcomes.](https://www.stacksync.com/blog#topic-ai-agent-operations) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Distinguish Solar End Customers from Installation Partners 7 min read read](https://www.stacksync.com/blog/distinguish-solar-end-customers-from-installation-partners) [App tips Genies for Solar Project Closeout: Assemble Serial Numbers, Completion Evidence, and Handover Records 5 min read read](https://www.stacksync.com/blog/genies-for-solar-project-closeout-assemble-serial-numbers-completion-evidence-and-handover-records) [App tips Solar Closeout Exceptions: Missing Serial Numbers, Changed Equipment, and Incomplete Handover Evidence 5 min read read](https://www.stacksync.com/blog/solar-closeout-exceptions-missing-serial-numbers-changed-equipment-and-incomplete-handover-evidence) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)