--- title: "Coordinate Closed-Won Onboarding Across Salesforce and NetSuite" description: "Coordinate Closed-Won Onboarding Across Salesforce and NetSuite. Follow the evidence, approvals, and completion checks with a copyable Genie job description." canonical: https://www.stacksync.com/blog/coordinate-closed-won-onboarding-across-salesforce-and-netsuite last_modified: 2026-09-18 --- # Coordinate Closed-Won Onboarding Across Salesforce and NetSuite > 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 Closed-won onboarding should validate the sold entity, billing contact, package, and required purchase order before creating downstream records. Author Ignacio Malpartida · GTM Engineer Published September 15, 2026 Updated September 18, 2026 Read time 8 min read APP TIPS ## Treat Closed Won as the start of a handoff Closed-won onboarding should validate the sold entity, billing contact, package, and required purchase order before creating downstream records. A Salesforce stage change signals that coordination can begin; it does not guarantee that every legal, billing, and provisioning input is complete. The automation should expose those gaps and keep the customer’s response connected to the opportunity. Use the opportunity ID as the durable handoff reference. Search for existing onboarding tickets, NetSuite customer links, sales orders, and provisioning requests before starting a new chain. The same opportunity can be edited or its event delivered more than once without representing a new sale. ![Validate the handoff: Read the Closed Won opportunity and verify legal entity, billing contact, package, and required purchase order.; Approve the setup: Present the complete setup and proposed existing-customer match for approval.; Confirm provisioning: Wait for an explicit successful provisioning result tied to the approved customer and package.](https://www.stacksync.com/images/blog-highlights/genies-closed-won-onboarding-guide.webp) *Validate the handoff: Read the Closed Won opportunity and verify legal entity, billing contact, package, and required purchase order.; Approve the setup: Present the complete setup and proposed existing-customer match for approval.; Confirm provisioning: Wait for an explicit successful provisioning result tied to the approved customer and package.* ## 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 | | --- | --- | | Salesforce | Closed Won event, legal and commercial handoff, and resulting record IDs. | | Zendesk | Onboarding case, missing-information requests, and customer responses. | | NetSuite | Approved customer match or creation and sales order. | | Postgres-backed provisioning process | Provisioning request, progress, and explicit completion confirmation. | | Setup approver | Approval of the validated customer setup before downstream creation. | Required context for this workflow design. ## Collect missing information and resume the same case Create or link a Zendesk onboarding ticket and request the specific missing fields. Explain what is needed in ordinary business language: the billing contact, legal entity, or required purchase-order reference. Keep the setup pending until the response resolves those requirements. A customer reply is a reason to revalidate, not automatic evidence that every gap is closed. Prepare the complete setup for approval, including the purchased package and the proposed match to any existing NetSuite customer. A trading name alone may not establish the legal entity. If the proposed customer link is ambiguous, obtain clarification before asking the reviewer to approve a downstream order against the wrong business. ## Create approved records and track provisioning separately After setup approval, create or link the NetSuite customer and sales order, then submit the provisioning request through the configured Postgres-backed process. Record each resulting identifier in Salesforce as it is confirmed. The implementation depends on the organization’s actual provisioning interface; Postgres is not a universal standard API for account activation. Distinguish request submission from provisioning success. Wait for the process to confirm completion for the approved package and customer. If one step fails after another succeeds, resume the missing step using the confirmed IDs. Mark onboarding complete only after provisioning confirmation, leaving unresolved failures and customer-information requests visible on the same onboarding case. ## A five-step operating sequence 1. 01 Validate the handoff Read the Closed Won opportunity and verify legal entity, billing contact, package, and required purchase order. Search existing downstream references. A repeated stage event should resume the same onboarding, not create another sales order. 2. 02 Collect missing inputs Use a Zendesk onboarding ticket to request the specific missing information and wait for the customer’s response. Revalidate the returned details against the setup requirements. An unrelated reply should not release the blocked provisioning action. 3. 03 Approve the setup Present the complete setup and proposed existing-customer match for approval. Resolve entity ambiguity before creation. If the customer changes the package or legal entity afterward, return the changed proposal for the relevant approval. 4. 04 Create and link records After approval, create or link the NetSuite customer and sales order and submit the configured provisioning request. Persist each confirmed ID back to Salesforce. Check destination records after an ambiguous timeout before retrying a potentially successful write. 5. 05 Confirm provisioning Wait for an explicit successful provisioning result tied to the approved customer and package. Record partial or failed outcomes and follow them through the existing process. Only mark onboarding complete after confirmation, retaining the linked evidence for the account team. ![Coordinate Closed-Won Onboarding Across Salesforce and NetSuite — validate the handoff, then collect missing inputs, then approve the setup, then create and link records, then confirm provisioning.](https://www.stacksync.com/images/blog-diagrams/genies-closed-won-onboarding.webp) *Coordinate Closed-Won Onboarding Across Salesforce and NetSuite — validate the handoff, then collect missing inputs, then approve the setup, then create and link records, then confirm provisioning.* ## Illustrative workflow example A Closed Won opportunity has a valid package but no required purchase order. The Zendesk ticket requests the PO. After the customer supplies it, the setup is revalidated and approved, NetSuite records are linked, and onboarding stays pending until provisioning confirms completion. 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 Salesforce handoff record linked to the Zendesk onboarding case, approved setup, NetSuite customer and sales order, provisioning request, and explicit provisioning confirmation. 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-closed-won-onboarding.webp) *Required systems feed case verification; missing evidence or decisions return to clarification before the workflow proceeds.* ## Approval and completion checklist - Validate legal entity, billing contact, purchased package, and any required purchase order. - Collect missing information in Zendesk and resume on the customer’s response. - Require setup approval before NetSuite records and provisioning submission. - Write confirmed IDs to Salesforce, prevent duplicates, and close only after provisioning confirmation. ## 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 validate legal entity, billing contact, purchased package, and any required purchase order. Write confirmed IDs to Salesforce, prevent duplicates, and close only after provisioning confirmation. 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. - Closed-won handoffs with complete approved setup - Duplicate customer, sales-order, or provisioning records - Onboardings closed with explicit provisioning confirmation 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. Closed won onboarding · Hard When a Salesforce opportunity becomes Closed Won, coordinate customer onboarding. Validate the legal entity, billing contact, purchased package, and any required purchase order. Open a Zendesk onboarding ticket to collect missing information and resume when the customer responds. Ask me to approve the setup, then create or link the NetSuite customer and sales order and submit a provisioning request through our Postgres-backed process. Write the resulting IDs back to Salesforce, avoid duplicate records, and mark onboarding complete only after provisioning is confirmed. Paste this into “Give your Genie a job description.” [Explore Stacksync Genies](https://www.stacksync.com/ai-agents). ## Apply this in industrial equipment and machinery: accepted configuration and commercial order line An equipment sale extends the Salesforce–NetSuite closed-won handoff into an approved machine configuration and commissioning prerequisites. Preserve the accepted order while coordinating site readiness and service dispatch; a won opportunity alone does not establish that the machine or site is ready. | Record to reconcile | Responsible owner | Rule to preserve | | --- | --- | --- | | Accepted configuration | Application engineering | Retain the approved option set and revision with its customer approval evidence. | | Commercial order line | Sales operations | Identify equipment, optional components and services separately even when sold in one deal. | | ERP transaction link | Order management | Preserve the destination order and line references for reconciliation and later change requests. | An exception to plan for: **The customer adds an option after procurement**. Route its cost and schedule effect for approval before updating accepted scope. Acceptance check for the pilot: the order retains the exact configuration version the customer accepted. The [industrial equipment and machinery hub](https://www.stacksync.com/industry/manufacturing/industrial-equipment-machinery) connects the broader operating context. These guides develop the specific record mappings and decisions for this application: - [Equipment manufacturers: connect Salesforce configurations to NetSuite orders](https://www.stacksync.com/blog/equipment-manufacturers-salesforce-netsuite-configured-order) - [Equipment commissioning readiness: connect sales promises, site prerequisites and service dispatch](https://www.stacksync.com/blog/equipment-commissioning-readiness-workflow) - [Salesforce and NetSuite two-way sync for equipment manufacturers](https://www.stacksync.com/use-case/equipment-salesforce-netsuite-two-way-sync) - [Commissioning-readiness automation for equipment manufacturers](https://www.stacksync.com/use-case/equipment-commissioning-readiness-automation) ## Related workflow and integration guides - [Resolve Missing Onboarding Information and Confirm Provisioning](https://www.stacksync.com/blog/resolve-missing-onboarding-information-and-confirm-provisioning) - [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) - [Research and Route HubSpot Demo Requests with AI Agents](https://www.stacksync.com/blog/research-and-route-hubspot-demo-requests-with-ai-agents) - [Detect Renewal Risk Using Salesforce, Product Usage, and Zendesk](https://www.stacksync.com/blog/detect-renewal-risk-using-salesforce-product-usage-and-zendesk) - [Aurora PostgreSQL and Salesforce in Both Directions, Step by Step](https://www.stacksync.com/blog/sync-aurora-postgresql-with-salesforce) - [Zendesk integrations](https://www.stacksync.com/connectors/zendesk) - [Netsuite integrations](https://www.stacksync.com/connectors/netsuite) ## 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. - [Zendesk: ticket comments and visibility](https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_comments/) FAQ ## Frequently asked questions What does the closed won onboarding workflow produce? A Salesforce handoff record linked to the Zendesk onboarding case, approved setup, NetSuite customer and sales order, provisioning request, and explicit provisioning confirmation. What should the team verify before the job can proceed? Validate legal entity, billing contact, purchased package, and any required purchase order. Collect missing information in Zendesk and resume on the customer’s response. 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 Zendesk integrations](https://www.stacksync.com/connectors/zendesk) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [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 AI agents for equipment aftermarket requests: prepare compatible parts proposals 4 min read read](https://www.stacksync.com/blog/equipment-genie-aftermarket-part-request-guide) [App tips Equipment parts AI exceptions: serial ambiguity, supersession and incomplete kits 4 min read read](https://www.stacksync.com/blog/equipment-genie-part-supersession-serial-exceptions) [App tips Equipment commissioning readiness: connect sales promises, site prerequisites and service dispatch 4 min read read](https://www.stacksync.com/blog/equipment-commissioning-readiness-workflow) ## 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/)