--- title: "Distinguish Solar End Customers from Installation Partners" description: "Distinguish Solar End Customers from Installation Partners. Review practical exception decisions, evidence checks, and a copyable Genie job description." canonical: https://www.stacksync.com/blog/distinguish-solar-end-customers-from-installation-partners last_modified: 2026-09-18 --- # Distinguish Solar End Customers from Installation Partners > 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 Distinguish a solar end customer from an installation partner using the inquiry’s stated relationship to the project, checked against existing account context. Author Ignacio Malpartida · GTM Engineer Published September 15, 2026 Updated September 18, 2026 Read time 7 min read APP TIPS ## Classify the requester’s role in this inquiry Distinguish a solar end customer from an installation partner using the inquiry’s stated relationship to the project, checked against existing account context. An end customer is enquiring for its own operation; an installation partner is working in a delivery or commercial relationship for customers. A business can play both roles on different projects. Do not classify solely from a company’s industry. An installer might purchase equipment for its own premises, and a property owner might submit on behalf of a managed portfolio. The useful routing question is what role this requester has in the current inquiry, not which label appears on a directory profile. ![Project role unclear: Ask own project or customer project. No speculative final route.; Existing partner relationship: Preserve owner context. No duplicate prospect.; Installer buying for own premises: Classify this inquiry by actual role. Industry label does not decide.](https://www.stacksync.com/images/blog-highlights/genies-commercial-inquiry-exceptions.webp) *Project role unclear: Ask own project or customer project. No speculative final route.; Existing partner relationship: Preserve owner context. No duplicate prospect.; Installer buying for own premises: Classify this inquiry by actual role. Industry label does not decide.* ## Evidence needed to resolve the exception Use this exception guide when reviewing a proposed Genie workflow or investigating a case that cannot proceed confidently. The tables describe operational decisions to configure in your environment. They are not claims that a connected application automatically supplies your organization’s policies, identity mappings, or approval process. | 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. ## Ask one clarification that changes the route When the message is unclear, ask whether the project is for the requester’s own business or for a customer they serve. If they represent another party, ask the relationship needed to route the inquiry, without demanding a full project specification before the first response. Keep the uncertainty visible in HubSpot until answered. Check whether the account already has an established customer or partner owner. A new inquiry should not erase that relationship. If the project involves a different role from the established one, flag it to the existing owner with the supporting message rather than changing the account’s overall classification without review. ## Build two different follow-up briefs For an end customer, focus on the stated facility, business need, project decision process, and missing scope. For a partner, focus on the customer project or partnership request, territory, services, and appropriate partner contact. In both cases, distinguish sourced business facts from information still to be confirmed. Avoid using company size or public revenue estimates to infer budget or readiness to buy. A large company may be exploring a small site, and an installer may be researching a future opportunity. The qualification workflow should improve the first conversation by asking the right questions and routing accurately, rather than prematurely declaring the project qualified for a particular commercial or technical offer. ## Decision table for common exceptions Use the condition in the first column to choose the next action. The final column describes the boundary that must remain true while the case is unresolved. Apply the organization’s actual policy and source records to the live case; do not treat an illustrative condition as proof that the condition exists. | Observed condition | Next action | Required boundary | | --- | --- | --- | | Project role unclear | Ask own project or customer project | No speculative final route | | Existing partner relationship | Preserve owner context | No duplicate prospect | | Installer buying for own premises | Classify this inquiry by actual role | Industry label does not decide | | Provider fact conflicts | Retain verified value and flag source | No silent overwrite | Exception decisions for commercial inquiry. ![The underlying commercial inquiry process: match the business, research public context, establish the role, apply owner rules, prepare the brief.](https://www.stacksync.com/images/blog-diagrams/genies-commercial-inquiry.webp) *The underlying commercial inquiry process: match the business, research public context, establish the role, apply owner rules, prepare the brief.* ## Illustrative exception and recovery A solar installer asks about its own office installation. The company’s industry suggests a partner, but the inquiry describes an end-customer project. The brief records that distinction and uses the approved routing rules for the actual request. 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 to record before resuming A sourced HubSpot project brief with the requester’s confirmed role, existing relationship, correct owner, and role-specific follow-up questions. Preserve the original finding and the evidence that resolves it. Record which person or system supplied the clarification, which proposal it applies to, and the action now permitted. Do not erase the uncertainty from the history: a later reviewer needs to understand why the case paused and why it resumed. ![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.* ## Boundaries that remain in force - 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. ## Review the case before restarting First verify that the new evidence resolves the original blocker rather than a different issue. Then check whether the case, source records, or proposed action changed during the wait. A response attached to the right ticket can still be insufficient if it refers to an earlier proposal or leaves a required quantity, identity, or approval unresolved. Run the relevant row from the decision table as a review scenario. Confirm that the job stops at the required boundary, asks for the specified information or decision, and resumes from the confirmed state. If a write or message may already have succeeded, inspect its destination before repeating it; if this job only prepares a draft or report, verify that it stays within that output scope. - Inquiries routed with an established requester role - Ambiguous roles clarified before final routing - Company attributes with recorded sources Track unresolved cases by their actual blocker and owner. A case waiting for clarification needs a different next action from one waiting for a confirmed result. Review the evidence when the state changes, and keep any still-unresolved completion condition visible instead of treating a successful intermediate step as the end of the work. ## 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 The distinction between a solar end customer and installation partner must survive into project and billing records. Apply that relationship model when fleet ownership changes so the service asset owner, legal payer, and partner remain separately traceable. | 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) - [Solar Fleet Ownership Changes: Align Salesforce Asset Owners With NetSuite Billing Customers](https://www.stacksync.com/blog/solar-fleet-ownership-changes-align-salesforce-asset-owners-with-netsuite-billing-customers) - [Salesforce–NetSuite for Solar Installation and O&M](https://www.stacksync.com/use-case/salesforce-netsuite-solar-om) ## Related workflow and integration guides - [Qualify and Route Commercial Solar Inquiries in HubSpot](https://www.stacksync.com/blog/qualify-and-route-commercial-solar-inquiries-in-hubspot) - [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) - [Identify Equipment Allocation, Permit, and Crew Blockers](https://www.stacksync.com/blog/identify-equipment-allocation-permit-and-crew-blockers) - [Verify Warranty Coverage and Customer Acceptance Before Closing Repairs](https://www.stacksync.com/blog/verify-warranty-coverage-and-customer-acceptance-before-closing-repairs) - [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 happen when the evidence is incomplete? Keep the affected action pending and obtain the missing source evidence or required decision. Route to the appropriate owner with a brief and relevant follow-up questions. 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 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 Qualify and Route Commercial Solar Inquiries in HubSpot 8 min read read](https://www.stacksync.com/blog/qualify-and-route-commercial-solar-inquiries-in-hubspot) [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/)