--- title: "Route Clinic Equipment Support Tickets Using Salesforce Asset Data" description: "Route Clinic Equipment Support Tickets Using Salesforce Asset Data. Follow the evidence, approvals, and completion checks with a copyable Genie job description." canonical: https://www.stacksync.com/blog/route-clinic-equipment-support-tickets-using-salesforce-asset-data last_modified: 2026-09-15 --- # Route Clinic Equipment Support Tickets Using Salesforce Asset Data > 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 Clinic equipment support routing matches a Zendesk report to the facility, registered device, and service agreement in Salesforce. Author Ignacio Malpartida · GTM Engineer Published September 15, 2026 Read time 6 min read APP TIPS ## Route the equipment issue with the correct asset context Clinic equipment support routing matches a Zendesk report to the facility, registered device, and service agreement in Salesforce. The output is an internal summary and an assignment to the appropriate service team. This workflow gathers administrative equipment context; it does not diagnose faults, provide clinical instructions, or require patient records. Start with the clinic’s known facility identifier and the device information in the ticket. Organizations can have several sites using the same model. A familiar clinic name and a product description may still leave multiple matching assets. Verify the facility-to-asset relationship before selecting a service entitlement or assigning a team. ![Confirm the facility: Use the clinic’s verified facility context and match it to Salesforce.; Check the agreement: Read the applicable service agreement for the confirmed asset.; Route the ticket: Apply established service-team routing rules and record the assignment.](https://www.stacksync.com/images/blog-highlights/genies-equipment-support-routing-guide.webp) *Confirm the facility: Use the clinic’s verified facility context and match it to Salesforce.; Check the agreement: Read the applicable service agreement for the confirmed asset.; Route the ticket: Apply established service-team routing rules and record the assignment.* ## 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 | | --- | --- | | Zendesk | Clinic’s equipment issue, clarification request, internal summary, and service-team assignment. | | Salesforce | Facility identity, registered assets, and the applicable service agreement. | Required context for this workflow design. ## Ask for the serial number when the match is ambiguous If several devices match, ask the clinic for the serial number through Zendesk and pause routing that depends on choosing the asset. Explain that the serial identifies the registered device and relevant service coverage. Request the specific equipment detail, not a broad collection of clinic records or screenshots that could include patient information. Once a unique device is established, read its registered location, model, agreement reference, and the service details needed for routing. An agreement for another device at the same site may have different terms. If no applicable agreement can be verified, flag the gap for the service team rather than inventing coverage or a response-time promise. ## Write an internal summary that reduces repetition Summarize the facility, asset identifier, reported issue in the clinic’s own terms, applicable agreement, evidence references, and any unresolved administrative question. Keep internal routing details as an internal Zendesk note. Use the established routing rules to select the service team responsible for that asset and coverage. Treat correct assignment as the completion of this routing job. Repair completion belongs to the service team’s subsequent process. If the report contains patient information, avoid copying it into the summary or using it for matching. The agent needs facility and equipment information only to perform the requested task. ## A five-step operating sequence 1. 01 Confirm the facility Use the clinic’s verified facility context and match it to Salesforce. Keep the report attached to that location. A clinic group name may cover multiple sites, and service routing depends on the actual registered facility. 2. 02 Resolve the device Compare the reported equipment with registered assets at the facility. If several match, request the serial number before continuing. Do not select the first model match or ask for patient records to compensate for a missing equipment identifier. 3. 03 Check the agreement Read the applicable service agreement for the confirmed asset. Preserve the reference and any uncertainty about coverage. A service arrangement for another device at the same clinic should not be applied by proximity. 4. 04 Summarize internally Write the reported issue, facility, serial or asset ID, agreement, and remaining question as an internal Zendesk note. Restrict the summary to equipment and facility information. Do not add clinical interpretation or patient details. 5. 05 Route the ticket Apply established service-team routing rules and record the assignment. This completes the administrative routing job. Do not imply that the equipment was diagnosed, repaired, or cleared for use merely because the support ticket reached the right team. ![Route Clinic Equipment Support Tickets Using Salesforce Asset Data — confirm the facility, then resolve the device, then check the agreement, then summarize internally, then route the ticket.](https://www.stacksync.com/images/blog-diagrams/genies-equipment-support-routing.webp) *Route Clinic Equipment Support Tickets Using Salesforce Asset Data — confirm the facility, then resolve the device, then check the agreement, then summarize internally, then route the ticket.* ## Illustrative workflow example A clinic reports that one of two identical registered units has an issue. The workflow requests the serial number, matches the response to one asset and its agreement, adds an internal note, and routes the existing ticket to that asset’s service team. 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 An internal Zendesk handoff containing facility, unique registered asset, reported equipment issue, agreement reference, routing rationale, and any unresolved administrative gap. 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-equipment-support-routing.webp) *Required systems feed case verification; missing evidence or decisions return to clarification before the workflow proceeds.* ## Approval and completion checklist - Match the clinic to the correct Salesforce facility and registered asset. - Ask for the serial number before proceeding when several devices match. - Use the applicable service agreement and add an internal Zendesk summary. - Route to the service team using facility and equipment information only, excluding patient records. ## 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 match the clinic to the correct Salesforce facility and registered asset. Route to the service team using facility and equipment information only, excluding patient records. 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. - Tickets routed with a unique facility and asset match - Ambiguous matches resolved before assignment - Internal summaries limited to facility and equipment information 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. Equipment support routing · Easy When a clinic reports an equipment issue in Zendesk, find the correct facility, registered asset, and service agreement in Salesforce. Add an internal summary and route the ticket to the appropriate service team. If several devices match, ask for the serial number before proceeding. Use facility and equipment information only, not patient records. Paste this into “Give your Genie a job description.” [Explore Stacksync Genies](https://www.stacksync.com/ai-agents). ## Related workflow and integration guides - [Resolve Ambiguous Device Reports with Serial Numbers and Service Agreements](https://www.stacksync.com/blog/resolve-ambiguous-device-reports-with-serial-numbers-and-service-agreements) - [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) - [Plan Clinic Supply Replenishment Across Postgres and NetSuite](https://www.stacksync.com/blog/plan-clinic-supply-replenishment-across-postgres-and-netsuite) - [Coordinate Supplier Recalls Across Inventory, CRM, and Support](https://www.stacksync.com/blog/coordinate-supplier-recalls-across-inventory-crm-and-support) - [How to Sync Zendesk with Salesforce: A Two-Way Integration Guide](https://www.stacksync.com/blog/how-to-sync-zendesk-with-salesforce) - [Zendesk integrations](https://www.stacksync.com/connectors/zendesk) - [Salesforce integrations](https://www.stacksync.com/connectors/salesforce) ## 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. - [Salesforce: assets, entitlements, and service agreements](https://help.salesforce.com/s/articleView?id=service.entitlements_overview.htm&language=en_US) - [Zendesk: ticket comments and visibility](https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_comments/) Start with one sync and see it hold Connect two systems, watch a record move both ways, then decide. [Start syncing](https://app.stacksync.com/) FAQ ## Frequently asked questions What does the equipment support routing workflow produce? An internal Zendesk handoff containing facility, unique registered asset, reported equipment issue, agreement reference, routing rationale, and any unresolved administrative gap. What should the team verify before the job can proceed? Match the clinic to the correct Salesforce facility and registered asset. Ask for the serial number before proceeding when several devices match. 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 Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [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 Coordinate Closed-Won Onboarding Across Salesforce and NetSuite 8 min read read](https://www.stacksync.com/blog/coordinate-closed-won-onboarding-across-salesforce-and-netsuite) [App tips Coordinate Equipment Repairs Across Service, Inventory, and Scheduling 8 min read read](https://www.stacksync.com/blog/coordinate-equipment-repairs-across-service-inventory-and-scheduling) [App tips Reconcile Contractor Quotes, Approved Work, and Maintenance Invoices 7 min read read](https://www.stacksync.com/blog/reconcile-contractor-quotes-approved-work-and-maintenance-invoices) ## 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/)