--- title: "Genies assemble fire and security service handoff packets" description: "Use Genies to assemble fire and security service context while keeping technical and commercial decisions with their owners." canonical: https://www.stacksync.com/blog/genies-for-fire-and-security-service-handoffs-assemble-inspection-asset-and-service-agreement-evidence last_modified: 2026-09-18 --- # Genies for Fire and Security Service Handoffs: Assemble Inspection, Asset, and Service-Agreement Evidence > 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 Use Genies to assemble fire and security service context while keeping technical and commercial decisions with their owners. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision A fire and security handoff Genie can gather inspection references, installed-asset context, service-agreement coverage and open follow-up records into a review packet. Require it to cite the source for each association and distinguish verified facts from missing or conflicting evidence. Its role is administrative preparation and routing. It should not certify an inspection, choose a technical remedy, determine compliance, or authorize remedial work based on a plausible-looking match. Explore the complete [fire, life-safety and security integrators integration and automation hub](https://www.stacksync.com/industry/construction/fire-life-safety-security-integrators) for the systems and processes around this guide. ![Summary card: Genies assemble fire and security service handoff packets](https://www.stacksync.com/images/blog-highlights/icp-genies-for-fire-and-security-service-handoffs-assemble-inspection-asset-and-service-agreement-evidence.webp) ## What this looks like in fire, life-safety and security integrators An integrator receives an inspection report for a property with several similar panel names. Salesforce holds customer and asset relationships; NetSuite holds the relevant commercial context. The service coordinator must identify the covered site, check existing work and determine who should review the finding. A Genie can assemble those records and flag the uncertain device match. A qualified reviewer and commercial owner then decide the appropriate next action. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Inspection reference | Inspection owner | Provide the original finding and its site or asset context. | | Asset candidate | Asset administrator | Confirm equipment identity when report labels differ from the register. | | Agreement context | Contract administration | Identify the current term and relevant service scope without inferring technical coverage. | | Service handoff packet | Service coordinator | Collect evidence, existing work and unresolved questions for the assigned reviewer. | ![Record ownership diagram: Inspection reference, Asset candidate, Agreement context](https://www.stacksync.com/images/blog-diagrams/icp-genies-for-fire-and-security-service-handoffs-assemble-inspection-asset-and-service-agreement-evidence.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Define the packet and its boundaries Ask the Genie to assemble evidence for a named report or set of findings. Specify the required fields: source reference, site, device candidate, current agreement, related work and unresolved questions. Make clear that the output is a review packet, not a certification or approved repair plan. 2. 02 Join records with visible evidence Use stable site and asset identifiers when available, then show any alternative matches when the report uses informal labels. A model should not hide ambiguity behind a single selected record. Include the source text and matching register fields so the asset owner can resolve the association. 3. 03 Check current commercial context Retrieve the relevant agreement term and customer relationship through accessible records. Distinguish current coverage from a pending renewal or expired term. The agent can show the agreement evidence, but deciding whether specific work is included may require contract review rather than keyword matching. 4. 04 Identify prior and open work Look for linked cases, quotes and work orders that might already address the same finding. Present related records without assuming they resolve it. A completed commercial job may still require separate technical review before anyone updates the finding's disposition. 5. 05 Route a concise next decision Create or prepare one owned handoff with the missing decision clearly stated. Send equipment ambiguity to asset administration, technical scope to the qualified reviewer and commercial authorization to the account owner. Record the accepted packet version and avoid generating repeated tasks for the same unresolved finding. 6. 06 Make the review queue intelligible to each owner Use the same packet reference but present the question relevant to the receiving team. Asset administration needs the conflicting device identifiers; contract administration needs the term and scope; the service reviewer needs the original finding and related work. A large undifferentiated AI summary makes each person repeat the sorting. A concise question with shared evidence keeps the handoff traceable while reducing unnecessary reading and avoiding conflicting parallel tasks. ![6-step operating sequence: Genies assemble fire and security service handoff packets](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-genies-for-fire-and-security-service-handoffs-assemble-inspection-asset-and-service-agreement-evidence.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Report label matches several devices List the candidates with evidence and ask the asset owner to confirm. ### Agreement status is stale or conflicting Show the source dates and route the discrepancy to contract administration. ### Prior work appears related but lacks closure evidence Link it for review without declaring the finding resolved. ## What to verify before expanding - Every asset association includes a supporting source. - The packet distinguishes current agreement from renewal proposals. - Technical conclusions remain outside the agent's authorized output. - One unresolved finding produces one owned review case. ## Connect this process to the rest of your operation [Explore Stacksync AI agents (Genies)](https://www.stacksync.com/ai-agents#genies-job-icp-fire-life-safety-security-integrators) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real inspection reference example and the exception your team handles most often, for example report label matches several devices. - [AI Service Handoffs for Fire and Security Integrators](https://www.stacksync.com/use-case/genies-fire-security-service-handoffs) - [Fire and Security Handoff Exceptions: Missing Device IDs, Conflicting Site Records, and Unapproved Remediation](https://www.stacksync.com/blog/fire-and-security-handoff-exceptions-missing-device-ids-conflicting-site-records-and-unapproved-remediation) - [Fire and Security Equipment Procurement: Match Supplier EDI Shipments to Project POs and Serial Records](https://www.stacksync.com/blog/fire-and-security-equipment-procurement-match-supplier-edi-shipments-to-project-pos-and-serial-records) - [Fire and Security Integrators: Align Salesforce Installed Equipment With NetSuite Customer and Service Records](https://www.stacksync.com/blog/fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records) - [Building Triggers and Workflows on Top of Your Bidirectional CRM Sync](https://www.stacksync.com/blog/building-triggers-and-workflows-on-top-of-your-bidirectional-crm-sync) - [Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Salesforce connector requirements](https://docs.stacksync.com/two-way-sync/connectors/salesforce) - [Stacksync NetSuite connector and object support](https://docs.stacksync.com/two-way-sync/connectors/netsuite) - [Stacksync Genies](https://www.stacksync.com/ai-agents) - [Stacksync event triggers](https://docs.stacksync.com/guides/event-triggers) FAQ ## Frequently asked questions Can the Genie summarize inspection language? It can prepare an administrative summary while preserving the source wording and references. A qualified reviewer must validate technical interpretation before it guides work or customer claims. Why pair this with two-way sync? Current connected records help the agent find the right customer, asset and agreement context. Sync provides the data foundation; the Genie assembles evidence and the workflow routes the decision. How do we judge a service handoff packet pilot? Evaluate correct record association, clarity of unresolved questions, duplicate-task prevention and reviewer corrections. Do not use a fluent summary as evidence that the agent understood a technical finding. 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 Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [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 Fire and Security Handoff Exceptions: Missing Device IDs, Conflicting Site Records, and Unapproved Remediation 5 min read read](https://www.stacksync.com/blog/fire-and-security-handoff-exceptions-missing-device-ids-conflicting-site-records-and-unapproved-remediation) [App tips Fire-System Inspection Follow-Ups: Route Deficiency Records to Approved Remedial Work 5 min read read](https://www.stacksync.com/blog/fire-system-inspection-follow-ups-route-deficiency-records-to-approved-remedial-work) [App tips New Security Installations: Route Customer Acceptance Before Activating Recurring Billing 5 min read read](https://www.stacksync.com/blog/new-security-installations-route-customer-acceptance-before-activating-recurring-billing) ## 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/)